As I don't like the fact we are naming images in amsn's code rather freely, I 
think we need some consistency.  Therefor,
I present a beginning of a specification I made.  I already applied some of 
these on my local copy of amsn and I think 
I'll just commit it and hope it doesn't break everything.  I could always just 
reverse the commit anyway. (Though I 
don't know how to do it yet ;))

Karel.

PS: If you don't like the idea, I'll revert changes if I find out how to do it 
but I won't reverse everything just because 


The specification:
You'll see all names start lowercase.  Everything before the first _ is the 
kind of image.  Then, if needed, an extra name
is appended if there are multiple sizes of the same image and as last the 
unique name of the image is given.
So, an image is named like:
kindWithFirstCharacterLowercase_{size}_{unique name}

Displaypictures:
        * Original size (or standard if set to automatically resize dps):
DONE            "displaypicture_std_$email" for contacts                        
                (now user_pic_$email)
DONE            "displaypicture_std_self" for the own dp in the dp changer      
                (my_pic ?)
DONE            "displaypicture_std_none"
        * 50x50 resized for notifications / on top of cl for self
DONE            "displaypicture_not_$email" for contacts' pictures (on 
notifications e.g.)      (smallpicture$email)
DONE            "displaypicture_not_self" for own dp, on top of CL e.g.         
                (my_pic_small ?)
TODO            "displaypicture_not_none"                                       
                
        * small dp on cl / could also be used when a user is added to a chat or 
whatever
DONE            "displaypicture_tny_$email" for contacts' pictures              
                (small_dp_$email)
TODO            "displaypicture_tny_self" for own dp -> for "added to chat"     
                                (?)
TODO            "displaypicture_tny_none"                                       
                (Think it's copied now/
                                                                                
                 recreated for every 
                                                                                
                 contact)
                Note: these tny dps could be used to put in front of every 
message of a user for example
Emoticons:
=Standard ones=
        * original size used in smiley substitution:
DONE            "emoticonStd_std_$trigger"                                      
                (smiley_$trigger)
=Custom ones=
        * original size used in smiley substitution:
DONE            "emoticonCustom_std_$trigger"                                   
                (custom_emoticon_$name)
                                                                                
                (custom_emoticon_image_
                                                                                
                 $name (if added in the 
                                                                                
                 current session ?!?)
TODO   Maybe we could name these after their descriptive "name" ?  For standard 
emoticons, the name is unique, for custom emoticons too while only the trigger 
*should* in fact, but we coded it otherwise.
=Custom one received in convo=
        * original size used in smiley substitution:
DONE            "emoticonCustomRcd_std_$file"

=All=
        * smaller version for smileys-menu:
                "emoticonAll_tny_$number
DONE

UI pixmaps
        *a skin's pixmaps, fromthe "pixmaps" dir
DONE            uiElement_std_$name                                             
                (pixmaps_name)
PROB            uiDynamicElement_$name          
        Note: I seem to have a small issue with the mainbar not showing 
sometimes ?
        *a base scrollbar image
TODO            uiScrollbar_$name
                
                
        
Special:

TODO    * tmp : temporary pixmap
        DOne for 2 instances .. we have more

                        
                



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Reply via email to