Do we need to throw legend graphic into the mix here Justin? We have a few sections of code where an SLD is scanned to produce a graphic.
Jody Garnett On Thu, Jul 10, 2014 at 11:45 AM, Justin Deoliveira < [email protected]> wrote: > Hi all, > > I have been working on making GeoServer capable of storing styles natively > in alternate languages. The most obvious use case being a better > integration for the css styling extension. The work is worth a GSIP but I > wanted to post here to start some initial discussion before doing up the > first draft of the proposal. > > For the impatient the current state of the work can be found here: > > https://github.com/jdeolive/geoserver/compare/style-plug > > The approach is to create an extension point named "StyleHandler" (which > will replace the current "Styles.Handler" enum) that can parse, encode, and > validate styles. With the new extension point the task then becomes > updating all the bits around it. Which will require some changes to a few > different subsystems. > > *Catalog/Config* > > A couple of changes to StyleInfo: > > 1. An additional property: the style format/language identifier > 2. Changing the "SLDVersion" property to the more generic > "FormatVersion" property. > > *WMS* > > To support styles directly in a WMS request (via SLD or SLD_BODY) the idea > is to add an additional "STYLE_FORMAT" parameter to identifier the format. > In the implementation I have now i have continued to use SLD and SLD_BODY > parameters for the style content, even though in non SLD cases it is a > misnomer. We could add more generic parameters and make the SLD specific > ones an alias for them... what do folks prefer? > > *Web UI* > > What I have done thus far is simply add a format field to the style editor > page. When creating a new style the user can choose the style format. > > > https://www.evernote.com/shard/s222/sh/76cb558c-b7d4-457a-9f93-4281ff631d2f/88f76db60e5d93212fa5551a0e20cc0f > > In the interest of simplicity I thought it best to simply disable the drop > down when editing a style: > > > https://www.evernote.com/shard/s222/sh/fa4aace6-2e58-4c99-9000-27595e1f94b8/24c790ea34050cf7a5ce6361fe23f142 > > Rationale being that since style handlers might not support both parsing > and encoding, like the css module transforming the same style between > formats would be tricky. > > *Rest API* > > The final bit is the rest api. Nothing too exciting here except that now > folks will be able to upload files in different formats. > > That is about it... let me know what you think! > > -Justin > > -- > Justin Deoliveira > VP Engineering | Boundless <http://boundlessgeo.com/> > [email protected] > @boundlessgeo <http://twitter.com/boundlessgeo/> > > > > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
