[Adium-devl] Connect/Disconnect Enable/Disable etc.

Juan Manuel Palacios jmpp at opendarwin.org
Thu Jul 27 19:00:54 UTC 2006


	A new commer here, but if what you want is user feedback, then my 
thoughts might be of help ;-)

On Jul 27, 2006, at 1:46 PM, Evan Schoenberg wrote:

> Adium 0.8x behavior:
>  * Autoconnect at startup if and only if 'autoconnect' is checked, 
> within the account's preferences
>  * With one or more accounts online, changing the global status 
> changes only the online accounts
>  * With no accounts online, changing the global status brings, well, a 
> fairly random selection of accounts online
>  * No ability to disable accounts

	Not much comment here, as I believe the 1.0 behavior is much better 
(apart from "working" in the first place ;-)

>
> Adium 1.0b7 behavior:
>  * Autoconnect all enabled accounts when starting up
>  * Changing the global status brings all enabled accounts into the 
> specified state, taking them online if necessary
>  * Disabled accounts are never affected by global status changes.  
> Changing a disable account to any online state both enables it and 
> brings it online
>  * Enabling a disabled account brings it online (in the current global 
> status)
>  * Disabling an enabled accounts takes it offline
>
> I feel like we've seen a fair number of useage cases that are actual 
> arguments for some compromise between the two (versus just people 
> being used to the old way of doing things).  The fact that we've 
> started resorted to telling people to hold shift while starting up 
> Adium to avoid autoconnect as a "solution" also makes me think we 
> should reevaluate this... nothing that subtle should ever be a serious 
> solution to a problem.

	This is sort of a "hidden trick", and I agree it shouldn't be a 
primary mean to avoid autoconnecting, I think there should be a 
preference entry to enable/disable the feature.

>
> Proposal:
>  * Bring back autoconnect as a per-account preference.  Newly added 
> accounts default to autoconnecting.

	Sounds good, though I do have an argument for per account Vs. global 
settings, like the icon preference (each account can use its own or the 
global one) and the "notify when typing" setting (which is only a per 
account preference). I'm not too sure when a certain setting should be 
either split or on a per account basis, made global or both. In any 
case, having a setting (per account and/or global) to specify whether 
or not autoconnect is to be performed seems like the right approach to 
me.

>  * When starting up, autoconnect all accounts which are 
> both (autoconnect == TRUE) and (enabled == TRUE)

	Logical.

>  * With one or more accounts online, changing the global status 
> changes only the online accounts

	I believe the global status should affect all enabled accounts, 
regardless of online or not. In my opinion the test here should be 
performed on (enabled == TRUE) and not on (online == TRUE). After all, 
the status you are discussing is 'global', i.e. affecting *all* 
accounts, short of the disabled ones (which are, needless to say, 
disabled and therefore should not be disturbed).

>  * With no accounts online, changing the global status... here's the 
> tricky part.

	My previous comment would cover this too. *Any* global status change 
should affect all enabled accounts, regardless of the change itself (to 
online, to offline, to away, etc... doesn't matter, I believe all 
enabled accounts should be affected, regardless of their current 
state).

>  * If multiple accounts were last taken offline simultaneously by 
> selecting the global Offline status, reconnect just those accounts
>       * If only one account was previously online, reconnect just that 
> account.

	This reconnect would happen when...? Upon an Adium restart? Global 
status change? In any case, affecting all enabled accounts upon a 
global change of status just seems logical to me.

>
> Thoughts?
>

	Hope those help! Regards,...


		Juan


PS: Reading back your original message, I realized all I did with my 
comments is support the way things are done in the current 1.0 betas, 
so I guess I could just summarize by saying you have my support for 
that ;-)





More information about the devel mailing list