> > Anyways, I'm not against the separation, as we said the data directory > layout in not intended for direct manipulation, I'm more > concerned about a smooth upgrade path and a simple setup for > simple usages than about a particular data directory layout.
I am not against modeling the separation in the data directory as of now. But I am against adding the notion of a map into the backend picture right now. It increases scope and we have bigger fish to fry at the moment imho. As I see it the upgrade path will be pretty smooth: 1. adopt data dir structure proposed here 2. implement maps in the backend 3. add the maps directory to the data directory structure 4. on start provide an "import facility" which creates a default map as described above > > Cheers > Andrea > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ 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
