aie aie aie.. we're going too far in this... first, Tom, the sash thing
will not generate any "why can't I resize anymore", it's a "sash look"
option, not a "disable sash".. even if it's width is set to 0, the sash is
still there, it's just it's 'reliefed part' that disappears...
and I agree, what amsn *does* should be user setting, what amsn looks
like, should be skin option...
now, what about the request "humm.. I'd like to customize my amsn and
change the sound that gets played when I get a new message.. I don't like
that guitar thing".. do we need to tell the user "in that case, either
overwrite the file in /usr/share/amsn/skins/default/sounds/.. or edit the
settings.xml file and modify the path... and if you don't have root
access, then you need to copy that skin, rename it, place it under
~/.amsn/skins, then do the above".. ouch!
I'll forward a mail in a few minutes that clears this...
KKRT
On Wed, 25 Jan 2006 17:42:05 -0500, Tom Jenkins
<[EMAIL PROTECTED]> wrote:
Jérôme Gagnon-Voyer wrote:
And I supose that all the options you want to remove from skins will
move inside the preferences?
I didn't say I wanted to remove all the skin settings, I said I thought
that some could be set by user & skin. Small stuff that only 'advanced'
users want could go in a plugin or something - somebody was talking
about a Tweak Amsn plugin or something, that would be ideal. But I
really think that things like the sash and dp options should be user
only, not skin, they are 'functionality' not 'theme' settings - when you
change a background colour, that doesnt change anything Amsn *does*,
just how it *looks*. If you change whether DPs are shown in the
contactlist, you are changing something Amsn *does* - and hence what the
user can do.
Simplicity is the key, someone opens aMSN, he doesn't need to start
going to preferences to adjust 10 settings that normally skins should
take care of. I don't like that. If they really want to change the look
of aMSN, then then should be able to adjust manually the settings of
the skins somewhere in the preferences, but we don't need to bloat the
current preferences with that.
I totally agree, and they won't have to do that. I'm just saying that
the skin shouldn't set stuff like whether to show display pictures or
resize sashes or stuff like that. For those settings, we have (config)
defaults that most users will like, and an entry in the prefs window (eg
Show display pictures on the contact list) - these surely have a place
in prefs, unlike options to override skin settings(i agree with you
there, and like i said above, maybe put them in a plugin of some sort...)
Le 25 janvier 2006 à 17:07, Tom Jenkins a écrit :
, like showing display pics on the contactlist and showing the resize
sash in the chatwindow should ONLY be user-configurable, NOT
skin-configurable. Do people agree or am I out on a limb here? :D
___________________________________________________________ To help you
stay safe and secure online, we've developed the all new Yahoo! Security
Centre. http://uk.security.yahoo.com
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
--
KaKaRoTo
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
