Roald, can you please move the widgets you created for the Catalog example from lib/ to examples/catalog? Because those widgets (I looked at SelectLayerFromContext and SaveContext, and there are also some xsl for which the same might apply) do not look like they are generic enough to be in lib, neither are they registered in config.xsd.
Thanks! Andreas. Roald de Wit wrote: > Hi Markus et al, > > As a start to get our catalog example in MB, i've uploaded a nearly > working stripped down version to the trunk (r3860). > > One can type in keywords in the 'Search for layers' section and choose a > service type. After searching the result list gets filled (replaced in > this case, since it's prefilled with a test result list). > > Once you click on 'add this layer' (+), it should be added to the main > context and update the map. For one reason or another the model doesn't > seem to get updated now. Don't use the (i) button please: it is supposed > to show metadata, but doesn't work now. > > The process in short: > - Search & conversion of results to a context document > (CatalogSearchForm widget) > - Add a found layer to the main context (SelectLayerFromContext) > > When you look at the SelectLayerFromContext widget, you'll see that it > effectively does nothing more than: > - having a modified copy of LayerControl.xsl > - have one method in the .js file that copies a layer to the main > context. > For a future version you can imagine to have LayerControl take care of > all of this in one widget. > > I presume that your biggest challenge at the moment will be to parse a > GetCapabilities document and convert it into an OWS Context. > > Tomorrow I'll cleanup the catalog example and fix the bugs. Please have > a look at it and tell me what you think. > > Greetings, Roald > > On Tue, 2008-02-19 at 15:13 +1100, Cameron Shorter wrote: > >> In the IRC meeting today, we discussed: >> 1. Putting out a 1.5rc2 in approx 3 weeks >> 2. Incorporating LISAsoft's catalog example into the codebase (moved >> from sandbox) >> 3. Deprecating OWSExplorer and contenxtEditor examples, as the >> functionality has been moved into LISAsoft's catalog example. >> 4. Markus Innerbner has volunteered to help with the Catalog example. >> >> Roald, >> Could you please outline what is required to move the Catalog from the >> sandbox into the 1_5 branch and the trunk. >> I'd like to add the capability to process (in order of priority) >> 1. WMS GetCapabilities >> 2. WFS GetCapabilities >> 3. WMC >> 4. Geonetwork Catalog query >> We need to explain to Markus what is required here. >> >> I assume we will need an EBRIM catalog and I've asked Cubewerx if they >> can stand one up for us. (as per the CGDIIP project we developed) >> >> --- >> >> Here is a quick summary of differences between OWSExplorer (old), >> contextEditor (old) and catalog (new) examples. >> >> Old: >> Capability queries of the numerous services (WMS, WFS, Catalog) are put >> into numerous XML models. There are then NUMEROUS pick widgets, one for >> each model, which allow you to pick a layer and put it into a target >> Context doc. >> >> New: >> Queries of services are converted directly into a Context document. Then >> we have ONE pick widget which selects a layer for the target Context. >> > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
