GeoServer : GSIP 97 - Promote CSS Styling module from Community to Extension
This page last changed on Jun 11, 2013 by email@example.com.
Promote CSS Styling module to extension.
Under Discussion, In Progress, Completed, Rejected, Deferred
The CSS styling extension has lived in the community modules area for a few years now. As clients of developers are starting to request a supported version it is time to promote to extension status.
Minimally, the CSS module can simply be refactored to use the ``org.geoserver.extension`` package instead of ``org.geoserver.community``. However, the GeoSolutions team is offering some time to improve the level of integration in the extension.
On the backend, integration could be improved by adding support for non-SLD styles to GeoServer's Catalog API.
On the frontend, the CSS styling extension adds a separate page for editing CSS styles and does not update the normal style editing page. A user attempting to edit a CSS style through the normal style editing workflow will be presented with the auto-generated SLD and any changes to this will be overwritten the next time the CSS is modified. The CSS editing workflow should be unified with SLD, and a few extra additions to the CSS editing page (a submit button that does not navigate away from the editor page, tools for configuring the layer associations for the style, a preview map) would be equally applicable to SLD styles and could be integrated into the main style workflow.
The GeoServer developer manual sets forth the following requirements before a module may be promoted to extension status:
In modifying the catalog to support non-SLD styles some changes to the on-disk format will be required. I believe this can be accomplished such that only configurations actually using CSS styles will encounter backwards compatibility problems.
|Document generated by Confluence on May 14, 2014 23:00|