Hi Lewis, Lewis Keen <[EMAIL PROTECTED]> wrote on 02/15/2006 04:09:31 AM:
> I've managed to now get the basic initial interface screen working now > and its looking good :) I'm hoping to open source this once I've > finished but with it being uni I'm not holding my breath :/ Well good luck! > On 2/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > The problem is the massive filter effect on the whole canvas: > I had a feeling it was the filter, and as soon as I took it away it > worked :) bit of a shame, it looked really good, I may implement that > as a setting that can be toggled by the user for fast machines (my one > at home is a mid to low-range machine). The problem is that the filter effects (some more than others) take a lot of work to evaluate (specular lighting is one of the worst). Without extra hints the implementation doesn't really know where it would make sense to cache a raster version of the document. This is the reason the 'static' property was added to SVG 1.2. There is a patch in bugzilla that adds this to Batik (not sure how clean it will apply right now). It didn't work in all cases but it can help. > > Lewis Keen <[EMAIL PROTECTED]> wrote on 02/12/2006 09:37:17 PM: > > > 3) More examples - are there any? > > The samples directory has lots of example SVG. > I looked at the examples and liked them :) only problem with them is > that they don't really give you any java-related examples. i guess > that's why I downloaded the squiggle source :) Well one of the key points is that at a fundamental level there isn't any difference between manipulating the SVG in Java and manipulating it in ECMAScript. Java will require some additional casts and stuff but Java can do everything that the ECMAScript does. So while you can't cut and paste the code the basic methods are identical. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
