Tutorial:Setting up Fenix with ConTEXT - Revision history

217.136.63.215 at 00:57, 25 December 2008

217.136.63.215 — Thu, 25 Dec 2008 00:57:21 GMT

←Older revision		Revision as of 00:57, 25 December 2008
Line 3:		Line 3:
	[[Category:setting up Fenix]]		[[Category:setting up Fenix]]

-	Setting up Fenix with [http://www.~~context~~.cx ConTEXT].	+	Setting up Fenix with [http://www.contexteditor.org/ ConTEXT].

	It is assumed [[Latest_Fenix_version\|Fenix Binaries]] are downloaded in a certain folder, thus in which fxi.exe and fxc.exe will be. With the Run and Lookup setup sections, a file is required: [[Media:ContextBatches.zip\|ConTEXTBatches.zip]]. It is required that this archive is extracted into the folder previously mentioned, the one containing fxi.exe and fxc.exe.		It is assumed [[Latest_Fenix_version\|Fenix Binaries]] are downloaded in a certain folder, thus in which fxi.exe and fxc.exe will be. With the Run and Lookup setup sections, a file is required: [[Media:ContextBatches.zip\|ConTEXTBatches.zip]]. It is required that this archive is extracted into the folder previously mentioned, the one containing fxi.exe and fxc.exe.

Sandman: /* Run (F11) */

Sandman — Sun, 30 Mar 2008 11:21:28 GMT

Run (F11)

←Older revision		Revision as of 11:21, 30 March 2008
Line 53:		Line 53:
	=== Run (F11) ===		=== Run (F11) ===
	# Setup Run hotkey:		# Setup Run hotkey:
-	## Execute: <code>XXXXXX\fxi.exe</code>.	+	## Execute: <code>XXXXXX\fxi.exe</code>. (NOTE: for [[Bennu_WIP2\|Bennu WIP2]] and later use <code>XXXXXX\bgdi.exe</code> instead)
	## Parameters: <code>"%p%F.dcb"</code>.		## Parameters: <code>"%p%F.dcb"</code>.
	## Save: <code>Nothing</code>.		## Save: <code>Nothing</code>.

Sandman at 10:02, 26 February 2008

Sandman — Tue, 26 Feb 2008 10:02:34 GMT

←Older revision		Revision as of 10:02, 26 February 2008
Line 10:		Line 10:

	For example, you extracted the binaries to <code>D:\Fenix\Executables\</code>, then you will need to replace <code>XXXXXX</code> with <code>D:\Fenix\Executables</code> (watch that last <code>\</code>, there only needs to be one).		For example, you extracted the binaries to <code>D:\Fenix\Executables\</code>, then you will need to replace <code>XXXXXX</code> with <code>D:\Fenix\Executables</code> (watch that last <code>\</code>, there only needs to be one).
		+
		+	== Advantages ==
		+	ConTEXT is a pretty handy text editor. It has quite a range of possibilities and the highlighter file is very up to date. When it is setup like described below, certain files are only needed in one directory: the fxi/fxc directory. These certain files contain: include files (.inc), Fenix header files (.fh) and DLL's (*.dll). Actually, any file can be included/imported if it's in the fxi/fxc directory. This brings advantages like saving disk space, updating a certain file is much easier and automatically affects all programs using it, not just one.

	== Syntax Highlighter ==		== Syntax Highlighter ==
Line 61:		Line 64:
	Repeat the following for the extensions wanted (prg, inc, fh):		Repeat the following for the extensions wanted (prg, inc, fh):
	# Click on the button Add and enter an extension.		# Click on the button Add and enter an extension.
-
-	== Advantages ==
-	ConTEXT is a pretty handy text editor. It has quite a range of possibilities and the highlighter file is very up to date. When it is setup like described above, certain files are only needed in one directory: the fxi/fxc directory. These certain files contain: include files (.inc), Fenix header files (.fh) and DLL's (*.dll). Actually, any file can be included/imported if it's in the fxi/fxc directory. This brings advantages like saving disk space, updating a certain file is much easier and automatically affects all programs using it, not just one.

Sandman at 21:27, 21 January 2008

Sandman — Mon, 21 Jan 2008 21:27:57 GMT

←Older revision		Revision as of 21:27, 21 January 2008
Line 41:		Line 41:
	## Parameters: <code>XXXXXX -g %n</code>.		## Parameters: <code>XXXXXX -g %n</code>.
	## Save: <code>All files before execution</code>.		## Save: <code>All files before execution</code>.
		+	## Enable Use short DOS names (if you tend to use spaces in paths/filenames, so enabling is safest)
	## Enable Capture console output.		## Enable Capture console output.
	## Compiler output parser rule: <code>Error in file %n at line %l:*</code>.		## Compiler output parser rule: <code>Error in file %n at line %l:*</code>.
Line 52:		Line 53:
	## Parameters: <code>"%p%F.dcb"</code>.		## Parameters: <code>"%p%F.dcb"</code>.
	## Save: <code>Nothing</code>.		## Save: <code>Nothing</code>.
		+	## Enable Use short DOS names (if you tend to use spaces in paths/filenames, so enabling is safest)
	* Replace <code>XXXXXX</code> by the path to the directory containing fxi.exe, ''without'' (double)quotes.		* Replace <code>XXXXXX</code> by the path to the directory containing fxi.exe, ''without'' (double)quotes.

Sandman at 21:58, 20 November 2007

Sandman — Tue, 20 Nov 2007 21:58:37 GMT

←Older revision		Revision as of 21:58, 20 November 2007
Line 30:		Line 30:
	## Parameters: <code>%w</code>.		## Parameters: <code>%w</code>.
	## Save: <code>Nothing</code>.		## Save: <code>Nothing</code>.
-	* Replace <code>XXXXXX</code> by the path to the directory you placed fxw.bat in '''without''' (double)quotes.	+	* Replace <code>XXXXXX</code> by the path to the directory you placed fxw.bat in, ''without'' (double)quotes.

	This will allow you to hit a button (F9-F12) to lookup the word currently under your cursor in ConTEXT on FenixWiki. Alternatively you can use <code>%?</code> instead of <code>%w</code>, to enter the word you're looking for. A possible setup is <code>%w</code> on F9 and <code>%?</code> on F12.		This will allow you to hit a button (F9-F12) to lookup the word currently under your cursor in ConTEXT on FenixWiki. Alternatively you can use <code>%?</code> instead of <code>%w</code>, to enter the word you're looking for. A possible setup is <code>%w</code> on F9 and <code>%?</code> on F12.
Line 44:		Line 44:
	## Compiler output parser rule: <code>Error in file %n at line %l:*</code>.		## Compiler output parser rule: <code>Error in file %n at line %l:*</code>.
	## Enable Scroll console to the last line.		## Enable Scroll console to the last line.
-	* Replace <code>XXXXXX</code> by the path to the directory containing fxc.bat and fxc.exe '''without''' (double)quotes.	+	* Replace <code>XXXXXX</code> by the path to the directory containing fxc.bat and fxc.exe, ''without'' (double)quotes.
	* Note that you can include codefiles and libraries located in the XXXXXX directory automatically now.		* Note that you can include codefiles and libraries located in the XXXXXX directory automatically now.

Line 52:		Line 52:
	## Parameters: <code>"%p%F.dcb"</code>.		## Parameters: <code>"%p%F.dcb"</code>.
	## Save: <code>Nothing</code>.		## Save: <code>Nothing</code>.
-	* Replace <code>XXXXXX</code> by the path to the directory containing fxi.exe '''without''' (double)quotes.	+	* Replace <code>XXXXXX</code> by the path to the directory containing fxi.exe, ''without'' (double)quotes.

	== File Associations ==		== File Associations ==

Sandman at 21:57, 20 November 2007

Sandman — Tue, 20 Nov 2007 21:57:46 GMT

←Older revision		Revision as of 21:57, 20 November 2007
Line 30:		Line 30:
	## Parameters: <code>%w</code>.		## Parameters: <code>%w</code>.
	## Save: <code>Nothing</code>.		## Save: <code>Nothing</code>.
-	* Replace <code>XXXXXX</code> by the path to the directory you placed fxw.bat in.	+	* Replace <code>XXXXXX</code> by the path to the directory you placed fxw.bat in '''without''' (double)quotes.

	This will allow you to hit a button (F9-F12) to lookup the word currently under your cursor in ConTEXT on FenixWiki. Alternatively you can use <code>%?</code> instead of <code>%w</code>, to enter the word you're looking for. A possible setup is <code>%w</code> on F9 and <code>%?</code> on F12.		This will allow you to hit a button (F9-F12) to lookup the word currently under your cursor in ConTEXT on FenixWiki. Alternatively you can use <code>%?</code> instead of <code>%w</code>, to enter the word you're looking for. A possible setup is <code>%w</code> on F9 and <code>%?</code> on F12.
Line 44:		Line 44:
	## Compiler output parser rule: <code>Error in file %n at line %l:*</code>.		## Compiler output parser rule: <code>Error in file %n at line %l:*</code>.
	## Enable Scroll console to the last line.		## Enable Scroll console to the last line.
-	* Replace <code>XXXXXX</code> by the path to the directory containing fxc.bat and fxc.exe.	+	* Replace <code>XXXXXX</code> by the path to the directory containing fxc.bat and fxc.exe '''without''' (double)quotes.
	* Note that you can include codefiles and libraries located in the XXXXXX directory automatically now.		* Note that you can include codefiles and libraries located in the XXXXXX directory automatically now.

Line 52:		Line 52:
	## Parameters: <code>"%p%F.dcb"</code>.		## Parameters: <code>"%p%F.dcb"</code>.
	## Save: <code>Nothing</code>.		## Save: <code>Nothing</code>.
-	* Replace <code>XXXXXX</code> by the path to the directory containing fxi.exe.	+	* Replace <code>XXXXXX</code> by the path to the directory containing fxi.exe '''without''' (double)quotes.

	== File Associations ==		== File Associations ==

Sandman at 23:30, 9 November 2007

Sandman — Fri, 09 Nov 2007 23:30:51 GMT

←Older revision		Revision as of 23:30, 9 November 2007
Line 15:		Line 15:
	# Restart ConTEXT		# Restart ConTEXT
	# File -> New		# File -> New
-	# Go to Tools -> Set Highlighter -> Customize Types..., select Foxpro, click on Edit and change "prg" to "prg2".	+	# Go to Tools -> Set Highlighter -> Customize Types..., select Foxpro, click on Edit and change "prg" to "prg2"; select Object Pascal, click on Edit and change "inc" to "inc2".

	You can meddle with the colours all you like: Options -> Environment Options -> Colors. You can also edit the colours in fenix.chl, if you find this easier. This can be handy for changing all backgrounds in a quick way.		You can meddle with the colours all you like: Options -> Environment Options -> Colors. You can also edit the colours in fenix.chl, if you find this easier. This can be handy for changing all backgrounds in a quick way.
Line 37:		Line 37:
	# Download the new fxc.bat ([[Media:ContextBatches.zip\|ConTEXTBatches.zip]]: extract into fxi/fxc folder) and replace the old one by it, if not done already.		# Download the new fxc.bat ([[Media:ContextBatches.zip\|ConTEXTBatches.zip]]: extract into fxi/fxc folder) and replace the old one by it, if not done already.
	# Setup Compile hotkey:		# Setup Compile hotkey:
-	## Execute: <code>XXXXXX\fxc.bat</code>.	+	## Execute: <code>XXXXXX\fxc.bat</code> (NOTE: for [[0.93\|Bennu 0.93]] use <code>XXXXXX\bgdc.bat</code> instead)
-	## Parameters: <code>"XXXXXX" -g "%n"</code>.	+	## Start in: <code>%p</code>
		+	## Parameters: <code>XXXXXX -g %n</code>.
	## Save: <code>All files before execution</code>.		## Save: <code>All files before execution</code>.
	## Enable Capture console output.		## Enable Capture console output.
Line 60:		Line 61:

	== Advantages ==		== Advantages ==
-	ConTEXT is a pretty handy text editor. It has quite a range of possibilities and the highlighter file is very up to date. When it is setup like described above, certain files are only needed in one directory: the fxi/fxc directory. These certain files contain: include files (.inc), Fenix header files (.fh) and DLL's (*.dll). Actually, any file can be included/imported if it's in the fxi/fxc directory. This brings advantages like saving disk space, updating a certain file is much easier and ~~updating~~ automatically affects all programs using it, not just one.	+	ConTEXT is a pretty handy text editor. It has quite a range of possibilities and the highlighter file is very up to date. When it is setup like described above, certain files are only needed in one directory: the fxi/fxc directory. These certain files contain: include files (.inc), Fenix header files (.fh) and DLL's (*.dll). Actually, any file can be included/imported if it's in the fxi/fxc directory. This brings advantages like saving disk space, updating a certain file is much easier and automatically affects all programs using it, not just one.

Sandman at 15:44, 13 September 2007

Sandman — Thu, 13 Sep 2007 15:44:39 GMT

←Older revision		Revision as of 15:44, 13 September 2007
Line 7:		Line 7:
	It is assumed [[Latest_Fenix_version\|Fenix Binaries]] are downloaded in a certain folder, thus in which fxi.exe and fxc.exe will be. With the Run and Lookup setup sections, a file is required: [[Media:ContextBatches.zip\|ConTEXTBatches.zip]]. It is required that this archive is extracted into the folder previously mentioned, the one containing fxi.exe and fxc.exe.		It is assumed [[Latest_Fenix_version\|Fenix Binaries]] are downloaded in a certain folder, thus in which fxi.exe and fxc.exe will be. With the Run and Lookup setup sections, a file is required: [[Media:ContextBatches.zip\|ConTEXTBatches.zip]]. It is required that this archive is extracted into the folder previously mentioned, the one containing fxi.exe and fxc.exe.

-	Here and there this folder will be denoted as <code>XXXXXX</code>. You will need to replace <code>XXXXXX</code> with the path to the directory you extracted the binaries to~~, in both ConTEXT as fxc.bat~~.	+	Here and there this folder will be denoted as <code>XXXXXX</code>. You will need to replace <code>XXXXXX</code> with the path to the directory you extracted the binaries to.

-	For example, you extracted the binaries to <code>D:\Fenix\Executables\</code>, then you will need to replace <code>XXXXXX</code> with <code>D:\Fenix\Executables</code> (watch that last <code>\</code>, there only needs to be one). ~~This needs to be done in ConTEXT as well as the batch file (fxc.bat)~~	+	For example, you extracted the binaries to <code>D:\Fenix\Executables\</code>, then you will need to replace <code>XXXXXX</code> with <code>D:\Fenix\Executables</code> (watch that last <code>\</code>, there only needs to be one).

	== Syntax Highlighter ==		== Syntax Highlighter ==
Line 27:		Line 27:
	# Download fxw.bat ([[Media:ContextBatches.zip\|ConTEXTBatches.zip]]: extract into fxi/fxc folder), if not done already.		# Download fxw.bat ([[Media:ContextBatches.zip\|ConTEXTBatches.zip]]: extract into fxi/fxc folder), if not done already.
	# Setup Lookup hotkey:		# Setup Lookup hotkey:
-	## Execute: <code>fxw.bat~~</code>.~~	+	## Execute: <code>XXXXXX\fxw.bat</code>.
-	~~## Start in: <code>XXXXXX~~</code>.	+
	## Parameters: <code>%w</code>.		## Parameters: <code>%w</code>.
	## Save: <code>Nothing</code>.		## Save: <code>Nothing</code>.
-	~~## Now~~ Replace <code>XXXXXX</code> by the path to the directory you placed fxw.bat in.	+	* Replace <code>XXXXXX</code> by the path to the directory you placed fxw.bat in.

	This will allow you to hit a button (F9-F12) to lookup the word currently under your cursor in ConTEXT on FenixWiki. Alternatively you can use <code>%?</code> instead of <code>%w</code>, to enter the word you're looking for. A possible setup is <code>%w</code> on F9 and <code>%?</code> on F12.		This will allow you to hit a button (F9-F12) to lookup the word currently under your cursor in ConTEXT on FenixWiki. Alternatively you can use <code>%?</code> instead of <code>%w</code>, to enter the word you're looking for. A possible setup is <code>%w</code> on F9 and <code>%?</code> on F12.
Line 49:		Line 48:
	=== Run (F11) ===		=== Run (F11) ===
	# Setup Run hotkey:		# Setup Run hotkey:
-	## Execute: <code>fxi.exe</code>.	+	## Execute: <code>XXXXXX\fxi.exe</code>.
	## Parameters: <code>"%p%F.dcb"</code>.		## Parameters: <code>"%p%F.dcb"</code>.
	## Save: <code>Nothing</code>.		## Save: <code>Nothing</code>.
-	## Replace <code>XXXXXX</code> by the path to the directory containing fxi.exe.	+	* Replace <code>XXXXXX</code> by the path to the directory containing fxi.exe.

	== File Associations ==		== File Associations ==

Sandman: /* Run (F11) */

Sandman — Thu, 13 Sep 2007 15:40:26 GMT

Run (F11)

←Older revision		Revision as of 15:40, 13 September 2007
Line 50:		Line 50:
	# Setup Run hotkey:		# Setup Run hotkey:
	## Execute: <code>fxi.exe</code>.		## Execute: <code>fxi.exe</code>.
-	## Start in: <code>XXXXXX</code>.
	## Parameters: <code>"%p%F.dcb"</code>.		## Parameters: <code>"%p%F.dcb"</code>.
	## Save: <code>Nothing</code>.		## Save: <code>Nothing</code>.

Sandman: /* Compile (F10) */

Sandman — Thu, 13 Sep 2007 15:39:49 GMT

Compile (F10)

←Older revision		Revision as of 15:39, 13 September 2007
Line 39:		Line 39:
	# Setup Compile hotkey:		# Setup Compile hotkey:
	## Execute: <code>XXXXXX\fxc.bat</code>.		## Execute: <code>XXXXXX\fxc.bat</code>.
-	~~## Start in: <code>%p</code>.~~	+	## Parameters: <code>"XXXXXX" -g "%n"</code>.
-	## Parameters: <code>-i "XXXXXX" -g "%n"</code>.	+
	## Save: <code>All files before execution</code>.		## Save: <code>All files before execution</code>.
	## Enable Capture console output.		## Enable Capture console output.
	## Compiler output parser rule: <code>Error in file %n at line %l:*</code>.		## Compiler output parser rule: <code>Error in file %n at line %l:*</code>.
	## Enable Scroll console to the last line.		## Enable Scroll console to the last line.
-	## Replace <code>XXXXXX</code> by the path to the directory containing fxc.bat and fxc.exe~~, in both the ConTEXT setup and fxc.bat~~.	+	* Replace <code>XXXXXX</code> by the path to the directory containing fxc.bat and fxc.exe.
-	~~## Parser rule is: <code>Error in file %n at line %l:~~*~~</code>.~~	+	* Note that you can include codefiles and libraries located in the XXXXXX directory automatically now.
-	Note that ~~the <code>-i "XXXXXX"</code> will allow~~ you to include codefiles in the ~~<code>~~XXXXXX~~</code>~~ directory.	+

	=== Run (F11) ===		=== Run (F11) ===