Yes, indeed QGIS is looking better with every
release. But I personally still appreciate the
GIS Manager, too.
From what I have seen, it would be a trivial
amount of extra work to enable an extension to register
itself in GIS Manager and QGIS. I don't think
it necessary to drop one in favour of the other -- yet.
Still the basic question remains:
Where best to sort new commands into existing menu hierachies?
Best,
Benjamin.
----- Originalnachricht -----
Von: Paolo Cavallini <cavallini@faunalia.it>
Datum: Donnerstag, 28. April 2005 9:56 am
Betreff: Re: [GRASS5] GRASS 6 extension manager
That's very good news. Thanks for this.
IMHO, it is not useful to work much on the tcl/tk GUI, as the new
road goes
toward qgis as a frontend; far better to start directly form this.
I have
seen what Radim has done recently, and it improves substantially
the
usability. See http://wiki.qgis.org/qgiswik
All the best.
pc
At 09:39, giovedì 28 aprile 2005, benducke@compuserve.de has
probably written:
> - how are we going to make new commands available in the
> GIS manager?
> Should the extension author be able to register them
> in any of GIS manager's menus?
> Or would it be better to have a menu 'Extensions' under
> which every extension registers its commands?
--
Paolo Cavallini
cavallini@faunalia.it www.faunalia.it www.faunalia.com
Piazza Garibaldi 5 - 56025 Pontedera (PI), Italy Tel: (+39)348-
3801953
At 10:08, giovedì 28 aprile 2005, benducke@compuserve.de has probably written:
Yes, indeed QGIS is looking better with every
release. But I personally still appreciate the
GIS Manager, too.
From what I have seen, it would be a trivial
amount of extra work to enable an extension to register
itself in GIS Manager and QGIS. I don't think
it necessary to drop one in favour of the other -- yet.
Still the basic question remains:
Where best to sort new commands into existing menu hierachies?
Where best to sort new commands into existing menu hierachies?
I think in its own extensions menu. When it is common for people to have
12+ extensions installed we can think about merging into the main menu
structure.
Not sure if I like a permanent "Extensions" menu or if it is better to
create it the first time it is needed.
For GPL-compatible stuff it is always nice to merge new modules into
the GRASS CVS if they are well written & useful so that everyone can use
it (better tested); it won't die if the host website/author loses
interest; and it "automatically" gets updates and fixes. Even obscure
stuff can be interesting to try out and get into.
But I fully accept people will want to write stuff only for themselves,
use non-GPL modules (eg r.cva, v.in.dwg), or use the extension system as
a test bed for new moduules they write.
I'm not familiar with tcl/tk-programming. but isn't it possible to just have
one extensionsbutton wich can be used to hide or unhide a bar with
extensionbuttons?
Marco
---------------------------------
Marco Lechner
dienstlich:
Institut fur Physische Geographie
Uni Freiburg
Werderring 4
79085 Freiburg
Fon 0761 / 203-3548
Mail marco.lechner@geographie.uni-freiburg.de
Where best to sort new commands into existing menu hierachies?
I think in its own extensions menu. When it is common for people to have
12+ extensions installed we can think about merging into the main menu
structure.
Not sure if I like a permanent "Extensions" menu or if it is better to
create it the first time it is needed.
For GPL-compatible stuff it is always nice to merge new modules into
the GRASS CVS if they are well written & useful so that everyone can use
it (better tested); it won't die if the host website/author loses
interest; and it "automatically" gets updates and fixes. Even obscure
stuff can be interesting to try out and get into.
But I fully accept people will want to write stuff only for themselves,
use non-GPL modules (eg r.cva, v.in.dwg), or use the extension system as
a test bed for new moduules they write.