CSS Support
As of late '03, the Standard Template object includes (very) limited support for cascading style sheets. Specifically, it will embed a text/css block at the start of each page that includes specifications for background color and font color, size, and family attributes specified in the template settings. This has generally proven sufficient for a large number of kinds of pages, but is insufficiently flexible for more advanced sites.
More flexible CSS support could be introduced with the following changes, roughly in priority order:
- Option (in StandardTemplate) to link to external css url or object, which would override the style settings in the template object. [Done - 031219]
- Option (in StandardTemplate) to view the css block that would be generated by the current template settings. This will aid in the transition to external style sheets.
- Support for
text/css mime type in DispatchServlet. [Done - 031219]
- Support in StandardTemplateWebView for rendering
text/css [Done - 031219]
- Should ensure that
If-Modified-Since header is handled properly
- Add class names (or ids) to HTML tags rendered by the wiki interpreter, as well as HTML rendered by other objects. This will allow custom stylesheets to tweak the appearance of output from different objects.
- Look for or design CSS editor tool. Text editing (or drag-and-drop) will be sufficient initially, but eventually we will want something easier and more robust.
- A minimal approach would be allow construction of a list of CSS elements, guided by spec options
- Convert StandardTemplate to use XSL for structural elements
Notes:
- Can we plan for media specification support? Do any browser actually support requesting alternate stylesheets for (e.g.) printing?
- A related feature would be to add options to the text object to allow selection of template and interpreter (for non-wiki interpreters)
|