Hi Justin,
I found the following proposal:
http://geoserver.org/display/GEOS/GSIP+23+-+Wicket+UI#GSIP23-WicketUI-proposal
There is a MapPage concept that you have mentioned before, it is got six
"likes" (i.e. approved) and its exactly what I need :)
I've went through the code and I can see some basic implementation, so I'm
thinking about fork the project and complete it. Is this is a good idea?
Also, if yes, should I code against master branch or 2.2?
thanks Alex
On Wed, Sep 5, 2012 at 12:59 AM, Justin Deoliveira <jdeol...@opengeo.org>wrote:
> Hi Alex,
>
> Some comments inline.
>
> On Tue, Sep 4, 2012 at 12:32 AM, Alexandre Djioev <dji...@gmail.com>wrote:
>
>> Hi Justin,
>>
>> thanks for replay. My original plan was to write a plugin, but I end up
>> moving to many files in and realized it is a horrible way to go.
>>
>> So I have following choices:
>>
>> 1) Make Catalog pluggable. sounds like clean but hard solution, I'm
>> worried about time limit...
>> 2) Fork GeoServer code, make so that LayerGroup can nest another
>> LayerGroup. To be honest I'm confused about this functionality, LayerGroup
>> imo is just one layer that can be viewed say in OL as a layer. How can you
>> view a LayerGroup with multiple LayerGroups inside? Well, I can flat them
>> up I guess, but then users might find it confusing. Also we have fields
>> like BBOX for LayerGroups that are not part of Themes.
>>
> Indeed. The layer group concept (even a nested one) will only get you so
> far. Perhaps nested workspaces are more what you need.
>
> 3) Form GeoServer, implement themes by coding into Catalog/extend
>> Workspace. Can do, but then I have my modified version of GS that is hard
>> to upgrade. Unless of course themes will be merged with GS (I'll will be
>> happy to contribute).
>
>
> Well it depends if your functionality requires modification to the
> geoserver core, or can be encapsulated entirely in a plugin. IF it requires
> core changes then indeed upgrades will be hard. In this case your best bet
> is to get it approved as a contribution and added directly into the
> GeoServer core. We have a proposal process for such changes.
>
> If all the additions can be encapsulated in a plugin then upgrades will
> generally be easy. All you need to worry about are api changes to the
> various extension point interfaces you implement. The question here is
> whether all the extension points you will need exist.
>
> In terms of the theme data structure you could maintain it outside of the
> catalog, maybe in an embedded database or something like that. Your theme
> object could make use of LayerGroup since you do have a requirement for
> ordering. But at the same time could also support sub themes.
>
> How will clients interact with a theme? For instance should a client be
> able to do a WMS request against a theme? Do you just intend to make the
> them structure available in some sort of custom service?
>
>>
>> Justin, can you advice me with the following step, I feel a bit lost :)
>
>
>> Thanks Alex
>>
>>
>>
>> On Tue, Sep 4, 2012 at 2:38 AM, Justin Deoliveira
>> <jdeol...@opengeo.org>wrote:
>>
>>> Hi Alexandre,
>>>
>>> Yeah, this thread probably makes more sense on geoserver-devel. That
>>> said I will comment a bit here. I don't; think you will find exactly what
>>> you need in terms of extension points in the CAtalog api. The api is
>>> designed to be extensible in terms of STore and Resource classes but there
>>> are not really any implementations outside of what is in the core catalog.
>>> So I imagine there are a number of bits missing to make it truly pluggable.
>>>
>>> It sounds like layer groups is close to what you want but not exactly in
>>> that currently a layer group can't contain another layer group (although
>>> that would be a nice addition imo). Also layer groups are
>>> just syntactic sugar for WMS and don't apply to any other services.
>>>
>>> The concept you are asking for is similar to the idea of a Map which I
>>> had before for which there is a catalog interface for but it remains
>>> unused.
>>>
>>> Anyways, I can see possibilities. Either you add a new type of object to
>>> the core catalog... which will be a significant modification to the core or
>>> you try to slightly improve on things that are there like LayerGroup or
>>> perhaps even the Workspace interface.
>>>
>>> -Justin
>>>
>>> On Mon, Sep 3, 2012 at 4:09 AM, Alexandre Djioev <dji...@gmail.com>wrote:
>>>
>>>> Hi everyone,
>>>>
>>>> I'm trying to write a theme plugin for GeoServer - geoserver interface
>>>> where you can maintain layers as a tree structure, similar to files
>>>> (layers) and directories (themes).
>>>>
>>>> 1) Themes can be inside of themes (just like directories)
>>>> 2) Same layer can be found in several themes.
>>>> 3) Order of layers inside of a theme is important.
>>>>
>>>> Then I want to create some rest interface that returns this tree as a
>>>> json, so that a client can pick it up and render it. Last part looks
>>>> quite straightforward but I'm confused with the first one.
>>>> I can see some similarity with LayerGroups so I want something like
>>>> this:
>>>>
>>>> LayerThemeInfo lt = catalog.getFactory().createLayerTheme();
>>>> lt.setName( "Theme1" );
>>>> lt.getLayers().add( catalog.getLayerByName(
>>>> "sf:PrimitiveGeoFeature" ) );
>>>> lt.getLayers().add( catalog.getLayerByName(
>>>> "sf:AggregateGeoFeature" ) );
>>>> catalog.add( lt );
>>>>
>>>> Question: how can I extend Catalog, any extension points? Or maybe any
>>>> examples that I can have a look at? Also I don't want to invent a bicycle,
>>>> maybe there is already a solution fot this problem?
>>>>
>>>> Thanks Alex
>>>>
>>>> P.S. Should I move this topic to geoserver-dev?
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Live Security Virtual Conference
>>>> Exclusive live event will cover all the ways today's security and
>>>> threat landscape has changed and how IT managers can respond.
>>>> Discussions
>>>> will include endpoint security, mobile security and the latest in
>>>> malware
>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>> _______________________________________________
>>>> Geoserver-users mailing list
>>>> Geoserver-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>>
>>>>
>>>
>>>
>>> --
>>> Justin Deoliveira
>>> OpenGeo - http://opengeo.org
>>> Enterprise support for open source geospatial.
>>>
>>>
>>
>>
>> --
>> Cheers, Alex
>>
>
>
>
> --
> Justin Deoliveira
> OpenGeo - http://opengeo.org
> Enterprise support for open source geospatial.
>
>
--
Cheers, Alex
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
