Hi David, the order is simply determined by the order the plugins finish loading their resources (GetCapabilities response for WMS, scripts for Google).
If we care about the order (do we? - I don't), it should be possible to do a final reordering when all sources have finished loading, based on the order they appear in the config. Would that work for you? If so, and if we really care, I'd ticket that. -Andreas. On Jul 21, 2010, at 23:58 , David Winslow wrote: > So, I am mostly done with the work I've been doing on producing > GXP-style viewer configurations in the Django app, and persisting > background layer visibility while I'm at it. However, I noticed > something a bit odd: on the current demo site, the wms server for the > GeoNode comes up as the default layer source in the "Add Layers" dialog, > but in my branch, it is the Google Layer listing instead. > > Possibly also relevant is the fact that in my working dir, the choice in > the dropdown for the WMS layer reads "My GeoServer WMS" while that on > the live site is labelled "capra". Maybe this affects sorting, maybe it > is an artifact of the ConfigManager still in place on the demo site. > > with that background in mind: > * Do we care? Is it okay to have that dialog default to a listing of > Google layers? Seems undesirable to me. > * If yes, how do we fix it? What needs to happen in the config to > change that ordering? Does GXP even allow us to specify this ordering? > > thanks. > > -- > David Winslow > OpenGeo - http://opengeo.org/ -- Andreas Hocevar OpenGeo - http://opengeo.org/ Expert service straight from the developers.
