Define profiles declaratively

Christopher Lenz — Tue, 06 Jan 2004 15:45:20 -0000

Currently, CSS profile plugged in as extensions must be
defined in Code implementing the
net.sourceforge.csseditor.IProfile interface, which has
methods such as getProperties() and
getPropertyInfo(String propertyName). The current
implementations of this interface for CSS 1 and CSS 2
basically only provide data and not anything in terms
of actual logic.

There should be a simple way to "implement" profiles in
the form of XML files. Such an XML file should have
information about:
- properties
- at-keywords
- pseudo-classes and -elements

This should also include descriptions that could be
displayed in tooltips etc.

For properties, the definition should include their
applicability (media groups, element types, ...) as
well as the allowed values. Pretty much a conversion of
the property definitions in the CSS spec as described
in http://www.w3.org/TR/CSS21/about.html#property-defs.

Recent changes to 1: Define profiles declaratively

Define profiles declaratively