| Summary: | XHTML as XML | ||
|---|---|---|---|
| Product: | [WebTools] WTP Source Editing | Reporter: | Patrick Schriner <pschriner> |
| Component: | wst.html | Assignee: | David Williams <david_williams> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | for.work.things, thatnitind |
| Version: | 0.7 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Patrick Schriner
I'll have to sort-through all these cases ... but, you know, the way its supposed to work in 3.1 and WTP is that you associate the file extension to the XML Content Type (on the Eclipse content type preferences page). And, our XML Editor is declared to be for the XML Content Type. This definitly works for the XML editor and completely "new" extensions (e.g. myFile.myType), but admit I have not tried with .html, since it is assigned to another type there might be something "getting in the way". (but, I thought, if you used XHTML in an HTML file, you should still get all the XML functionality ... is there something missing? Did you want tabletree page, for example? Plus, you are correct about the validtor ... that's another bug, bug 86385. The HTML editor is missing the "design" tab & editor view (at least for me?) (I guess that´s what you call tabletree page ;-)). Interesting idea. Does this boil down to editor filename/content-type associations at this point? I tried this again with a Ganymede JEE release; It is possible to associate the XML editor to HTML & HTM file type extensions (and it is fairly trivial). If you use the XML editor, you have all the features I requested - source, tree and validation. Therefor I would recommend closing this bug as fixed? > Therefor I would recommend closing this bug as fixed?
Sounds good to me.
|