<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font face="Helvetica, Arial, sans-serif">Hi Andreas,</font></p>
<p><font face="Helvetica, Arial, sans-serif">thanks to you and to
Paolo and Vincent who also provided useful information to my
questions.</font></p>
<p><font face="Helvetica, Arial, sans-serif">It is now pretty clear
what's the status of the projects, and I hope this thread will
also help other people having to make a choice between the
different webclients alternatives, today.</font></p>
<p>My approach (if anyone is interested) will be to give Lizmap and
GIS.Lab a try as the feasible solutions right now for the
deployment environment I have, and will then try QWC II when it is
more mature.</p>
All the best to the development of QWC II, and of course to the
other projects, Lizmap and GIS.Lab. <br>
<br>
Thanks again.<br>
<br>
<div class="moz-cite-prefix">El 02/06/16 a las 02:49, Neumann,
Andreas escribió:<br>
</div>
<blockquote cite="mid:399452a6ab2b70865e0803f726c80770@carto.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>Hi again,</p>
<p>Adding some additional info regarding the QWC II project. It is
anticipated/planned to collaborate, if possible with the
MapStore2 project of the italian company "Geosolutions". They
have very similar goals than QWC II, so some code/components
could be shared or jointly developed. See <a
moz-do-not-send="true"
href="http://www.geo-solutions.it/blog/mapstore-2-modern-webmapping/"><a class="moz-txt-link-freetext" href="http://www.geo-solutions.it/blog/mapstore-2-modern-webmapping/">http://www.geo-solutions.it/blog/mapstore-2-modern-webmapping/</a></a> </p>
<p>Greetings,</p>
<p>Andreas</p>
<p>On 2016-06-02 08:11, Neumann, Andreas wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left:
#1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<p>Hi Daniel,</p>
<p>What you discovered/write below, is quite accurate.</p>
<p>As one of the authors and users of QGIS Web Client I I add
some comments.</p>
<p>QGIS Web Client 1 is technologically "end of life" (old ExtJS
version 3, OpenLayers 2) - also the code is not so nicely
structured. It will still receive some smaller updates,
though. For this reason we decided to rewrite QGIS Web Client
II from scratch, based on modern libraries (OpenLayers 3,
ReactJS) and a better, more modular update. You can find a
spec document (<a moz-do-not-send="true"
href="https://docs.google.com/document/d/1QHF7c3Z1yv-Y86fiAAb2I02fP6BysQXO5nd4y-qaR8A/edit?usp=sharing">https://docs.google.com/document/d/1QHF7c3Z1yv-Y86fiAAb2I02fP6BysQXO5nd4y-qaR8A/edit?usp=sharing</a>)
and a design study for the GUI interface (<a
moz-do-not-send="true"
href="https://drive.google.com/file/d/0B0h3PAH5uoY6UG82Y19BdW9IR0U/view?usp=sharing"><a class="moz-txt-link-freetext" href="https://drive.google.com/file/d/0B0h3PAH5uoY6UG82Y19BdW9IR0U/view?usp=sharing">https://drive.google.com/file/d/0B0h3PAH5uoY6UG82Y19BdW9IR0U/view?usp=sharing</a></a>).
QWC II will be fully responsive (one version for both desktop
and mobile) and it is planned for a later edition to get a
nice configuration and deployment plugin (inspired by the
Boundless Web App Builder). You can expect initial useful QWC
II versions in Q4 2016, but a lot of the additional
development will happen in 2017.</p>
<p>QGIS Web Client II will be financed by Swiss, Swedish and
German gov authorities. Development starts in early July and
LizMap is primarily developed and used in France and other
more southern countries (like Italy, Spain I think). But both
projects can be used, contributed and enhanced by anyone. Both
versions need a bit of OS/Server know-how to install, mainly
for the server part and middleware/micro services.</p>
<p>One bigger difference is, that Lizmap requires a middleware,
while QGIS web client does not (but should be enhanced by some
microservices (serverside scripts), such as for searching).
Currently, LizMap has more features than QGIS Web Client I
(specifically for editing/attribute table display), but I
think that QGIS web client II will catch up on that. So there
is some "friendly competition" between the two projects and
both contribute to QGIS server enhancements.</p>
<p>So, if you need a lot of the LizMap features that QWC I
doesn't have now, I would go with that - but if you need a
basic viewer (query, print out, DXF export, etc.), with nice
search, you could give QWC I a try and then change to QWC II
in 2017. I believe that QWC II will have a very nice GUI (see
<a moz-do-not-send="true"
href="https://drive.google.com/file/d/0B0h3PAH5uoY6UG82Y19BdW9IR0U/view?usp=sharing">https://drive.google.com/file/d/0B0h3PAH5uoY6UG82Y19BdW9IR0U/view?usp=sharing</a>) and
will be fully responsive. During 2017 we will also focus on
easy configuration/deployment. If you believe in QWC II, then
of course you will be invited to join on whatever level you
choose (specifiyng new features, financing, developing,
documenting, etc.) - once the initial QWC II version will be
in the QGIS github repository. The initial version will be
developed by Sourcepole in Switzerland, but later other
devs/companies are invited to join.</p>
<p>Please let me know if you have additional questions.</p>
<p>Greetings,<br>
Andreas</p>
<p>On 2016-06-02 00:38, Daniel Vicente Lühr Sierra wrote:</p>
<blockquote style="padding: 0 0.4em; border-left: #1010ff 2px
solid; margin: 0;">
<div class="pre" style="margin: 0; padding: 0; font-family:
monospace;"><span style="white-space: nowrap;">Hi all,</span><br>
<br>
<span style="white-space: nowrap;">(Please, I'm sorry if multiple copies of this message arrive to the list, I sent it first with out being subscribed and apparently it didn't get through)</span><br>
<br>
<span style="white-space: nowrap;">I am working on a couple projects which involve the implementation of</span><br>
<span style="white-space: nowrap;">small scale spatial data infrastructures (Spatial DB + GIS server + GIS</span><br>
<span style="white-space: nowrap;">webclient). I have good knowledge in C/C++ and Python development but my</span><br>
<span style="white-space: nowrap;">JavaScripts skills are "weak" to say the least.</span><br>
<br>
<span style="white-space: nowrap;">I have QGIS server working + a PostGIS enabled PostgreSQL DB, and the</span><br>
<span style="white-space: nowrap;">users (which are familiar with QGIS desktop) will develop map projects</span><br>
<span style="white-space: nowrap;">with QGIS desktop.</span><br>
<br>
<span style="white-space: nowrap;">Now, for the choice of a web-client I have found two alternatives which</span><br>
<span style="white-space: nowrap;">apparently work with QGIS server "in mind" (make use of its extensions,</span><br>
<span style="white-space: nowrap;">like print composer, etc.):</span><br>
<span style="white-space: nowrap;">* QGIS web client.</span><br>
<span style="white-space: nowrap;">* Lizmap web client.</span><br>
<br>
<span style="white-space: nowrap;">First, I would like to know if any or both projects are "officially"</span><br>
<span style="white-space: nowrap;">active (I understand by the timestamps in github that both are, but</span><br>
<span style="white-space: nowrap;">Lizmap looks more "lively"). Also, I read somewhere in the list about a</span><br>
<span style="white-space: nowrap;">QGIS webclient "Mk. II" being worked on.</span><br>
<br>
<span style="white-space: nowrap;">Second, I would like to know if QGIS-webclient has support for WFS</span><br>
<span style="white-space: nowrap;">layers, or if it is easy to implement (OpenLayers should be able to</span><br>
<span style="white-space: nowrap;">handle WFS, but I don't know if that functionality has been implemented in the webclient).</span><br>
<br>
<span style="white-space: nowrap;">Finaly, just by reading the documentation (I haven't tested Lizmap,</span><br>
<span style="white-space: nowrap;">yet), it looks like Lizmap has more features (and more modern) than QGIS</span><br>
<span style="white-space: nowrap;">web client, like a workaround to include the base layer in a printed</span><br>
<span style="white-space: nowrap;">copy of the map, WFS-"ready", links to media files, portable</span><br>
<span style="white-space: nowrap;">devices-friendly, embedded user access control, animation support for</span><br>
<span style="white-space: nowrap;">temporal vector layers, and others, at the expense of a slighltly more</span><br>
<span style="white-space: nowrap;">complex way of generating the up of and FTP server) project output (requires the use of a</span><br>
<span style="white-space: nowrap;">plugin and optionally the set).</span><br>
<span style="white-space: nowrap;">I would like to read opinions of anyone who has tried both clients and</span><br>
<span style="white-space: nowrap;">had a chance to compare them.</span><br>
<br>
<span style="white-space: nowrap;">Any insight in these matters is highly appreciated.</span><br>
<br>
Thanks</div>
</blockquote>
<p> </p>
<div> </div>
<!-- html ignored --><br>
<div class="pre" style="margin: 0; padding: 0; font-family:
monospace">_______________________________________________<br>
Qgis-user mailing list<br>
<a moz-do-not-send="true"
href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a><br>
List info: <a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>
Unsubscribe: <a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a></div>
</blockquote>
<p> </p>
<div> </div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel Vicente Lühr Sierra
IEEE Member
IEEE Student Branch Counselor - Universidad Austral de Chile
</pre>
</body>
</html>