I don't really have a strong opinion on where the webclient would be located in svn ( webclient in https://svn.osgeo.org/qgis/webclient vs. https://svn.osgeo.org/qgis/trunk/qgis/webgis_client).
The directory above would save some bandwidth for most people that compile the code, the directory below has better visibility. Don't know what the number of files is in the webclient. If there are lots of files, I'd tend to https://svn.osgeo.org/qgis/webclient, otherwise to https://svn.osgeo.org/qgis/trunk/qgis/webgis_client Regards, Marco Am Freitag, 1. April 2011, um 14.37:15 schrieb Paolo Cavallini: > Il giorno ven, 01/04/2011 alle 13.27 +0200, Andreas Neumann ha scritto: > > I think it makes sense to separate the two completely. Most QGIS > > > > desktop users won't care about a webgis client. And some QGIS Server > > users may want to run their own webgis viewer or use QGIS Server just as > > a regular WMS. > > Sorry to insist -I do not want to bother. We currently have many > functions that are of limited, specialized use. I think our current > approach (keep everything in one place, and leave to packagers the > choice of splitting packages) is more sane. > For instance, in Debian we have: > === > p libqgis-dev - Quantum GIS - development files > i A libqgis1.7.0 - Quantum GIS - shared libraries > i A python-qgis - Python bindings to Quantum GIS > i A python-qgis-common - Python bindings to Quantum GIS - > architecture-independent fi > i qgis - Geographic Information System (GIS) > p qgis-api-doc - Quantum GIS API documentation > i A qgis-common - Quantum GIS - architecture-independent data > i qgis-mapserver - Quantum GIS mapserver > i qgis-plugin-grass - GRASS plugin for Quantum GIS > i qgis-plugin-grass-common - GRASS plugin for Quantum GIS - > architecture-independent data > i A qgis-providers - collection of data providers to Quantum GIS > i A qgis-providers-common - collection of data providers to Quantum GIS > - architecture-i > p qgis-sqlanywhere1.7.0 - Quantum GIS sql anywhere plugin and provider > === > so most users will not install, e.g. qgis-sqlanywhere1.7.0, etc. > I think the same could apply to the webgis. > All the best. > > > It will be easy to install and configure, and hopefully well > > > > documented, though. > > > > But I doubt that it will satisfy everybody's need. > > > > Andreas > > > > On Fri, 01 Apr 2011 13:17:41 +0200, Paolo Cavallini wrote: > > > Il giorno ven, 01/04/2011 alle 13.11 +0200, Andreas Neumann ha > > > > > > scritto: > > >> Paolo, the qgis webclient, although it works with QGIS server, will > > >> not > > >> > > >> be delivered by default with QGIS. It will reside in a parallel > > >> repository, just like the QGIS documentation or the articles. > > >> > > >> Besides > > >> > > >> Jürgens work on the WMS server tab in the project properties it has > > >> > > >> no > > >> > > >> influence on QGIS desktop. So no need to hold back because of my > > >> webclient. > > >> > > >> User will need to check out qgis webclient manually. It will not be > > >> delivered together with QGIS. > > > > > > Why so? Wouldn't it be better (and simpler for users) to keep > > > everything > > > in one place? > > > All the best. -- Dr. Marco Hugentobler Sourcepole - Linux & Open Source Solutions Churerstrasse 22, CH-8808 Pfäffikon SZ, Switzerland marco.hugentob...@sourcepole.ch http://www.sourcepole.ch Technical Advisor QGIS Project Steering Committee _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
