I used JGO lib to create JGO Document in elcipse plugin.
I’m not sure what you mean when you say that “the above code is working fine with JGo 1.3”. The DefaultDocument class and in fact the entire com.nwoods.jgo.svg package did not exist prior to JGo 4.1.
Sorry! the above code is working fine with JGo 4.1.
Generated SVG in Document object contains with <jgoxml:JGoClass and <ellipse elements which are not qualified in SVG viewer like Batik SVG Viewer and Adobe SVG Viewer.
Please can you suggest, how to replace this elements in new SVG Document Object. Present, I am removing these elements to show in Adobe SVG Viewer/Batik SVG Viewer. With this change, I am getting different svg which is not original.
Some times, I used to get group of nodes which the group identifies with boundary box. If i am using this type of SWING jgo view , i am not able to get the actual SVG.
Please can you help on this.
If the GenerateJGoXML property of DefaultDocument is set to “true”, JGo will generate JGoClass elements that are not part of SVG. These elements allow the generated XML to be read back in to JGo to recreate the original JGoDocument. If you are not reading the generated XML back into JGo, you do not need to generate these elements. Just set GenerateJGoXML to false.
How to use ImageObserver with JGo packages.
You should be able to use ImageObserver with JGo 5.1. What problem are you having? Did you perhaps change from using JGo Swing to JGo SWT? In JGo Swing, JGoImage is an ImageObserver. In JGo SWT, JGoImage is an ImageLoaderListener.