#5 Provide an HTML editor

[Christopher Lenz]

Providing an editor for HTML files is a high priority
item, this being a project that wants to deliver tool
support for web development.

The HTML editor can be based on the XML editor with
some tweaks to support SGML syntax. XML files with an
HTML DOCTYPE should also open in the HTML editor.

The outline page should show the structure of the
document by displaying block elements such as headings,
paragraphs and tables with nice icons. The normal XML
outlining which puts every tag into the outline is not
appropriate here.

For parsing HTML files and extracting the model for the
outline we should consider using NekoHTML.

Handling of embedded scripts and stylesheets in not in
the scope of this RFE, and should be handled in a later
release.

[Igor Malinin]

Logged In: YES
user_id=346040

I don't like neko. It tries to fix most error's in the
document which is good for browsers, or processing existing
pages, but is not good for development tool. IMHO dev tool
should (must) show all errors to the developer. We just need
a customization to XML parser that understands tags that
need not be closed, and tags like <script>.

[Christopher Lenz]

Logged In: YES
user_id=10889

As long as NekoHTML provides a way to get at the errors,
there's no problem in my opinion. It also seems to be quite
configurable via features/properties.

Basically, I consider NekoHTML "a customization" of an XML
parser (Xerces in this case) "that undestands tags that need
not be closed". But I've not extensively used it myself yet,
so I may be wrong.

[Igor Malinin]

Logged In: YES
user_id=346040

Uhm... I was not very clear. When I told about XML parser I
meant not traditional SAX/DOM, but a parser for
non-well-formed documents as described in a bug #899541.