Hi all: sorry if I'm wrong, but I guess you have never touched de icons.svg.
1º If the icons are ok, then the setup or tar.bz or whatever should be ok. If the MAKE is wrong the compiling will be wrong, etc.
2º Icons, side by side in the same canvas with hidden names are hard to manage. You want to click one and you click the other you are not concentrate in the job with icons flying around.
3º If I like alignment icons (which is not the case) is hard just to substitute only those icons. Is hard to make a theme from two or more.
4º Somebody says Inkscape doesn't need themeing. As long as it's beeing used in several platforms/enviroments it should and people will ask for it sooner or later, for the shake of integration. Old school designers use to work which such a different interfaces that integration with desktop wasn't an issue. Now, if you usee Gnome, Kde, Mac and Windows, it should at last has four themes. I am not going to do all of them indeed.
Well at this point, all icons shouldn't really need to be redone, because GTK should now which system is running on and move from one theme to another for system interaction icons like: open, print, etc. even pick them from the system stock icons.
5º The last argument is not new. I would like to hear a real advantage of a monolithic file. No themeing system that I know is based upon a monolithic file. Some times they try to reduce it us much as possible, but at the end you have several files. Sorry, I forgot wallpapers: they are monolithic files ;) If there is no real advantage my four other arguments should win (yeah!!)
Really guys, I don't want to steal your sleep with this conversation, just don't remove the png icons possibility (and complete it, because there are some icons that can only be in xpm format)
Yours: Néstor Díaz
El Martes, 16 de Marzo de 2004 07:37, Bob Jamison escribió:
Peter Linnell wrote:
One more good reason for a single icon file: packaging.
One of the things which has helped to make my life easier is the sane way inkscape is setup as a source tarball and a well done configure script. This made making decent rpms miles easier.
And the fewer dependencies and fewer installation hacks, the better.
If you have spent half a night chasing down missing files (sometimes icons) and fixing broken makefiles trying to build an rpm - you'll understand completely ;)
--- which we have been doing recently with those pesky individual .xmp files!!!
Peter
Oh, and dont forget CSS and XSLT being able to morph everything... themes and portability.
I don't know who originally came up with the idea of one file leveraging the benefits of XML. Makes life for -us- (the #1 reason) so much easier. Smart dude. I owe that man a beer! ;-)
Bob
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel