Hi, As asked by Andreas, here's a quick (but I hope clear) explanation to tell why we forgot about the FeatureView.
What we wanted at first was a way to display feature attributes, one feature at a time. In the simplest case, the list of attribute would be guessed from the feature itself and would be displayed in a standard "key: value" view. We also wanted to allow user to define his own template in the case he knows what attributes to display. Using a FeatureView for that purpose wasn't possible for the following issues : - The AttributeStore has not been designed to guess the list of attributes from a feature, - The template that the user would have given to the FeatureView would have been applied to each AttributeStore record, ie. to each attribute. This means that it wouldn't be impossible to have custom templates for features. Regards, Pierre On Wed, May 26, 2010 at 4:36 PM, Pierre Giraud <[email protected]> wrote: > Hi folks, > > We worked on the FeatureBrowser one and there's a ticket [1] with > patch already open and ready for review. > Note that, after more reflexion, it appeared to be unnecessary to > create a FeatureView class. > Check out the corresponding sandbox [2] for a live example. > > Feedbacks appreciated. > > Pierre > > [1] http://trac.geoext.org/ticket/288 > [2] > http://dev.geoext.org/sandbox/camptocamp/extensions/geoext.ux/ux/FeatureBrowser/examples/featurebrowser.html > > On Thu, May 20, 2010 at 2:44 PM, Eric Lemoine > <[email protected]> wrote: >> Hi >> >> We at Camptocamp are considering implementing two new GeoExt >> components: FeatureView and FeatureBrowser. Presumably, FeatureView >> would be in "core" and FeatureBrowser in "extensions". >> >> FeatureView is a specific Ext.DataView for viewing information related >> to a feature. A FeatureView is configured with a feature or an >> AttributeStore (including a feature), and with an XTemplate, >> optionally. If no XTemplate is specified in the configuration, a >> default one is provided by the FeatureView. >> >> FeatureBrower is an Ext Panel for viewing a collection of features in >> pages, one feature per page. FeatureBrowser uses FeatureView >> internally. FeatureBrowser is configured with an array of >> AttributeStore's, or an array of features (or a FeatureStore) and an >> AttributeStore configuration object. FeatureBrowser can also receive >> an XTemplate, which it will pass to FeatureView. FeatureBrowser >> triggers "viewfeature" events when going from one page to another, >> this for example allows to highlight the feature on the map. >> >> See the screenshot attached to this email. The screenshot shows a >> popup with a FeatureBrowser containing two FeatureView's. Note that >> the popup isn't part of the components we're proposing here. >> >> What do people think? Do these components sound useful? >> >> Thanks for any feedback, >> >> -- >> Eric Lemoine >> >> Camptocamp France SAS >> Savoie Technolac, BP 352 >> 73377 Le Bourget du Lac, Cedex >> >> Tel : 00 33 4 79 44 44 96 >> Mail : [email protected] >> http://www.camptocamp.com >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://www.geoext.org/cgi-bin/mailman/listinfo/dev >> >> > > > > -- > Pierre GIRAUD > Géomaticien, Analyste > > Camptocamp France SAS > Savoie Technolac, BP 352 > 73377 Le Bourget du Lac, Cedex > > Tel : 00 33 4 79 44 44 93 > Mail : [email protected] > http://www.camptocamp.com > -- Pierre GIRAUD Géomaticien, Analyste Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac, Cedex Tel : 00 33 4 79 44 44 93 Mail : [email protected] http://www.camptocamp.com _______________________________________________ Dev mailing list [email protected] http://www.geoext.org/cgi-bin/mailman/listinfo/dev
