[Qgis-developer] Form widgets: decouple widget type from "hidden" or not

[Andreas Neumann]

Hi Matthias,

I probably took a wrong timing for such a discussion. We should
re-discuss this again then 2.0 is out.

QGIS web client does not display different widgets or forms so far. But
we plan to add such functionality, starting from the simple ones ;-)

The GetProjectSettings command delivers widget type information but may
not yet provide all necessary details. I can later ask Marco to add
missing bits.

I know about the already crowded GUI situation. On the other hand, the
table also has its advantages - quick overview over everything and ease
of use.

Maybe the september meeting would be a good time to rediscuss the form
issues again. Jürgen will be there and Nathan will be there, hopefully
you as well.

I'll be patient and wait for version 2.1 ;-)

Andreas

Am 04.06.2013 18:05, schrieb Matthias Kuhn:
> Hi
> 
> If I understand correctly, you want to show a different form in QGIS 
> desktop and the QGIS web client.h
> I'm not familiar with the code that generates the forms for the web 
> client, but reading your question, I guess that it generates it's form 
> based on the definition made in the vector layer properties / field 
> tab. As far as I remember, there was no support for ui files or drag 
> and drop designed forms in the web client (unless this changed 
> meanwhile), so if you generate a drag and drop form and skip the field 
> you mentioned, does this not lead to the desired result?
> 
> There are a couple of other discussions or ideas related to this. One 
> being brought up by Jürgen IIRC, which involved being able to define 
> multiple form layouts for a layer which could then be used based on the 
> context, in which a form is being shown (e.g. feature identify, 
> attribute table => form view, embedded form and this list could be 
> expanded with web services, involved user etc.)
> The other discussion I remember was by Denis or Nathan (not sure) and 
> it's more about the organization of the fields tab in the layer 
> properties. My main concern about your idea is that it will add yet 
> another field to an already overly crowded table which defines the 
> representation of the fields. Instead of a table, there should be group 
> boxes which will make it a lot easier to manage the fields.
> 
> Under the hood, I've been writing a new API for the widgets which will 
> make maintenance for all the widgets a lot easier and providing custom 
> widgets should be straightforward (also from python). I'll integrate 
> this API into 2.1 but will probably not yet port the old widgets to the 
> new API but the relations widget will be based on the new API.
> Maybe webclient widgets could be ported to the same new API? I didn't 
> think about it yet, but it could be worth a thought. As mentioned, I 
> don't know the webclient code, so I'm not sure if this is feasible.
> 
> Matthias
> 
> On Die 04 Jun 2013 17:14:46 CEST, Andreas Neumann wrote:
>> Hi,
>>
>> I have projects where I want to define a widget type (for QGIS web
>> client projects) but want to hide the field in QGIS desktop. I know - it
>> sounds strange, but it is a requirement.
>>
>> I therefore want to discuss whether we could have a separate column next
>> to the WMS and WFS column, labeled "Desktop" with a checkbox that
>> defines if the field is visible in QGIS desktop or not.
>>
>> Then we could still define a widget type (for QGIS web client) but hide
>> the field in QGIS desktop. We could then remove the "Hidden" widget
>> type, which isn't a widget anyway.
>>
>> This is kind of similar to the "editable" status we introduced a couple
>> of weeks/months ago - where we initially had the separate "immutable"
>> widget type where only line input widgets were supported.
>>
>> Any thoughts?
>>
>> Thanks,
>> Andreas
>> _______________________________________________
>> Qgis-developer mailing list
>> Qgis-developer at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
> 
>