<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Alessandro,</p>
Thanks a lot for these detailed insights!<br>
<br>
<div class="moz-cite-prefix">On 04/17/2018 12:44 PM, Alessandro
Pasotti wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAL5Q672_gYVm2KtFoAFB3UWnv8NWuQT+Sema_TN5n2o44S9GqQ@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">Hi,<br>
<br>
</div>
<div class="gmail_extra">I'll try to address all concerns in a
single mail (what a challenge!)<br>
<br>
</div>
<div class="gmail_extra">First I would like to say that
everybody has access to a different set of "average/typical
users" and I cannot claim any statistical relevance to the
group of users I've been in touch with.<br>
<br>
</div>
<div class="gmail_extra">But the user's feedback that I've got
so far is that the Value-Relation widget (V-RW) is easier to
use and to understand: its scope it's limited to how data are
entered and viewed and does not depend on a
model-project-level constraint (the Relation-Reference R-RW
does).<br>
<br>
</div>
<div class="gmail_extra">Those (statistically insignificant)
users were quite emotional and ready to fight to keep V-RW
live and healthy :)<br>
</div>
</div>
</blockquote>
<br>
May they be statistically significant or not, the opinion counts and
is important to be considered. I assume, the main requirement here
is an easy setup (i.e. directly in the widget, no roundtrip via
project properties). As long as this is not implemented, the value
relation widget will stay alive.<br>
<br>
Let's focus on what other requirements are potential show-stoppers
and then decide if it's worth moving on.<br>
<br>
<blockquote type="cite"
cite="mid:CAL5Q672_gYVm2KtFoAFB3UWnv8NWuQT+Sema_TN5n2o44S9GqQ@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">Code-wise I totally agree that the two
widgets could share more logic and options, but given the
intricacies of the attr-table and widgets-forms logic this is
not trivial at all, and it's not in scope with this QEP 116
enhancement.<br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Coming to the new functionalities
introduced by QEP 116, the way they will be implemented will
make them easily reusable in the context of the R-RW:<br>
<br>
</div>
<div class="gmail_extra">- form scope context with geometry and
attributes<br>
</div>
<div class="gmail_extra">- form scope available in both the form
and the attribute table<br>
</div>
</div>
</blockquote>
<br>
And that's what I really like about it!<br>
<br>
<blockquote type="cite"
cite="mid:CAL5Q672_gYVm2KtFoAFB3UWnv8NWuQT+Sema_TN5n2o44S9GqQ@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Of course existing bugs and glitches in
the V-RW workflow will be fixed on the way when they not imply
rewriting the whole QGIS core ;)<br>
<br>
<div class="gmail_extra">What could be considered here, is to
add a second goal to the campaign for making the new
features available to the R-RW too, what do you think?<br>
</div>
</div>
</div>
</blockquote>
<br>
As written in my previous email, please do !!<br>
<br>
<blockquote type="cite"
cite="mid:CAL5Q672_gYVm2KtFoAFB3UWnv8NWuQT+Sema_TN5n2o44S9GqQ@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_extra">
<div class="gmail_extra"><br>
</div>
</div>
But even without this additional goal, I still think that this
QEP (which is not a complete refactoring of the whole
form/attr-table *-R widgets) is a step forward and in the
direction of a future better integration of the existing
*-R-widgets.<br>
<div class="gmail_extra"><br>
</div>
<br>
<div class="gmail_extra">That's why I'm joining Nyall's call
to contribute and make this a reality.<br>
</div>
<br>
<br>
</div>
<div class="gmail_extra">Also note that some of Règis
requirements, like a geographical dynamic filter will be
possible with an expression like:<br>
<br>
... AND contains(buffer( $current_form_geometry, 10),
$geometry)<br>
</div>
</div>
</blockquote>
<br>
... and even better with the R-R widget where it will be possible to
dynamically adjust the range from the form (thinking of advanced
search functionality in a popup or so), its new infrastructure
allows for some very cool additions which I hope to be able to
implement soon ;)<br>
<br>
Please keep up the good work and let us know what's required to
bring this to relation reference too!<br>
<br>
Best regards<br>
Matthias<br>
<br>
<blockquote type="cite"
cite="mid:CAL5Q672_gYVm2KtFoAFB3UWnv8NWuQT+Sema_TN5n2o44S9GqQ@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">note that this expression is the one
used to filter the values in the related layer, and it will
have access to the geometry of the feature currently being
edited/added in the form (or table row) as well as to the form
(row) values, so:<br>
<br>
</div>
<div class="gmail_extra">- $current_form_geometry = the geometry
of the feature currently being edited in the form<br>
</div>
<div class="gmail_extra">- $geometry = the geometry of the
related layer that is being filtered to get the list of values
for the combo/search/etc...<br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Also note that the V-RW is already used
in the identify results panel (and form of course).<br>
<br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Cheers<br>
<br>
-- <br>
<div class="m_-8678018939614742598gmail_signature"
data-smartmail="gmail_signature">Alessandro Pasotti<br>
w3: <a href="http://www.itopen.it" target="_blank"
moz-do-not-send="true">www.itopen.it</a></div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
QGIS-Developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:QGIS-Developer@lists.osgeo.org">QGIS-Developer@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div class="moz-signature">
<title></title>
<div class="moz-signature"> <span style="text-align: left;
color: #000000; font-family: 'Verdana', sans-serif;
font-size: 10pt">Matthias Kuhn</span><br>
<a href="mailto:matthias@opengis.ch" target="_blank"> <span
style="text-align: left; color: #000000; font-family:
'Verdana', sans-serif; font-size: 8pt">matthias@opengis.ch</span>
</a><br>
<span style="text-align: left; color: #000000; font-family:
'Verdana', sans-serif; font-size: 8pt"><a
href="tel:+41764356763">+41 (0)76 435 67 63</a></span><br>
<div> <a href="http://www.opengis.ch"> <img
moz-do-not-send="false"
src="cid:part4.595D162D.BA70B31A@opengis.ch"
alt="OPENGIS.ch Logo" height="80" width="200"></a> </div>
</div>
</div>
</div>
</body>
</html>