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

[Huidae Cho]

I'm not talking about the current structure. Yes, the modules are the CLI
right now and the GUI calls the CLI modules internally. What I'm saying is
that it would great if we could separate the logic and CLI and put the
logic in plugins and let the CLI and GUI calls the logic. GUI would be
independent on CLI and directly call the logic plugin. Here, I'm saying
plugin because each module could be implemented as a mod_*.so just like
Apache modules. Then we could implement a CLI environment that can load
mod_*.so as needed dynamically. In the same way, other programs can call
mod_*.so without creating a separate process for individual modules.

Actually, even now, GRASS libs are called directly from GDAL for handling
raster/vector maps.



On Fri, May 2, 2014 at 9:58 AM, Moritz Lennert <mlennert at club.worldonline.be
> wrote:

> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20140502/e66017ae/attachment.html>