Justin Deoliveira ha scritto:
> Question. Is everything under org.geoserver.web.wicket intended to be 
> totally generic? Or just any component used in more than once place? The 
> reason i ask is because browsing through the directory I see the class 
> "WorkspaceChoice", which makes me think that common widgets/controls for 
> the catalog will go under this structure.

Well, isn't the UI meant to deal mostly with catalog configuration?
All the models I can think of that would go in wicket/models are
wrappers of catalog elements as well.
Whilst there are a few classes that can be totally generic, I think
most of them would be GeoServer and catalog specific, and there
are classes that can be in a gray area.
For example, a bbox editor, is that catalog specific?
We'd use it only in catalog pages so far, but maybe some new demo page
could use it as well. But the same could happen to a layer chooser.
What I mean is, it's usage is specific today, but tomorrow a demo
or a new service configuration could make the component used outside
of the catalog "space".
So I would have trouble deciding where to put each component.
If we follow you lead we'd start having a component/model/converter
set of packages under wicket, but also one under data, and maybe
some under the services? And what triggers the creation of a new
subset of those packages?
I don't really have good grips on this kind of classification,
and would probably put everything in that generic package until
some sort of evident pattern emerges, but if you feel strongly
about it, we could go for it anyways, and I'll ask you where
to put components/modules/converters I'm not sure about.

Cheers
Andrea



-- 
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to