https://sourceforge.net/p/csseditor/feature-requests/1/2004-01-06T15:45:20ZRecent changes to 1: Define profiles declaratively2004-01-06T15:45:20Z2004-01-06T15:45:20ZChristopher Lenzhttps://sourceforge.net/u/cell/https://sourceforge.net0b1dad07d1e38bffd4786f27a875e12e1c8d79a0

<div class="markdown_content"><p>Currently, CSS profile plugged in as extensions must be<br /> defined in Code implementing the<br /> net.sourceforge.csseditor.IProfile interface, which has<br /> methods such as getProperties() and<br /> getPropertyInfo(String propertyName). The current<br /> implementations of this interface for CSS 1 and CSS 2<br /> basically only provide data and not anything in terms<br /> of actual logic.</p> <p>There should be a simple way to "implement" profiles in<br /> the form of XML files. Such an XML file should have<br /> information about:<br /> - properties<br /> - at-keywords<br /> - pseudo-classes and -elements</p> <p>This should also include descriptions that could be<br /> displayed in tooltips etc.</p> <p>For properties, the definition should include their<br /> applicability (media groups, element types, ...) as<br /> well as the allowed values. Pretty much a conversion of<br /> the property definitions in the CSS spec as described<br /> in <a href="http://www.w3.org/TR/CSS21/about.html#property-defs." rel="nofollow">http://www.w3.org/TR/CSS21/about.html#property-defs.</a></p></div>