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

[Moritz Lennert]

On 02/05/14 14:29, Huidae Cho wrote:
> 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.
>

I don't think I understand: there is no such thing as grass-lib that can 
be called from either a grass-cli _or_ a grass-gui. The GUI actually 
calls grass modules. And these modules _are_ the CLI. And as many 
discussions have shown before, GRASS libs should not be called from 
anything else but GRASS modules.

Moritz