[GRASS-dev] WxPython front-end to ps.map
mlennert at club.worldonline.be
Fri Feb 9 03:33:32 EST 2007
On 09/02/07 04:46, Michael Barton wrote:
> Thematic maps and charts seem like they should be a vector option rather
> than separate layers. This could be done with GUI code without needing to
> combine the d.* modules. However, if we did true vector rendering for
> primitives, we'd want the same quality in thematic maps and charts.
> I'm not sure if this makes any considered recoding any easier or not. But
> the upshot is that vector primitives, thematic maps, and charts seem the
> best candidates for some reworking of the C code for display. Most of the
> other d.* effects can work with current code or be replaced by GUI generated
> graphics if we want. As you point out, this is more work at the GUI coding
> end. I'm not sure which will take more effort.
I'm not sure I completely understand what you mean here, and as we are
still (albeit slowly, I admit) working on a C replacement of
d.vect.thematic, it would be good to know what we should take into account.
I do have to agree with Glynn, though, in that we should try to not code
two parallel and different ways of drawing things, one for the command
line and one for the GUI. I am afraid that this would almost inevitably
lead to inconsistencies and definitely to twice the work load trying to
keep everything up to date. IMHO, GRASS's strength is its modularity and
the GUI should be on top of that, not replace it.
More information about the grass-dev