[GRASS-dev] Re: [GRASSGUI] qgis interface alike

[Jachym Cepicky]

hi,

Fwd: grass-dev

2007/3/26, William Kyngesburye <woklist at kyngchaos.com>:
> On Mar 26, 2007, at 4:27 AM, Jachym Cepicky wrote:
>
> > Hi,
> > costumized toolboxes (or module menus) are required by some users.
> > I suggest:
> >
> > 1) create $HOME/.grass directory as directory for user settings
> > 2) introduce another environment variabl $GISRCDIR (or similar)
> > 3) create $GISRCDIR/gui
> > 3) create $GISRCDIR/gui/custom
> > 4) custom menus could be simple text (csv) or XML files stored in
> > $GISRCDIR/gui/custom
> >
> > jachym
> >
> This gets into something I've been working on in the OSX build
> system.  A user configuration dir.  Before anyone sets anything that
> may be hard to change in the future, that $HOME/.grass (is that what
> you intend GISRCDIR to be?) should be configurable during the build,
> with appropriate defaults per platform.

yes,

jachym

>
> For OSX, that would be $HOME/Library/GRASS, at least.  I already have
> that in the OSX app build, and extended further by adding a GRASS
> version: $HOME/Library/GRASS/6.3.  Currently, user addon modules are
> stored here in "Modules".
>
> Linux platforms could be ~/.grass.  Windows would probably be
> different, though similar to OSX - somewhere in a user's home
> preferences/config dir, whatever that is.

ok
>
>
> > 2007/3/26, Moritz Lennert <mlennert at club.worldonline.be>:
> >> On 25/03/07 21:11, Daniel Calvelo wrote:
> >> > On 3/25/07, Michael Barton <michael.barton at asu.edu> wrote:
> >> GIS.
> >> >
> >> >> What might make more sense, in terms of flexibility, is to make
> >> selected
> >> >> GRASS commands also available (i.e., beyond the complex menu
> >> >> hierarchy) via
> >> >> a graphical 'tool box', as Trevor Wiens has suggested. Since
> >> trying to
> >> >> create a tool box for all 300+ commands would result in an
> >> interface as
> >> >> complicated as the menus themselves, maybe we could make a tool
> >> box that
> >> >> lets users 'plug in' or remove different command groups (e.g.,
> >> >> hydrology or
> >> >> terrain).
> >> >
> >> > That's what I meant by "Can the qgis plugin interface make sense
> >> as a
> >> > "quick toolbox" alongside the heavier wxgui?". My concern is
> >> whether
> >> > and how that would confuse users (especially newcomers) instead of
> >> > giving them a gentler learning curve.
> >> >
> >> > I like the idea of having task-related or thematic groupings.
> >> Another
> >> > fine idea from Radim is the building of the command icons with a
> >> very
> >> > simple symbology; that might help making those thematic toolboxes
> >> > friendlier.
> >>
> >> I think that having the possibility of easily creating customized
> >> toolboxes would be very helpful. This would allow us, for example, to
> >> create a specific toolbox for a course grouping only those
> >> commands you
> >> really need, with reasonable defaults, etc. This would be a very nice
> >> tool to ease entry into GRASS.
> >>
> >> So, yes, I like Daniel's idea (and Radim's work ;-) ), since with
> >> it the
> >> user only has to edit text files and add a few images to create
> >> such a
> >> customised tool.
> >>
>
> -----
> William Kyngesburye <kyngchaos at kyngchaos.com>
> http://www.kyngchaos.com/
>
> [Trillian]  What are you supposed to do WITH a maniacally depressed
> robot?
>
> [Marvin]  You think you have problems?  What are you supposed to do
> if you ARE a maniacally depressed robot?  No, don't try and answer,
> I'm 50,000 times more intelligent than you and even I don't know the
> answer...
>
> - HitchHiker's Guide to the Galaxy
>
>
>


-- 
Jachym Cepicky
e-mail: jachym.cepicky gmail com
URL: http://les-ejk.cz
GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub