Hi John, John Jones <[EMAIL PROTECTED]> wrote on 10/16/2005 03:21:03 PM:
> How adaptable is the Batik toolkit to working in SWT-based applications? This probably depends on what you are looking for. > I have seen a project by Holongate.org to build a 'bridge' to do this, > but from the people that know Batik best... what does and does not work > in SWT? So I don't know anything about SWT. The real question is what are looking at SWT for? The internals of Batik are very dependent on Java2D for rendering, I get the impression that many SWT apps never even touch Java2D, so if this is your goal then Batik will essentially be a non-starter. If your goal is to have a Squiggle like display in an SWT based application then I think the 'problems' are mostly restricted to replacing the current Swing components (batik/swing/**) with SWT components. The main interface point here will likely have to be the Java2D BufferedImage (Batik renders to a BufferedImage, which the SWT component renders to the screen). I don't know if there are reasonable methods in SWT to render a BufferedImage into an SWT component. > I haven't investigated deeply, so the limitations/incompatibility may > be limited to the Java2D <--> SWT interaction. > > If anyone has any insight, I'd be glad to hear it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
