nviz_cmd - was Re: [GRASS-dev] Re: [GRASS GIS] #392: backport G_is_c_null_value() to devbr6

Martin Landa landa.martin at gmail.com
Fri Dec 19 13:23:35 EST 2008


Hi,

2008/12/19 Paul Kelly <paul-grass at stjohnspoint.co.uk>:

[...]

>> group of modules
>>
>> nviz
>>
>> in GRASS6:
>>
>> nviz_cmd becomes nviz.cmd
>
> Well as I said above I feel it is a bad idea to make any last minute changes
> now if we're intending to tag 6.4.0RC1 imminently, so I'd vote for keeping
> everything as-is for 6.4 now.

OK, on the other side, I don't see any reason why to postpone the decision.

>> in GRASS7:
>>
>> nviz_cmd becomes nviz.cmd
>> d.nviz becomes nviz.fly
>
> My comments before about the name nviz being inherently meaningless still
> stand here. Yes it's instantly recognisable to GRASS users as the 3-D
> visualisation command, similarly to r.in.gdal being instantly recognisable
> as an import command. But the reasons Markus gave for renaming r.in.gdal to
> r.import (which I eventually came round to agreeing with) stand here also
> for renaming nviz_cmd to something more meaningful. I think we need to sit
> back and look at the functionality and the GUI integration and come up with
> a nice meaningful name for 7.x.

Sorry for possible misunderstanding, would be option to name a new
group of modules as '3d' instead of 'nviz'. In the result:

3d.cmd
3d.fly

?

Martin

-- 
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *


More information about the grass-dev mailing list