[Community] PrimaGIS 0.6 : is better ergonomy for ZCO Datastore possible ?
kai.hanninen at mbconcert.fi
Wed Sep 27 23:59:16 EEST 2006
Gérard Vidal wrote:
> Hi Kai
>> You're correct that the current "Data source" selection interface is
>> far from optimal. It simply lists all the feature types from all data
>> stores configured within the gis_tool and this can get really big
>> when the number of data stores grows.
>> The biggest problem is the editing form and I'd be willing to put some
>> effort into including an improvement for that before the 0.6 release.
>> Would this be something you'd like to help us with? It wouldn't have
>> to be necessarily coding. Good ideas, mock-ups, etc would also be
> OK you can count on me (not for coding of course) but for ideas (not
> necesseraly good :-[ ) and comments no problem !
>> I could put together a custom widget for the data source selection
>> that would handle the large number of data stores / feature types in a
>> better and more consistent way (possibly using some AJAX callbacks
>> that would pull in stuff on-demand or something). I'm open to
>> suggestions on how such a widget should look and operate.
> I don(t know if it is possible I just push some ideas.
> My first proposal should be to list zcos instead of layers and when a
> ZCO is choosen the list of available layers appears. (Something like
> what you get when software companies want you to give your country /
> state/town I cannot remember where I saw such a process)
> The hierachical approach will simplify the interface
This was simple enough for me to manage with my currently limited
resources. I put in a new widget that uses two <select> fields to show
only the relevant feature types for a given data store. This is in
MochiKit) to operate on the DOM.
Could you try this out and see if it helps you. If it's useful I can
polish it up a bit and add i18n etc.
Kai Hänninen +358-50-558-7935
Software engineer www.mbconcert.fi
MB Concert Ky kai.hanninen at mbconcert.fi
More information about the Community