Hello All,
I'm now well versed in how to implement new icons in Inkscape. If you design icons and would like to help develop an excellent icon theme for Inkscape, then either A.) jump on chat and I can show you how to edit icons, and/or B.) Make your icons and forward them to me and I will implement them.
There are plenty of icons left to designed.
Don't forget that artists are developers as well...
I'm moving all icons in the application to icons.svg which is by default at: /usr/local/lib/inkscape/icons/icons.svg
If you open that file up and copy how those were laid out, and then name the group of the file icon uniquely, that is the best way to understand how to add/edit icons. Forward me any changes and I'll add them into the app.
Jon
El Lunes, 15 de Marzo de 2004 02:45, Jonathan Phillips escribió:
Hello All,
I'm now well versed in how to implement new icons in Inkscape. If you design icons and would like to help develop an excellent icon theme for Inkscape, then either A.) jump on chat and I can show you how to edit icons, and/or B.) Make your icons and forward them to me and I will implement them.
There are plenty of icons left to designed.
Don't forget that artists are developers as well...
I'm moving all icons in the application to icons.svg which is by default at: /usr/local/lib/inkscape/icons/icons.svg
If you open that file up and copy how those were laid out, and then name the group of the file icon uniquely, that is the best way to understand how to add/edit icons. Forward me any changes and I'll add them into the app.
Jon
Hi Jon: I agree the svg format is the best, but I don't think the most comfortable method is having a unique file icons.svg with icons inside. -If the file breaks, the whole interface is broken. -the relation between the icon and the name of the icon is not direct, you must open icons.svg in inkscape, click the icon, maybe first ungroup it, and also open the xml editor. If you now the name is hard to find the icon, and if you got an icon and want to find a name is hard too. I think it's easier to make skins with masks for xmms. -Inkscape is the only application to use the only-one-file method, except windows moreicons.dll. If we want to use the icons in Scribus and The Gimp it will be quite hard to export all of them and also keep two versions synchronised: pngs/svgs/only-one-file-svg On the other hand is more likely that many more apps, including The Gimp (GTK libraries) and Scribus (Qt libraries) will support and already support svg graphics for their interfaces, but all of them in the same file.
Is there any good reason to use a one-file-svg to store Inkscape icons?
What about different svg icons with different names? tool-freehand-pencil.svg.
yours: Néstor Díaz
On Mon, 2004-03-15 at 15:50, nestor diaz wrote:
Is there any good reason to use a one-file-svg to store Inkscape icons?
Wouldn't it just be much easier to use a directory to hold the icons?
In fact, there should be a logical structure: /image /themes /default /big /HighContrast The images should be placed inside directories. /default freehand-tool.svg export-svg spiral.svg
My question is, does Inkscape support single svg icons as in my example? If so, how hard could it be to code an option to make bigger or smaller a toolbar on-the-fly? (I guess inkscape could do this kind of stuff with "svg" pretty well)
Yours: Nestor
El Lunes, 15 de Marzo de 2004 16:03, Charles Goodwin escribió:
On Mon, 2004-03-15 at 15:50, nestor diaz wrote:
Is there any good reason to use a one-file-svg to store Inkscape icons?
Wouldn't it just be much easier to use a directory to hold the icons?
Removed CC's, no need to Cc the user list
On Mon, 15 Mar 2004, nestor diaz wrote:
Date: Mon, 15 Mar 2004 20:28:45 +0100 From: nestor diaz <nestordiaz@...207...> Reply-To: inkscape-user@lists.sourceforge.net To: Charles Goodwin <charlie@...208...> Cc: Inkscape ML inkscape-devel@lists.sourceforge.net, Jonathan Phillips <jon@...15...>, inkscape-users inkscape-user@lists.sourceforge.net Subject: [Inkscape-user] Re: [Inkscape-devel] inkscape interface icons
In fact, there should be a logical structure: /image /themes /default /big /HighContrast
This reminds me, the High contrast themes are all actually done in SVG but were rasterized. I talked to Jimmac about it at GUADEC and the files are either in Gnome CVS or he has them somewhere. I was interested in turning them into a proper SVG theme and then doing a variant with more colours than just two but I never got around to it.
- Alan
El Lunes, 15 de Marzo de 2004 20:53, Alan Horkan escribió:
Removed CC's, no need to Cc the user list
On Mon, 15 Mar 2004, nestor diaz wrote:
Date: Mon, 15 Mar 2004 20:28:45 +0100 From: nestor diaz <nestordiaz@...207...> Reply-To: inkscape-user@lists.sourceforge.net To: Charles Goodwin <charlie@...208...> Cc: Inkscape ML inkscape-devel@lists.sourceforge.net, Jonathan Phillips <jon@...15...>, inkscape-users inkscape-user@lists.sourceforge.net Subject: [Inkscape-user] Re: [Inkscape-devel] inkscape interface icons
In fact, there should be a logical structure: /image /themes /default /big /HighContrast
This reminds me, the High contrast themes are all actually done in SVG but were rasterized. I talked to Jimmac about it at GUADEC and the files are either in Gnome CVS or he has them somewhere. I was interested in turning them into a proper SVG theme and then doing a variant with more colours than just two but I never got around to it.
- Alan
I have used them to make a version for a high and technical school here in spain, for a modified Gorilla Theme, because white silouhettes inside the orange circles wasn't accessible at all. yours: Nestor
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
Charles Goodwin wrote:
On Mon, 2004-03-15 at 15:50, nestor diaz wrote:
Is there any good reason to use a one-file-svg to store Inkscape icons?
Wouldn't it just be much easier to use a directory to hold the icons?
Several good reasons for a single file:
1) This one file fixes one of our big problems: maintaining the path to icon resources. having a single file for Inkscape icons is analogous to caching them at startup. We get the SVG equivalent of GtkIconFactory for free.
2) "Theming" could be trivial. Just use another file.
3) Also, the file is self-documenting. We can annotate the icons ON THE PAGE ITSELF, and just add the file to our docs.
Bob
Plus, is there really much of a need for themeability of Inkscape? In fact it kinda doesn't make usability sense to change the known icons on the fly.
While I understand the idea behind splitting these files into individual ones, and fully support that plan for moving Inkscape to themeability, I must say that I still feel the best course of action is to add icons where not present, and then convert any non-svg (xpms) into icons.svg.
Please help me out on this one! After this task is done, then we should look into some of that reorganization.
Jon
On Mon, 2004-03-15 at 13:42, Bob Jamison wrote:
Charles Goodwin wrote:
On Mon, 2004-03-15 at 15:50, nestor diaz wrote:
Is there any good reason to use a one-file-svg to store Inkscape icons?
Wouldn't it just be much easier to use a directory to hold the icons?
Several good reasons for a single file:
- This one file fixes one of our
big problems: maintaining the path to icon resources. having a single file for Inkscape icons is analogous to caching them at startup. We get the SVG equivalent of GtkIconFactory for free.
"Theming" could be trivial. Just use another file.
Also, the file is self-documenting. We can
annotate the icons ON THE PAGE ITSELF, and just add the file to our docs.
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
nestor diaz wrote:
I agree the svg format is the best, but I don't think the most comfortable method is having a unique file icons.svg with icons inside. -If the file breaks, the whole interface is broken. https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Actually, I think it's good that it's all or nothing - it makes it hard to leave out one icon, and it makes it really obvious if there is a problem :)
njh
On Tue, 2004-03-16 at 00:12, Nathan Hurst wrote:
Actually, I think it's good that it's all or nothing - it makes it hard to leave out one icon, and it makes it really obvious if there is a problem :)
Fair point. Also all inkscape code should be in one .cpp file.
Yes, I'm being facetious. And, yes, the comparison isn't the greatest but it does highlight the issues. One giant file is harder to manage that a broken down set. As for 'missing one out', won't that (or shouldn't that) be shown up by a warning when running Inkscape that a icon could not be loaded? Or does it just fail silently?
Charles Goodwin wrote:
On Tue, 2004-03-16 at 00:12, Nathan Hurst wrote:
Actually, I think it's good that it's all or nothing - it makes it hard to leave out one icon, and it makes it really obvious if there is a problem :)
Fair point. Also all inkscape code should be in one .cpp file.
certainly we should move to using one single makefile.
Yes, I'm being facetious. And, yes, the comparison isn't the greatest but it does highlight the issues. One giant file is harder to manage that a broken down set. As for 'missing one out', won't that (or shouldn't that) be shown up by a warning when running Inkscape that a icon could not be loaded? Or does it just fail silently?
the only reason to break .cpp files into smaller pieces is if the single file would be too hard to comprehend. the icons file is easy to comprehend.
njh
Yeah, I'll try to get to that b4 our release...next week is shit for me though...
Jon
On Mon, 2004-03-15 at 20:49, Nathan Hurst wrote:
Charles Goodwin wrote:
On Tue, 2004-03-16 at 00:12, Nathan Hurst wrote:
Actually, I think it's good that it's all or nothing - it makes it hard to leave out one icon, and it makes it really obvious if there is a problem :)
Fair point. Also all inkscape code should be in one .cpp file.
certainly we should move to using one single makefile.
Yes, I'm being facetious. And, yes, the comparison isn't the greatest but it does highlight the issues. One giant file is harder to manage that a broken down set. As for 'missing one out', won't that (or shouldn't that) be shown up by a warning when running Inkscape that a icon could not be loaded? Or does it just fail silently?
the only reason to break .cpp files into smaller pieces is if the single file would be too hard to comprehend. the icons file is easy to comprehend.
njh
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
participants (6)
-
Alan Horkan -
Bob Jamison -
Charles Goodwin -
Jonathan Phillips -
Nathan Hurst -
nestor diaz