[GeoNetwork-devel] Design choice XForms GUI: need advice

Hi Evert and Simon (and list),

The following is something that will affect the course of our project
and I'd like to get your advise on this:

Currently when we build our XForms editor, we do it in 2 steps (from a
MVC point of view):

1) Create the controls (input fields, etc) for each possible field,
based on a filled template document. They will determine the 'view': the
looks of the form on the screen.

2) Create the 'Model': load the metadatadocument (is a GN representation
of it) and all other instances (snippets (static now), labels and help)
and rules.

We have a challenge with step 1: our form will only show fields that are
present in the filled template document that we base our form on. Any
field that is not in there will not be visible in our end form.

This has advantages and disadvantages:
Advantage: the template document acts as a configuration document for
the form and the owner (Evert) has full control over what to show and
what not. Creating a different form for a different group of users only
requires a new document template to be made.

Disadvantage: every possible field that you want the form to be able to
show (deep into the GML bit even) you need to fill in the template form
(and then also: only once). That can be quite a lot of work.

Does such a fully filled template exist at all (for testing purposes
maybe)? If so, could you point us to where we can find it?

Is this approach acceptable for a first phase?

We can also go down a more difficult path and that is to make the XForm
more generic. This might be possible (not sure), but has the risk of
putting more 'smartness' in the XForm and therefore maybe slowing it
down. The customisation (by Evert) would then be at the level of the
XForms instead of the template document. This option will definitely
slow down the project but has advantages as well.

We'd like to hear your opinions on this ASAP.

Thanks, Roald

--
Roald de Wit
Software Engineer
roald.dewit@anonymised.com

Commercial Support for Open Source GIS Software
http://lisasoft.com/LISAsoft/SupportedProducts/

Hi Roald,

On Jun 11, 2008, at 3:07 AM, Roald de Wit wrote:

Hi Evert and Simon (and list),

1) Create the controls (input fields, etc) for each possible field,
based on a filled template document. They will determine the 'view': the
looks of the form on the screen.

We have a challenge with step 1: our form will only show fields that are
present in the filled template document that we base our form on. Any
field that is not in there will not be visible in our end form.

Would it be an option to propose a similar concept as currently used in the advanced editor? There the first level empty elements (like in the current advanced editor) that could used could be shown and be expanded based on template snippets (using + and - signs or so).

Normally, a user wouldn't see those extra fields, but only when explicitly required, he could do something like selecting a checkbox to actually show them.

Ciao,
Jeroen

Thanks, Roald

--
Roald de Wit
Software Engineer
roald.dewit@anonymised.com

Commercial Support for Open Source GIS Software
http://lisasoft.com/LISAsoft/SupportedProducts/

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork