[csseditor-devel] [ csseditor-Feature Requests-871727 ] Define profiles declaratively

[SourceForge.net <no...@so...>]

Feature Requests item #871727, was opened at 2004-01-06 16:45
Message generated for change (Settings changed) made by cell
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=616966&aid=871727&group_id=97094

Category: Profiles
Group: Release 0.1.0
Status: Open
Priority: 5
Submitted By: Christopher Lenz (cell)
Assigned to: Christopher Lenz (cell)
>Summary: Define profiles declaratively

Initial Comment:
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.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=616966&aid=871727&group_id=97094