[GRASS-dev] Who wants GUI and who does not and why

[Huidae Cho]

I agree. grass-cli and grass-gui should be completely independent and at
the same level. They are simply two different UIs that directly depend on
grass-lib. The user wants either grass-cli & grass-lib or grass-gui &
grass-lib.

Now, my opinion is if we put analysis and modeling code in grass-lib,
grass-lib would be too big or, for some users, it would contain too much
irrelevant code if all they want is simply GIS operations. Very
field-specific code such as hydrology, remote sensing, ... should be
separated out from the grass-lib and put in another layer of the libraries.
grass-cli/gui will interact with that layer directly.

grass-lib <-> grass-plugins <-> grass-cli, grass-gui, other GISs: Full
analysis/modeling suite

grass-lib <-> other GISs: Simple GIS data manipulation very common in all
fields.

Regards,
Huidae


On Fri, May 2, 2014 at 4:32 AM, Rainer M Krug <Rainer at krugs.de> wrote:

> Luca Delucchi <lucadeluge at gmail.com> writes:
>
> > On 18 April 2014 11:15, Pietro <peter.zamb at gmail.com> wrote:
> >> Hi Vaclav,
> >>
> >> actually I'm a bit more extremist... :-)
> >>
> >> I would like to split GRASS in three main parts:
> >> - grass-lib
> >> - grass-cli
> >> - grass-gui
> >>
> >
> > I also like this idea...
>
> I think this would be a very good idea as it would make the whole GRASS
> ecosystem more transparent and easier (in my opinion) to maintain and to
> use certain aspects from different applications.
>
> Re functionality in the GUI:
>
> The question would be if the split is
>
> lib--cli--gui
>
> or
>
>    |--cli
> lib|
>    |--gui
>
> in other words, if the cli is just a non graphical UI or THE interface
> to the lib, through which the gui operates. I think the first design
> approach would be the better one.
>
> Cheers,
>
> Rainer
>
> >
> >>
> >> At least should be possible to build these parts separately, leaving
> >> the decision to split in several packages to the package maintainer of
> >> each distribution (Debian, Fedora, etc.).
> >>
> >
> > I think that someone is already doing something like this.
> > But I don't know more because I usually compile myself GRASS
> >
> >> Regards
> >>
> >> Pietro
> >>
>
> --
> Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
> Biology, UCT), Dipl. Phys. (Germany)
>
> Centre of Excellence for Invasion Biology
> Stellenbosch University
> South Africa
>
> Tel :       +33 - (0)9 53 10 27 44
> Cell:       +33 - (0)6 85 62 59 98
> Fax :       +33 - (0)9 58 10 27 44
>
> Fax (D):    +49 - (0)3 21 21 25 22 44
>
> email:      Rainer at krugs.de
>
> Skype:      RMkrug
>
> PGP: 0x0F52F982
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20140502/28c0f2eb/attachment.html>