Hi Seth,
I did receive the package thanks, I haven't had any time to look
at it (real work has been a monster lately).
"Seth Tager" <[EMAIL PROTECTED]> wrote on 04/18/2006 04:54:07 PM:
> > Perhaps you save some intermediate memory but if I give you
> > an java.awt.Path with the data what is the difference from calling
> > 20 different methods (like PathParser does)? You can pull the data
> > out of the path object at least as easily as implement the PathHandler
> > interface...
>
> I think you lose the potential to handle dynamic content. I'm not
> concerned about dynamic content at the moment, but if I'm thinking
> about a general solution I figure I should work toward one that would
> support it in theory.
Well I don't think you lose this in this particular case but others
might be a problem...
> > I would expect that many people would prefer to implement the
Graphics2D
> > interface to import SVG data - it may be useful for importing other
data
> > as well. However it can be a bit lossy.
>
> I hadn't thought of that, and it sounds like the easier way to go for
> some situations, but the lossy aspect is important. I assume things
> like filters get transformed into drawImage calls, which is what you
> mean by lossy, no?
Yes, filters for example are translated into drawImage calls (also
things like group opacity).
> > I really don't think I follow you here. Do you care to share your
> > work so far?
>
> I'd be happy to send it to you. I tried posting it to the list about a
> week ago but it was rejected as being too large (300k). I cc'd you
> directly, but I didn't get a reply so I'm not sure if you got it. Can
> I send you a copy offline?
Thanks for sending it, as I said I just haven't had time to check it
out. If you want a wider audience for it you could create a Bugzilla
entry
(mark it as an RFE) and attach the changes.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
