David Winslow wrote:
> On Tue, 2009-04-07 at 10:08 +1000, Jody Garnett wrote:
>> Where are you at with this one David? It has been six days - are you
>> putting it to a vote? do you have enough feedback etc?
> 
> Yes, let's put it to a vote.  From last week's IRC meeting, I believe I
> have a +1 from aaime and simboss, +0 from jdeolive.  (Please correct me
> if I'm wrong.)
I am +1, although I would prefer the interface be renamed (which I will 
kindly point out might have helped Jody figure out better what the point 
is ;) )
> 
>> My own preference (collaborate at the geotools level) is too much work
>> even if the end result would be nice.
>>
>> Just as with the REST api I find the practice of voting to accept work
>> difficult when the work (and design decisions) are already made.
>> Indeed I find nothing on either page to help me understand what the
>> design is:
>> - http://geoserver.org/display/GEOS/GSIP+35+-+WMS+Decorations   (is
>> all about the short commings of the existing work)
>> - http://geoserver.org/display/GEOS/WMS+Decorations (is a bit more
>> about how to build and use the result)
>>
>> I am looking for how this facility integrates with the configuration
>> classes? are they configured at a Map level? Or turned on via a format
>> option or something? Are they set up once in code for the server and
>> visible on every request? You already note they need to be removed for
>> geowebcache...
> 
> The configuration is completely orthogonal to the org.geoserver.catalog
> classes, much as templates and permissions are.  Decoration layouts are
> defined in XML files, which can be referenced by name in a format option
> as described in both the GSIP and the wiki page.  These layouts are
> global; at present there is no association between layouts and any other
> configuration entity.
> 
> Disabling the feature is as simple as neglecting to define any layout
> files.
> 
>> Can this be used to package up the "watermark" functionaltiy in a cleaner 
>> form.
> 
> The existing watermark configuration is already interpreted as an extra
> 'static image' decoration which is appended to each layout.
> 
> --
> David Winslow
> OpenGeo - http://opengeo.org/
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel


-- 
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to