[xml-dev] Fwd: Re: [nbdev] XML Module extension proposal...

,--------------- Forwarded message (begin)

 Subject: Re: [nbdev] XML Module extension proposal...
 From: Petr Kuzel <[email protected]>
 Date: Wed, 29 Jan 2003 19:01:03 +0100

 Adam Fowler wrote:
 
 > Hello all,
 > 
 > I'm new to this, so bear with me. (I've had a quick read through the
 > proposal guidelines.)
 > 
 > I noticed on the XML module page that they wanted a system that would
 > "provide infrastructure for better, easier and rapid development of new
 > modules for different XML domains, e.g. DocBook, XHTML, SVG, etc.".
 
 Yes, it's XML modules goal. Still a lot of things missing to
 fulfill it. Mainly spare time to realize it :-).
  
 > I believe this can be done by craftily using CSS, like the XMLMind
 > XMLEditor[1] does. Provide an interface that allows users to associate
 > DTDs with a stylesheet for a visual editor (FrontPage-esque), and code
 > the editor so that it forces the author to strictly conform to the DTD.
 > This will allow XML authors to visually edit their XML files, without
 > having to worry about DTD conformance. (This REALLY got on my nerves
 > when going through the Tomcat-Book[2] project's source by hand, as
 > certain people *glare* used plain text editors and randomly chose
 > element ids. Granted the softs weren't/aren't available tho'.)
 
 Do you have experience with designing such editor? I guess it's
 long-term task even for skilled developer.
  
 > As the XML Registry is already part of the XML project code, the battle
 
 It's still subject of incompatible API changes.
 
 > is already half won. Other more advanced features could be added later
 > such as:
 >   - In built support for DocBook (Use this as an example so others can
 > write additions to support other XML DTDs.)
 >   - Support for GUI insertion of high level elements, such as sections
 > etc in DocBook, or a rectangular box in SVG. Provides feature similar to
 > Word's styles drop down selector(heading, title, section etc.). This
 > works great in LyX[3] for LaTeX.
 >   - Enhanced XSL Transform functionality by providing users with default
 > DTD options. E.g. for DocBook DTD, use this stylesheet, these GUI
 > insertion elements, and these filters for output (x filter for HTML
 > output, y filter for XSL:fo/PDF output etc.) using these options.
 > (override default variables, such as CSS stylesheet to use.)
 >   - Allow users to specify that they wish to restrict elements that
 > authors use, without them having to re-write the DTD. This is useful for
 > large collaborative projects and professional publishers.
 
 Impressive list!
  
 > There's probably a few other things you could add too. Because of the
 > way NetBeans and the XML module have been coded, the basic functionality
 > should be relatively easy(!) to code. (Good work BTW.) I'm quite happy
 > to go away and code the thing, after being given a few pointers. (XML
 > module guys? Any ideas/help you could give to get started would be much
 > appreciated. E.g. how do I code for NetBeans!!!)
 
 http://www.netbeans.org/devhome/community/contribute.html
 
 I see four basic stones: Swing, XML, CSS (missing) model and EditorCookie
 interface.
  
 > Tell me what you all think, anyway. It'd be a great feature - having a
 > WYSIWYM XML editor - if we could code it.
 
 Yes, it'd be indeed. However users say final word. Let ask them
 in advance if they really want it (NetBeans was recently recognized
 as Java IDE).
 
   Cc.

`--------------- Forwarded message (end)