+1 for all of the above.
I'd suggest to use just three categories for the plugins at this stage:
Vector, Raster and General, where General would contain things like Grass,
ManageR, GDALTools.
I agree. The first step could be just one level with the proposed
categories. The nested model was
On Wed, 2009-11-04 at 11:40 +0100, G. Allegri wrote:
+1 for all of the above.
I'd suggest to use just three categories for the plugins at this stage:
Vector, Raster and General, where General would contain things like Grass,
ManageR, GDALTools.
I agree. The first step could be just one
Do you prefer at the bottom? Why? Usually their located in the principal
toolbar, as they're core functionalities for a gis, not service
utilities...
2009/11/4 Νίκος Αλεξανδρής nikos.alexand...@felis.uni-freiburg.de
On Wed, 2009-11-04 at 11:40 +0100, G. Allegri wrote:
+1 for all of the
On Wed, 2009-11-04 at 13:17 +0100, G. Allegri wrote:
Do you prefer at the bottom? Why? Usually their located in the
principal toolbar, as they're core functionalities for a gis, not
service utilities...
Hmm... yes. I just wanted to show the group-box. I was to lazy to edit
more and put it on
Ok :) thanks anyway for the mock
2009/11/4 Νίκος Αλεξανδρής nikos.alexand...@felis.uni-freiburg.de
On Wed, 2009-11-04 at 13:17 +0100, G. Allegri wrote:
Do you prefer at the bottom? Why? Usually their located in the
principal toolbar, as they're core functionalities for a gis, not
service
On Tue, 2009-11-03 at 22:55 +0100, G. Allegri wrote:
Hi all.
In these days I was watching my qgis plugins toolbar growin' and
growin'... That's good, it means a lot of good code is being written,
but I was wondering if it's the time to consider organizing the
plugins under common
Hi all.
In these days I was watching my qgis plugins toolbar growin' and
growin'... That's good, it means a lot of good code is being written,
but I was wondering if it's the time to consider organizing the
plugins under common task/feature/etc groups. It is a common structure
in many GIS
Nikos, I didn't notice your suggestion. Good to know that it's not an
isolated idea :)
My two cents.
In general I feel confortable with a nested model. We could provide a
first top-level grouping based on the qgis layer type the plugin
operates on, i.e. raster and vector. We can further subdivide
On Wed, 2009-11-04 at 00:14 +0100, G. Allegri wrote:
Nikos, I didn't notice your suggestion. Good to know that it's not an
isolated idea :)
My two cents.
In general I feel confortable with a nested model. We could provide a
first top-level grouping based on the qgis layer type the plugin
