Community
Participate
Working Groups
From EclipseXSLT bug report: I would like to have different color on HTML and HTML related elements. Maybe the ability to add new "Content type" selections and set color of each individually?
Changing this to XML project and would like to expand a little on the requirement. It would be really, really cool if it was possible to change the colour of an xml element based on its namespace. For example, if all xsl elements could be coloured differently to the rest of the document, it would be much easier to read an XSL file. Is this possible?
Might be possible courtesy of bug 224209 in the next release.
moving to wtp.inc.xsl
doug this is something we might have to do by extending the LineStyleProviders to recognize at least the XSL Namespaced elements and providing different coloring for them. I don't know if the XML source editor has plans to allow for the XML editor to have namespace specific coloring or not? Nitin is this something you guys are looking at for 3.1?
Tentatively adding this for 1.0M3, if time permits may move it up in the schedule.
Here is what I see needs to be done to implement this: * Add an XSL Editor Preference Page * Under the XSL Editor preference Page add the Syntax Highlighting * Provide a Syntax Highlighting preferences for xsl:elements and attributes. Base this off of the existing XML colors. * Implement a LineStyleProvider for the XSL Editor. Additional items that can be done: * Move the XSL Templates so that they appear under the Editor menu option.
This is now implemented. The default for XSL is to be bold, but this can be changed by the User through the new XSL Syntax Coloring preference page. There still needs to be some more tweaking done to the code, and little bit more refactoring to allow easier maintenance, as well as listening for property change events, but it should work as designed. I'll open separate bugs for the other features and refactorings. There is also a new LineStyleProvider test as well.
No Editor menu has been implemented yet, should we do this to follow the same pattern as the XML files?
mass update to 3.1 target due to movement from wtp incubator to wtp source editing lost the original milestones.
