<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Vedran, <br>
</p>
<p>thanks for raising this proposals<br>
</p>
<div class="moz-cite-prefix">On 24/04/2025 10:12, Vedran Stojnović
via QGIS-PSC wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAL9iSMGSaEqn3tSB_10CfPEZjW=iu0NM8WOdw8nUSK+frd26Vw@mail.gmail.com">
<div class="moz-text-html" lang="x-unicode">
<div dir="ltr">
<div>Hi PSC,</div>
<div><br>
</div>
<div>since I didn't get any response in QGIS Developer mailing
list, I am forwarding this to PSC mailing list, I consider
this a PSC decision and would love to hear at least some
feedback.</div>
<div><br>
</div>
</div>
</div>
</blockquote>
<p>PSC is not driving features from above, we rely on the
contributors and help in finding consensus when it doesn't happen
by itsel, or help in funding un-fundable changes. </p>
<p>If your changes are small features, did you already file a
feature request in Github and discuss it there ? Good pratice is
to open feature requests, then trigger discussions in the
developper's list for implementation help or further discussion. <br>
If you propose a massive change breaking UI, API, user workflows,
you must write down an enhancement proposal (QEP) in the dedicated
repository. Contributors will ask for implementation details,
migration plans etc.. there. </p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAL9iSMGSaEqn3tSB_10CfPEZjW=iu0NM8WOdw8nUSK+frd26Vw@mail.gmail.com">
<div class="moz-text-html" lang="x-unicode">
<div dir="ltr">
<div>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr">
<div>[..]<br>
</div>
<div>What I'm thinking of? Few examples:</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<p>Let's discuss a closed list of items. Migrating to QGIS4.0 is not
the moment of breaking all things. This transition is a major
change, but not a rebuild from the ground up. <br>
</p>
<blockquote type="cite"
cite="mid:CAL9iSMGSaEqn3tSB_10CfPEZjW=iu0NM8WOdw8nUSK+frd26Vw@mail.gmail.com">
<div class="moz-text-html" lang="x-unicode">
<div dir="ltr">
<div>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr">
<div>1) change some default settings for QGIS Desktop</div>
<div>- e.g. left double click on layer to open attribute
table for vector layers instead of opening properties
(no other software that I used in my life opens
properties on left double click), for raster layers it
could do a zoom extents on raster (logic to open image
on double click)</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<p>This is a legitimate feature request, rather minimal, and that
could be driven by a setting. I don't agree that opening the
attribute table is the only action that makes sense. Inkscape
triggers a layer rename (F2) for instance. opening the attribute
table for massive table is probably something you don't want to
happen to easily. Not sure you will get a consensus for the
default action, but having settings for this makes sense to me. <br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAL9iSMGSaEqn3tSB_10CfPEZjW=iu0NM8WOdw8nUSK+frd26Vw@mail.gmail.com">
<div class="moz-text-html" lang="x-unicode">
<div dir="ltr">
<div>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr">
<div><br>
</div>
<div>2) change name(s) of some native algorithms - I
find some of them confusing</div>
<div>- e.g. <a class="moz-txt-link-rfc2396E" href="native:polygonize">"native:polygonize"</a> uses lines
(mathematically defined lines - which only have start
pt and end pt) and creates polygons, but we have also
<a class="moz-txt-link-rfc2396E" href="native:linestopolygons">"native:linestopolygons"</a> which by description also
uses lines and converts them to polygons, but actually
expects polylines (polygons drawn as line layer), and
then we have <a class="moz-txt-link-freetext" href="gdal:polygonize">gdal:polygonize</a> which converts raster to
vector polygons</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<p><br>
</p>
<p>I think that can be done directly in Pull request, as long as we
have common naming rules. I'm not sure if thess already exists,
maybe we should write minimal rules first. Could you take this
action ?<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAL9iSMGSaEqn3tSB_10CfPEZjW=iu0NM8WOdw8nUSK+frd26Vw@mail.gmail.com">
<div class="moz-text-html" lang="x-unicode">
<div dir="ltr">
<div>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr">
<div>3) remove deprecated functions from expression
calculator</div>
<div><br>
</div>
<div>4) change logic in some algorithms/expressions</div>
- e.g. "point_n" function is 1-indexed instead of
0-indexed (QGIS/issues/29100)</div>
</div>
</div>
</div>
</div>
</blockquote>
<p>Agreed. (this doesn't mean this will happen, someone has to take
the cleanup action)<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAL9iSMGSaEqn3tSB_10CfPEZjW=iu0NM8WOdw8nUSK+frd26Vw@mail.gmail.com">
<div class="moz-text-html" lang="x-unicode">
<div dir="ltr">
<div>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr">
<div><br>
</div>
<div>...</div>
<div><br>
</div>
<div>I'm sure that other developers/contributors/users
have their own ideas...</div>
<div><br>
</div>
<div>So I would love to see something like this as type
of process similar to QEP - where a user/contributor
could propose a change, and than it can be commented
from everyone, but in the end should be voted from
core developers or by PSC:</div>
<div>- does it make sense </div>
<div>- is it doable or too complicated and so on...</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
feature requests are the way to go. Let's address things in separate
issues / threads / pull request. <br>
We are not obliged to push all changes in QGIS4, QGIS has a fast
release cycle exactly for this. <br>
<blockquote type="cite"
cite="mid:CAL9iSMGSaEqn3tSB_10CfPEZjW=iu0NM8WOdw8nUSK+frd26Vw@mail.gmail.com">
<div class="moz-text-html" lang="x-unicode">
<div dir="ltr">
<div>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr">
<div><br>
</div>
<div>We're kind of short on time, but I believe that
this can be done until October.</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
Are you saying you have ressources to code things yourself? <br>
<p><br>
</p>
<p>All the best</p>
<p>Régis<br>
</p>
<blockquote type="cite"
cite="mid:CAL9iSMGSaEqn3tSB_10CfPEZjW=iu0NM8WOdw8nUSK+frd26Vw@mail.gmail.com">
<div class="moz-text-html" lang="x-unicode">
<div dir="ltr">
<div>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr">
<div><br>
</div>
</div>
</div>
<span class="gmail_signature_prefix">-- </span><br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">Srdačan pozdrav / Kind regards,
<div>Vedran Stojnović.</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<div class="moz-text-plain" wrap="true" graphical-quote="true"
style="font-family: -moz-fixed; font-size: 12px;"
lang="x-western">
<pre wrap="" class="moz-quote-pre">_______________________________________________
QGIS-PSC mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:QGIS-PSC@lists.osgeo.org" moz-do-not-send="true">QGIS-PSC@lists.osgeo.org</a>
<a class="moz-txt-link-freetext"
href="https://lists.osgeo.org/mailman/listinfo/qgis-psc"
moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a>
</pre>
</div>
</blockquote>
<div id="grammalecte_menu_main_button_shadow_host"
style="width: 0px; height: 0px;"></div>
</body>
</html>