GRASS 6.3 Feature Plan: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
(modify Makefile system to support translated HTML pages)
(adding keywords to every grass command and script)
Line 38: Line 38:
* rewrite most of the g3d modules to fulfil the grass function naming convention --[[User:Huhabla|huhabla]] 20:47, 14 August 2006 (CEST)
* rewrite most of the g3d modules to fulfil the grass function naming convention --[[User:Huhabla|huhabla]] 20:47, 14 August 2006 (CEST)
* <del>rewrite of r.to.rast3, r.to.rast3elev, v.out.vtk and r.out.vtk to fulfil the grass function naming convention</del> --[[User:Huhabla|huhabla]] 20:47, 14 August 2006 (CEST)
* <del>rewrite of r.to.rast3, r.to.rast3elev, v.out.vtk and r.out.vtk to fulfil the grass function naming convention</del> --[[User:Huhabla|huhabla]] 20:47, 14 August 2006 (CEST)
* adding keywords to every grass command and script [http://grass.itc.it/pipermail/grass-dev/2006-August/025164.html]
** display commands
** database commands
** general commands
** gis commands
** imagery commands
** misc commands
** paint commands
** photo commands
** postscript commands
** raster commands
** raster3D commands
** vector commands


=== Finished ===
=== Finished ===

Revision as of 13:24, 19 August 2006

GRASS 6.3.x feature plan

About feature plan

To make GRASS releases more often and more predictable, here is GRASS next releases feature plan. This feature plan has to be filled by developers working on GRASS 6.3.

Basic principles:

  1. Add a short feature description, bug No., etc. what You want to see and what YOU will implement or fix in upcoming GRASS 6.3 to #TODO list. Sign it using four tildes ~~~~!
  2. If You work on it, and You think it will make to next release, MOVE to #In progress section.
  3. When You finish and commit Your work, MOVE it to #Finished section.

Warning After freeze start, You will not be able to commit any new features till freeze end. Only bugfixes and commits related to items listed in In progress section.

TODO

  • Make sqlite the default DB?
  • Create GRASS Addons SVN repository and really use GEM
  • drop d.m display manager (as now almost unmaintained; there is gis.m and/or a python based GUI)
  • raster maps: implement SQL based time series support
  • modify Makefile system to support translated HTML pages. Store translated HTML files in centralized directory with locale specific subdirs, file name is module name.

Wishes

  • Create 3D animation w nviz showing GRASS 3D coolness. MarisN 12:00, 4 August 2006 (CEST)
  • here are some examples to get inspired (apparently that's already possible):
  • Convince the users to use ParaView [1] for sophisticated animations --huhabla 20:47, 14 August 2006 (CEST)
    • (Add support for Paraview in GDAL/OGR or add GDAL/OGR support in ParaView to read directly data from GRASS) see diskussion

In progress

  • Database connection for v.out.vtk --huhabla 20:47, 14 August 2006 (CEST)
    • single column support for numerical data (int, float, double)
    • GRASSRGB column support
    • multiple column support for vector data
  • rewrite most of the g3d modules to fulfil the grass function naming convention --huhabla 20:47, 14 August 2006 (CEST)
  • rewrite of r.to.rast3, r.to.rast3elev, v.out.vtk and r.out.vtk to fulfil the grass function naming convention --huhabla 20:47, 14 August 2006 (CEST)
  • adding keywords to every grass command and script [2]
    • display commands
    • database commands
    • general commands
    • gis commands
    • imagery commands
    • misc commands
    • paint commands
    • photo commands
    • postscript commands
    • raster commands
    • raster3D commands
    • vector commands

Finished