This wiki is out of date, use the continuation of this wiki instead

Tutorial:Setting up Fenix with ConTEXT

From FenixWiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 19:07, 6 August 2007 (edit)
Sandman (Talk | contribs)

← Previous diff
Revision as of 21:24, 6 August 2007 (edit) (undo)
Sandman (Talk | contribs)

Next diff →
Line 2: Line 2:
[[Category:tutorials]] [[Category:tutorials]]
-Setting up Fenix with [http://www.context.cx 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.+Setting up Fenix with [http://www.context.cx 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. Here and there this folder will be denoted as <code>XXXXXX</code>. You will need to replace <code>XXXXXX</code> with 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)
== Syntax Highlighter == == Syntax Highlighter ==

Revision as of 21:24, 6 August 2007


Setting up Fenix with ConTEXT. It is assumed 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: 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 XXXXXX. You will need to replace XXXXXX with the directory you extracted the binaries to. For example, you extracted the binaries to D:\Fenix\Executables\, then you will need to replace XXXXXX with D:\Fenix\Executables (watch that last /, there only needs to be one). This needs to be done in ConTEXT as well as the batch file (fxc.bat)

Contents

Syntax Highlighter

  1. Place fenix.chl in the folder ConTEXT\Highlighters
  2. Restart ConTEXT
  3. File -> New
  4. Go to Tools -> Set Highlighter -> Customize Types..., select Foxpro, click on Edit and change "prg" to "prg2".

Compile

Image:Compilesetup.PNG

  1. Download the new fxc.bat (ConTEXTBatches.zip: extract into fxi/fxc folder) and replace the old one by it.
  2. Setup ConTEXT like on the screenshot. Replace XXXXXX by the directory containing fxc.bat and fxc.exe, in both the ConTEXT setup and the fxc.bat. Parser rule is: Error in file %n at line %l:*.
  3. Note that the -i "XXXXXX" will allow you to include codefiles in the XXXXXX directory.

Run

Image:Runsetup.PNG

  1. Setup ConTEXT like on the screenshot. Replace XXXXXX by the directory containing fxi.exe.

Lookup on this wiki

Image:Lookupsetup.PNG

  1. Download fxw.bat (ConTEXTBatches.zip: extract into fxi/fxc folder).
  2. Setup ConTEXT like on the screenshot. Replace XXXXXX by the directory you placed fxw.bat in, the fxc.bat.

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 %? instead of %w, to enter the word you're looking for. A possible setup is %w on F9 and %? on F12.

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.

Source

Fenix for ConTEXT

Personal tools