Vincent Hardy wrote: > This is insulting. > > You may not have found yet what you wanted in the Batik software, > but I do not see why you would make such a comment.
Eh, so be it. As I said, I was venting after a couple of days of frustration working with what I consider to be a poorly archticted piece of code for the requirements that we need in this part of the world. I never vent and criticise something without providing a bunch of reasons why I am justifying it (unless someone decides to send 6MB attachments to lists) Anyway, I've sent a very long and detailed reply to the Batik list, there's no need to repeat it for the J3D people. The short summary is - we've already done exactly this within the Xj3D project, and I think all your justifications are invalid. You can run SVG content with any old DOM, just as we can run X3D content from any old DOM. You must be able to run SVG content as a document fragment within a much larger document framework where the document was parsed by someone else. Absolutely critical requirement. It is possible to do, you just need to think outside the box a little. Anyway, we'll continue the technical discussions over on the Batik list.... > Batik may not be perfect (but what is?), and we are open to comments. > But Batik offers a lot of functionality, and I am convinced it offers > what you need. I'm convinced otherwise, but we'll sort out those differences hopefully. > This is incorrect. You can do a lot in Batik without the JSVGCanvas: > you can use Renderers directly, you can use GraphicsNodeRable8Bit > GraphicsNodeRed8Bit, etc.... Too high-level. I need to get down at the GraphicsNode level, with my own BufferedImage (prefer RenderedImage so that I can work with VolatileImage instances). I want and need to tell you exactly when I want the SVG content to render, not when you think it would be nice to. > format. People are doing it and our sample rasterizer application > does it. You could too. Oh.... Paul Flavin post! :) > - SVG is a 600+ pages specification which uses other specifications > (CSS, DOM, SMIL) of comparable sizes. Yup. X3D will be probably twice that size at least. The EAI spec for VRML97 was 100 pages. No big deal. -- Justin Couch http://www.vlc.com.au/~justin/ Java Architect & Bit Twiddler http://www.yumetech.com/ Author, Java 3D FAQ Maintainer http://www.j3d.org/ ------------------------------------------------------------------- "Humanism is dead. Animals think, feel; so do machines now. Neither man nor woman is the measure of all things. Every organism processes data according to its domain, its environment; you, with all your brains, would be useless in a mouse's universe..." - Greg Bear, Slant ------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
