Hey Jasleen, Cameron, > At the moment Jasleen has the error console showing the XML where the > error is, and we both thought it’d be useful if you could click a > button/link in that error entry so that the element could be edited. > This could be achieved by opening Ivan’s enhanced DOM Viewer window and > selecting the relevant element.
Here's a bit more on the enhancements on the DOMViewer that might be useful. The DOMViewer would need the DocumentUpdater (which is the BridgeContext or the UpdateManager) to be set in order to perform the updates on the canvas. The tree showing the nodes in the document containts the info of the document nodes, so it might be sufficient to pass the element to the DOMViewer to edit it. Jasleen, I have tried your patch and browsed a little through the ErrorConsole. I noticed that, the ErrorConsole needs the JSVGCanvas passed in order to get its parent frame. I guess keeping it there just in case we want to edit the element isn't the best way to do it. Maybe to get that info through an interface? Then the element that caused the error should be found and passed to DOMViewer along with the DocumentUpdater, to allow editing of that element. I also think that creating the DOMViewer to edit the element should be implemented somehow as in squiggle, since we don't want to create new DOMViewer instance each time we edit the element from the ErrorConsole (or we do?) Any thoughts? Ivan -- View this message in context: http://www.nabble.com/Some-collaboration-between-your-projects-tf4023643.html#a11570793 Sent from the Batik - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
