<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Il 09/03/2018 10:24 PM, Christopher Gray ha scritto:<br>
    <blockquote type="cite"
cite="mid:CAPWG4dUVWRopnKHxKwRu2UHmCeFvk7RVeoFnOmBK7W4VghEiYQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <div dir="ltr"><span style="color:rgb(0,0,0)">After reading the
          explanations here, I found some more details about QWC2 in a
          Google Doc here: </span>
        <div style="color:rgb(0,0,0)"><a
href="https://docs.google.com/document/d/1QHF7c3Z1yv-Y86fiAAb2I02fP6BysQXO5nd4y-qaR8A/edit"
            target="_blank" moz-do-not-send="true">https://docs.google.com/document/d/1QHF7c3Z1yv-Y86fiAAb2I02fP6BysQXO5nd4y-qaR8A/edit</a></div>
        <div style="color:rgb(0,0,0)"><br>
        </div>
        <div style="color:rgb(0,0,0)">It says "The code should be part
          of the main QGIS github project page at <a
            href="https://github.com/qgis/" target="_blank"
            moz-do-not-send="true">https://github.com/qgis/</a> - the
          group active around QWC II decides who will get commit rights
          to this repository", which suggests if any version were to be
          official, it would be QWC2. Further, the document explains the
          desire to have clear integration between QGIS projects and the
          QWC2 interface.</div>
        <div style="color:rgb(0,0,0)"><br>
        </div>
        <div style="color:rgb(0,0,0)">Assuming this is the case, I would
          suggest a change to the website that references QWC2 and
          perhaps briefly explains the difference between the
          "Components" and "demo". <br clear="all">
          <div>
            <div dir="ltr"
              class="gmail-m_-135525064540346935gmail_signature"><br>
            </div>
          </div>
          If QWC2 is not so closely tied to QGIS, it could be very
          useful to briefly list options like QWC2, EQWC, Lizmap,
          GeoServer, GISQuick, etc. It seems hard to grasp and navigate
          all of the options up front... and it is not necessarily a GIS
          learning curve so much as a work-flow and program setup
          learning curve. </div>
        <div style="color:rgb(0,0,0)"><br>
        </div>
        <div style="color:rgb(0,0,0)"><br>
        </div>
      </div>
    </blockquote>
    I agree, a clear explanation would be useful. Feel free to suggest
    one.<br>
    All the best.<br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Paolo Cavallini - <a class="moz-txt-link-abbreviated" href="http://www.faunalia.eu">www.faunalia.eu</a>
QGIS & PostGIS courses: <a class="moz-txt-link-freetext" href="http://www.faunalia.eu/training.html">http://www.faunalia.eu/training.html</a>
<a class="moz-txt-link-freetext" href="https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis">https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis</a></pre>
  </body>
</html>