The reason why I want it to be a skin option instead of a user option is
simply to avoid having too many options... a while ago (a few years already)
we had decided that if we ever need to add a new option, we would remove one
too.. that's why we didn't have a lot of options added to the preferences
window, and we try to avoid adding new options as much as possible.. the
users are already completely lost with all the options we have, so it's
bad...
having a skin option also has a good reason.. like the underline option,
it's simply because a skin provides you with a look and feel for the app, so
it decides how it should be.. some skins wouldn't be good with underlining
(not sure, but it's a hypothesis that we assume is true), the same with the
boxes, or with the coloring of the nickname depending on the status, etc...
What happens if the user removes the boxes and the skin becomes really bad
because of that? it's his fault, yes, but in the end, we are the ones who
have to suffer from it .. yeah, I'm the one who has to answer lots of n00b
questions on the forums... and many, many users tend to mess around with
options, enable/disable some options they don't know what they do, just to
"try them out" and then forget them like that, then they have problems and
blame it on us!...
anyways, I wouldn't mind having a 'skin options override' plugin or
something that would allow a user to override some options from the skins
without actually having to modify the settings.xml.. that could help,
especially for stuff like the underline option...
Anyways! Having a skin option will also allow like I said before, the old
skins to remain compatible since old skins won't have the boxes, new skins
will have them...
my 2 cents.
KaKaRoTo
On Sun, Feb 1, 2009 at 5:49 AM, square87 <squar...@gmail.com> wrote:
> Sorry Kakaroto, but it's not the same thing to have an user option or a
> skin option?
> I'd prefer user option because a skin option it's a little bit hided... the
> same is for underline it's a nice feature, but if an user want it he should
> edit the xml skin file... and it's not simply for all users...
>
> Btw skin opt or user opt i can do it... if there isn't any voluntary
>
> a last thing we can have two opts...
> 1) hide all boxes
> 2) hide only user's boxes (and it's a great opt... i think... at least for
> me :P )
>
> *Square87*
>
>
> 2009/1/31 Youness Alaoui <kakar...@kakaroto.homelinux.net>
>
>> No, options is not a good idea... I think the user must have a fast skin,
>> that's it... what makes it so slow is the fact that we have that many
>> options to check everytime we're drawing...
>>
>> The most CPU consuming processes I think are :
>>
>> 1 - dealing with transparency.. so alpha blending in images should be
>> avoided when possible
>>
>> 2 - resizing of images.. which means the box image for a group... same
>> with the scrollbar and I think the topbar of the chat window.. those are the
>> images being resized depending on the geometry of the win... in our case,
>> the group box is the one causing an issue...
>>
>> Maybe have a skin option (not a user option) that says 'use_box' or
>> something.. so if there is no box_* files, then amsn will not load the
>> images, and resize a 0x0 image to XxY, etc...
>>
>> This should also fix the problem so many people have... they change the
>> skin and all skins have that box_* thing even if it's not supposed to,
>> simply because most of our skins are old and unmaintained and do not have
>> the box_* files, so the ones from default skin are taken... So having the
>> 'use_box' option set to false by default would be great!
>>
>> KaKaRoTo
>>
>> On Sat, Jan 31, 2009 at 3:35 AM, square87 <squar...@gmail.com> wrote:
>>
>>> I don't know what is better. It depends from user... if he has many users
>>> or not, if he likes an eye candy skin or a light skin... so personally i
>>> don't know.
>>>
>>> But maybe a poll should be: do you want to put a skin wizard? do you want
>>> put in amsn both skins and then the user chooses? For you what should be the
>>> default skin?
>>>
>>> And... if you want a can try to put some options to customize the skin
>>> (show only boxes around group name 0/1 | show boxes around group 0/1
>>> etc...). Yes i know we already have so many opts :-\ but this is what i
>>> think
>>>
>>> with love :)
>>> *
>>> Square87*
>>>
>>> 2009/1/30 Youness Alaoui <kakar...@kakaroto.homelinux.net>
>>>
>>>> We should either update the skin, or change the skin...
>>>> I suggest a vote...
>>>> Changing the skin (to the minimal skin) :
>>>> pros :
>>>> Much faster aMSN!!!
>>>> Smaller binary size
>>>>
>>>> cons :
>>>> Not the same eye candy..
>>>> Users don't like stuff that change too much...
>>>>
>>>>
>>>> I don't vote yet as I don't know...
>>>> however, it might be interesting to see how aMSN performs
>>>> with the saphire skin WITHOUT the box_* pixmaps.. I think
>>>> the resizing of those pixmaps and the alpha blending is
>>>> causing all our CPU problems...
>>>> Also note that most users comments over the skin were that
>>>> they didn't like the boxes around the groups, so I would
>>>> suggest removing them from the next release...
>>>>
>>>> KaKaRoTo
>>>>
>>>> On Thu, Jan 29, 2009 at 12:31:09PM -0200, Gustavo A. Díaz wrote:
>>>> > Hi,
>>>> >
>>>> > Once I've posted in the ML about including the new version of Sapphire
>>>> Skin
>>>> > if you want.... Is almost finished, and I finishing to design the hole
>>>> set
>>>> > of smiles that integrates better with the skin style (since the
>>>> current set
>>>> > of smiles are not mine...). Examples: http://amsn.lnxteam.org/?p=76
>>>> >
>>>> > You can see how the skin looks (main Window):
>>>> >
>>>> http://amsn.lnxteam.org/wp-content/uploads/2009/01/amsn_sapphire25.png
>>>> > Anything else to check, you can download the SVN: *svn://
>>>> > svn.tuxfamily.org/svnroot/amsnskins/amsnskins/trunk/Sapphire/2.5/*
>>>> >
>>>> > Cheers.
>>>> >
>>>> >
>>>> > 2009/1/28 Vivia Nikolaidou <vi...@ee.auth.gr>
>>>> >
>>>> > >
>>>> > > DONE:
>>>> > > - N810: Bind menu button to show right click menu
>>>> > >
>>>> > > Not quite. Menu button called ::tk::FirstMenu which bugged so I
>>>> substituted
>>>> > > it with an empty proc, and made ctrl+click fire <<Button3>
>>>> > > events if we're on maemo.
>>>> > >
>>>> > > 0.98 TODO:
>>>> > > - Add missing pixmaps to minimal skin and make sure tab flickering
>>>> > > is visible
>>>> > > - Fix MSNP2P stuff that broke with WLM 2009
>>>> > > - Finish VoIP UI
>>>> > > - Small annoyance: when a CW gets opened because they nudge you, you
>>>> don't
>>>> > > see their DP
>>>> > > - Apply patch from PEACEYALL's thread
>>>> > > - Make ListChoose draw in a canvas
>>>> > > - Make webcam work for BSD systems
>>>> > >
>>>> > >
>>>> > >
>>>> ------------------------------------------------------------------------------
>>>> > > This SF.net email is sponsored by:
>>>> > > SourcForge Community
>>>> > > SourceForge wants to tell your story.
>>>> > > http://p.sf.net/sfu/sf-spreadtheword
>>>> > > _______________________________________________
>>>> > > Amsn-devel mailing list
>>>> > > Amsn-devel@lists.sourceforge.net
>>>> > > https://lists.sourceforge.net/lists/listinfo/amsn-devel
>>>> > >
>>>> > >
>>>> >
>>>> >
>>>> > --
>>>> > Gustavo A. Díaz
>>>> > GDNet Projects
>>>> > www.gdnet.com.ar
>>>>
>>>> >
>>>> ------------------------------------------------------------------------------
>>>> > This SF.net email is sponsored by:
>>>> > SourcForge Community
>>>> > SourceForge wants to tell your story.
>>>> > http://p.sf.net/sfu/sf-spreadtheword
>>>> > _______________________________________________
>>>> > Amsn-devel mailing list
>>>> > Amsn-devel@lists.sourceforge.net
>>>> > https://lists.sourceforge.net/lists/listinfo/amsn-devel
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> This SF.net email is sponsored by:
>>>> SourcForge Community
>>>> SourceForge wants to tell your story.
>>>> http://p.sf.net/sfu/sf-spreadtheword
>>>> _______________________________________________
>>>> Amsn-devel mailing list
>>>> Amsn-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/amsn-devel
>>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by:
>>> SourcForge Community
>>> SourceForge wants to tell your story.
>>> http://p.sf.net/sfu/sf-spreadtheword
>>> _______________________________________________
>>> Amsn-devel mailing list
>>> Amsn-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/amsn-devel
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> Amsn-devel mailing list
>> Amsn-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/amsn-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Amsn-devel mailing list
> Amsn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amsn-devel
>
>
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
