Hi Horst
I also like to have the node tools in a pull-down menu.
Still I think the separation basic editing toolbar / advanced editing toolbar
makes sense because some advanced tools are probably used less frequently, so
user should have the possibility to show/hide this toolbar depending on
Hi,
On Mon, 15 Jun 2009 22:37:35 +0200
Agustin Lobo alobolis...@gmail.com wrote:
I'm a bit confused by the FAQ entry regarding
citation:
Quantum GIS Development Team (YEAR). GNU General Public License.
http://qgis.osgeo.org;
Should we just write the current year?
I guess it depends on
it is very good opportunity to create two repos for the same plugin. One for
stable and one for experimental purposes.
For those, who didn't enable experimental plugins,
how can we enable the experimental plugins in the qgis in order to fetch the
plugin from repo if the repo is tagged as
On Tue, 16 Jun 2009 08:31:13 +0200
Otto Dassau otto.das...@gmx.de wrote:
Hi,
On Mon, 15 Jun 2009 22:37:35 +0200
Agustin Lobo alobolis...@gmail.com wrote:
I'm a bit confused by the FAQ entry regarding
citation:
Quantum GIS Development Team (YEAR). GNU General Public License.
Hugentobler Marco wrote:
Hi Horst
I also like to have the node tools in a pull-down menu.
Still I think the separation basic editing toolbar / advanced editing toolbar
makes sense because some advanced tools are probably used less frequently, so
user should have the possibility to show/hide
Hi Agustin,
in your case, maybe the Geoinformatics article written by the current PSC
members for the QGIS 1.0 release in February this year can be used.
I added the link to the article on the wiki Journals page. It would be
great if more people can provide links to other articles about QGIS
Tuesday 16 of June 2009 08:47:06 Volkan Kepoglu napisał(a):
it is very good opportunity to create two repos for the same plugin. One for
stable and one for experimental purposes.
You can either create the two repos and recommend the unstable one only for
'experimenting' users, or put two
Well, I assume that the two plugins I posted will remain in the wild as they
are designed from a tester's point of view and from an educational point of
view.
I would say that plugins that are general enough to benifit ,majority of QGIS
users make it to the core. For the other SPECIALIZED
Just as I am going through a pseudo code exercise of release.py I see three
cases.
1. Current and previous stable versions VERSION
2. A Beta version is is being tested an on its way to stable. BETA
3. An unstable snapshot of the development trunk
For a community plugin repo I assume that multiple authors might be involved in
the development of a plugin
For the element... author_nameSomeone/author_name
Can this be a comman separated value.
I am thinking of automaticaly generating this from an AUTHORS.txt file
Also, is there an e-mail
Tuesday 16 of June 2009 15:18:37 Sampson, David napisał(a):
For a community plugin repo I assume that multiple authors might be involved
in the development of a plugin
For the element... author_nameSomeone/author_name
Can this be a comman separated value.
sure
I am thinking of
Tuesday 16 of June 2009 15:03:11 Sampson, David napisał(a):
Just as I am going through a pseudo code exercise of release.py I see three
cases.
1. Current and previous stable versions VERSION
2. A Beta version is is being tested an on its way to stable. BETA
I don't want to speak on behalf of the community, I just came across what I
figured would work for the central repo and kinda matches typical; open source
projects that facilitate the three options.
Cheers
-Original Message-
From: qgis-user-boun...@lists.osgeo.org
So I have posted a plugins.xml file that I thought might work base don
previous examples.
I double checked the version numbers and did have to make some changes
http://voxel.dl.sourceforge.net/sourceforge/qgiscommunitypl/plugins.xml
I tried using absolute links to the files residing in
For the record, this is the error that is returned from qgis
Error reading repository: Qgis Community plugin Repository
Couldn't parse output from the repository
Cheers
-Original Message-
From: qgis-user-boun...@lists.osgeo.org
[mailto:qgis-user-boun...@lists.osgeo.org] On Behalf
Tuesday 16 of June 2009 17:59:08 Sampson, David napisał(a):
For the record, this is the error that is returned from qgis
Error reading repository: Qgis Community plugin Repository
Couldn't parse output from the repository
Hi, this error is a bit mysterious. If I open the file with Kate
I plopped mine in the htdocs dir of OSGEO4W and it worked
After you log out of SourceForge or leave the project page for a length of time
the direct download links are forwarded to their HTML interface instead of a
direct download.
I am not sure if there is a way around this or not. I
Yes, I'm in the same case than Maning.
Agus
maning sambale wrote:
Documentation perhaps? I tried using
http://apps.sourceforge.net/trac/qgismetaedit/
But never, got past loading the example xmls, I am having difficulty editing.
I'm a newbie in metadata editing, normally I just create a simple
18 matches
Mail list logo
