cocoaforge

The problem with your request is that in order to do this, a complete redesign and rewrite of adium will be required. It simply doesn't worth the effort...

hmmm.. in that case you'll just have to get used to it

I wonder why Adium 2 doesn't allow a simple message config like 1 did, if you don't want to use any sort of mesage style. Or does it and I missed it? I was happy with Adium 1, but I think it's time to move on (even if I hate the tabs on the bottom). You don't have to use tabs if you don't want to...

cosmosheep wrote:

wschmps04 wrote:I tried that, but it still didn't work!!!! :-(
a picture of my adium prefs is http://wschamps04.com/adiumprefs.jpg
and one of my growl prefs is http://wschamps04.com/growlprefs.jpg

thanks

your screen shots come up blank, for me at least...

same thing for me

open the treminal and type "cd ~/Library/Application\ Support/", press return, and then type "ln -s path/to/your/adium/support/folder Adium 2.0".
but before you do this, move your Adium 2.0 to wherever you want.

if you have a problem with editing your adium build every time, you could also try to create a symbolic link instead of your adium 2.0 folder.
i *think* it should work, but i didn't try it.

ive actually done this alot too, when im switching between SVN, release, and beta.. i second memark, could it be stored in documents? or a customizable destination? edit: actually could you create an alias folder called logs and place that in your /users/defult/logs place and have the real folder s...

your logs are in ~/Library/Application Support/Adium 2.0/Users/Default/Logs

I don't really know - one of the devs will have to comment on this. But, i do know that there is a way to produce a universal binary that works in PPC/x86 Tiger AND on panther using xcode 2.1
The universal binary format has been in OS X for a long time.

Adium as been updated to work with xcode 2.1. Upgrade to xcode 2.1 and open adium.xcodeproj. Everything should work with xcode 2.1.

Excellent Job! I like it!
Only one minor thing i noticed is that the shadow of this widget is a bit smaller then the shadow of all the other widgets. Is it only me?
Anyway, i'll say it again - great gob.

Ofri

I don't like the fact that sheets arrest the window and prevent you from making any changes while the dialog is open. Unless I've misunderstood them, sheets were designed to replace modal dialogues, and shouldn't be used otherwise. Any sort of modal dialogue will "arrest the window", so t...

Yep. Plugins that are PPC only will not be able to load into a x86 app. Both the app and the plugins/bundles/frameworks it loads, should be either PPC or x86. You can't mix the two 'cause a PPC app (and all it's plugins) will be loaded within Rosetta and a x86 app will run natively. Therefor, you o...

But plugins will need to be recompiled. You sure? Aren't they fairly dependent on Cocoa calls and Adium-specific calls? I mean, I'm sure some will, but certainly not all. Yep. Plugins that are PPC only will not be able to load into a x86 app. Both the app and the plugins/bundles/frameworks it loads...

I'm no dev genius here. But doesn't it also means that we have to relocate the xtras and stuff like that? Which gets saved within the app itself? No, as above it just means a few changes when building it in xcode, Mac OS X isn't changing; so the way application support files are used (i.e xtras) wo...

komrade wrote:thanks, i managed to send a ticket already

now i can only hope

Don't worry, it will appear sooner or later...

We're considering making the autoreply required on AIM and impossible on MSN... just have it follow whatever the protocol expects. Thoughts? I really like it the way it is now. My friends got used to it and i find it a very very useful feature. How about making an option to autoreply only on protoc...

This plugin does not work well with v0.8. I started rewriting it, but now i have a lot of exams as school so please be patient. As the developer of this plugin, I highly recommend you NOT to use the current version with adium 0.8. It will make adium VERY unstable as it was written for adium 0.7 and ...

also you probably should add "Frameworks/AIUtilities Framework/build" to the Framework Search Paths...

I tried using the Adium 0.81 source and I still get the same problem. In Adium.pch it pulls up on this line: #import <AIUtilities/AIStringUtilities.h> //Everybody should be localizing their strings And says something along the lines of: File or directory does not exist. I followed the directions sp...