Derek P. Moore wrote:
I've got it pretty much figured out by now. I had to complete the task of fleshing out all the necessary StockIDs before I could get started, though. We need to use IconFactory/IconSet objects to tie Inkscape- specific icons to Inkscape-specific StockIDs (for an end result similar to Gtk::Stock::* or GTK_STOCK_*).
I need one thing to finish the icon work in the Gtkmm code: Could anybody here write up a script to rip apart icons.svg into separate files?
A single icons.svg file is convenient for artists (a single place to work on all the icons), and its where the legacy code gets all its SVG icons, but it doesn't play well with IconFactory. I need separate .svg files per icon.
Can someone script this up, so we can automate the creation of the separate icon files from icons.svg?
As soon as I get separate icons files, I'll get them implemented in the Gtkmm codebase (and we'll have icon themes as an inherent byproduct of properly implementing StockID/IconFactory).
Thanks,
Derek
(Btw, the Gtkmm code now has theme-able keybindings via '/usr/share/inkscape/ui/keybindings.rc'. The morning of New Year's Eve, I decided to finish all the menu-related StockIDs/StockItems and implement loading keybindings from a file at runtime via AccelMap before the Old Year was up. I completed my goal with 45 minutes to spare, while riding in a car from one New Year's party to another. *grin*)
Does the file really need to be broken up? We are already using the IconFactory, and merely checking the icons.svg file first before loading the old-fashioned Stone Age bitmap icons, which hopefully are headed for the bitbucket.
With the Gtkmm wrapper of IconFactory, it would seem to be easier to do this wedge in Gtkmm with a simple subclassing than is already done in Gtk/C. A little bit of C++ coding by a couple of people could save many hours of work for many others.
Bob