[GRASS-dev] GUI toolkits

[Glynn Clements]

Trevor Wiens wrote:

> As you may recall this question was asked some time ago and the general
> feeling was that a separate GRASS GUI was desirable. The main reasons
> stated for that as I recall were:

[snip]

> 2. GRASS is primarily written in C so if we want to use a compiled
> language, C would be the natural choice.

This is only relevant if the GUI actually links to GRASS libraries,
which isn't necessarily a good idea. The design of the GRASS libraries
doesn't really lend itself to persistent applications.

Integrating C and C++ code isn't particularly hard; one of the key
design goals of C++ was compatibility with C. The primary objection to
C++ is that it tends to be much harder to "dip into" C++ code than C
code, even if you're equally fluent in both languages.

-- 
Glynn Clements <glynn at gclements.plus.com>