GRASS 6.3 Feature Plan: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
(some cleanup)
Line 3: Line 3:


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.
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:
# 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 <nowiki>~~~~</nowiki>!
# If You work on it, and You think it will make to next release, '''MOVE''' to  ''[[#In progress]]'' section.
# When You finish and commit Your work, '''MOVE''' it to ''[[#Finished]]'' section.
'''''Warning''''' After [[GRASS_6.3_release_schedule|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 GRASS 6.3.0 ===
=== TODO GRASS 6.3.0 ===

Revision as of 10:20, 15 October 2007

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.

TODO GRASS 6.3.0

There is the release branch for 6.3.x, see details at CVS: tags and branches. A release branch is considered as "frozen", only bugfixes can be done.

Beta0

  • complete and stabilize the native winGRASS port (seems to be in a good shape now)
Must do
  • replace r.proj with r.proj.seg
  • d.text with d.text.new
  • r.out.gdal sets NoData wrong #405
Mostly done?
  • use GEM for GRASS Addons SVN - status unclear
Wishlist
  • modify Makefile system to support translated HTML pages. Store translated HTML files in centralized directory with locale specific subdirs, file name is module name.
  • Implement vector improvements as suggested by Radim
  • Integrate i.points.auto (merge into i.vpoints) - see also Image processing - note that A Scianna/Palermo has modernized version
  • Make sqlite the default DB? <- needs more testing, for 6.5?
  • drop d.m display manager (as now almost unmaintained; there is gis.m and/or a python based GUI)
Some people still prefer it (see posts to grass-dev) and I will fix bugs in it, but not enhance/add new modules to it without good reason. So I don't see the need to drop it before the WxPython version is ready. It's not hurting us any keeping it. --Hamish
We should keep plain d.mon interface but why keep d.m, if gis.m has become really good? Probably we should clearly state, that d.m is UNMAINTAINED and OBSOLETE? MarisN 08:24, 16 February 2007 (CET)


In progress

  • native MS Windows port
  • 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 (done for ps.map)
    • 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)
  • adding further (organized) keywords to every grass command and script [1] and [2]:
    • display commands
    • database commands
    • general commands
    • imagery commands
    • misc commands
    • paint commands
    • photo commands
    • postscript commands
    • raster commands
    • raster3D commands
    • vector commands
  • continue with wxpython prototype
  • write (Python based?) GUI wizard to create new locations (MN and terrestris.de)
  • implement Python-SWIG interface
  • less verbose commands
Retrieved from "https://grasswiki.osgeo.org/w/index.php?title=GRASS_6.3_Feature_Plan&oldid=4887"