Talk:GRASS 6.3 Feature Plan - Revision history

Neteler at 13:14, 15 August 2006

2006-08-15T13:14:42Z

← Older revision		Revision as of 13:14, 15 August 2006
Line 2:		Line 2:
	[[User:MarisN\|MarisN]] 15:45, 4 August 2006 (CEST)		[[User:MarisN\|MarisN]] 15:45, 4 August 2006 (CEST)

			: Another opinion could cover the idea, that wishes may attract '''new''' developers...
	----		----

⚠️Huhabla at 18:48, 14 August 2006

2006-08-14T18:48:58Z

← Older revision		Revision as of 18:48, 14 August 2006
Line 5:		Line 5:

	There are already export modules for the VTK dataformat in grass,		There are already export modules for the VTK dataformat in grass,
	so there is no need to implement this is gdal/ogr.		so there is no need to implement this in gdal/ogr.
	* r.out.vtk		* r.out.vtk
	* v.out.vtk		* v.out.vtk

⚠️Huhabla at 18:45, 14 August 2006

2006-08-14T18:45:22Z

← Older revision		Revision as of 18:45, 14 August 2006
Line 1:		Line 1:
	My idea is to tighten developers and they features with release schedule. There is no point to list feature which nobody will implement or will not implement till THIS release. This should be a '''PLAN''' and not a '''wish list'''. This should be for non-abstract stuff, but for tasks that ''can'' and ''should'' be done before target release. Users then could look at this page to see - whats coming next, which bugs would be fixed etc.		My idea is to tighten developers and they features with release schedule. There is no point to list feature which nobody will implement or will not implement till THIS release. This should be a '''PLAN''' and not a '''wish list'''. This should be for non-abstract stuff, but for tasks that ''can'' and ''should'' be done before target release. Users then could look at this page to see - whats coming next, which bugs would be fixed etc.
	[[User:MarisN\|MarisN]] 15:45, 4 August 2006 (CEST)		[[User:MarisN\|MarisN]] 15:45, 4 August 2006 (CEST)

			----

	There are already export modules for the VTK dataformat in grass,		There are already export modules for the VTK dataformat in grass,
	so there is no need to implement this is gdal/ogr.		so there is no need to implement this is gdal/ogr.
	* r.~~otu~~.vtk		* r.out.vtk
	* v.out.vtk		* v.out.vtk
	* r3.out.vtk		* r3.out.vtk
Line 14:		Line 16:
	is the base for ParaView. And you need to handle the grass lib functions		is the base for ParaView. And you need to handle the grass lib functions
	within C++.		within C++.
			--[[User:Huhabla\|huhabla]] 20:45, 14 August 2006 (CEST)

⚠️Huhabla at 18:43, 14 August 2006

2006-08-14T18:43:48Z

← Older revision		Revision as of 18:43, 14 August 2006
Line 1:		Line 1:
	My idea is to tighten developers and they features with release schedule. There is no point to list feature which nobody will implement or will not implement till THIS release. This should be a '''PLAN''' and not a '''wish list'''. This should be for non-abstract stuff, but for tasks that ''can'' and ''should'' be done before target release. Users then could look at this page to see - whats coming next, which bugs would be fixed etc.		My idea is to tighten developers and they features with release schedule. There is no point to list feature which nobody will implement or will not implement till THIS release. This should be a '''PLAN''' and not a '''wish list'''. This should be for non-abstract stuff, but for tasks that ''can'' and ''should'' be done before target release. Users then could look at this page to see - whats coming next, which bugs would be fixed etc.
	[[User:MarisN\|MarisN]] 15:45, 4 August 2006 (CEST)		[[User:MarisN\|MarisN]] 15:45, 4 August 2006 (CEST)

			There are already export modules for the VTK dataformat in grass,
			so there is no need to implement this is gdal/ogr.
			* r.otu.vtk
			* v.out.vtk
			* r3.out.vtk
			are doing the job very well.
			And the output files of these modules are the standard input format for ParaView.

			And to patch ParaView to read directly from grass database should be a wish
			for grass7. Because you need to implement this functionality in VTK, which
			is the base for ParaView. And you need to handle the grass lib functions
			within C++.

⚠️MarisN at 13:45, 4 August 2006

2006-08-04T13:45:55Z

New page

My idea is to tighten developers and they features with release schedule. There is no point to list feature which nobody will implement or will not implement till THIS release. This should be a '''PLAN''' and not a '''wish list'''. This should be for non-abstract stuff, but for tasks that ''can'' and ''should'' be done before target release. Users then could look at this page to see - whats coming next, which bugs would be fixed etc.
[[User:MarisN|MarisN]] 15:45, 4 August 2006 (CEST)