You two.. stop the discussion..
Harry, this is amsn project, a project developed by many developers for
their users... + you're not part of the team, you're a contributor, that's
true (which reminds me, did anyone check if his name was in the TODO ?),
but you're not part of the team and yet, you're requesting many things to
make it look like you want.. + you're asking for GUI refactoring.. look at
all the trouble we had when we changed the option 'connect as appear
offline' into 'conenct as <status>', so many people complained about
loosing their options! + I don't want to loose time on many options
+ complicated options, that will need not only docs, but also many support
time for many n00b users + it will also need a lot of QA time.. without
talking about the code to generate it.. and if not true, then we lost a
lot of time for one stupid thing that noone ever used!
From what I see, it looks like you're trying to make amsn customized to
your need... I know you're also trying to help and do it for the users,
but you seem to forget that not all users are like you.. I suggest this a
few emails ago, that if you want this behavior, then code it and keep it
local..
there is no way we should remove any settings, that's for sure..
even if it's better, we're not going to add any more complicated options
to amsn
amsn is configurable but has a limit, we find the best way to do it and we
do it that way, users will have to bear with the default look .. end of
discussion
Vivia, you're authorized to add those 3 options you talked about, and also
remove the $psm from custom/global nick (although I don't like the fact
that users will need to touch 2 settings to get the look they want, but I
have no choice if I want tht code to stay simple and clean and won't take
much time to work on, etc..)
Apart from that, I'm fed up with this subject, and I lost so much time
reading this, and my head hurts now. So stop the discussion, if you want
something harry, then do it locally and that's it.
I think that concludes it, and let's do it the best for the devels and the
users.. simple for the users, simple for the devels.
Thanks,
KaKaRoTo
On Sat, 04 Feb 2006 06:06:15 -0500, Harry Vennik <[EMAIL PROTECTED]>
wrote:
Op zaterdag 4 februari 2006 11:18, schreef Vivia Nikolaidou:
> I suggest doing it this way:
> - Remove the Global nick setting
> - Remove 'Show email on contactlist instead of nick' option
Won't these confuse people who are currently using them - and make them
lose their options?
Yeah, maybe. I thought of that after sending the e-mail. For 'show email
on
cl' it is simple however. Stay checking the option after loading the
config
and have the default for the cl option depend on it. ('$nick ($status) -
$psm' if not set, '$email ($status)' if set). This way the setting wil
get
converted automatically. Maybe we can even do something similar to
convert
the global nick setting. Needs some thought to find the right way to
setup
the new settings based on it, but once you've got that, the coding
should be
fairly easy.
> - Have a new setting how a contact should be referenced in the top of
a
> chat window. With '$nick <$email> ($status)' being the best default
> IMO.
Is this important enough so we add an option for it?
If you want me to remove the PSM, or put it after the status, I can do
it.
But I think that it's a detail, we can find a default that everyone
likes
and stick to it.
Maybe just move the status before the PSM and display the PSM in
italics?
Maybe stick to some default here indeed (leave it as is, the way it is
truncated makes up for the huge length the description may have with psm
included), have the option for in the chatwindow itself instead. It's
more
useful there.
> - Have a new setting how a contact should be referenced in the CL,
with
> the current behaviour to be default: '$nick ($status) - $psm'. (And
me
> setting it to '$nick ($status)\n$psm' of course)
$nick ($status)\n$psm) is a bad idea because you'll always be getting
the
\n :)
Hehe, yeah, but it's the best I can get with these options, and I
wouldn't
really care. And we can always have the \n automatically removed if it
is the
last char, or if there is whitespace only from \n to end-of-string.
Anyway, even so, global nicknames also have effect on the
chatwindow... so we need a THIRD setting for how they will be referenced
in the chatwindow? And how about all those users who want all 3 to be
similar (eg email addresses) and will have their settings erased and
will
have to go to 3 places to redo them?
New suggestions above solve most of this I think.
-------------------------------------------------------
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
-------------------------------------------------------
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
