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 15:44, 13 September 2007 (edit)
Sandman (Talk | contribs)
m
← Previous diff		 Current revision (00:57, 25 December 2008) (edit) (undo)
217.136.63.215 (Talk)

 
(6 intermediate revisions not shown.)
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.
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 15: Line 18:
# 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 30: Line 33:
## 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 37: Line 40:
# 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 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>.
## 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.
=== 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>.
-* Replace <code>XXXXXX</code> by the path to the directory containing fxi.exe.+## 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.
== File Associations == == File Associations ==
Line 58: 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 updating automatically affects all programs using it, not just one. 

Current revision


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 path to 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).

Contents

[edit] 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.

[edit] 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"; 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.

Should you add native Fenix keywords to the highlighter, which were forgotten, be so kind as to notify of the addition on the Fenix.chl discussion page.

[edit] Hotkeys

The setting up here happens in Options -> Environment Options -> [Execute Keys]. To add hotkeys for Fenix, click on the button Add and enter prg,inc,fh for extensions. Noted are generally used hotkeys between brackets, but this can be altered.

[edit] Lookup on this wiki (F9/F12)

  1. Download fxw.bat (ConTEXTBatches.zip: extract into fxi/fxc folder), if not done already.
  2. Setup Lookup hotkey:
    1. Execute: XXXXXX\fxw.bat.
    2. Parameters: %w.
    3. Save: Nothing.
  • Replace XXXXXX 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 %? instead of %w, to enter the word you're looking for. A possible setup is %w on F9 and %? on F12.

[edit] Compile (F10)

  1. Download the new fxc.bat (ConTEXTBatches.zip: extract into fxi/fxc folder) and replace the old one by it, if not done already.
  2. Setup Compile hotkey:
    1. Execute: XXXXXX\fxc.bat (NOTE: for Bennu 0.93 use XXXXXX\bgdc.bat instead)
    2. Start in: %p
    3. Parameters: XXXXXX -g %n.
    4. Save: All files before execution.
    5. Enable Use short DOS names (if you tend to use spaces in paths/filenames, so enabling is safest)
    6. Enable Capture console output.
    7. Compiler output parser rule: Error in file %n at line %l:*.
    8. Enable Scroll console to the last line.
  • Replace XXXXXX 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.

[edit] Run (F11)

  1. Setup Run hotkey:
    1. Execute: XXXXXX\fxi.exe. (NOTE: for Bennu WIP2 and later use XXXXXX\bgdi.exe instead)
    2. Parameters: "%p%F.dcb".
    3. Save: Nothing.
    4. Enable Use short DOS names (if you tend to use spaces in paths/filenames, so enabling is safest)
  • Replace XXXXXX by the path to the directory containing fxi.exe, without (double)quotes.

[edit] File Associations

The setting up here happens in Options -> Environment Options -> [File Associations].

Repeat the following for the extensions wanted (prg, inc, fh):

  1. Click on the button Add and enter an extension.
Retrieved from "http://fenixwiki.booleansoup.com/index.php/Tutorial:Setting_up_Fenix_with_ConTEXT"
Personal tools