[Mapbender-dev] [gsoc09] Admininterface ideas

Christoph Baudson christoph.baudson at wheregroup.com
Wed May 27 10:55:25 EDT 2009

Personally, I like the object centric view, because it saves a lot of 
forms in the long run. It will make it easier to develop new 
administration modules.

I'm not quite sure how to handle the dependencies between objects, for 
example WFS and WFS conf. Creating a new WFS conf would be under the WFS 
tab, but for editing an existing WFS conf, you would need another tab 
"WFS conf" (you don't necessarily know which WFS the conf is associated 
with). I'm not sure if this is intuitive.

We would have to find out the work flows for each task and try to 
optimize them with any of the two models. For example, take setting up a 
spatial request environment: You need to load a WFS, create a WFS conf, 
associate the WFS conf with a GUI, Load a WMS, and associate the WMS 
with the WFS conf (in order to see what you can query).

It would be nice if such a use case would be possible without severe 


karim@ schrieb:
> Dear List,
> I met with Christoph yesterday to discuss what the new admininterface for mapbender could look like.
> This is a summary of our discussion.
> I created two nonfunctional sketches to illustrate two ideas  
> A) A more "function centric" view (see [1])
>  This is similar to the admin2_.., so I won't explain much.
>  The entries here are roughly grouped by functionality.
>  After opening the desired function, the objects to operate on
>  are selected.
> B) A more "object centric" view (see [2])
>  This is what I came up with before digging into the depth of the mapbender code.
>  The top menu (Users | WMS | WFS | GUI | Options)  could be tabs, 
>  that select different modules.  In the example "Users" is open 
>  (because it is very simple) to show the basic idea.
>  WMS, WFS, GUI and  Users all act similar in that there is a list of them,
>  and each entry needs to be configured.
>  The list on the left lists the entries, lets a user apply a simple filter on the name of the entry and 
>  links to the "add new <entry>".
>  Clicking on a listentry opens it's configuration pages. In my example
>  setting the username, password, etc. is done underneath the "core data"-tab
>  and users rights could be assigned underneath the "rights"-tab.
>  The desired object is selected first and the functionality exposed afterwards.
> These are just rough sketches,  and now I am looking for ideas, questions and criticism
> from you to find out where I should be going. 
> Seven, I recall you expressing interest in the userinterface design, I am very open to suggestions.
> Regards,
> Karim
> [1] http://karim.malhas.de/gsoc09/sketchA.html
> [2] http://karim.malhas.de/gsoc09/sketchB.xml
> ------------------------------------------------------------------------
> _______________________________________________
> Mapbender_dev mailing list
> Mapbender_dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapbender_dev



W h e r e G r o u p GmbH & Co. KG

Siemensstraße 8
53121 Bonn

Christoph Baudson

Fon: +49 (0)228 / 90 90 38 - 15
Fax: +49 (0)228 / 90 90 38 - 11
christoph.baudson at wheregroup.com
Amtsgericht Bonn, HRA 6788

WhereGroup Verwaltungs GmbH
vertreten durch:
Olaf Knopp, Peter Stamm

More information about the Mapbender_dev mailing list