Hi, > I'm guessing that reading WTKX won't be significantly more efficient than > reading SVG, since they are structurally pretty similar. Plus, an > SVGSerializer would allow us to read SVG directly into a Pivot app without > first transforming it. I agree, but are you thinking to use Batik from the SVGSerializer, or do all the work in our code ? Reading well an SVG file could be complex (it's a complex format), but maybe only a subset could be more simple, for example SVG Tiny.
And, from what I know, SVG hasn't the definition for some of our GUI components, so this is only for the graphics part (drawings, etc, for WTKD files) ? Reference: http://www.w3.org/Graphics/SVG/ Surely one great thing on SVG is that's a vectorial format, so we can scale its graphics at runtime in a simple way. Trick: why not have also the ability to save the imported SVG into Pivot WTKD Drawing format, so we could have more optimized graphics one time imported, for example for icons, etc ... Or if the WTKD will be the imported format, could we think on add the ability to save the digested info loaded from those files in a binary serializable format (to avoid parsing, etc) ? This could be an utility under our Tools, choosing one or more resolution, ect ... What do you think ? Bye, Sandro
