[GRASS5] Zoom

[Radim Blazek]

On Monday 22 April 2002 10:40 pm, Carl Worth wrote:
>  > I would suggest:
>  > d.zoom -p : Click button one to pan center point
>  > d.zoom -w : Click-and-drag button one to zoom in
>  > d.zoom -u : Click button one to unzoom step-wise
>  >
>  > Should not be problem to call by user interface.
>
> I guess those would work. But, I would prefer naming the functionality
> "d.pan" rather than "d.zoom -p". I'm a big fan of making interfaces
> that actually name the functionality being provided.

I think that it is not question of name, but of duplicating
code and additional work. To maintaine 3 modules is more work than to
maintain one. If you look at d.zoom, d.pan, most of the code is (was)
identical or similar. Don't forget that you have also man pages,
links to manpages, and links from manpages to manpages ...

I thought, that it was general conclusion in grass list, that
we want to reduce the number of modules. In last months appeared also
new d.vect.area, d.vect.lines so that we have 3 modules for displaying 
vectors. So, what is the situation now?

There is one problem with modules with too many options: if some options
depend on other options, it is impossible (now) to generate automaticaly
GUI for such module (which would enable/disable options, depending on
others). It is possible to write interactive version, but again, it cannot
be used to generate appropriate GUI/XML. 
Glynn, I remember that you have once mentioned "groups of options" -
could it help here, do you have a conception for that or it was just idea?


Radim