From 6f9f45c64b0aed4a8e6b87d2caaa93c8d717ad02 Mon Sep 17 00:00:00 2001 From: Peter Dell Date: Sun, 27 Aug 2023 11:16:52 +0200 Subject: [PATCH] Update HTML documentation Spelling --- .../help/ide-credits.section.html | 8 +- com.wudsn.ide.lng/help/ide-faq.section.html | 722 ++++++++------ .../help/ide-features.section.html | 909 +++++++++++------- .../help/ide-installation.section.html | 569 ++++++----- .../help/ide-releases.section.html | 190 ++-- .../help/ide-tutorials.section.html | 183 ++-- 6 files changed, 1579 insertions(+), 1002 deletions(-) diff --git a/com.wudsn.ide.lng/help/ide-credits.section.html b/com.wudsn.ide.lng/help/ide-credits.section.html index 89be6a15..15453fe4 100644 --- a/com.wudsn.ide.lng/help/ide-credits.section.html +++ b/com.wudsn.ide.lng/help/ide-credits.section.html @@ -4,7 +4,7 @@ - + @@ -30,7 +30,7 @@ + rel="noopener noreferrer">MADS and Mad Pascal @@ -49,7 +49,7 @@ - + @@ -67,7 +67,7 @@ - + diff --git a/com.wudsn.ide.lng/help/ide-faq.section.html b/com.wudsn.ide.lng/help/ide-faq.section.html index 8b284a39..0962f3c1 100644 --- a/com.wudsn.ide.lng/help/ide-faq.section.html +++ b/com.wudsn.ide.lng/help/ide-faq.section.html @@ -1,395 +1,557 @@ -

Here you can find the answers to some frequently asked questions. If your question is not answered here, please have - a look at the video tutorials or contact me.

+

