GRASS Programming Howto - Revision history

Neteler at 17:12, 9 February 2018

2018-02-09T17:12:50Z

← Older revision		Revision as of 17:12, 9 February 2018
Line 1:		Line 1:
	~~{{RemoveOrConserve}}~~

	* (Temporary solution here, becoming a Doxygen page in the source code.)		* (Temporary solution here, becoming a Doxygen page in the source code.)
	* See also [http://grass.osgeo.org/programming7/ GRASS 7 Programmer's manual]		* See also [http://grass.osgeo.org/programming7/ GRASS 7 Programmer's manual]
Line 18:		Line 16:
	manual with some changes where needed. So let's start (26-01-2003) and		manual with some changes where needed. So let's start (26-01-2003) and
	make it more fun/ease to program for GRASS.		make it more fun/ease to program for GRASS.


	Greetings		Greetings
Line 26:		Line 23:
	The Netherlands		The Netherlands

			Update '''2018''': an initial overhaul has been done.

	== Tools ==		== Tools ==

2018-02-09T17:11:40Z

overhauled

2018-02-09T14:10:50Z

Display Symbols: add links to source code

← Older revision		Revision as of 14:10, 9 February 2018
Line 1,232:		Line 1,232:

	To see custom symbols in the GUI, you need to make a thumbnail image with ps.map and		To see custom symbols in the GUI, you need to make a thumbnail image with ps.map and
	inkscape. See gui/symbols/README in the grass source code for a script to do that.		inkscape. See [https://trac.osgeo.org/grass/browser/grass/trunk/gui/images/symbols/README gui/images/symbols/README]
			in the grass source code for more instructions and a [https://trac.osgeo.org/grass/browser/grass/trunk/tools/symbol_to_img.sh script] to do that.
	Put the resulting pngs in the same ./gui/images/symbols/ directory structure.		Put the resulting pngs in the same ./gui/images/symbols/ directory structure.

			=== File format description ===
	<pre>		<pre>
	Symbol drawing commands are stored in a text file (one file for each symbol)		Symbol drawing commands are stored in a text file (one file for each symbol)

2018-02-09T12:42:17Z

info about where to put example PNG files for symbols (thanks to Mary Muir)

← Older revision		Revision as of 12:42, 9 February 2018
Line 1,230:		Line 1,230:

	For user contributed symbols see the [[IconSymbols]] wiki page.		For user contributed symbols see the [[IconSymbols]] wiki page.

			To see custom symbols in the GUI, you need to make a thumbnail image with ps.map and
			inkscape. See gui/symbols/README in the grass source code for a script to do that.

			Put the resulting pngs in the same ./gui/images/symbols/ directory structure.

	<pre>		<pre>

2015-03-04T16:23:48Z

← Older revision		Revision as of 16:23, 4 March 2015
Line 1:		Line 1:
	* ~~temporary~~ solution here, ~~eventually it becomes~~ a ~~doygenized~~ page in ~~SVN~~.		{{RemoveOrConserve}}

			* Temporary solution here, becoming a Doxygen page in the source code.

	* See also [http://grass.osgeo.org/programming6/ GRASS 6 Programmer's manual]		* See also [http://grass.osgeo.org/programming6/ GRASS 6 Programmer's manual]

2014-06-27T14:45:37Z

← Older revision		Revision as of 14:45, 27 June 2014
Line 108:		Line 108:
	=== Once you have the code (new one or fixed one) ===		=== Once you have the code (new one or fixed one) ===

	Now if you decide to add or change something do this according to the rules explained in the {{twiki\|SUBMITTING}} files (there is one for each language) and take a look at the "[http://www.gnu.org/prep/standards.html GNU Coding Standards]". Some other hints and needs for the Grass programmer:		Now if you decide to add or change something do this according to the rules explained in the {{twiki\|Submitting\|SUBMITTING}} files (there is one for each language) and take a look at the "[http://www.gnu.org/prep/standards.html GNU Coding Standards]". Some other hints and needs for the Grass programmer:

	* Document you're new code well, and in browsing other code and gaining valuable insights, also document this either here, but especially in the code itself.		* Document you're new code well, and in browsing other code and gaining valuable insights, also document this either here, but especially in the code itself.

2014-06-27T14:45:10Z

← Older revision		Revision as of 14:45, 27 June 2014
Line 108:		Line 108:
	=== Once you have the code (new one or fixed one) ===		=== Once you have the code (new one or fixed one) ===

	Now if you decide to add or change something do this according to the rules explained in the {{~~trac~~\|SUBMITTING}} files (there is one for each language) and take a look at the "[http://www.gnu.org/prep/standards.html GNU Coding Standards]". Some other hints and needs for the Grass programmer:		Now if you decide to add or change something do this according to the rules explained in the {{twiki\|SUBMITTING}} files (there is one for each language) and take a look at the "[http://www.gnu.org/prep/standards.html GNU Coding Standards]". Some other hints and needs for the Grass programmer:

	* Document you're new code well, and in browsing other code and gaining valuable insights, also document this either here, but especially in the code itself.		* Document you're new code well, and in browsing other code and gaining valuable insights, also document this either here, but especially in the code itself.

2014-06-27T14:44:33Z

← Older revision		Revision as of 14:44, 27 June 2014
Line 108:		Line 108:
	=== Once you have the code (new one or fixed one) ===		=== Once you have the code (new one or fixed one) ===

	Now if you decide to add or change something do this according to the rules explained in the {{~~src~~\|SUBMITTING}} files (there is one for each language) and take a look at the "[http://www.gnu.org/prep/standards.html GNU Coding Standards]". Some other hints and needs for the Grass programmer:		Now if you decide to add or change something do this according to the rules explained in the {{trac\|SUBMITTING}} files (there is one for each language) and take a look at the "[http://www.gnu.org/prep/standards.html GNU Coding Standards]". Some other hints and needs for the Grass programmer:

	* Document you're new code well, and in browsing other code and gaining valuable insights, also document this either here, but especially in the code itself.		* Document you're new code well, and in browsing other code and gaining valuable insights, also document this either here, but especially in the code itself.

2014-02-15T17:17:22Z

← Older revision		Revision as of 17:17, 15 February 2014
Line 1:		Line 1:
	* temporary solution here, eventually it becomes a doygenized page in SVN.		* temporary solution here, eventually it becomes a doygenized page in SVN.

	* See also [http://~~download~~.osgeo.org/grass/~~grass6_progman~~/ GRASS 6 Programmer's manual]		* See also [http://grass.osgeo.org/programming6/ GRASS 6 Programmer's manual]
			* See also [http://grass.osgeo.org/programming7/ GRASS 7 Programmer's manual] (updated, recommended)

	== Introduction ==		== Introduction ==

			HINT: this page origins from 2006 - outdated.

	The reason for starting this Howto is the fact that it's very hard to		The reason for starting this Howto is the fact that it's very hard to

2013-08-03T00:52:47Z

Display Symbols

← Older revision		Revision as of 00:52, 3 August 2013
Line 1,228:		Line 1,228:
	<pre>		<pre>
	Symbol drawing commands are stored in a text file (one file for each symbol)		Symbol drawing commands are stored in a text file (one file for each symbol)
	which are located in $GISBASE/etc/symbol/group/name or ~~mapset~~/symbol/group/name		which are located in $GISBASE/etc/symbol/group/name or $MAPSET/symbol/group/name

	S_read() searches first in mapsets and then in $GISBASE (symbol names in		S_read() searches first in mapsets and then in $GISBASE (symbol names in