Justin Deoliveira wrote:
>> If possible I would like to add a user interface requirement to 
>> extensions; I understand that this sets a high bar for an extension 
>> but I think it is important that extensions be "product ready" to the 
>> same level we expect of geoserver modules.
> I disagree here. A UI is nice and often needed but there often cases 
> where a UI is unnecessary, like data store extensions where we do 
> fancy introspection to create the UI. With the new configuration and a 
> java bean only philosophy for config objects i see this being more 
> popular.
That is an interesting and fair insight. If there is a fancy 
introspection system to make the contribution show up in the user 
interface that is fine by me. My focus here is on providing the user 
community some assurances as to what they can expect when something is 
dubbed as a "GeoServer extension" - I would like such things to be 
considered as additional as functionality that is "ready made" with the 
same attention to user experience as the core product.
> It also limits the scope of extensions imho. It limits them to things 
> we want to manage with the user interface... Like for instance it 
> might make sense for a certain extension to be configured via a rest 
> interface, or some other tool for that matter.
I am not sure I am comfortable with the generalities here - it seems you 
have a different level of contribution in mind than me. Perhaps we can 
offer some additional examples?
- I am thinking of large blocks of functionality like WPS; where I 
expect a user interface with the ability to manage "thread pool" 
settings for example.
- If you are talking about bundling up some additional DataStore that 
would be fine as well; and I agree the existing user interface would 
integrate them with the over all experience (that is the result of hard 
work done in anticipation of new DataStores; as such it would be easier 
to contribute additional DataStores..).
- I can also consider a tile cache, or a user track where a directory, 
or local hsql database will be created and/or managed - I would expect a 
configuration screen to perform some common admin tasks

What kind of contributions are you thinking of here Justin? What can be 
managed by just a REST API? Even a REST API (for say usage metrics) may 
have some interaction with the security system should it not?

Jody

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to