Hey Ivan. Ivan Andjelkovic: > The "interim period" is going just fine. I have downloaded > batik-1_7beta (I used 1.6 before) from SVN and done some browsing > through the code, especially the DOMViewer class. I've been trying > some of the stuff on the Viewer, and would appreciate your comments on > some of the following issues.
Cool, ok. (Sorry about the detail in replying…) > 1) Regarding the tree: > Adding pop-up menu to the nodes in the tree, containing "remove" and > "add new node" items. Remove option would remove selected nodes from > the document (as well as from the tree). Add new node option would > open the dialog, from which the node type and the node attributes have > to be chosen (and maybe some other options), and append that node as a > child to the selected node from the tree. The issues here are the > compatibility of the parent node and the appended one, determining the > required attributes according to the node type, filling the values of > the attributes with valid values etc. Yeah that sounds like a good start. If using pop-up menus, you could just ensure that only the menu items corresponding to compatible node types are enabled/visible. > 2) The attributes (name/value) table: > Making the the value column of the table editable, so the attribute > values can be changed; Adding the pop-up menu to remove and add new > attribute through a dialog. > > 3) Making the text area for comment, text or cdata_section node editable. Yup. > 4) Tracking the changes of the document structure. As Thomas > suggested, adding Mutation Event Listeners would manage the update of > DOMViewer whenever the document structure changes, including using the > DOMViewer itself to change the document. Yes, I think using the standard DOM mutation listeners would be best for tracking changes to the document structure. (For the CSS properties, you’ll have to use a CSSEngineListener on the CSSEngine.) > I plan to continue working on these issues, as well as to browse > deeper into the Batik's architecture. Great. > >Are you guys going to have a wiki or blog or something to document your > >progress? There's no requirement to, but it may be useful for me (and > >the other devs) to see where you're at. > > I can create a wiki page (perhaps http://www.wikidot.com ?) or share a > document on the google docs. There’s also an Apache wiki you can use: http://wiki.apache.org/xmlgraphics-batik/ It’s not pretty, but a good thing is that updates to pages there send notification mails to batik-dev. I’d suggest using that over an external site, if a wiki is what you’d like to use. -- Cameron McCormack, http://mcc.id.au/ xmpp:[EMAIL PROTECTED] ▪ ICQ 26955922 ▪ MSN [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
