Sorry if this idea will sound stupid, but I'll write it anyway:
What about always handling the bitmaps internally (like for example Illustrator does), and give the user the choice to save SVG with: a) embedded bitmap (default behaviour) b) save svg with linked bitmap (write bitmap to disk beside the SVG)
The swith between the "internal bitmap handling" and "link bitmaps" could be placed somewhere in the Inkscape Preferences window...
Molumen
----- Original Message ----- From: "Ted Gould" <ted@...11...> To: "Inkscape Devel List" inkscape-devel@lists.sourceforge.net Cc: "Christopher Brown" <audiere@...400...> Sent: Wednesday, July 18, 2007 7:33 PM Subject: [Inkscape-devel] Changed bitmap handling
This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
--------------------------------------------------------------------------------
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hello all,
As you guys are aware Chris is working on putting some bitmap editing tools into Inkscape for is GSoC project. There's a couple things that are difficult on the user interaction front that I wanted to bring up and see what people think.
Basically, there are two types of images: embedded and linked. There is two types of linked images that are read-only and ones that we can write. So what should happen when someone does a bitmap operation on these types of image? How should undo/redo be handled?
I'm leaning towards saying "always embed" at this point. It's simpler and probably does something similar to what most people want anyway. We don't need file dialogs or temporary files. What does everyone think about this? Chris, did I state the problem correctly?
--Ted