[qgis-qwc2] Status check qwc2

[Karl Magnus Jönsson]

Thanks for a really fast answer. I've come up with to more questions:

·         Invit did some work on the client for redlining. There is still need for extend the server API to render this for printing. I suppose it's not in the plans for this fall. Is it much work to do? And who can do it?

·         Would it be possible to use the one request for each layer approach without having to rebuild the whole client?

Karl-Magnus Jönsson | Gis-Utvecklare
Geografisk information
Miljö- och samhällsbyggnadsförvaltningen
Kristianstads kommun
Besöksadress: Västra Storgatan 12
Postadress: 291 80 Kristianstad


Från: qgis-qwc2 [mailto:qgis-qwc2-bounces at lists.osgeo.org] För Sandro Mani
Skickat: den 24 augusti 2017 13:58
Till: qgis-qwc2 at lists.osgeo.org
Ämne: Re: [qgis-qwc2] Status check qwc2


Hi

On 24.08.2017 13:45, Karl Magnus Jönsson wrote:
Hi all!
We are about to decide what our next step for QWC2 will be. It would be valuable knowing what other people planning, doing and using the project. I have a few questions:

·         Is there any plans for development in the near future and what is the focus then?
We at Sourcepole will be doing some development this fall focusing on various topics, among the most interesting ones perhaps stuff like editing, importing external WMS layers, visualizing height profiles.


·         Is there anyone got an public web client in production or testing to get inspired how to configure?
I suppose Kanton Zug has a good example: https://services.geo.zg.ch/qwc2


·         Our approach to get good performance in our previous clients is to seed and cache requests for the layers in the map. In qwc2 every change in layer visibility or transparency results in a new request that is hard to cache efficient. I suppose that is an intended behavior. How are you thinking about getting good performance and user experience?
I suppose the alternative is be to have one WMS request for each layer instead of one request for all layers, which is easier to cache but performs worse if no cache is available.


·         Another concern is how to customize without interfering too much with the code. For example if we want to develop an alternative layer tree widget. Could we just add our module and turn off the present without destroying it's functionality? Is the code enough flexible and modular? Maybe a tricky question to answer. But the intention from the beginning was to have a flexible and modular client.
The codebase is modular, see [1], components are self-contained (as far as it makes sense) and can be individually activated/deactivated/replaced.

Hope this helps
Sandro

[1] https://github.com/qgis/qwc2/tree/master/QWC2Components/plugins
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-qwc2/attachments/20170824/c98d27d0/attachment-0001.html>