This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | DocBook support | ||
---|---|---|---|
Product: | xml | Reporter: | _ lkramolis <lkramolis> |
Component: | Code | Assignee: | issues@xml <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
URL: | http://www.oasis-open.org/docbook/ | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | 22160, 22152, 22789 | ||
Bug Blocks: |
Description
_ lkramolis
2002-10-14 17:31:50 UTC
Well, I'd have a whole host of suggestions for a UI - such as: - An editor with a tree view of the document docked into it, so that you can select a subelement and only see the text of that subelement (filtering out trivial tags like <para> but exposing document sections like section or chapter, etc. - Ability to define a subset of the dtd available for code completion (docbook is huge and contains tons of tags only useful if you're writing a particular type of document) - Integration with Apache FOP or the Docbook XSLT stuff so that you can "compile" an html or pdf build of the book (Jesse already did this - see the build tasks he wrote if you still have a checkout of the ftp copy of the book sources) - A UI for defining that subset - Some kind of floating palette allowing you to quickly wrap a section of text in some kind of tags And, well, I can think of lots more things, but this is probably already more than you wanted to hear! -Tim There is an elementary DocBook support module in contrib. |