© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
(In reply to Jeff Griffiths (:canuckistani) from comment #3)
> If we do this, are we considering doing it for html view source as well? It
> would be great if the syntax highlighting matched the user's theme settings.
That would be my assumption: we would likely transition to the same (read-only) editor-like thing (most likely our source editor widget) for all file types, including HTML, and highlighting, etc. would be based on whatever that editor does for different file types.
The current HTML view source tool is not easily extensible for other file types at all. It's a special mode of Gecko's HTML parser, so there's no obvious way to just "enable" JS, etc. support. Something would need to parse the JS, emit tags for highlighting, etc. which editors already know how to do.
One problem we'd have to contend with is that the current HTML view source is able to handle very large documents efficiently because of its design. Some people (at least bz, IIRC) would be sad if the new approach was slow for these cases.
Some day this could also tie into our plans for a resources view in the toolbox, in which case it could be a true editor, not just read-only.