Here, you can find the answers to frequently asked questions. If + your question is unanswered, please review the video tutorials or + contact me.

  • Configuration -
    • +
  • How do I associate my + source file extensions with the correct editor?
    • +
  • Why must I put + ";@com.wudsn.ide.lng.hardware=..." in the source file?
    • +
  • Why do I see wrong messages + in the "Problems" view?
    • +
  • Editing -
    • +
  • Why is editing sometimes + slow, or is everything blocked, showing the wait cursor?
    • +
  • Is there support for + source version control?
    • +
  • Is there support for + the block selection mode?
    • +
  • Why does "CTRL-Space" not + open content assist?
    • +
  • Why do "CTRL-SHIFT-0/9" + and other key combinations not work?
    • +
  • Compiling -
    • +
  • Why is MADS the primary + compiler?
    • +
  • Why do I get the + error "No ORG defined" when compiling the example from the + tutorial?
    • +
  • Why are the errors + and warnings from an included file assigned to the primary source + file in the problems view?
    • +
  • How do I convert + from ATASM format to MADS format?
    • +
  • How does ATASM generate + segments in executable files?
    • +
  • How do I compile into ROM + images?
    • +
  • How do I compile into disk + images?
    • +
  • How to run a makefile script + instead of an emulator?
    • +
  • Emulation -
    • +
  • How can I use other + emulators?
    • +

    Installation

    How do I install Java?

    -

    I recommend you visit OpenJDK and follow the instructions to download and - install the latest version. Make sure the Java version, the Eclipse version, and your operating system have the - same architecture. Newer versions of Java only support 64-bit architectures.

    +

    + I recommend you visit OpenJDK + and follow the instructions to download and install the latest + version. Make sure the Java version, the Eclipse version, and your + operating system have the same architecture. Newer versions of Java + only support 64-bit architectures. +

    -

    When I try to start a .jar file via double-click, nothing happens. What is wrong?

    -

    You probably have the wrong Java version installed or set a default. Open a shell window and enter "java -jar - <yourfile.jar>". If this works, then you have the wrong program or java version associated with the - ".jar" file extension in the registry. You can fix that by setting the path to the correct Java installation - folder using "REGEDIT.EXE" for the path "Compute\HKEY_CLASSES_ROOT\jarfile\shell\open".

    -

    Java jar file registry entry

    -

    If starting from the command line does not work, you should see a more detailed error message about the - reason for that.

    +

    Nothing happens When I try to start a .jar file via + double-click. What is wrong?

    +

    You probably have the wrong Java version installed or set a + default. Open a shell window and enter "java -jar + <yourfile.jar>". If this works, then you have the wrong program + or Java version associated with the ".jar" file extension in the + registry. You can fix that by setting the path to the correct Java + installation folder using "REGEDIT.EXE" for + "Compute\HKEY_CLASSES_ROOT\jarfile\shell\open".

    +

    + Java jar file registry entry +

    +

    If starting from the command line does not work, you should see + a more detailed error message about why.

    How do I install Eclipse?

    -

    If you are not familiar with Eclipse at all, make sure that you have installed the Eclipse platform - distribution only - without Java or J2EE tools. This distribution is much smaller (normally around - 60-80 MB instead of 170 MB) and will not confuse you with tons of features and buttons you do not need at - all. See the section "Installing Eclipse" on the tab "Installation" for the required steps. If you use - Windows, you can use one of the zero installation distributions of WUDSN IDE which are linked on the tab - "Installation". They are simply ".zip" archives that already contain Eclipse and everything else."

    +

    + If you are unfamiliar with Eclipse, ensure you have installed the Eclipse + platform distribution without Java or J2EE tools. This distribution + is much smaller (typically around 60-80 MB instead of 170 MB) and + will not confuse you with many features and buttons you do not need. + See the "Installing Eclipse" section for the required steps on the " + Installation " tab. If you use Windows, you can use one of the zero + installation distributions of WUDSN IDE, which are linked on the tab + "Installation". They are ".zip" archives containing Eclipse and + everything else." +

    -

    When I try to start Eclipse I get an error like "Failed to load the JNI shared library 'C:\Program Files +

    When I try to start Eclipse, I get an error like "Failed to + load the JNI shared library 'C:\Program Files (x86)\Java\jre6\bin\client\jvm.dll'". What is wrong?

    -

    The Eclipse version and the Java version on your system are not compatible. The Eclipse is not pure Java but - uses platform-specific native libraries to run and debug Java efficiently. For example, you must install the - 64-bit version of Java (JRE or JDK) if you want to use the 64-bit version of Eclipse. This is a frequent - issue under Windows 7 because by default there is only the 32-bit version of Java installed. See the section - "Installing Eclipse" on the tab "Installation" for the required steps.

    +

    The Eclipse version and the Java version on your system are not + compatible. The Eclipse is not pure Java but uses platform-specific + native libraries to run and debug Java efficiently. For example, you + must install the 64-bit version of Java (JRE or JDK) if you want to + use the 64-bit version of Eclipse. This is a frequent issue under + Windows 7 because, by default, only the 32-bit version of Java is + installed. See the "Installing Eclipse" section for the required + steps on the " Installation " tab.

    How do I use Eclipse at?

    -

    Start the built-in help of Eclipse via the menu "Help/Help Content" and read the section "Workbench User - Guide".

    - Workbench user guide +

    Start the built-in help of Eclipse via the "Help/Help Content" + menu and read the "Workbench User Guide" section.

    + Workbench user guide

    Why is WUDSN IDE not available via the update site?

    -

    Most likely you typed in the wrong update site URL, for example, using "wusdn" instead of "wudsn". The - correct URL is "http://www.wudsn.com/update". In addition, you should disable the checkbox "Hide items that - are already installed", so you see what really is there. See the section "Installing WUDSN IDE" on the tab - "Installation" for the required steps.

    - Installation dialog with update site +

    You likely typed in the wrong update site URL, for example, + using "wusdn" instead of "wudsn". The correct URL is + "http://www.wudsn.com/update". In addition, you should uncheck the + checkbox "Hide items that are already installed" to see what is + there. See the "Installing WUDSN IDE" section for the required steps + on the " Installation " tab.

    + Installation dialog with update site
    -

    Why do I get "Unable to read repository at ... Read timed out" when accessing the update site?

    -

    This error message indicates the Eclipse program is somehow blocked from accessing the site. If you are - behind a proxy server, check the general proxy server settings in the Eclipse preferences. If you use a - firewall or internet security tool, make sure "Eclipse.exe", "java.exe", "javaw.exe" or the corresponding - program on your host platform are allowed to cannot to the internet. Maybe you have to change the settings, - so you are prompted to allow access interactively.

    +

    Why do I get "Unable to read repository at ... Read timed + out" when accessing the update site?

    +

    This error message indicates the Eclipse program is somehow + blocked from accessing the site. If you are behind a proxy server, + check the general proxy server settings in the Eclipse preferences. + If you use a firewall or internet security tool, make sure + "Eclipse.exe", "java.exe", "javaw.exe," or the corresponding program + on your host platform are allowed to cannot to the internet. Maybe + you have to change the settings so you are prompted to allow access + interactively.

    -

    Why do I get "Cannot complete the install because one or more required items could not be found" when - updating the plugin from the update site?

    -

    This error message indicates that the Eclipse version you are running is too old. - Check the releases page for - the required minimum Eclipse version for every WUDSN IDE release.

    +

    Why do I get "Cannot complete the install because one or more + required items could not be found" when updating the plugin from the + update site?

    +

    + This error message indicates that the Eclipse version you are running + is too old. Check the releases page for the + required minimum Eclipse version for every WUDSN IDE release. +

    -

    Why is the "Assembler" section not visible in the preferences?

    -

    If the WUDSN IDE sections and features are not visible after a successful installation, you are probably - using an outdated Java version. For example, Java 1.6 is out of maintenance since 2013/02. This seems to be a common problem on Mac - OS X even in Mavericks (10.9), which still uses Java 1.6 by default. Make sure you have at least the Java - version that is mentioned in the installation section for the IDE installed and that Eclipse is actually - started using that version.

    +

    Why is the "Assembler" section not visible in the + preferences?

    +

    + If the WUDSN IDE sections and features are not visible after a + successful installation, you probably use an outdated Java version. + For example, Java 1.6 has been out of maintenance + since 2013/02. This seems to be a common problem on Mac OS X, even + in Mavericks (10.9), which still uses Java 1.6 by default. Ensure you + have at least the Java version mentioned in the installation section + for the IDE installed and that Eclipse has started using that + version. +

    Configuration

    Why do I see wrong messages in the "Problems" view?

    -

    The default configuration of the "Problems" view shows all errors from all files in the current project. - While this is a good default for Java programming, it does not fit at all for compiling single independent - assembler files. Therefore you have to configure the "Problems" view accordingly. See the section - "Installing Eclipse" on the tab "Installation" for the required steps.

    +

    The default configuration of the "Problems" view shows all + errors from all files in the current project. While this is a good + default for Java programming, it is unsuitable for compiling single + independent assembler files. Therefore, you have to configure the + "Problems" view accordingly. See the "Installing Eclipse" section for + the required steps on the " Installation " tab.

    -

    How do I associate my source file extensions with the correct editor?

    -

    The IDE supports many different compilers and provides a specialized editor for each of them. Typically you - have some preferred source file extension (".asm" or ".a") and a preferred compiler. The procedure to - associate the file extension with the editor via the preferences is described in this video tutorial WUDSN IDE Tutorial 3: Setting up Editors and File - Extensions correctly.

    +

    How do I associate my source file extensions with the correct + editor?

    +

    + The IDE supports many different compilers and provides a specialized + editor for each. Typically, you have some preferred source file + extension (".asm" or ".a") and a preferred compiler. The procedure to + associate the file extension with the editor via the preferences is + described in this video tutorial WUDSN IDE + Tutorial 3: Setting up Editors and File Extensions correctly. +

    -

    Why do I have to put ";@com.wudsn.ide.lng.hardware=..." in the source file?

    -

    The association with the file extension with the editor for your compiler (that is done in the preferences, - see before) does not determine for which platform you want to create output. Therefore this additional - annotation in the main source file is required used to tell the IDE which is the target platform. It is used - to find the correct compiler and emulator settings, which can differ per platform. Every compiler has a - default platform (see the online help in the IDE) but can also be used on every other platform. Therefore - you have to specify the target platform in the main source file if you use a non-default platform.

    +

    Why must I put ";@com.wudsn.ide.lng.hardware=..." in the + source file?

    +

    The association with the file extension with your compiler's + editor (done in the preferences; see before) does not determine which + platform you want to create output. Therefore, this additional + annotation in the main source file must tell the IDE, which is the + target platform. It is used to find the correct compiler and emulator + settings, which can differ per platform. Every compiler has a default + platform (see the online help in the IDE), but it can also be used on + every other platform. Therefore, you must specify the target platform + in the main source file if you use a non-default platform.

    Editing

    -

    Why is editing sometimes slow or even everything blocked showing the wait cursor?

    -

    The core of WUDSN IDE uses the Eclipse Platform Runtime only and does not require any additional plugins. It - starts and runs very fast with that configuration and I personally used it on daily basis. So if you - experience performance problems, try to download and run the zero installation distribution of WUDSN IDE. - Performance problems are very likely caused by additional plugins or themes installed. Often these - plugins are not only slow but broken. Check the ".metadata/.log" file in the workspace folder. In some - Eclipse versions, this is also available via "Window/Show View.../Error Log".

    +

    Why is editing sometimes slow, or is everything blocked, + showing the wait cursor?

    +

    The core of WUDSN IDE uses the Eclipse Platform Runtime only + and does not require any additional plugins. It starts quickly and + dashes with that configuration, and I use it daily. So, if you + experience performance problems, try to download and run the zero + installation distribution of WUDSN IDE. Performance problems are very + likely caused by additional plugins or themes installed. Often, these + plugins are not only slow but broken. Check the ".metadata/.log" file + in the workspace folder. In some Eclipse versions, this is available + via "Window/Show View.../Error Log".

    Is there support for source version control?

    -

    Yes, there are several plugins available to connect Eclipse to CVS or subversion. Also, the "Local History" - feature is installed by default. You can configure it in the preferences. It automatically records all - changes to the source file and lets you compare versions in place.

    - Source version control +

    Yes, several plugins are available to connect Eclipse to CVS or + subversion. Also, the "Local History" feature is installed by + default. You can configure it in the preferences. It automatically + records all changes to the source file and lets you compare versions + in place.

    + Source version control
    -

    Is there support for block selection mode?

    -

    Yes, there is a toolbar button and the shortcut "ALT+SHIFT+A" to toggle block selection mode in all text - editors. This can be very useful for adding and removing common prefixes such as line numbers.

    - Is there support for a block selection mode? +

    Yes, a toolbar button and the shortcut "ALT+SHIFT+A" to toggle + block selection mode in all text editors. This can be useful for + adding and removing common prefixes such as line numbers.

    + Toggle block selection mode -

    In case the toolbar button is not visible, you have to set it to visible via the menu entry "Customize - Perspective" in the context menu of the main toolbar. In the customizing dialog, you have to activate the - commend group "Editor Presentation" and then the toolbar entries you want to see.

    - If the toolbar button is not visible, you have to set it to + visible via the menu entry "Customize Perspective" in the context + menu of the main toolbar. In the customizing dialog, you must + activate the "Editor Presentation" command group and the toolbar + entries you want to see.

    + Toggle block selection mode
    -

    Why does CTRL-Space not open content assist?

    -

    There is a known key conflict when using Messenger Plus Live! v4.85.0.386 with Microsoft Messenger 2009 on - Windows 7 Ultimate. This may also occur in other versions of course. Justin Payne has provided the following - description of the solution.

    +

    Why does "CTRL-Space" not open content assist?

    +

    There is a known keyboard assignment conflict when using + Messenger Plus Live! v4.85.0.386 with Microsoft Messenger 2009 on + Windows 7 Ultimate. This may also occur in other versions, of course. + Justin Payne has provided the following description of the solution.

    1. Startup and log into MS Messenger.
      2. -
    2. From the main window, hit the ALT key to bring up the main menu and select "Plus! | Preferences & - Options".
      3. -
    3. From the Preferences Windows, Select the Messenger tab and uncheck "Activate Messenger Lock with a - system-wide shortcut" OR change the value in its text box to something other than "CTRL + Space"
      4. +
    4. From the main window, hit the ALT key to bring up the main + menu and select "Plus! | Preferences & Options".
      5. +
    5. From the Preferences windows, Select the Messenger tab and + uncheck "Activate Messenger Lock with a system-wide shortcut" OR + change the value in its text box to something other than "CTRL + + Space".
    6. Press the "OK" button.

    Why do CTRL-SHIFT-0/9 and other key combinations not work?

    -

    You probably have another program outside of Eclipse that has already captured these keys or key - combinations. A frequent problem is the Windows Input Methods Editor (IME) which is used to switch - keyboard layouts. For example, if you are using multiple keyboard layouts, the CTRL-Space is mapped to - allow you to cycle between the different keyboard regional layouts. You should probably be aware of how - to turn the feature off since you're probably using this feature, but if you don't...

    +

    You probably have another program outside of Eclipse that has + already captured these keys or key combinations. A frequent problem + is the Windows Input Methods Editor (IME), which is used to switch + keyboard layouts. For example, if you use multiple keyboard layouts, + the CTRL-Space is mapped to allow you to cycle between the different + keyboard regional keyboard layouts. You should be aware of how to + turn the feature off since you're probably using this feature, but + if you don't...

    Windows 7

    1. Within "Windows Control Panel", open "Region and Settings".
      2. -
    2. Select the "Keyboard and Languages" tab, select "Change Keyboards...".
      3. -
    3. In the "Text Services and Input Languages" windows, select "Advanced Key Settings".
      4. -
    4. In the "Hot Keys for input languages" list box, select "Between input languages" and then select - "Change Key Sequence..."
      5. -
    5. In the "Change Key Sequence" window, choose another radio button other than the one next to - CTRL+Shift. At best you choose "(None)".
      6. -
    6. Click OK until you closed all popup windows.
      7. +
    7. Select the "Keyboard and Languages" tab and "Change + Keyboards...".
      8. +
    8. In the "Text Services and Input Languages" windows, select + "Advanced Key Settings".
      9. +
    9. In the "Hot Keys for input languages" list box, select + "Between input languages" and then select "Change Key Sequence..."
      10. +
    10. In the "Change Key Sequence" window, choose another radio + button other than the one next to CTRL+Shift. At best, you choose + "(None)".
      11. +
    11. Click OK until you close all popup windows.

    Windows 10

      -
    1. Open "Control Panel\Clock, Language, and Region\Language\Advanced settings.
      2. -
    2. Click "Change Language bar hot keys".
      3. +
    3. Open "Control Panel\Clock, Language, and + Region\Language\Advanced settings.
      4. +
    4. Click the "Change Language bar hot keys".
    5. Set all key sequences to "(None)".
      6. -
    6. Click OK until you closed all popup windows.
      7. +
    7. Click OK until you close all popup windows.
    -

    Of course, this is Windows 7/10 and we know how Microsoft loves to change their layouts and names, but in - fact, this option is available back to Windows XP.
    + Of course, this is Windows 7/10, and we know how Microsoft loves to + change its layouts and names, but this option is available back to + Windows XP.
    Configure Windows IME hot keys

    + alt="Configure Windows IME hot keys" /> +

    Compiling

    Why is MADS the primary compiler?

    -

    When I started with WUDSN IDE, ATASM was the first supported compiler. The reason was simple: 90% of my - sources are in ATASM format. ATASM is very comprehensive and fast. Its capabilities to define constants - and byte sequences are very complete (".BYTE", ".WORD", ".DBYTE", ".FLOAT", ".SBYTE" for ATASCII, - ".CBYTE" for terminated strings, separate offset for all constants). Over time additional platform - compilers have been added and support for them will be completed step by step. When the support for MADS - was rather complete, I found that it is the most powerful compiler I have ever seen and used. The - support for ".PROC/.ENDPROC" has revolutionized the way I write assembler code now. It allows logical - structuring and visibility control without any runtime overhead. At the same time, MADS is compatible - with MAC/65 and XASM, and even ATASM sources can be adapted to MADS with a few minor changes described - below. Therefore MADS is the primary compiler since WUDSN IDE version 1.6.0.

    +

    When I started with WUDSN IDE, ATASM was the first supported + compiler. The reason was simple: 90% of my sources are in ATASM + format. ATASM is very comprehensive and fast. Its capabilities to + define constants and byte sequences are extensive (".BYTE", ".WORD", + ".DBYTE", ".FLOAT", ".SBYTE" for ATASCII, ".CBYTE" for terminated + strings, separate offset for all constants). Over time, additional + platform compilers have been added, and their support will be + completed step by step. When the support for MADS was relatively + complete, I found it the most powerful compiler I have ever seen and + used. The support for ".PROC/.ENDPROC" has revolutionized how I + write assembler code. It allows logical structuring and visibility + control without any runtime overhead. At the same time, MADS is + compatible with MAC/65 and XASM, and even ATASM sources can be + adapted to MADS with a few minor changes described below. Therefore, + MADS has been the primary compiler since WUDSN IDE version 1.6.0.

    -

    Why do I get the error "No ORG defined" when compiling the example from the tutorial?

    -

    Since WUDSN IDE version 1.6.0 MADS is the primary compiler that is registered for the file extensions - ".asm" upon installation. You are trying to run the code example for version 1.5.0 or before, which is - in ATASM format. Therefore you can either

    +

    Why do I get the error "No ORG defined" when compiling the + example from the tutorial?

    +

    Since WUDSN IDE version 1.6.0 MADS is the primary compiler + registered for the file extensions ".asm" upon installation. You are + trying to run the code example for version 1.5.0 or before, which is + in ATASM format. Therefore, you can either.

    -

    Why are the errors and warnings from an include file assigned to the main source file in the problems - view?

    -

    You use a case-insensitive file system and have used different upper or lower case writing in the source - include statement than in the actual file system. For example, you have written "ICL 'example.asm'" for - a file named "Example.asm" on the file system. In Eclipse the file names of all resources are treated as - case-sensitive, even if the underlying file system is case-insensitive. Therefore the file name issued - by the compiler will not match the file name of the source include. As a fallback, the IDE assigns - the error message to the main source file. To fix this, you have to adapt the spelling of the file name - in the source include statement.

    +

    Why are the errors and warnings from an included file + assigned to the primary source file in the problems view?

    +

    You use a case-insensitive file system and have used different + upper or lower-case writing in the statement than in the actual file + system. For example, you have written "ICL 'example.asm'" for a file + named "Example.asm" on the file system. In Eclipse, the file names + of all resources are treated as case-sensitive, even if the + underlying file system is case-insensitive. Therefore, the file name + issued by the compiler will not match the file name. The IDE assigns + the error message to the primary source file as a fallback. To fix + this, you must adapt the spelling of the file name in the source + include statement.

    -

    How do I convert an ATASM source to MADS format?

    -

    Because both ATASM's and MADS's syntax are based on the MAC/65 syntax. There are not really many - differences. Therefore manual conversion using "Find/Replace (CTRL-F)" is very easy.

    +

    How do I convert from ATASM format to MADS format?

    +

    Because both ATASM's and MADS's syntax are based on the MAC/65 + syntax. There are not many differences. Therefore, manual conversion + using "Find/Replace (CTRL-F)" is easy.

      -
    • Replace the origin definition "* = address" with "ORG address".
      • +
    • Replace the origin definition "* = address" with "ORG + address".
    • Replace ".INCLUDE" with "ICL" for source includes.
    • Replace ".INCBIN" with "INS" for binary includes.
      • -
    • Replace "* = $2E0; .WORD address" with "RUN address" to specify the run address.
      • -
    • Replace "* = $2E2; .WORD address" with "INI address" to specify the init address.
      • -
    • Check the quotes of ".BYTE" and "DTA" statements. In MADS, single quotes result in ASCII codes, - double quotes in ATARI screen codes.
      • -
    • Remove all ".BANK" statements. While ATASM sorts and merges all segments within one bank statement, - MADS simply uses the order of segments as defined in the source file. Every "ORG" statement +
    • Replace "* = $2E0; .WORD address" with "RUN address" to + specify the run address.
      • +
    • Replace "* = $2E2; .WORD address" with "INI address" to + specify the initialization address.
      • +
    • Check the quotes of ".BYTE" and "DTA" statements. In MADS, + single quotes result in ASCII codes and double quotes in ATARI + screen codes.
      • +
    • Remove all ".BANK" statements. While ATASM sorts and merges + all segments within one bank statement, MADS uses the order of + segments defined in the source file. Every "ORG" statement automatically generates a new file segment.

    How does ATASM generate segments in executable files?

    -

    A helpful feature for small projects is that by default ATASM sorts the segments by address and warns if - the same address is overwritten by code or data. Since version 1.05 the ".BANK" directive is available, - which allows you to create COM files with "INITAD" segments and arbitrary segment counts. If you don't - use the ".BANK" directive, ATASM will sort the segments by their address and will put consecutive blocks - into a single segment by default. While this saves some bytes, it might be confusing if you are used to - other assemblers. Note that you have to use the ".SET 6" directive to set the assembler origin offset in - every bank if you use it in one of the banks.

    -
    ; Bank 0
    .bank
    .set 6,0
    - * = $8000
    start lda #0
    jmp *

    ; Bank 1
    .bank .set 6,0
    * = $2e0 -
    .word start;

    ; Bank 2
    .bank
    .set 6,$4300-$C000
    * = $C000 -
    lda #1
    sta label+1
    label lda #2
    jmp *
    +

    A helpful feature for small projects is that, by default, + ATASM sorts the segments by address and warns if the same address is + overwritten by code or data. Since version 1.05, the ".BANK" + directive is available, which allows you to create COM files with + "INITAD" segments and arbitrary segment counts. If you don't use the + ".BANK" directive, ATASM will sort the segments by their address and + put consecutive blocks into a single segment by default. While this + saves some bytes, it might be unclear if you are used to other + assemblers. Note that you must use the ".SET 6" directive to set the + assembler origin offset in every bank if you use it in one of the + banks.

    +
    + ; Bank 0
    .bank
    .set 6,0
    * = $8000
    start + lda #0
    jmp *

    ; Bank 1
    .bank .set 6,0
    * + = $2e0
    .word start;

    ; Bank 2
    .bank
    .set + 6,$4300-$C000
    * = $C000
    lda #1
    sta label+1
    label + lda #2
    jmp * +

    How do I compile into ROM images?

    -

    Plain ROM Images do not have header bytes by default, or at least they do not have the same header bytes - as executable files. In order to create raw object files without headers, compiler-specific options have - to be used. Some cases are listed below. See the manual of the specific compiler for more details.

    +

    Plain ROM Images do not have header bytes by default, or at + least they do not have the same header bytes as executable files. + Compiler-specific options must be used to create raw object files + without headers. Some cases are listed below. See the manual of the + specific compiler for more details.

      -
    • ACME: Use the compiler parameter " -f plain " instead of "-f cbm" (default) to switch to - "plain" mode without a header
      • -
    • ATASM: Extend the compiler parameter "-o${outputFilePath}" to " -r -o${outputFilePath}" to - switch to "raw" mode without header
      • -
    • MADS: Use " OPT h-f+ " at the very beginning of the source file to disable the COM header and enable - "fill" mode, i.e. no segments are created if there are gaps in the object code
      • +
    • ACME: Use the compiler parameter " -f plain " + instead of "-f cbm" (default) to switch to "plain" mode without a + header +
      • +
    • ATASM: Extend the compiler parameter "-o${outputFilePath}" + to " -r -o${outputFilePath}" to switch to "raw" mode without + header +
      • +
    • MADS: Use " OPT h-f+ " at the very beginning of the + source file to turn off the COM header and enable "fill" mode, + i.e., no segments are created if there are gaps in the object code +

    How do I compile into disk images?

    Atari 8-bit
    -

    For Atari 8-bit, the ATASM compiler has a dedicated parameter to write the executable file directly into - ".ATR" or ".XFD" disk images. The disk image must be formatted with Atari DOS 2.0S, Atari DOS DOS 2.5, - or a compatible DOS. All Atari 8-bit disk formats can be created using the "dir2atr.exe" tool of the AtariSIO - tools by Matthias Reichl (hias). The tool can create a complete disk image with arbitrary DOS - (Atari DOS 2.5, MyDos, SpartaDOS) and size based on a folder that contains "DOS.SYS", "DUP.SYS" (or the - equivalent files of the respective DOS) and all other files requires. I have packaged an example - including the "dir2atr" tool, a batch script to call the tool and the emulator, and the "files" folder - in this archive. Unpack the archive to your output folder. Double-click - "makefile.bat" to see how the disk image is created and started. Read section How to run a makefile script instead of an emulator? for the details on - how to configure the call to "makefile.bat". For productive usage, you should of course put the "hias" - folder into a central location and use the most recent version from hias' website. For MacOS X users, the - download also contains a "makefile.sh" script and MacOS X binaries of Matthias Reichl's tools. The - binaries have been provided by Fredrick Holst (freetz) and you can find the latest versions on his website.

    +

    + For Atari 8-bit, the ATASM compiler has a dedicated parameter to + write the executable file directly into ".ATR" or ".XFD" disk + images. The disk image must be formatted with Atari DOS 2.0S, DOS + 2.5, or a compatible DOS. All Atari 8-bit disk formats can be + created using the "dir2atr.exe" tool of the AtariSIO tools by Matthias Reichl + (hias). The command line tool can create a complete disk image with + arbitrary DOS (Atari DOS 2.5, MyDos, SpartaDOS) and size based on a + folder that contains "DOS.SYS", "DUP.SYS" (or the equivalent files + of the respective DOS) and all other files requires. I have packaged + an example, including the "dir2atr" tool, a batch script to call the + command line tool and emulator, and this archive's "files" folder. + Unpack the archive to your output folder. Double-click + "makefile.bat" to see how the disk image is created and started. + Read the section "How to run a + makefile script instead of an emulator?" for the details on + configuring the call to "makefile.bat". For productive usage, you + should put the "hias" folder into a central location and use the + most recent version from Matthias Reichl's website. For MacOS X + users, the download also contains a "makefile.sh" script and MacOS X + binaries of Matthias Reichl's tools. The binaries have been provided + by Fredrick Holst (freetz), and you can find the latest versions on + his website. +

    Apple II
    -

    For Apple II, WUDSN IDE automatically generates a bootable AppleDos 3.3 disk image with the extension - ".dsk" if one of the predefined emulators is used for execution. If you want to use another DOS or disk - size or if you want to put more files onto the disk after compilation, you can use the command line - version of AppleCommander to achieve this. Create a makefile script and - configured it as described in How to run a makefile script instead of an - emulator?. In the case of Apple Disk images always remember to use the correct file - content/load/run address. The IDE needs to know the load address of an executable file in order to store - this information in the directory entry. To detect the load address from the executable file, the IDE - evaluates the file extension. Supported extensions are ".b", ".prg" and ".xex". Here's the logic for the - built-in disk image creation:

    +

    + For Apple II, WUDSN IDE automatically generates a bootable AppleDos + 3.3 disk image with the extension ".dsk" if one of the predefined + emulators is used for execution. If you want to use another DOS or + disk size or if you're going to put more files onto the disk after + compilation, you can use the command line version of AppleCommander to + achieve this. Create and configure a makefile script as described in + "How to run a makefile script instead + of an emulator?". In the case of Apple Disk images, always remember + to use the correct file content/load/run address. The IDE needs to + know the load address of an executable file to store this + information in the directory entry. The IDE evaluates the file + extension to detect the load address from the executable file. + Supported extensions are ".b", ".prg," and ".xex". Here's the logic + for the built-in disk image creation: +

      -
    • File extension ".b"
      // AppleDos 3.3 binary file: start-lo,start-hi,length-lo,length-hi,data -
      address = getWord(outputFileContent, 0);length = length - 4;content = - getData(outputFileContent, 4);
      • -
    • File extension ".prg" and length > 2
      // C64 program file: start-lo,start-hi,data
      - address = getWord(outputFileContent, 0);length = length - 2;content = getData(outputFileContent, 2); +
    • File extension ".b"
      // AppleDos 3.3 binary file: + start-lo, start-hi, length-lo, length-hi, data
      address = + getWord(outputFileContent, 0);length = length - 4;content = + getData(outputFileContent, 4); +
      • +
    • File extension ".prg" and length > 2
      // C64 + program file: start-lo, start-hi, data
      address = + getWord(outputFileContent, 0);length = length - 2;content = + getData(outputFileContent, 2); +
      • +
    • File extension ".xex" and length > 6 and + (getWord(outputFileContent, 0) & 0xffff) == 0xffff)
      // + AtariDOS 2.5 binary file:$ff, $ff, start-lo, start-hi, end-lo, + end-hi, data
      address = getWord(outputFileContent, 2);length + = length - 6;content = getData(outputFileContent, 6);
      • -
    • File extension ".xex" and length > 6 and (getWord(outputFileContent, 0) & 0xffff) == 0xffff) -
      // AtariDOS 2.5 binary file:$ff,$ff,start-lo,start-hi,end-lo,end-hi,data
      address = - getWord(outputFileContent, 2);length = length - 6;content = getData(outputFileContent, 6);
    -
    Other hardwares
    -

    If you find a tool similar to "dir2atr.exe" for the Atari 8-bit or "AppleCommander" for the Apple II, you - can use create your own script and run it as described in How to run a - makefile script instead of an emulator?.

    +
    Other hardware
    +

    + If you find a tool similar to "dir2atr.exe" for the Atari 8-bit or + "AppleCommander" for the Apple II, you can create your script and + run it as described in "How to run a + makefile script instead of an emulator?". +

    How can I run a makefile or script instead of an emulator?

    -

    Sometimes it is useful to run a makefile script instead of the emulator, for example, if the output file - shall be combined with other files into a single ATR file. To execute such a script select "User Defined - Application" as the "Default Application to open Output File". Specify the path to the shell as "Path to - Application". On the command line, you can then use the standard variables to start the shell, pass the - name of the script and pass the file path of the compiled output file. Since the working directory at - the time of execution is the output folder of the compiler you must place the script file there or you - must specify the script file with its absolute path. If you are using Windows and "cmd.exe" as your - shell, you must specify "/c" before the name of the script to prevent "cmd.exe" from remaining as a - process after the script has finished. The resulting command line is "${runnerExecutablePath} /c - makefile.bat ${outputFilePath}", assuming "makefile.bat" is located in the output folder". See section - How do I compile into disk images? for the description of how to use this - for compiling complete disk images.

    - + Sometimes, running a makefile script instead of the emulator is + helpful, for example, if the output file is combined with other + files into a single ATR file. To execute such a script, select "User + Defined Application" as the "Default Application to open Output + File". Specify the path to the shell as "Path to Application". On + the command line, you can then use the standard variables to start + the command shell and pass the script's name and the file path of + the compiled output file. Since the working directory during + execution is the compiler's output folder, you must place the script + file there or specify the script file with its absolute path. If you + are using Windows and "cmd.exe" as your shell, you must add "/c" + before the name of the script to prevent "cmd.exe" from remaining as + a process after the script has finished. The resulting command line + is "${runnerExecutablePath} /c makefile.bat ${outputFilePath}", + assuming "makefile.bat" is located in the output folder". See + section "How do I compile into disk + images?" for the description of how to use this for compiling + complete disk images. +

    + Configure makefile script

    Emulation

    How can I use other emulators?

    -

    You can "re-use" the existing tabs and simply specify another emulator's executable. If you use "User - Defined Application", you can specify whatever you want. When using "User Defined Application", no disk - image is created or updated. You can use this setting to have your own script which puts the executable - file onto a disk image of your choice using additional tools like "dir2atr.exe" or "AppleCommander" for - example.

    +

    You can "re-use" the existing tabs and specify another + emulator's executable. Using "User Defined Application", you can + select whatever you want. When using "User Defined Application", no + disk image is created or updated. You can use this setting to have + your script, which puts the executable file onto a disk image of + your choice, using additional tools like "dir2atr.exe" or + "AppleCommander," for example.

    \ No newline at end of file diff --git a/com.wudsn.ide.lng/help/ide-features.section.html b/com.wudsn.ide.lng/help/ide-features.section.html index fbcef13d..403f6c18 100644 --- a/com.wudsn.ide.lng/help/ide-features.section.html +++ b/com.wudsn.ide.lng/help/ide-features.section.html @@ -2,32 +2,40 @@ -
    General IDE enhancements   » top
    +
    + General IDE enhancements   » top +
    Open folder action in context menuSort action in text editor context menu -
  • The online help contains the entry "WUDSN IDE Guide" which contains multiple sections. +
  • The online help contains the entry "WUDSN IDE Guide" which + contains multiple sections. -
    Integrated Help
    • +
    Integrated Help + -
    Fully integrated assembler editor   » top
    +
    + Fully integrated assembler editor   » top +
    -
    Content outline and source folding   » top
    +
    + Content outline and source folding   » top +
    -
    Content assist and code completion   » top
    +
    + Content assist and code completion   » top +
    - + -
    Hex Editor   » top
    +
    + Hex Editor   » top +
    This is very helpful to turn parts of a file into source code. The + possibility to copy/paste into the binary file itself in order to + modify is prepared but not working yet and will be completed later.
    + Hex Editor context menu -
  • The possible file modes for a binary file are computed automatically and used as default when opening the file +
  • Support for binary files, Atari COM files, and Atari Disk + Images
    Hex Editor file mode selection
    • +
  • The possible file modes for a binary file are computed + automatically and used as default when opening the file
  • Unsupported file modes are detected and cannot be used
    • -
  • Files with a block structure get an outline in the outline view
    • -
  • Files with a corrupted block structure are detected and displayed as good as possible
    Hex Editor outline view
    Hex Editor with corrupted Atari COM file
    • +
  • Files with a block structure get an outline in the outline + view
    • +
  • Files with a corrupted block structure are detected and + displayed as good as possible
    Hex Editor outline view
    Hex Editor with corrupted Atari COM file +
    • -
    Graphics Editor   »
    +
    + Graphics Editor   » +
    CompilerAseembler / Compiler Contributor
    MADS Tomasz Biela (tebe)
    Graphic library or toolGraphic Library or Tool Contributor
     
    Sound librarySound Library Contributor
    @@ -389,155 +498,211 @@
  • Viewer for GIF/JPG/BMP/PNG images
    • -
  • Available via context menu including multi-file-selection to open several files at once
    Open With Graphics Editor
    • -
  • The "Open With Graphics Editor" menu entry closes an existing editor in case the file is already opened and - thereby forces the file to be opened with the graphics editor. In addition, the graphics editor is set as the - default editor for this file. As a consequence double-clicking the file in the package explorer will open it - automatically with the graphics editor, no matter which type of file it actually is. This saves you from always - using the context menu, just because the file has no known file type. You can change the default editor again by - just using the "Open With" context menu entry
    • +
  • Available via context menu including multi-file-selection to + open several files at once
    Open With Graphics Editor +
    • +
  • The "Open With Graphics Editor" menu entry closes an existing + editor in case the file is already opened and thereby forces the file + to be opened with the graphics editor. In addition, the graphics + editor is set as the default editor for this file. As a consequence + double-clicking the file in the package explorer will open it + automatically with the graphics editor, no matter which type of file + it actually is. This saves you from always using the context menu, + just because the file has no known file type. You can change the + default editor again by just using the "Open With" context menu entry
  • Available via hyperlink navigation for binary includes
    • -
  • Conversion from binary files or 8-bit images files to GIF/JPG/BMP/PNG images +
  • Conversion from binary files or 8-bit images files to + GIF/JPG/BMP/PNG images - Conversion from binary files or 8-bit images files to GIF/JPG/BMP/PNG images
    • -
  • Conversion from GIF/JPG/BMP/PNG images to binary files or 8-bit images using JavaScript. + Conversion from binary files or 8-bit images files to GIF/JPG/BMP/PNG images +
    • +
  • Conversion from GIF/JPG/BMP/PNG images to binary files or + 8-bit images using JavaScript. -
    Conversion from GIF/JPG/BMP/PNG images to binary files or 8-bit images files
    • -
  • The image palette view associated with the graphics editor displays the palette entries and the color histogram. - It supports filtering of unused colors, sorting by index and color frequencies, pre-settings, and editing the - palette when displaying 8-bit images
    Image palette view +
  • Separate aspect ratio for loading and displaying the image + file
    • +
  • Default scripts are included. They can be adjusted and saved + along with the other parameters
    • +
    Conversion from GIF/JPG/BMP/PNG images to binary files or 8-bit images files -
  • Conversion files with extension ".cnv" are used to save the conversion direction and all conversion parameters -
    • -
  • Support for relative file paths. If the file path is in the same folder as the ".cnv" file, it is automatically - converted to a relative file path when the file name is defaulted or picked from the file browser dialog. This - allows to move the ".cnv" file and the referenced source files around together without breaking the saved paths +
  • The image palette view associated with the graphics editor + displays the palette entries and the color histogram. It supports + filtering of unused colors, sorting by index and color frequencies, + pre-settings, and editing the palette when displaying 8-bit images
    + Image palette view
    • +
  • Conversion files with extension ".cnv" are used to save the + conversion direction and all conversion parameters
    • +
  • Support for relative file paths. If the file path is in the + same folder as the ".cnv" file, it is automatically converted to a + relative file path when the file name is defaulted or picked from the + file browser dialog. This allows to move the ".cnv" file and the + referenced source files around together without breaking the saved + paths
    • -
    Preferences for editing   » top
    +
    + Preferences for editing   » top +
    -
    Preferences for compiling   » top
    +
    + Preferences for compiling   » top +
    Make sure that you don't remove parameters when you specify your own + values
    If not, either creating the label definition file or + parsing the compiler log may fail -
  • Preferences can be maintained for all possible applications of all compilers in parallel +
  • Preferences can be maintained for all possible applications of + all compilers in parallel
    • -
  • Download links, configurable paths, and default command lines for Atari++, Atari800Win, Atari800MacX emulators - per compiler
    • -
  • The default file extension filter is set to "*.exe" on Windows and "*.*" on all other operating systems
    - Preferences for compilers
    • +
  • Download links, configurable paths, and default command lines + for Atari++, Atari800Win, Atari800MacX emulators per compiler
    • +
  • The default file extension filter is set to "*.exe" on Windows + and "*.*" on all other operating systems
    Preferences for compilers +
    • -
    Annotations for compiling   » top
    +
    + Annotations for compiling   » top +
    -
    Known bugs   » top
    +
    + Known bugs   » top +

    Open bugs:

    Fixed bugs:

    -
    Planned features   » top
    +
    + Planned features   » top +
    -
    Installing Altirra, Atari800 and other emulators   » top
    +
    + Installing Altirra, Atari800, and other emulators   » top +
    -
    Creating and compiling an example project   » top
    +
    + Creating and compiling an example project   » + top +
    -
    Further information on assembler programming   » top
    +
    + Further information on assembler programming   » top +
    \ No newline at end of file diff --git a/com.wudsn.ide.lng/help/ide-releases.section.html b/com.wudsn.ide.lng/help/ide-releases.section.html index 90283495..9ab20353 100644 --- a/com.wudsn.ide.lng/help/ide-releases.section.html +++ b/com.wudsn.ide.lng/help/ide-releases.section.html @@ -1,8 +1,12 @@ -

    The following table lists all releases of WUDSN IDE, the required minimum Java - and Eclipse version, the link to the - release news article, and the release news video. For releases before 1.6.0 no downloads and no videos are offered. - The latest stable version is always available via the update site "https://www.wudsn.com/update/stable". The daily version - and older versions are available via version-specific update sites listed below.

    +

    + The following table lists all releases of WUDSN IDE, the required + minimum Java + and Eclipse + versions, the link to the release news article, and the release news + video. The latest stable version is always available via the update + site "https://www.wudsn.com/update/stable". The daily and older + versions are available via version-specific update sites listed below. +

    @@ -17,11 +21,12 @@ - - + @@ -30,8 +35,9 @@ - + @@ -40,11 +46,10 @@ - - + + @@ -52,10 +57,11 @@ - - + + @@ -63,10 +69,11 @@ - - + + @@ -74,10 +81,11 @@ - - + + @@ -85,10 +93,11 @@ - - + + @@ -96,10 +105,11 @@ - - + + @@ -107,10 +117,11 @@ - - + + @@ -118,10 +129,11 @@ - - + + @@ -129,10 +141,11 @@ - - + + @@ -140,8 +153,9 @@ - + @@ -150,8 +164,9 @@ - + @@ -160,8 +175,9 @@ - + @@ -170,8 +186,9 @@ - + @@ -180,8 +197,9 @@ - + @@ -190,8 +208,9 @@ - + @@ -200,8 +219,9 @@ - + @@ -210,8 +230,9 @@ - + @@ -220,24 +241,35 @@ - +
    daily updated permanentlyJava 11 + Java 11 4.19 https://www.wudsn.com/update/dailyreadread n/a
    Java 11 4.19 https://www.wudsn.com/update/stablereadread Planned
    Java 1.8 4.10 https://www.wudsn.com/update/1.7.1readPlanned - - readPlanned
    1.7.0Java 1.6 4.3.1 https://www.wudsn.com/update/1.7.0readwatchreadwatch
    1.6.6Java 1.6 4.3.1 https://www.wudsn.com/update/1.6.6readwatchreadwatch
    1.6.5Java 1.7 4.3.1 https://www.wudsn.com/update/1.6.5readwatchreadwatch
    1.6.4Java 1.6 3.6.0 https://www.wudsn.com/update/1.6.4readwatchreadwatch
    1.6.3Java 1.6 3.6.0 https://www.wudsn.com/update/1.6.3readwatchreadwatch
    1.6.2Java 1.6 3.6.0 https://www.wudsn.com/update/1.6.2readwatchreadwatch
    1.6.1Java 1.6 3.6.0 not availablereadwatchreadwatch
    1.6.0Java 1.5 3.6.0 https://www.wudsn.com/update/1.6.0readwatchreadwatch
    1.5.0Java 1.5 3.6.0 not availablereadread not available
    Java 1.5 3.3.0 not availablereadread not available
    Java 1.5 3.3.0 not availablereadread not available
    Java 1.5 3.3.0 not availablereadread not available
    Java 1.5 3.3.0 not availablereadread not available
    Java 1.5 3.3.0 not availablereadread not available
    Java 1.5 3.3.0 not availablereadread not available
    Java 1.5 3.3.0 not availablereadread not available
    Java 1.5 3.3.0 not availablereadread not available
    -

    Before version 1.7.2, so-called "zero installation distributions" were been provided for Windows. They contain the Eclipse Platform, the Java Runtime Environment, the latest stable version of the WUDSN IDE plugin, -all supported compilers, and an emulator for each supported platform. All paths to folders, compilers, and emulators -are pre-configured. Unpack the content of this archive to the directory "C:\jac\wudsn" and click the "WUDSN IDE-64 -bit" link. Eclipse will open with the predefined workspace that contains "Hello World" examples for different platforms.

    +

    Before version 1.7.2, so-called "zero installation distributions" + were provided for Windows. They contain the Eclipse Platform, the Java + Runtime Environment, the latest stable version of the WUDSN IDE plugin, + all supported compilers, and an emulator for each platform. All paths + to folders, compilers, and emulators are pre-configured. Unpack the + content of this archive to the directory "C:\jac\wudsn" and click the + "WUDSN IDE-64 bit" link. Eclipse will open with the predefined + workspace that contains "Hello World" examples for different platforms.

    \ No newline at end of file diff --git a/com.wudsn.ide.lng/help/ide-tutorials.section.html b/com.wudsn.ide.lng/help/ide-tutorials.section.html index 80d56b4c..3105a186 100644 --- a/com.wudsn.ide.lng/help/ide-tutorials.section.html +++ b/com.wudsn.ide.lng/help/ide-tutorials.section.html @@ -1,87 +1,136 @@ -

    When I was thinking about creating tutorials, I decided not to simply write text but to create short videos instead. - They are best viewed in full-screen mode and in HD video resolution. I think this is the best way to show how things - are intended to be used. On the other hand, these tutorials cannot tackle every detail of a supported feature. So - please also check the features section. All videos are also available for download on - Pigwa

    +

    + When thinking about creating tutorials, I decided not to write text but + to create short videos. They are best viewed in full-screen mode and HD + video resolution. For me, videos are the best way to show how things + are intended to be used. On the other hand, these tutorials cannot + tackle every detail of a supported feature. So please also check the + features section. All videos are also available for download on Pigwa. +

    - - + + - - + + - - + + - - + + - - + + - - + + - - + + - - + +
    Part 1: Introduction, Installation and Use
    Tutorial part 1     		Part 2: Setting up Perspective, Views and Editors -
    Tutorial part 2     		Part 1: + Introduction, Installation and Use
    + Tutorial part 1 +     		Part + 2: Setting up Perspective, Views, and Editors
    + Tutorial part 2 +
    Part 3: Setting up Editors and File Extensions - correctly
    Tutorial part 3     		Part 4: Syntax Highlighting and Content Assist -
    Tutorial part 4     		Part + 3: Setting up Editors and File Extensions correctly
    + Tutorial part 3 +     		Part 4: + Syntax Highlighting and Content Assist
    + Tutorial part 4 +
    Part 5: Working with Projects, Folders and Files -
    Tutorial part 5     		Part 6: Content Outline and Navigation - the - Heart of the IDE
    Tutorial part 6 -     		Part 5: + Working with Projects, Folders and Files
    + Tutorial part 5 +     		Part + 6: Content Outline and Navigation - the Heart of the IDE
    + Tutorial part 6 +
    Part 7: New Features in Version 1.6.0
    - Tutorial part 7 -     		Part 8: New Features in Version 1.6.2
    - Tutorial part 8 -     		Part 7: New + Features in Version 1.6.0
    + Tutorial part 7 +     		Part 8: New + Features in Version 1.6.2
    + Tutorial part 8 +
    Part 9: Source Level Debugging
    - Tutorial part 9 -     		Part 10: Adding Support for an Additional - Assembler
    Tutorial part 10     		Part 9: Source Level + Debugging
    + Tutorial part 9 +     		Part + 10: Adding Support for an Additional Assembler
    + Tutorial part 10 +
    Part 11: New Features in Version 1.6.3
    - Tutorial part 11 -     		Part 12: New Features in Version 1.6.4
    - Tutorial part 12 -     		Part 11: New + Features in Version 1.6.3
    + Tutorial part 11 +     		Part 12: New + Features in Version 1.6.4
    + Tutorial part 12 +
    Part 13: New Features in Version 1.6.5
    - Tutorial part 13 -     		Part 14: New Features in Version 1.6.6
    - Tutorial part 14 -     		Part 13: New + Features in Version 1.6.5
    + Tutorial part 13 +     		Part 14: New + Features in Version 1.6.6
    + Tutorial part 14 +
    Part 15: New Features in Version 1.7.0
    - Tutorial part 13 -     		 Part 15: New + Features in Version 1.7.0
    + Tutorial part 13 +
    \ No newline at end of file