6502
/
wudsn-ide
mirror of https://github.com/peterdell/wudsn-ide.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update HTML documentation 

Spelling
This commit is contained in:
Peter Dell 2023-08-27 11:16:52 +02:00
parent 1931ed010a
commit 6f9f45c64b
6 changed files with 1579 additions and 1002 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
com.wudsn.ide.lng/help/ide-credits.section.html
View File

@ -4,7 +4,7 @@
<table>
<tbody>
<tr>
<th>Compiler</th>
<th>Aseembler / Compiler</th>
<th>Contributor</th>
</tr>
<tr>
@ -30,7 +30,7 @@
</tr>
<tr>
<td><a href="https://mads.atari8.info" target="_blank"
rel="noopener noreferrer">MADS</a></td>
rel="noopener noreferrer">MADS and Mad Pascal</a></td>
<td>Tomasz Biela (tebe)</td>
</tr>
<tr>
@ -49,7 +49,7 @@
</tbody>
<tbody>
<tr>
<th>Graphic library or tool</th>
<th>Graphic Library or Tool</th>
<th>Contributor</th>
</tr>
<tr>
@ -67,7 +67,7 @@
<td style="border-width: 0px; background-color: white;"> </td>
</tr>
<tr>
<th>Sound library</th>
<th>Sound Library</th>
<th>Contributor</th>
</tr>
<tr>

722
com.wudsn.ide.lng/help/ide-faq.section.html
View File

@ -1,395 +1,557 @@
<p>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.</p>
<p>Here, you can find the answers to frequently asked questions. If
your question is unanswered, please review the video tutorials or
contact me.</p>
<ul>
<li><a href="#Installation">Installation</a>
<ul>
<li><a href="#FAQJavaInstallation">How do I install Java?</a></li>
<li><a href="#FAQJavaJarStart">When I try to start a .jar file via double-click, nothing happens. What is
wrong?</a></li>
<li><a href="#FAQEclipseInstallation">How do I install Eclipse?</a></li>
<li><a href="#FAQEclipseInstallationWin7">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? </a>
</li>
<li><a href="#FAQWUDSNInstallationUpdateSite">Why is WUDSN IDE not available via the update site?</a></li>
<li><a href="#FAQWUDSNInstallationUpdateSiteBlocked">Why do I get "Unable to read repository at ... Read
timed out" when accessing the update site?</a></li>
<li><a href="#FAQWUDSNInstallationUpdateSiteRequiredItems">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?</a>
</li>
<li><a href="#FAQJavaJarStart">When I try to start a .jar
file via double-click, nothing happens. What is wrong?</a></li>
<li><a href="#FAQEclipseInstallation">How do I install
Eclipse?</a></li>
<li><a href="#FAQEclipseInstallationWin7">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? </a></li>
<li><a href="#FAQWUDSNInstallationUpdateSite">Why is WUDSN
IDE not available via the update site?</a></li>
<li><a href="#FAQWUDSNInstallationUpdateSiteBlocked">Why do
I get "Unable to read repository at ... Read timed out" when
accessing the update site?</a></li>
<li><a href="#FAQWUDSNInstallationUpdateSiteRequiredItems">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?</a></li>
<li><a href="#FAQEclipseUserGuide">How do I use Eclipse?</a></li>
<li><a href="#FAQWUDSNInstallationPreferencesNotVisible">Why is the "Assembler" section not visible in the
preferences?</a></li>
</ul>
</li>
<li><a href="#FAQWUDSNInstallationPreferencesNotVisible">Why
is the "Assembler" section not visible in the preferences?</a></li>
</ul></li>
<li><a href="#Configuration">Configuration</a>
<ul>
<li><a href="#FAQFileAssociations">How do I associate my source file extensions with the correct editor?</a>
</li>
<li><a href="#FAQHardwareAnnotation">Why do I have to put ";@com.wudsn.ide.lng.hardware=..." in the source
file?</a></li>
<li><a href="#FAQProblemsView">Why do I see wrong messages in the "Problems" view?</a></li>
</ul>
</li>
<li><a href="#FAQFileAssociations">How do I associate my
source file extensions with the correct editor?</a></li>
<li><a href="#FAQHardwareAnnotation">Why must I put
";@com.wudsn.ide.lng.hardware=..." in the source file?</a></li>
<li><a href="#FAQProblemsView">Why do I see wrong messages
in the "Problems" view?</a></li>
</ul></li>
<li><a href="#Editing">Editing</a>
<ul>
<li><a href="#FAQEclipseSpeed">Why is editing sometimes slow or even everything is blocked showing the wait
cursor?</a></li>
<li><a href="#FAQSourceVersionControl">Is there support for source version control?</a></li>
<li><a href="#FAQBlockSelectionMode">Is there support for block selection mode?</a></li>
<li><a href="#FAQContentAssist">Why does CTRL-Space not open content assist?</a></li>
<li><a href="#FAQCtrlShiftShortcuts">Why do CTRL-SHIFT-0/9 and other key combinations not work?</a></li>
</ul>
</li>
<li><a href="#FAQEclipseSpeed">Why is editing sometimes
slow, or is everything blocked, showing the wait cursor?</a></li>
<li><a href="#FAQSourceVersionControl">Is there support for
source version control?</a></li>
<li><a href="#FAQBlockSelectionMode">Is there support for
the block selection mode?</a></li>
<li><a href="#FAQContentAssist">Why does "CTRL-Space" not
open content assist?</a></li>
<li><a href="#FAQCtrlShiftShortcuts">Why do "CTRL-SHIFT-0/9"
and other key combinations not work?</a></li>
</ul></li>
<li><a href="#Compiling">Compiling</a>
<ul>
<li><a href="#FAQPrimaryCompiler">Why is MADS the primary compiler?</a></li>
<li><a href="#FAQPrimaryCompilerExample">Why do I get the error "No ORG defined" when compiling the example
from the tutorial?</a></li>
<li><a href="#FAQErrorsFromIncludeFiles">Why are the errors and warnings from an include file assigned to
the main source file in the problems view?</a></li>
<li><a href="#FAQATASMtoMADSConversion">How do I convert an ATASM source to MADS format?</a></li>
<li><a href="#FAQATASMSegments">How does ATASM generate segments in executable files?</a></li>
<li><a href="#FAQROMImages">How do I compile into ROM images?</a></li>
<li><a href="#FAQDiskImages">How do I compile into disk images?</a></li>
<li><a href="#FAQRunMakefile">How to run a makefile script instead of an emulator?</a></li>
</ul>
</li>
<li><a href="#FAQPrimaryCompiler">Why is MADS the primary
compiler?</a></li>
<li><a href="#FAQPrimaryCompilerExample">Why do I get the
error "No ORG defined" when compiling the example from the
tutorial?</a></li>
<li><a href="#FAQErrorsFromIncludeFiles">Why are the errors
and warnings from an included file assigned to the primary source
file in the problems view?</a></li>
<li><a href="#FAQATASMtoMADSConversion">How do I convert
from ATASM format to MADS format?</a></li>
<li><a href="#FAQATASMSegments">How does ATASM generate
segments in executable files?</a></li>
<li><a href="#FAQROMImages">How do I compile into ROM
images?</a></li>
<li><a href="#FAQDiskImages">How do I compile into disk
images?</a></li>
<li><a href="#FAQRunMakefile">How to run a makefile script
instead of an emulator?</a></li>
</ul></li>
<li><a href="#Emulation">Emulation</a>
<ul>
<li><a href="#FAQOtherEmulators">How can I use other emulators?</a></li>
</ul>
</li>
<li><a href="#FAQOtherEmulators">How can I use other
emulators?</a></li>
</ul></li>
</ul>
<h3 id="Installation">Installation</h3>
<div id="FAQJavaInstallation">
<h4>How do I install Java?</h4>
<p>I recommend you visit <a href="https://openjdk.java.net">OpenJDK</a> 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.</p>
<p>
I recommend you visit <a href="https://openjdk.java.net">OpenJDK</a>
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.
</p>
<div id="FAQJavaJarStart">
<h4>When I try to start a .jar file via double-click, nothing happens. What is wrong?</h4>
<p>You probably have the wrong Java version installed or set a default. Open a shell window and enter "java -jar
&lt;yourfile.jar&gt;". 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".</p>
<p><img src="productions/java/ide/faq/java-jarfile-registry.png" alt="Java jar file registry entry" /></p>
<p>If starting from the command line does not work, you should see a more detailed error message about the
reason for that.</p>
<h4>Nothing happens When I try to start a .jar file via
double-click. What is wrong?</h4>
<p>You probably have the wrong Java version installed or set a
default. Open a shell window and enter "java -jar
&lt;yourfile.jar&gt;". 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".</p>
<p>
<img src="productions/java/ide/faq/java-jarfile-registry.png"
alt="Java jar file registry entry" />
</p>
<p>If starting from the command line does not work, you should see
a more detailed error message about why.</p>
</div>
<div id="FAQEclipseInstallation">
<h4>How do I install Eclipse?</h4>
<p>If you are not familiar with Eclipse at all, make sure that you have installed the <b>Eclipse platform
distribution</b> 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."</p>
<p>
If you are unfamiliar with Eclipse, ensure you have installed the <b>Eclipse
platform distribution</b> 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."
</p>
</div>
<div id="FAQEclipseInstallationWin7">
<h4>When I try to start Eclipse I get an error like "Failed to load the JNI shared library 'C:\Program Files
<h4>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?</h4>
<p>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.</p>
<p>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.</p>
</div>
<div id="FAQEclipseUserGuide">
<h4>How do I use Eclipse at?</h4>
<p>Start the built-in help of Eclipse via the menu "Help/Help Content" and read the section "Workbench User
Guide".</p>
<img src="productions/java/ide/faq/ide-workbench-user-guide.png" alt="Workbench user guide" />
<p>Start the built-in help of Eclipse via the "Help/Help Content"
menu and read the "Workbench User Guide" section.</p>
<img src="productions/java/ide/faq/ide-workbench-user-guide.png"
alt="Workbench user guide" />
</div>
<div id="FAQWUDSNInstallationUpdateSite">
<h4>Why is WUDSN IDE not available via the update site?</h4>
<p>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.</p>
<img src="productions/java/ide/faq/ide-update-site.png" alt="Installation dialog with update site" />
<p>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.</p>
<img src="productions/java/ide/faq/ide-update-site.png"
alt="Installation dialog with update site" />
</div>
<div id="FAQWUDSNInstallationUpdateSiteBlocked">
<h4>Why do I get "Unable to read repository at ... Read timed out" when accessing the update site?</h4>
<p>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.</p>
<h4>Why do I get "Unable to read repository at ... Read timed
out" when accessing the update site?</h4>
<p>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.</p>
</div>
<div id="FAQWUDSNInstallationUpdateSiteRequiredItems">
<h4>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?</h4>
<p>This error message indicates that the Eclipse version you are running is too old.
Check the <a href="/index.php/ide/releases" target="_blank" rel="noopener noreferrer">releases</a> page for
the required minimum Eclipse version for every WUDSN IDE release.</p>
<h4>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?</h4>
<p>
This error message indicates that the Eclipse version you are running
is too old. Check the <a href="index.php/ide/releases"
target="_blank" rel="noopener noreferrer">releases</a> page for the
required minimum Eclipse version for every WUDSN IDE release.
</p>
</div>
<div id="FAQWUDSNInstallationPreferencesNotVisible">
<h4>Why is the "Assembler" section not visible in the preferences?</h4>
<p>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 <a
href="http://www.oracle.com/technetwork/java/eol-135779.html" target="_blank"
rel="noopener noreferrer">out of maintenance since 2013/02</a>. 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.</p>
<h4>Why is the "Assembler" section not visible in the
preferences?</h4>
<p>
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 <a
href="http://www.oracle.com/technetwork/java/eol-135779.html"
target="_blank" rel="noopener noreferrer">out of maintenance
since 2013/02</a>. 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.
</p>
</div>
<h3 id="Configuration">Configuration</h3>
<div id="FAQProblemsView">
<h4>Why do I see wrong messages in the "Problems" view?</h4>
<p>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.</p>
<p>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.</p>
</div>
<div id="FAQFileAssociations">
<h4>How do I associate my source file extensions with the correct editor?</h4>
<p>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 <a
href="http://www.youtube.com/watch?v=QgQOle36hRA">WUDSN IDE Tutorial 3: Setting up Editors and File
Extensions correctly</a>.</p>
<h4>How do I associate my source file extensions with the correct
editor?</h4>
<p>
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 <a
href="http://www.youtube.com/watch?v=QgQOle36hRA">WUDSN IDE
Tutorial 3: Setting up Editors and File Extensions correctly</a>.
</p>
</div>
<div id="FAQHardwareAnnotation">
<h4>Why do I have to put ";@com.wudsn.ide.lng.hardware=..." in the source file?</h4>
<p>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.</p>
<h4>Why must I put ";@com.wudsn.ide.lng.hardware=..." in the
source file?</h4>
<p>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.</p>
</div>
<h3 id="Editing">Editing</h3>
<div id="FAQEclipseSpeed">
<h4>Why is editing sometimes slow or even everything blocked showing the wait cursor?</h4>
<p>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".</p>
<h4>Why is editing sometimes slow, or is everything blocked,
showing the wait cursor?</h4>
<p>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".</p>
</div>
<div id="FAQSourceVersionControl">
<h4>Is there support for source version control?</h4>
<p>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.</p>
<img src="productions/java/ide/faq/ide-version-control.gif" alt="Source version control" />
<p>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.</p>
<img src="productions/java/ide/faq/ide-version-control.gif"
alt="Source version control" />
</div>
<div id="FAQBlockSelectionMode">
<h4>Is there support for block selection mode?</h4>
<p>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.</p>
<img src="productions/java/ide/faq/ide-editor-toggle-block-selection-mode.png"
<h4>Is there support for a block selection mode?</h4>
<p>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.</p>
<img
src="productions/java/ide/faq/ide-editor-toggle-block-selection-mode.png"
alt="Toggle block selection mode" />
<p>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.</p>
<img src="productions/java/ide/faq/ide-editor-block-selection-mode-toolbar.gif"
<p>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.</p>
<img
src="productions/java/ide/faq/ide-editor-block-selection-mode-toolbar.gif"
alt="Toggle block selection mode" />
</div>
<div id="FAQContentAssist">
<h4>Why does CTRL-Space not open content assist?</h4>
<p>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.</p>
<h4>Why does "CTRL-Space" not open content assist?</h4>
<p>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.</p>
<ol>
<li>Startup and log into MS Messenger.</li>
<li>From the main window, hit the ALT key to bring up the main menu and select "Plus! | Preferences &amp;
Options".</li>
<li>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"</li>
<li>From the main window, hit the ALT key to bring up the main
menu and select "Plus! | Preferences &amp; Options".</li>
<li>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".</li>
<li>Press the "OK" button.</li>
</ol>
<div id="FAQCtrlShiftShortcuts">
<h4>Why do CTRL-SHIFT-0/9 and other key combinations not work?</h4>
<p>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...</p>
<p>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...</p>
<p>Windows 7</p>
<ol>
<li>Within "Windows Control Panel", open "Region and Settings".</li>
<li>Select the "Keyboard and Languages" tab, select "Change Keyboards...".</li>
<li>In the "Text Services and Input Languages" windows, select "Advanced Key Settings".</li>
<li>In the "Hot Keys for input languages" list box, select "Between input languages" and then select
"Change Key Sequence..."</li>
<li>In the "Change Key Sequence" window, choose another radio button other than the one next to
CTRL+Shift. At best you choose "(None)".</li>
<li>Click OK until you closed all popup windows.</li>
<li>Select the "Keyboard and Languages" tab and "Change
Keyboards...".</li>
<li>In the "Text Services and Input Languages" windows, select
"Advanced Key Settings".</li>
<li>In the "Hot Keys for input languages" list box, select
"Between input languages" and then select "Change Key Sequence..."</li>
<li>In the "Change Key Sequence" window, choose another radio
button other than the one next to CTRL+Shift. At best, you choose
"(None)".</li>
<li>Click OK until you close all popup windows.</li>
</ol>
<p>Windows 10</p>
<ol>
<li>Open "Control Panel\Clock, Language, and Region\Language\Advanced settings.</li>
<li>Click "Change Language bar hot keys".</li>
<li>Open "Control Panel\Clock, Language, and
Region\Language\Advanced settings.</li>
<li>Click the "Change Language bar hot keys".</li>
<li>Set all key sequences to "(None)".</li>
<li>Click OK until you closed all popup windows.</li>
<li>Click OK until you close all popup windows.</li>
</ol>
<p>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. <br /> <img
<p>
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. <br /> <img
src="productions/java/ide/faq/windows-text-services-and-input-languages.png"
alt="Configure Windows IME hot keys" /></p>
alt="Configure Windows IME hot keys" />
</p>
</div>
<h3 id="Compiling">Compiling</h3>
<div id="FAQPrimaryCompiler">
<h4>Why is MADS the primary compiler?</h4>
<p>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.</p>
<p>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.</p>
</div>
<div id="FAQPrimaryCompilerExample">
<h4>Why do I get the error "No ORG defined" when compiling the example from the tutorial?</h4>
<p>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</p>
<h4>Why do I get the error "No ORG defined" when compiling the
example from the tutorial?</h4>
<p>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.</p>
<ul>
<li>Convert the source t MADS format as described in <a href="#FAQATASMtoMADSConversion">How do I
convert an ATASM source to MADS format?</a> , this is the recommended way</li>
<li>Open the source with the ATASM editor using "Open With..." in the context menu of the Project
Explorer</li>
<li>Change the default editor for the file extension ".asm" in the preferences for "File Associations"
as described in the video tutorial <a href="http://www.youtube.com/watch?v=QgQOle36hRA&amp;hd=1"
target="_blank" rel="noopener noreferrer">Part 3: Setting up Editors and File Extensions
correctly</a>.</li>
<li>Convert the source to MADS format as described in <a
href="#FAQATASMtoMADSConversion">How do I convert from ATASM
format to MADS format?</a> This is the recommended way.
</li>
<li>Open the source with the ATASM editor using "Open With..."
in the context menu of the Project Explorer.</li>
<li>Change the default editor for the file extension ".asm" in
the preferences for "File Associations" as described in the video
tutorial <a
href="http://www.youtube.com/watch?v=QgQOle36hRA&amp;hd=1"
target="_blank" rel="noopener noreferrer">Part 3: Setting up
Editors and File Extensions correctly</a>.
</li>
</ul>
</div>
<div id="FAQErrorsFromIncludeFiles">
<h4>Why are the errors and warnings from an include file assigned to the main source file in the problems
view?</h4>
<p>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.</p>
<h4>Why are the errors and warnings from an included file
assigned to the primary source file in the problems view?</h4>
<p>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.</p>
</div>
<div id="FAQATASMtoMADSConversion">
<h4>How do I convert an ATASM source to MADS format?</h4>
<p>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.</p>
<h4>How do I convert from ATASM format to MADS format?</h4>
<p>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.</p>
<ul>
<li>Replace the origin definition "* = address" with "ORG address".</li>
<li>Replace the origin definition "* = address" with "ORG
address".</li>
<li>Replace ".INCLUDE" with "ICL" for source includes.</li>
<li>Replace ".INCBIN" with "INS" for binary includes.</li>
<li>Replace "* = $2E0; .WORD address" with "RUN address" to specify the run address.</li>
<li>Replace "* = $2E2; .WORD address" with "INI address" to specify the init address.</li>
<li>Check the quotes of ".BYTE" and "DTA" statements. In MADS, single quotes result in ASCII codes,
double quotes in ATARI screen codes.</li>
<li>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
<li>Replace "* = $2E0; .WORD address" with "RUN address" to
specify the run address.</li>
<li>Replace "* = $2E2; .WORD address" with "INI address" to
specify the initialization address.</li>
<li>Check the quotes of ".BYTE" and "DTA" statements. In MADS,
single quotes result in ASCII codes and double quotes in ATARI
screen codes.</li>
<li>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.</li>
</ul>
</div>
<div id="FAQATASMSegments">
<h4>How does ATASM generate segments in executable files?</h4>
<p>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.</p>
<div style="font-family: courier, monospace; font-size: 13px;">; Bank 0 <br /> .bank <br /> .set 6,0 <br />
* = $8000 <br /> start lda #0 <br /> jmp * <br /> <br /> ; Bank 1 <br /> .bank .set 6,0 <br /> * = $2e0
<br /> .word start; <br /> <br /> ; Bank 2 <br /> .bank <br /> .set 6,$4300-$C000 <br /> * = $C000
<br /> lda #1 <br /> sta label+1 <br /> label lda #2 <br /> jmp *</div>
<p>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.</p>
<div style="font-family: courier, monospace; font-size: 13px;">
; Bank 0 <br />.bank <br />.set 6,0 <br />* = $8000 <br />start
lda #0 <br />jmp * <br /> <br />; Bank 1 <br />.bank .set 6,0 <br />*
= $2e0 <br />.word start; <br /> <br />; Bank 2 <br />.bank <br />.set
6,$4300-$C000 <br />* = $C000 <br />lda #1 <br />sta label+1 <br />label
lda #2 <br />jmp *
</div>
</div>
<div id="FAQROMImages">
<h4>How do I compile into ROM images?</h4>
<p>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.</p>
<p>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.</p>
<ul>
<li>ACME: Use the compiler parameter " <b>-f plain</b> " instead of "-f cbm" (default) to switch to
"plain" mode without a header</li>
<li>ATASM: Extend the compiler parameter "-o${outputFilePath}" to " <b>-r</b> -o${outputFilePath}" to
switch to "raw" mode without header</li>
<li>MADS: Use " <b>OPT h-f+</b> " 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</li>
<li>ACME: Use the compiler parameter " <b>-f plain</b> "
instead of "-f cbm" (default) to switch to "plain" mode without a
header
</li>
<li>ATASM: Extend the compiler parameter "-o${outputFilePath}"
to " <b>-r</b> -o${outputFilePath}" to switch to "raw" mode without
header
</li>
<li>MADS: Use " <b>OPT h-f+</b> " 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
</li>
</ul>
</div>
<div id="FAQDiskImages">
<h4>How do I compile into disk images?</h4>
<h5>Atari 8-bit</h5>
<p>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 <a
href="http://www.horus.com/~hias/atari/" target="_blank" rel="noopener noreferrer">AtariSIO
tools</a> 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 <a href="productions/java/ide/downloads/makefiles.zip" target="_blank"
rel="noopener noreferrer">archive</a>. Unpack the archive to your output folder. Double-click
"makefile.bat" to see how the disk image is created and started. Read section <a
href="#FAQRunMakefile">How to run a makefile script instead of an emulator?</a> 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 <a
href="http://frederik.hol.st/atari/8-bit/AtariSIO4Mac/" target="_blank"
rel="noopener noreferrer">website</a>.</p>
<p>
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 <a
href="http://www.horus.com/~hias/atari/" target="_blank"
rel="noopener noreferrer">AtariSIO tools</a> 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 "<a href="#FAQRunMakefile">How to run a
makefile script instead of an emulator?</a>" 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 <a href="http://frederik.hol.st/atari/8-bit/AtariSIO4Mac/"
target="_blank" rel="noopener noreferrer">website</a>.
</p>
<h5>Apple II</h5>
<p>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 <a href="https://sourceforge.net/projects/applecommander/" target="_blank"
rel="noopener noreferrer">AppleCommander</a> to achieve this. Create a makefile script and
configured it as described in <a href="#FAQRunMakefile">How to run a makefile script instead of an
emulator?</a>. 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:</p>
<p>
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 <a
href="https://sourceforge.net/projects/applecommander/"
target="_blank" rel="noopener noreferrer">AppleCommander</a> to
achieve this. Create and configure a makefile script as described in
"<a href="#FAQRunMakefile">How to run a makefile script instead
of an emulator?</a>". 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:
</p>
<ul>
<li>File extension ".b" <br /> // AppleDos 3.3 binary file: start-lo,start-hi,length-lo,length-hi,data
<br /> address = getWord(outputFileContent, 0);length = length - 4;content =
getData(outputFileContent, 4);</li>
<li>File extension ".prg" and length &gt; 2 <br /> // C64 program file: start-lo,start-hi,data <br />
address = getWord(outputFileContent, 0);length = length - 2;content = getData(outputFileContent, 2);
<li>File extension ".b" <br />// AppleDos 3.3 binary file:
start-lo, start-hi, length-lo, length-hi, data <br />address =
getWord(outputFileContent, 0);length = length - 4;content =
getData(outputFileContent, 4);
</li>
<li>File extension ".prg" and length &gt; 2 <br />// C64
program file: start-lo, start-hi, data <br />address =
getWord(outputFileContent, 0);length = length - 2;content =
getData(outputFileContent, 2);
</li>
<li>File extension ".xex" and length &gt; 6 and
(getWord(outputFileContent, 0) &amp; 0xffff) == 0xffff) <br />//
AtariDOS 2.5 binary file:$ff, $ff, start-lo, start-hi, end-lo,
end-hi, data <br />address = getWord(outputFileContent, 2);length
= length - 6;content = getData(outputFileContent, 6);
</li>
<li>File extension ".xex" and length &gt; 6 and (getWord(outputFileContent, 0) &amp; 0xffff) == 0xffff)
<br /> // AtariDOS 2.5 binary file:$ff,$ff,start-lo,start-hi,end-lo,end-hi,data <br /> address =
getWord(outputFileContent, 2);length = length - 6;content = getData(outputFileContent, 6);</li>
</ul>
<h5>Other hardwares</h5>
<p>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 <a href="#FAQRunMakefile">How to run a
makefile script instead of an emulator?</a>.</p>
<h5>Other hardware</h5>
<p>
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 "<a href="#FAQRunMakefile">How to run a
makefile script instead of an emulator?</a>".
</p>
</div>
<div id="FAQRunMakefile">
<h4>How can I run a makefile or script instead of an emulator?</h4>
<p>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
<a href="#FAQDiskImages">How do I compile into disk images?</a> for the description of how to use this
for compiling complete disk images.</p>
<img src="productions/java/ide/faq/ide-assembler-preferences-compilers-makefile.png"
<p>
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 "<a href="#FAQDiskImages">How do I compile into disk
images?</a>" for the description of how to use this for compiling
complete disk images.
</p>
<img
src="productions/java/ide/faq/ide-assembler-preferences-compilers-makefile.png"
alt="Configure makefile script" />
</div>
<h3 id="Emulation">Emulation</h3>
<div id="FAQOtherEmulators">
<h4>How can I use other emulators?</h4>
<p>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.</p>
<p>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.</p>
</div>
</div>
</div>

909
com.wudsn.ide.lng/help/ide-features.section.html
View File

File diff suppressed because it is too large Load Diff

569
com.wudsn.ide.lng/help/ide-installation.section.html
View File

@ -1,241 +1,358 @@
<p id="ide_installation">
The recommended way to install WUDSN IDE, is the <a href="https://github.com/peterdell/wudsn-ide-install#readme" target="_blank"
rel="noopener noreferrer">WUDSN IDE Installer</a>. It is currently available for Window 64-bit, version for macOS and Linux are planned.</p>
<p>
If you use another operating system or want to use the an older version of WUDSN or want to install assemblers,
compilers and emulators more selectively, read the descriptions of the installation steps below.
In case something is not correct or not working, please contact me.</p>
The recommended way to install WUDSN IDE is the <a
href="https://github.com/peterdell/wudsn-ide-install#readme"
target="_blank" rel="noopener noreferrer">WUDSN IDE Installer</a>. It
is available for Windows 64-bit, macOS and Linux.
</p>
<p>If you use another operating system, want to use an older version
of WUDSN, or wish to install assemblers, compilers, and emulators more
selectively, read the descriptions of the installation steps below. In
case something is not correct or not working, please get in touch with
me.</p>
<ul>
<li><a href="#InstallingEclipse">Installing Eclipse</a></li>
<li><a href="#InstallingWUDSNIDE">Installing WUDSN IDE</a></li>
<li><a href="#InstallingAssemblersAndCompilers">Installing assemblers and compilers like ATASM, MADS, XASM...</a></li>
<li><a href="#InstallingEmulators">Installing Altirra, Atari800 and other emulators</a></li>
<li><a href="#CreatingExampleProject">Creating and compiling an example project</a></li>
<li><a href="#FurtherAssemblerProgrammingInformation">Further information on assembler programming</a></li>
<li><a href="#InstallingEclipse">Installing Eclipse</a></li>
<li><a href="#InstallingWUDSNIDE">Installing WUDSN IDE</a></li>
<li><a href="#InstallingAssemblersAndCompilers">Installing
assemblers and compilers like ATASM, MADS, XASM...</a></li>
<li><a href="#InstallingEmulators">Installing Altirra,
Atari800, and other emulators</a></li>
<li><a href="#CreatingExampleProject">Creating and compiling
an example project</a></li>
<li><a href="#FurtherAssemblerProgrammingInformation">Further
information on assembler programming</a></li>
</ul>
<h5 id="InstallingEclipse">Installing Eclipse   <a href="#ide_installation">» top</a></h5>
<h5 id="InstallingEclipse">
Installing Eclipse   <a href="#ide_installation">» top</a>
</h5>
<ul>
<li>Download Eclipse from <a href="https://www.eclipse.org/downloads" target="_blank"
rel="noopener noreferrer">https://www.eclipse.org/downloads</a>.</li>
<li>If you don't know which version to take, use <a
href="https://archive.eclipse.org/eclipse/downloads/drops4/R-4.12-201906051800/#PlatformRuntime"
target="_blank" rel="noopener noreferrer">Eclipse 4.12 Platform Runtime Binary (81 MB)</a> for WUDSN IDE
1.7.1 and newer. <a
href="https://archive.eclipse.org/eclipse/downloads/drops4/R-4.3.2-201402211700/#PlatformRuntime"
target="_blank" rel="noopener noreferrer">Eclipse 4.3.2 Platform Runtime Binary (61 MB)</a> for WUDSN IDE
1.7.0 and older. <br /> This is a minimum size installation that does not include the
<a href="https://jdk.java.net/" target="_blank">Java Development Toolkit (JDT)</a>.
WUDSN IDE has no dependency on the JDT but of course on the Java Runtime Environment (JRE). Make sure you
also have the 64-bit version of the JRE installed if you want to use the 64-bit version of Eclipse.</li>
<li>Unzip the downloaded archive file and store the contained folder "eclipse" where you want Eclipse to be located
on your local hard drive.</li>
<li>Start the Eclipse executable from that folder.</li>
<li>Upon the first start, you are prompted to specify the folder where the workspace shall be located.</li>
<li>Normally a start link a created to this end. You can use the parameter "-nl" to specify the locale if you want.
Use "en_US" for English or "de_DE" for German. Example: "C:\Program Files\Eclipse\4.12\eclipse\eclipse.exe"
-Xmx512M -nl en_US"</li>
<li>It is recommended to create the workspace folder in your home directory.</li>
<li>After you have read the welcome page and got familiar with the Eclipse UI, just switch to the Resource
perspective.</li>
<li>Open the view "Problems" via the menu "Window/Show View/Problems" and then click the entry "Configure
Contents..." from its view menu. <br /> <img src="productions/java/ide/installation/ide-problems-view-01.png"
alt="Open configuration of the problems view" /></li>
<li>Select the configuration "All Errors", the radio button "On selected element and its children" and the
checkboxes "Error", "Warning" and "Info". <br /> <img
src="productions/java/ide/installation/ide-problems-view-02.png" alt="Configuration of the problems view" />
</li>
<li>Now Eclipse itself is ready and you can proceed with step <a href="#InstallingWUDSNIDE">Installing WUDSN
IDE</a>.</li>
<li>Download Eclipse from <a
href="https://www.eclipse.org/downloads" target="_blank"
rel="noopener noreferrer">https://www.eclipse.org/downloads</a>.
</li>
<li>If you don't know which version to take, use <a
href="https://archive.eclipse.org/eclipse/downloads/drops4/R-4.12-201906051800/#PlatformRuntime"
target="_blank" rel="noopener noreferrer">Eclipse 4.12 Platform
Runtime Binary (81 MB)</a> for WUDSN IDE 1.7.1 and newer. Use <a
href="https://archive.eclipse.org/eclipse/downloads/drops4/R-4.3.2-201402211700/#PlatformRuntime"
target="_blank" rel="noopener noreferrer">Eclipse 4.3.2 Platform
Runtime Binary (61 MB)</a> for WUDSN IDE 1.7.0 and older. <br />This
minimum-size installation does not include the <a
href="https://jdk.java.net/" target="_blank" rel="noopener">Java
Development Toolkit (JDT)</a>. WUDSN IDE does not depend on the JDT but
on the Java Runtime Environment (JRE). Ensure you also have the 64-bit
version of the JRE installed if you want to use the 64-bit version of
Eclipse.
</li>
<li>Unzip the downloaded archive file and store the " eclipse "
folder where you want Eclipse to be located on your local hard drive.</li>
<li>Start the Eclipse executable from that folder.</li>
<li>Upon the first start, you are prompted to specify the folder
where the workspace shall be located.</li>
<li>Normally, a start link is created to this end. You can use the
parameter "-nl" to specify the locale. Use "en_US" for English or
"de_DE" for German. Example: "C:\Program
Files\Eclipse\4.12\eclipse\eclipse.exe" -Xmx512M -nl en_US"</li>
<li>Creating the workspace folder in your home directory is
recommended.</li>
<li>After you have read the welcome page and got familiar with the
Eclipse UI, switch to the Resource perspective.</li>
<li>Open the view "Problems" via the menu "Window/Show
View/Problems" and then click the entry "Configure Contents..." from
its view menu. <br />
<img src="productions/java/ide/installation/ide-problems-view-01.png"
alt="Open configuration of the problems view" />
</li>
<li>Select the configuration "All Errors", the radio button "On
selected element and its children", and the checkboxes "Error",
"Warning", and "Info". <br />
<img src="productions/java/ide/installation/ide-problems-view-02.png"
alt="Configuration of the problems view" />
</li>
<li>Now Eclipse is ready, and you can proceed with <a
href="#InstallingWUDSNIDE">Installing WUDSN IDE</a>.
</li>
</ul>
<h5 id="InstallingWUDSNIDE">Installing WUDSN IDE   <a href="#ide_installation">» top</a></h5>
<h5 id="InstallingWUDSNIDE">
Installing WUDSN IDE   <a href="#ide_installation">» top</a>
</h5>
<ul>
<li>Start Eclipse</li>
<li>Select the entry "Install New Software..." from the menu "Help".</li>
<li>Enter "https://www.wudsn.com/update/stable" in the "Work with" field and press ENTER.</li>
<li>Select the latest version of the feature "WUDSN IDE" for in and press the button "Next". <br /> You don't need
to install the "General Eclipse Enhancements" feature as it is already included in the "WUDSN IDE" feature".
</li>
<li>Review the installation details and press the button "Next".</li>
<li>Read the license agreement, choose the option "I accept..." and press the button "Finish".</li>
<li>In case you get a security warning that the content is unsigned, confirm the warning by pressing the button
"OK".</li>
<li>When you are prompted to restart Eclipse now, press the button "Yes".</li>
<li>As always with updates, it may happen that the update fails for whatever reason or the installed version turns
out to have severe issues. For example, the required Java version might not be available on your machine. In
this case, you can uninstall it via the link "What is already installed" in the "Install New Software..." dialog
and restart the IDE. Then you can reinstall the latest version from "https://www.wudsn.com/update/stable" or previously
released versions from the locations listed on the <a href="https://www.wudsn.com/index.php/ide/releases">Releases</a> page. <br /> <img
src="productions/java/ide/installation/ide-installation-steps.gif" alt="IDE installation steps" /></li>
<li>Start Eclipse</li>
<li>Select the entry "Install New Software..." from the menu
"Help".</li>
<li>Enter "https://www.wudsn.com/update/stable" in the "Work with"
field and press ENTER.</li>
<li>Select the latest version of the feature "WUDSN IDE" for in
and press "Next". <br />You don't need to install the "General
Eclipse Enhancements" feature as it is already included in the "WUDSN
IDE" feature".
</li>
<li>Review the installation details and press the button "Next".</li>
<li>Read the license agreement, choose "I accept..." and press the
" Finish " button.</li>
<li>If you get a security warning that the content is unsigned,
confirm the alert by pressing the " OK " button.</li>
<li>When prompted to restart Eclipse now, press the " Yes "
button.</li>
<li>As always, with updates, the update may fail for whatever
reason, or the installed version has severe issues. For example, the
required Java version might not be available on your machine. In this
case, uninstall it via the link "What is already installed" in the
"Install New Software..." dialog and restart the IDE. Then, you can
reinstall the latest version from
"https://www.wudsn.com/update/stable" or previously released versions
from the locations listed on the <a
href="https://www.wudsn.com/index.php/ide/releases">Releases</a> page.
<br />
<img src="productions/java/ide/installation/ide-installation-steps.gif"
alt="IDE installation steps" />
</li>
</ul>
<h5 id="InstallingAssemblersAndCompilers">Installing assemblers and compilers like ATASM, MADS, XASM...   <a href="#ide_installation">» top</a></h5>
<h5 id="InstallingAssemblersAndCompilers">
Installing assemblers and compilers like ATASM, MADS, XASM...   <a
href="#ide_installation">» top</a>
</h5>
<ul>
<li>Start Eclipse</li>
<li>Select the entry "Preferences" from the menu "Window" (in Windows and Linux) or the menu "Eclipse" (in Mac OS X)
</li>
<li>Open the preferences page "Languages/Assembler/Atari 8-bit Assemblers" or the respective page for your platform.</li>
<li>Select the tab for the assembler or compiler of your choice. The following assemblers and compilers are or will be supported: <br />
<table>
<tbody>
<tr>
<th>Language</th>
<th>Tool</th>
<th>Default Target Platform</th>
</tr>
<tr>
<td>Assembler</td>
<td>ACME</td>
<td>C64</td>
</tr>
<tr>
<td>Assembler</td>
<td>ASM6</td>
<td>NES</td>
</tr>
<tr>
<td>Assembler</td>
<td>ATASM</td>
<td>Atari 8-bit</td>
</tr>
<tr>
<td>Assembler</td>
<td>DASM</td>
<td>Atari 2600</td>
</tr>
<tr>
<td>Assembler</td>
<td>KickAss</td>
<td>C64</td>
</tr>
<tr>
<td>Assembler</td>
<td>MADS</td>
<td>Atari 8-bit</td>
</tr>
<tr>
<td>Assembler</td>
<td>XASM</td>
<td>Atari 8-bit</td>
</tr>
<tr>
<td>Assembler</td>
<td>TASS</td>
<td>C64 (in preparation)</td>
</tr>
<tr>
<td>Pascal</td>
<td>MadPascal</td>
<td>Atari 8-bit</td>
</tr>
</tbody>
</table>
</li>
<li>There are 3 ways to download the assemblers / compilers:
<ul>
<li>Option 1: Download the <a
href="https://github.com/peterdell/wudsn-ide-tools/archive/refs/heads/main.zip" target="_blank"
rel="noopener noreferrer">complete assemblers / compilers / emulators package for WUDSN IDE</a>
including the Windows, Linux and macOS X versions where available.
This is the simplest way to get all of them for many operating systems.
The archive contains a readme file with the date of the last update and the included program versions.</li>
<li>Option 2: Download single assemblers / compilers from <a href="https://github.com/peterdell/wudsn-ide-tools" target="_blank"
rel="noopener noreferrer">https://github.com/peterdell/wudsn-ide-tools<a>. Use this option if you prefer to only download what you actually need.</li>
<li>Option 3: Click the "Download" link to open the home page of the assembler / compiler. Use this option, if you need the most recent version of the assembler / compiler.</li>
</ul>
</li>
<li>Follow the instruction on the download site to install the assembler / compiler to the folder of your choice.</li>
<li>In the section "Browse..." button for the field "Path to Compiler" to locate the executable.</li>
<li>If no explicit assembler / compiler parameters are specified, the default parameters are used.</li>
<li>If explicit assembler / compiler parameters are specified, the default parameters are ignored.</li>
<li>The variable "${sourceFilePath}" is replaced by the absolute path to the source file. <br /> The variable
"${outputFilePath}" is replaced by the absolute path to the output file. <br /> For more variables see section
"Preferences for assembling and compiling" on the "Features" page.</a></li>
<li>Choose if you want to use the source folder or the temporary folder as the output folder.</li>
<li>Choose the file extension for the output file, for example, ".xex" or ".bin"</li>
<li>Press the button "OK".</li>
<li>Using the button "Restore Defaults" all values are reset, except for the paths to the assembler / compilers. <br /> <br />
<img src="productions/java/ide/features/ide-assembler-preferences-compilers.gif"
alt="Configuration of aseembler / compiler executable path" /></li>
<li>Using the button "Default" in the "File Associations" preferences you can set the default editor for a file
extension, for example, "MADS" for "*.asm". <br /> <img
src="productions/java/ide/features/ide-editor-file-associations.gif" alt="IDE file associations" /></li>
<li>Start Eclipse</li>
<li>Select the entry "Preferences" from the menu "Window" (in
Windows and Linux) or the menu "Eclipse" (in Mac OS X)</li>
<li>Open the preferences page "Languages/Assembler/Atari 8-bit
Assemblers" or the respective page for your platform.</li>
<li>Select the tab for the assembler or compiler of your choice.
The following assemblers and compilers are or will be supported: <br />
<table>
<tbody>
<tr>
<th>Language</th>
<th>Tool</th>
<th>Default Target Platform</th>
</tr>
<tr>
<td>Assembler</td>
<td>ACME</td>
<td>C64</td>
</tr>
<tr>
<td>Assembler</td>
<td>ASM6</td>
<td>NES</td>
</tr>
<tr>
<td>Assembler</td>
<td>ATASM</td>
<td>Atari 8-bit</td>
</tr>
<tr>
<td>Assembler</td>
<td>DASM</td>
<td>Atari 2600</td>
</tr>
<tr>
<td>Assembler</td>
<td>KickAss</td>
<td>C64</td>
</tr>
<tr>
<td>Assembler</td>
<td>MADS</td>
<td>Atari 8-bit</td>
</tr>
<tr>
<td>Assembler</td>
<td>XASM</td>
<td>Atari 8-bit</td>
</tr>
<tr>
<td>Assembler</td>
<td>TASS</td>
<td>C64 (in preparation)</td>
</tr>
<tr>
<td>Pascal</td>
<td>MadPascal</td>
<td>Atari 8-bit</td>
</tr>
</tbody>
</table>
</li>
<li>There are three ways to download the assemblers/compilers:
<ul>
<li>Option 1: Download the <a
href="https://github.com/peterdell/wudsn-ide-tools/archive/refs/heads/main.zip"
target="_blank" rel="noopener noreferrer">complete
assemblers/compilers/emulators package for WUDSN IDE</a>, including the
Windows, Linux, and macOS X versions where available. This is the
simplest way to get all of them for many operating systems. The
archive contains a readme file with the date of the last update and
the included program versions.
</li>
<li>Option 2: Download single assemblers/compilers from <a
href="https://github.com/peterdell/wudsn-ide-tools" target="_blank"
rel="noopener noreferrer">https://github.com/peterdell/wudsn-ide-tools</a><a>.
Use this option if you prefer only to download what you need.</a></li>
<li>Option 3: Click the "Download" link to open the home page of
the assembler/compiler. Use this option if you need the most recent
version of the assembler/compiler.</li>
</ul>
</li>
<li>Follow the instructions on the download site to install the
assembler/compiler in the folder of your choice.</li>
<li>In the section "Browse..." button for the field "Path to
Compiler" to locate the executable.</li>
<li>The default parameters are used if no explicit
assembler/compiler parameters are specified.</li>
<li>The default parameters are ignored if explicit
assembler/compiler parameters are specified.</li>
<li>The absolute path to the source file replaces the variable
"${sourceFilePath}". <br />The absolute path to the output file
replaces the variable "${outputFilePath}". <br />For more variables,
see the "Preferences for assembling and compiling" section on the
"Features" page.
</li>
<li>Choose if you want to use the source or temporary folders as
the output folder.</li>
<li>Choose the file extension for the output file, for example,
".xex" or ".bin".</li>
<li>Press the button "OK".</li>
<li>All values are reset using the "Restore Defaults" button,
except for the paths to the assembler/compilers. <br />
<br />
<img
src="productions/java/ide/features/ide-assembler-preferences-compilers.gif"
alt="Configuration of aseembler / compiler executable path" />
</li>
<li>Using the button "Default" in the "File Associations"
preferences, you can set the default editor for a file extension, for
example, "MADS" for "*.asm". <br />
<img
src="productions/java/ide/features/ide-editor-file-associations.gif"
alt="IDE file associations" />
</li>
</ul>
<h5 id="InstallingEmulators">Installing Altirra, Atari800 and other emulators   <a href="#ide_installation">» top</a></h5>
<h5 id="InstallingEmulators">
Installing Altirra, Atari800, and other emulators   <a
href="#ide_installation">» top</a>
</h5>
<ul>
<li>Start Eclipse.</li>
<li>Select the entry "Preferences" from the menu "Window" (for Windows and Linux) or "Eclipse" (for Mac OS X).</li>
<li>Open the preferences page "Languages/Assembler/Atari 8-bit Assemblers" and select to tab for your assembler.</li>
<li>The field "Default Application to open Output File" is defaulted to "Operating System Default Application".
<ul>
<li>If you have the emulator registered as the default application for the extension of the output file, for
example, "Altirra", "Atari800" or "Atari800MacX" for ".xex", you don't need to configure anything in addition
and can skip the steps below.</li>
<li>If your operating system, like for example Linux, does not support default applications or if you need a
special output file extension and special parameters to open the output file in the emulator you can
choose the emulator in the field "Application to open Output File" and configure the command line on the
corresponding tab.</li>
<li>You can also use the "User Defined Application" to open the output file with an arbitrary application
like a script, linker, or whatever.</li>
</ul>
</li>
<li>If you have not yet downloaded the corresponding emulator, you can use the download link on the tab of the
emulator and follow the instructions on the download site to install the emulator.</li>
<li>Use the "Browse..." button for the field "Path to Application" to locate the executable. If required you can
specify your own command-line based on the default command line displayed.<br />Note: Under Mac OS-X, you must
specify the path to the actual executable inside the ".app" folder. To see this path you have to select "Show
Package Contents" in the context menu of the ".app" folder. For the "Stella" emulator installed in the
"/Applications/Stella.app" folder this means "/Applications/Stella.app/Contents/MacOS/Stella".</li>
<li>If no explicit command line is specified, the default command line is used.</li>
<li>If an explicit command line is specified, the default command line is ignored.</li>
<li>The variable "${runnerExecutablePath}" is replaced by the path to the application executable. <br /> The
variable "${outputFilePath}" is replaced by the absolute path to the output file. <br /> For more variables see section
"Preferences for assembling and compiling" on the "Features" page.</li>
<li>Press the button "OK".</li>
<li>In case you also need the Atari ROM files, you can find them in the file <a
href="http://www.emulators.com/freefile/pcxf380.zip" target="_blank"
rel="noopener noreferrer">PCXF380.ZIP</a> which is available at <a
href="http://www.emulators.com/download.htm" target="_blank"
rel="noopener noreferrer">http://www.emulators.com</a>.</li>
<li><img src="productions/java/ide/features/ide-assembler-preferences-compilers.gif"
alt="Configuration of emulator executable path" /></li>
<li>Start Eclipse.</li>
<li>Select the entry "Preferences" from the menu "Window" (for
Windows and Linux) or "Eclipse" (for Mac OS X).</li>
<li>Open the preferences page "Languages/Assembler/Atari 8-bit
Assemblers" and select the tab for your assembler.</li>
<li>The field "Default Application to open Output File" is
defaulted to "Operating System Default Application".
<ul>
<li>Suppose you have the emulator registered as the default
application for the extension of the output file, for example,
"Altirra", "Atari800," or "Atari800MacX" for ".xex". In that case,
you don't need to configure anything in addition and can skip the
steps below.</li>
<li>If your operating system, like, for example, Linux, does not
support default applications or if you need a particular output file
extension and particular parameters to open the output file in the
emulator, you can choose the emulator in the field "Application to
open Output File" and configure the command line on the
corresponding tab.</li>
<li>You can also use the "User Defined Application" to open the
output file with an arbitrary application like a script, linker, or
whatever.</li>
</ul>
</li>
<li>Suppose you have not yet downloaded the corresponding
emulator. In that case, you can use the download link on the tab of
the emulator and follow the instructions on the download site to
install the emulator.</li>
<li>Use the "Browse..." button for the "Path to Application" field
to locate the executable. Specify your command line based on the
default command line displayed.<br />Note: Under Mac OS-X, you must
specify the path to the actual executable inside the ".app" folder. To
see this path, select "Show Package Contents" in the context menu of
the ".app" folder. For the "Stella" emulator installed in the
"/Applications/Stella.app" folder, this means
"/Applications/Stella.app/Contents/MacOS/Stella".
</li>
<li>The default command line is used if no explicit command line
is specified.</li>
<li>If an explicit command line is specified, the default command
line is ignored.</li>
<li>The variable "${runnerExecutablePath}" is replaced by the path
to the application executable. <br />The absolute path to the output
file replaces the variable "${outputFilePath}". <br />For more
variables, see the "Preferences for assembling and compiling" section
on the "Features" page.
</li>
<li>Press the button "OK".</li>
<li>If you also need the Atari ROM files, you can find them in the
file <a href="http://www.emulators.com/freefile/pcxf380.zip"
target="_blank" rel="noopener noreferrer">PCXF380.ZIP</a>, which is
available at <a href="http://www.emulators.com/download.htm"
target="_blank" rel="noopener noreferrer">http://www.emulators.com</a>.
</li>
<li><img
src="productions/java/ide/features/ide-assembler-preferences-compilers.gif"
alt="Configuration of emulator executable path" /></li>
</ul>
<h5 id="CreatingExampleProject">Creating and compiling an example project   <a href="#ide_installation">» top</a></h5>
<h5 id="CreatingExampleProject">
Creating and compiling an example project   <a href="#ide_installation">»
top</a>
</h5>
<ul>
<li>Start Eclipse.</li>
<li>Select the entry "New/Project" from the menu "File".</li>
<li>Select the wizard "General/Project" and press the button "Next".</li>
<li>Enter the project name "Atari800" and press the button "Finish".</li>
<li>The new project will appear in the "Project Explorer".</li>
<li>Select the newly created project and open its context menu.</li>
<li>Select the entry "New/File", enter the file name "Example.asm" and press the button "Finish".</li>
<li>The new empty file will now be opened in the MADS editor.</li>
<li>Copy the following source text and paste it into the file: <br />
<div style="font-family: courier, monospace; font-size: 13px;"><br /> ; WUDSN IDE Atari Rainbow Example - MADS
syntax <br /> <br />       org $4000 ;Start of code <br /> <br /> start lda #0 ;Disable screen DMA <br />
      sta 559 <br /> loop  lda $d40b ;Load VCOUNT <br />       clc <br />       adc 20 ;Add counter <br />
      sta $d40a <br />       sta $d01a ;Change background color <br />       jmp loop <br /> <br />
      run start ;Define run address</div>
</li>
<li>Select the entry "Build and run" from the menu "Language" or press "SHIFT-CTRL-9".</li>
<li>Enjoy your famous first rainbow effect.</li>
<li>In case of problems, open the view "Problems" and the output of the view "Console" for details and post a
message with the screenshots in the <a
href="https://www.atariage.com/forums/index.php?showtopic=145386&amp;view=getnewpost" target="_blank"
rel="noopener noreferrer">English AtariAge forum</a> if you get stuck: <br /> <br /> <img
src="productions/java/ide/installation/ide-project-example.gif"
alt="Congratulations, when you did everything correctly - this is your first rainbow effect" /></li>
<li>Start Eclipse.</li>
<li>Select the entry "New/Project" from the menu "File".</li>
<li>Select the wizard "General/Project" and press the button
"Next".</li>
<li>Enter the project name "Atari800" and press "Finish".</li>
<li>The new project will appear in the "Project Explorer".</li>
<li>Select the newly created project and open its context menu.</li>
<li>Select the entry "New/File", enter the file name
"Example.asm", and press the button "Finish".</li>
<li>The new empty file will now be opened in the MADS editor.</li>
<li>Copy the following source text and paste it into the file: <br />
<div style="font-family: courier, monospace; font-size: 13px;">
<br />; WUDSN IDE Atari Rainbow Example - MADS syntax <br />
<br />      org $4000 ;Start of code <br />
<br />start lda #0 ;Disable screen DMA <br />      sta 559 <br />loop  lda
$d40b ;Load VCOUNT <br />      clc <br />      adc 20 ;Add counter
<br />      sta $d40a <br />      sta $d01a ;Change background
color <br />      jmp loop <br />
<br />      run start ;Define run address
</div>
</li>
<li>Select the entry "Build and run" from the menu "Language" or
press "SHIFT-CTRL-9".</li>
<li>Enjoy your famous first rainbow effect.</li>
<li>In case of problems, open the view "Problems" and the output
of the "Console" view for details and post a message with the
screenshots in the <a
href="https://www.atariage.com/forums/index.php?showtopic=145386&amp;view=getnewpost"
target="_blank" rel="noopener noreferrer">English AtariAge forum</a>
if you get stuck: <br />
<br />
<img src="productions/java/ide/installation/ide-project-example.gif"
alt="Congratulations, when you did everything correctly - this is your first rainbow effect" />
</li>
</ul>
<h5 id="FurtherAssemblerProgrammingInformation">Further information on assembler programming   <a
href="#ide_installation">» top</a></h5>
<h5 id="FurtherAssemblerProgrammingInformation">
Further information on assembler programming   <a
href="#ide_installation">» top</a>
</h5>
<ul>
<li>The source includes containing the equates for hardware registers and operating system for <a
href="productions/atari800/ide/SystemEquates.asm" target="_blank" rel="noopener noreferrer">Atari 8-bit</a>
and <a href="productions/atari2600/ide/VCS.asm" target="_blank" rel="noopener noreferrer">Atari VCS</a> in MADS
format.</li>
<li><a href="https://www.atariarchives.org/agagd/" target="_blank" rel="noopener noreferrer">Atari Graphics &amp;
Arcade Game Design</a>, <a href="https://www.atariarchives.org/dere/" target="_blank"
rel="noopener noreferrer">DeRe Atari</a>, and <a href="https://www.atariarchives.org/mapping/"
target="_blank" rel="noopener noreferrer">Mapping the Atari</a> at <a href="https://www.atariarchives.org/"
target="_blank" rel="noopener noreferrer">AtariArchives.org</a></li>
<li>AtariAge forum for <a href="https://atariage.com/forums/forum/51-atari-5200-8-bit-programming" target="_blank"
rel="noopener noreferrer">Atari 5200 / 8-bit Programming</a></li>
<li>The source code files contain the equates for hardware
registers and operating systems for <a
href="productions/atari800/ide/SystemEquates.asm" target="_blank"
rel="noopener noreferrer">Atari 8-bit</a> and <a
href="productions/atari2600/ide/VCS.asm" target="_blank"
rel="noopener noreferrer">Atari VCS</a> in MADS format.
</li>
<li><a href="https://www.atariarchives.org/agagd/" target="_blank"
rel="noopener noreferrer">Atari Graphics &amp; Arcade Game Design</a>,
<a href="https://www.atariarchives.org/dere/" target="_blank"
rel="noopener noreferrer">DeRe Atari</a>, and <a
href="https://www.atariarchives.org/mapping/" target="_blank"
rel="noopener noreferrer">Mapping the Atari</a> at <a
href="https://www.atariarchives.org/" target="_blank"
rel="noopener noreferrer">AtariArchives.org</a></li>
<li>AtariAge forum for <a
href="https://atariage.com/forums/forum/51-atari-5200-8-bit-programming"
target="_blank" rel="noopener noreferrer">Atari 5200 / 8-bit
Programming</a></li>
</ul>

190
com.wudsn.ide.lng/help/ide-releases.section.html
View File

@ -1,8 +1,12 @@
<p>The following table lists all releases of WUDSN IDE, the required minimum <a href="https://jdk.java.net/" target="_blank">Java</a>
and <a href="https://www.eclipse.org/" target="_blank">Eclipse</a> 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.</p>
<p>
The following table lists all releases of WUDSN IDE, the required
minimum <a href="https://jdk.java.net/" target="_blank" rel="noopener">Java</a>
and <a href="https://www.eclipse.org/" target="_blank" rel="noopener">Eclipse</a>
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.
</p>
<table>
<tbody>
<tr>
@ -17,11 +21,12 @@
<tr>
<td>daily</td>
<td>updated permanently</td>
<td>Java 11
<td>Java 11</td>
<td>4.19</td>
<td>https://www.wudsn.com/update/daily</td>
<td><a href="https://atariage.com/forums/topic/145386-wudsn-ide-the-free-integrated-atari-8-bit-development-plugin-for-eclipse/"
target="_blank" rel="noopener noreferrer">read</a></td>
<td><a
href="https://atariage.com/forums/topic/145386-wudsn-ide-the-free-integrated-atari-8-bit-development-plugin-for-eclipse/"
target="_blank" rel="noopener noreferrer">read</a></td>
<td>n/a</td>
</tr>
<tr>
@ -30,8 +35,9 @@
<td>Java 11</td>
<td>4.19</td>
<td>https://www.wudsn.com/update/stable</td>
<td><a href="https://www.wudsn.com/index.php/191-wudsn-ide-update-1-7-2" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a
href="https://www.wudsn.com/index.php/191-wudsn-ide-update-1-7-2"
target="_blank" rel="noopener noreferrer">read</a></td>
<td>Planned</td>
</tr>
<tr>
@ -40,11 +46,10 @@
<td>Java 1.8</td>
<td>4.10</td>
<td>https://www.wudsn.com/update/1.7.1</td>
<td><a href="https://www.wudsn.com/index.php/175-wudsn-ide-update-1-7-1" target="_blank"
rel="noopener noreferrer">read</a></td>
<td>Planned
<!-- <a href="https://www.youtube.com/watch?v=TODO;hd=1" target="_blank">watch</a> -->
</td>
<td><a
href="https://www.wudsn.com/index.php/175-wudsn-ide-update-1-7-1"
target="_blank" rel="noopener noreferrer">read</a></td>
<td>Planned <!-- <a href="https://www.youtube.com/watch?v=TODO;hd=1" target="_blank">watch</a> --></td>
</tr>
<tr>
<td>1.7.0</td>
@ -52,10 +57,11 @@
<td>Java 1.6</td>
<td>4.3.1</td>
<td>https://www.wudsn.com/update/1.7.0</td>
<td><a href="https://www.wudsn.com/index.php/110-wudsn-ide-update-1-7-0" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=YdSjIwaFd90;hd=1" target="_blank"
rel="noopener noreferrer">watch</a></td>
<td><a
href="https://www.wudsn.com/index.php/110-wudsn-ide-update-1-7-0"
target="_blank" rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=YdSjIwaFd90;hd=1"
target="_blank" rel="noopener noreferrer">watch</a></td>
</tr>
<tr>
<td>1.6.6</td>
@ -63,10 +69,11 @@
<td>Java 1.6</td>
<td>4.3.1</td>
<td>https://www.wudsn.com/update/1.6.6</td>
<td><a href="https://www.wudsn.com/index.php/109-wudsn-ide-update-1-6-6-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=PNsV16tTrBc;hd=1" target="_blank"
rel="noopener noreferrer">watch</a></td>
<td><a
href="https://www.wudsn.com/index.php/109-wudsn-ide-update-1-6-6-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=PNsV16tTrBc;hd=1"
target="_blank" rel="noopener noreferrer">watch</a></td>
</tr>
<tr>
<td>1.6.5</td>
@ -74,10 +81,11 @@
<td>Java 1.7</td>
<td>4.3.1</td>
<td>https://www.wudsn.com/update/1.6.5</td>
<td><a href="https://www.wudsn.com/index.php/9-wudsn-ide-update-1-6-5-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=M2aU5wwrDew;hd=1" target="_blank"
rel="noopener noreferrer">watch</a></td>
<td><a
href="https://www.wudsn.com/index.php/9-wudsn-ide-update-1-6-5-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=M2aU5wwrDew;hd=1"
target="_blank" rel="noopener noreferrer">watch</a></td>
</tr>
<tr>
<td>1.6.4</td>
@ -85,10 +93,11 @@
<td>Java 1.6</td>
<td>3.6.0</td>
<td>https://www.wudsn.com/update/1.6.4</td>
<td><a href="https://www.wudsn.com/index.php/30-wudsn-ide-update-1-6-4-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=SsM9GofiD4k;hd=1" target="_blank"
rel="noopener noreferrer">watch</a></td>
<td><a
href="https://www.wudsn.com/index.php/30-wudsn-ide-update-1-6-4-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=SsM9GofiD4k;hd=1"
target="_blank" rel="noopener noreferrer">watch</a></td>
</tr>
<tr>
<td>1.6.3</td>
@ -96,10 +105,11 @@
<td>Java 1.6</td>
<td>3.6.0</td>
<td>https://www.wudsn.com/update/1.6.3</td>
<td><a href="https://www.wudsn.com/index.php/40-wudsn-ide-update-1-6-3-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=KOtfAdY-OnA;hd=1" target="_blank"
rel="noopener noreferrer">watch</a></td>
<td><a
href="https://www.wudsn.com/index.php/40-wudsn-ide-update-1-6-3-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=KOtfAdY-OnA;hd=1"
target="_blank" rel="noopener noreferrer">watch</a></td>
</tr>
<tr>
<td>1.6.2</td>
@ -107,10 +117,11 @@
<td>Java 1.6</td>
<td>3.6.0</td>
<td>https://www.wudsn.com/update/1.6.2</td>
<td><a href="https://www.wudsn.com/index.php/48-wudsn-ide-update-1-6-2-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=ok2zJM-J3hw;hd=1" target="_blank"
rel="noopener noreferrer">watch</a></td>
<td><a
href="https://www.wudsn.com/index.php/48-wudsn-ide-update-1-6-2-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=ok2zJM-J3hw;hd=1"
target="_blank" rel="noopener noreferrer">watch</a></td>
</tr>
<tr>
<td>1.6.1</td>
@ -118,10 +129,11 @@
<td>Java 1.6</td>
<td>3.6.0</td>
<td>not available</td>
<td><a href="https://www.wudsn.com/index.php/49-wudsn-ide-update-1-6-1-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=ok2zJM-J3hw;hd=1" target="_blank"
rel="noopener noreferrer">watch</a></td>
<td><a
href="https://www.wudsn.com/index.php/49-wudsn-ide-update-1-6-1-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=ok2zJM-J3hw;hd=1"
target="_blank" rel="noopener noreferrer">watch</a></td>
</tr>
<tr>
<td>1.6.0</td>
@ -129,10 +141,11 @@
<td>Java 1.5</td>
<td>3.6.0</td>
<td>https://www.wudsn.com/update/1.6.0</td>
<td><a href="https://www.wudsn.com/index.php/60-wudsn-ide-update-1-6-0-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=fnA_xg_XIRc;hd=1" target="_blank"
rel="noopener noreferrer">watch</a></td>
<td><a
href="https://www.wudsn.com/index.php/60-wudsn-ide-update-1-6-0-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td><a href="https://www.youtube.com/watch?v=fnA_xg_XIRc;hd=1"
target="_blank" rel="noopener noreferrer">watch</a></td>
</tr>
<tr>
<td>1.5.0</td>
@ -140,8 +153,9 @@
<td>Java 1.5</td>
<td>3.6.0</td>
<td>not available</td>
<td><a href="https://www.wudsn.com/index.php/69-wudsn-ide-update-1-5-0-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a
href="https://www.wudsn.com/index.php/69-wudsn-ide-update-1-5-0-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td>not available</td>
</tr>
<tr>
@ -150,8 +164,9 @@
<td>Java 1.5</td>
<td>3.3.0</td>
<td>not available</td>
<td><a href="https://www.wudsn.com/index.php/70-wudsn-ide-update-1-4-4-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a
href="https://www.wudsn.com/index.php/70-wudsn-ide-update-1-4-4-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td>not available</td>
</tr>
<tr>
@ -160,8 +175,9 @@
<td>Java 1.5</td>
<td>3.3.0</td>
<td>not available</td>
<td><a href="https://www.wudsn.com/index.php/74-wudsn-ide-update-1-4-3-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a
href="https://www.wudsn.com/index.php/74-wudsn-ide-update-1-4-3-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td>not available</td>
</tr>
<tr>
@ -170,8 +186,9 @@
<td>Java 1.5</td>
<td>3.3.0</td>
<td>not available</td>
<td><a href="https://www.wudsn.com/index.php/77-wudsn-ide-update-1-4-2-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a
href="https://www.wudsn.com/index.php/77-wudsn-ide-update-1-4-2-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td>not available</td>
</tr>
<tr>
@ -180,8 +197,9 @@
<td>Java 1.5</td>
<td>3.3.0</td>
<td>not available</td>
<td><a href="https://www.wudsn.com/index.php/79-wudsn-ide-update-1-4-0-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a
href="https://www.wudsn.com/index.php/79-wudsn-ide-update-1-4-0-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td>not available</td>
</tr>
<tr>
@ -190,8 +208,9 @@
<td>Java 1.5</td>
<td>3.3.0</td>
<td>not available</td>
<td><a href="https://www.wudsn.com/index.php/81-wudsn-ide-update-1-3-2-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a
href="https://www.wudsn.com/index.php/81-wudsn-ide-update-1-3-2-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td>not available</td>
</tr>
<tr>
@ -200,8 +219,9 @@
<td>Java 1.5</td>
<td>3.3.0</td>
<td>not available</td>
<td><a href="https://www.wudsn.com/index.php/83-wudsn-ide-update-1-2-0-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a
href="https://www.wudsn.com/index.php/83-wudsn-ide-update-1-2-0-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td>not available</td>
</tr>
<tr>
@ -210,8 +230,9 @@
<td>Java 1.5</td>
<td>3.3.0</td>
<td>not available</td>
<td><a href="https://www.wudsn.com/index.php/86-wudsn-ide-update-1-1-0-released" target="_blank"
rel="noopener noreferrer">read</a></td>
<td><a
href="https://www.wudsn.com/index.php/86-wudsn-ide-update-1-1-0-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td>not available</td>
</tr>
<tr>
@ -220,24 +241,35 @@
<td>Java 1.5</td>
<td>3.3.0</td>
<td>not available</td>
<td><a href="https://www.wudsn.com/index.php/88-first-official-version-1-0-0-of-wudsn-ide-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td><a
href="https://www.wudsn.com/index.php/88-first-official-version-1-0-0-of-wudsn-ide-released"
target="_blank" rel="noopener noreferrer">read</a></td>
<td>not available</td>
</tr>
</tbody>
</table>
<p>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.</p>
<p>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.</p>
<ul>
<li>WUDSN IDE 1.7.1: <a href="https://www.wudsn.com/productions/java/ide/downloads/1.7.1/wudsn-ide-win64.zip"
target="_blank" rel="noopener noreferrer">Windows 64-bit version</a></li>
<li>WUDSN IDE 1.7.0: <a href="https://www.wudsn.com/productions/java/ide/downloads/1.7.0/wudsn-ide-win64.zip"
target="_blank" rel="noopener noreferrer">Windows 64-bit version</a>, <a
href="https://www.wudsn.com/productions/java/ide/downloads/1.7.0/wudsn-ide-win32.zip" target="_blank"
rel="noopener noreferrer">Windows 32-bit version</a></li>
<li>WUDSN IDE 1.6.6: <a href="https://www.wudsn.com/productions/java/ide/downloads/1.6.6/wudsn-ide-win64.zip"
target="_blank" rel="noopener noreferrer">Windows 64-bit version</a>, <a
href="https://www.wudsn.com/productions/java/ide/downloads/1.6.6/wudsn-ide-win32.zip" target="_blank"
rel="noopener noreferrer">Windows 32-bit version</a></li>
<li>WUDSN IDE 1.7.1: <a
href="https://www.wudsn.com/productions/java/ide/downloads/1.7.1/wudsn-ide-win64.zip"
target="_blank" rel="noopener noreferrer">Windows 64-bit version</a></li>
<li>WUDSN IDE 1.7.0: <a
href="https://www.wudsn.com/productions/java/ide/downloads/1.7.0/wudsn-ide-win64.zip"
target="_blank" rel="noopener noreferrer">Windows 64-bit version</a>,
<a
href="https://www.wudsn.com/productions/java/ide/downloads/1.7.0/wudsn-ide-win32.zip"
target="_blank" rel="noopener noreferrer">Windows 32-bit version</a></li>
<li>WUDSN IDE 1.6.6: <a
href="https://www.wudsn.com/productions/java/ide/downloads/1.6.6/wudsn-ide-win64.zip"
target="_blank" rel="noopener noreferrer">Windows 64-bit version</a>,
<a
href="https://www.wudsn.com/productions/java/ide/downloads/1.6.6/wudsn-ide-win32.zip"
target="_blank" rel="noopener noreferrer">Windows 32-bit version</a></li>
</ul>

183
com.wudsn.ide.lng/help/ide-tutorials.section.html
View File

@ -1,87 +1,136 @@
<p>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
<a href="http://ftp.pigwa.net/stuff/media/videos/tutorials/WUDSN/WUDSN%20IDE/" target="_blank">Pigwa</a></p>
<p>
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 <a
href="http://ftp.pigwa.net/stuff/media/videos/tutorials/WUDSN/WUDSN%20IDE/"
target="_blank" rel="noopener">Pigwa</a>.
</p>
<table>
<tbody>
<tr>
<td id="Part1:IntroductionInstallationandUse"><b>Part 1: Introduction, Installation and Use</b> <br /> <a
href="https://www.youtube.com/watch?v=36MFqY55yR0&amp" target="_blank"
rel="noopener noreferrer"> <img src="productions/java/ide/tutorials/ide-tutorial-01-video.png"
alt="Tutorial part 1" /> </a></td>
<td id="Part2:SettingupPerspectiveViewsandEditors"><b>Part 2: Setting up Perspective, Views and Editors</b>
<br /> <a href="https://www.youtube.com/watch?v=fJ24OiGA8wY&amp" target="_blank"
rel="noopener noreferrer"> <img src="productions/java/ide/tutorials/ide-tutorial-02-video.png"
alt="Tutorial part 2" /> </a></td>
<td id="Part1:IntroductionInstallationandUse"><b>Part 1:
Introduction, Installation and Use</b> <br />
<a href="https://www.youtube.com/watch?v=36MFqY55yR0&amp;amp"
target="_blank" rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-01-video.png"
alt="Tutorial part 1" />
</a></td>
<td id="Part2:SettingupPerspectiveViewsandEditors"><b>Part
2: Setting up Perspective, Views, and Editors</b> <br />
<a href="https://www.youtube.com/watch?v=fJ24OiGA8wY&amp;amp"
target="_blank" rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-02-video.png"
alt="Tutorial part 2" />
</a></td>
</tr>
<tr>
<td id="Part3:SettingupEditorsandFileExtensionscorrectly"><b>Part 3: Setting up Editors and File Extensions
correctly</b> <br /> <a href="https://www.youtube.com/watch?v=QgQOle36hRA&amp" target="_blank"
rel="noopener noreferrer"> <img src="productions/java/ide/tutorials/ide-tutorial-03-video.png"
alt="Tutorial part 3" /> </a></td>
<td id="Part4:SyntaxHighlightingandContentAssist"><b>Part 4: Syntax Highlighting and Content Assist</b>
<br /> <a href="https://www.youtube.com/watch?v=d1kPdMVeJL0&amp" target="_blank"
rel="noopener noreferrer"> <img src="productions/java/ide/tutorials/ide-tutorial-04-video.png"
alt="Tutorial part 4" /> </a></td>
<td id="Part3:SettingupEditorsandFileExtensionscorrectly"><b>Part
3: Setting up Editors and File Extensions correctly</b> <br />
<a href="https://www.youtube.com/watch?v=QgQOle36hRA&amp;amp"
target="_blank" rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-03-video.png"
alt="Tutorial part 3" />
</a></td>
<td id="Part4:SyntaxHighlightingandContentAssist"><b>Part 4:
Syntax Highlighting and Content Assist</b> <br />
<a href="https://www.youtube.com/watch?v=d1kPdMVeJL0&amp;amp"
target="_blank" rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-04-video.png"
alt="Tutorial part 4" />
</a></td>
</tr>
<tr>
<td id="Part5:WorkingwithProjectsFoldersandFiles"><b>Part 5: Working with Projects, Folders and Files</b>
<br /> <a href="https://www.youtube.com/watch?v=AdrkxVVCEzI&amp" target="_blank"
rel="noopener noreferrer"> <img src="productions/java/ide/tutorials/ide-tutorial-05-video.png"
alt="Tutorial part 5" /> </a></td>
<td id="Part6:ContentOutlineandNavigationtheHeartofthIDE"><b>Part 6: Content Outline and Navigation - the
Heart of the IDE</b> <br /> <a href="https://www.youtube.com/watch?v=VHmnvsOaW1M&amp"
target="_blank" rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-06-video.png" alt="Tutorial part 6" /> </a>
</td>
<td id="Part5:WorkingwithProjectsFoldersandFiles"><b>Part 5:
Working with Projects, Folders and Files</b> <br />
<a href="https://www.youtube.com/watch?v=AdrkxVVCEzI&amp;amp"
target="_blank" rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-05-video.png"
alt="Tutorial part 5" />
</a></td>
<td id="Part6:ContentOutlineandNavigationtheHeartofthIDE"><b>Part
6: Content Outline and Navigation - the Heart of the IDE</b> <br />
<a href="https://www.youtube.com/watch?v=VHmnvsOaW1M&amp;amp"
target="_blank" rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-06-video.png"
alt="Tutorial part 6" />
</a></td>
</tr>
<tr>
<td id="Part7:NewFeaturesInVersion1.6.0"><b>Part 7: New Features in Version 1.6.0</b> <br /> <a
href="https://www.youtube.com/watch?v=fnA_xg_XIRc" target="_blank" rel="noopener noreferrer">
<img src="productions/java/ide/tutorials/ide-tutorial-07-video.png" alt="Tutorial part 7" /> </a>
</td>
<td id="Part8:NewFeaturesInVersion1.6.2"><b>Part 8: New Features in Version 1.6.2</b> <br /> <a
href="https://www.youtube.com/watch?v=ok2zJM-J3hw" target="_blank" rel="noopener noreferrer">
<img src="productions/java/ide/tutorials/ide-tutorial-08-video.png" alt="Tutorial part 8" /> </a>
</td>
<td id="Part7:NewFeaturesInVersion1.6.0"><b>Part 7: New
Features in Version 1.6.0</b> <br />
<a href="https://www.youtube.com/watch?v=fnA_xg_XIRc" target="_blank"
rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-07-video.png"
alt="Tutorial part 7" />
</a></td>
<td id="Part8:NewFeaturesInVersion1.6.2"><b>Part 8: New
Features in Version 1.6.2</b> <br />
<a href="https://www.youtube.com/watch?v=ok2zJM-J3hw" target="_blank"
rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-08-video.png"
alt="Tutorial part 8" />
</a></td>
</tr>
<tr>
<td id="Part9:SourceLevelDebugging"><b>Part 9: Source Level Debugging</b> <br /> <a
href="https://www.youtube.com/watch?v=uljtoXE8EZI" target="_blank" rel="noopener noreferrer">
<img src="productions/java/ide/tutorials/ide-tutorial-09-video.png" alt="Tutorial part 9" /> </a>
</td>
<td id="Part10:AddingSupportforanAdditionalAssembler"><b>Part 10: Adding Support for an Additional
Assembler</b> <br /> <a href="https://www.youtube.com/watch?v=ZtnyzpNnf-g" target="_blank"
rel="noopener noreferrer"> <img src="productions/java/ide/tutorials/ide-tutorial-10-video.png"
alt="Tutorial part 10" /> </a></td>
<td id="Part9:SourceLevelDebugging"><b>Part 9: Source Level
Debugging</b> <br />
<a href="https://www.youtube.com/watch?v=uljtoXE8EZI" target="_blank"
rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-09-video.png"
alt="Tutorial part 9" />
</a></td>
<td id="Part10:AddingSupportforanAdditionalAssembler"><b>Part
10: Adding Support for an Additional Assembler</b> <br />
<a href="https://www.youtube.com/watch?v=ZtnyzpNnf-g" target="_blank"
rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-10-video.png"
alt="Tutorial part 10" />
</a></td>
</tr>
<tr>
<td id="Part11:NewFeaturesInVersion1.6.3"><b>Part 11: New Features in Version 1.6.3</b> <br /> <a
href="https://www.youtube.com/watch?v=KOtfAdY-OnA" target="_blank" rel="noopener noreferrer">
<img src="productions/java/ide/tutorials/ide-tutorial-11-video.png" alt="Tutorial part 11" /> </a>
</td>
<td id="Part12:NewFeaturesInVersion1.6.4"><b>Part 12: New Features in Version 1.6.4</b> <br /> <a
href="https://www.youtube.com/watch?v=SsM9GofiD4k" target="_blank" rel="noopener noreferrer">
<img src="productions/java/ide/tutorials/ide-tutorial-12-video.png" alt="Tutorial part 12" /> </a>
</td>
<td id="Part11:NewFeaturesInVersion1.6.3"><b>Part 11: New
Features in Version 1.6.3</b> <br />
<a href="https://www.youtube.com/watch?v=KOtfAdY-OnA" target="_blank"
rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-11-video.png"
alt="Tutorial part 11" />
</a></td>
<td id="Part12:NewFeaturesInVersion1.6.4"><b>Part 12: New
Features in Version 1.6.4</b> <br />
<a href="https://www.youtube.com/watch?v=SsM9GofiD4k" target="_blank"
rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-12-video.png"
alt="Tutorial part 12" />
</a></td>
</tr>
<tr>
<td id="Part13:NewFeaturesInVersion1.6.5"><b>Part 13: New Features in Version 1.6.5</b> <br /> <a
href="https://www.youtube.com/watch?v=M2aU5wwrDew" target="_blank" rel="noopener noreferrer">
<img src="productions/java/ide/tutorials/ide-tutorial-13-video.png" alt="Tutorial part 13" /> </a>
</td>
<td id="Part14:NewFeaturesInVersion1.6.6"><b>Part 14: New Features in Version 1.6.6</b> <br /> <a
href="https://www.youtube.com/watch?v=PNsV16tTrBc" target="_blank" rel="noopener noreferrer">
<img src="productions/java/ide/tutorials/ide-tutorial-14-video.png" alt="Tutorial part 14" /> </a>
</td>
<td id="Part13:NewFeaturesInVersion1.6.5"><b>Part 13: New
Features in Version 1.6.5</b> <br />
<a href="https://www.youtube.com/watch?v=M2aU5wwrDew" target="_blank"
rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-13-video.png"
alt="Tutorial part 13" />
</a></td>
<td id="Part14:NewFeaturesInVersion1.6.6"><b>Part 14: New
Features in Version 1.6.6</b> <br />
<a href="https://www.youtube.com/watch?v=PNsV16tTrBc" target="_blank"
rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-14-video.png"
alt="Tutorial part 14" />
</a></td>
</tr>
<tr>
<td id="Part15:NewFeaturesInVersion1.7.9"><b>Part 15: New Features in Version 1.7.0</b> <br /> <a
href="https://www.youtube.com/watch?v=YdSjIwaFd90" target="_blank" rel="noopener noreferrer">
<img src="productions/java/ide/tutorials/ide-tutorial-15-video.png" alt="Tutorial part 13" /> </a>
</td>
<td id="Part16:"> </td>
<td id="Part15:NewFeaturesInVersion1.7.9"><b>Part 15: New
Features in Version 1.7.0</b> <br />
<a href="https://www.youtube.com/watch?v=YdSjIwaFd90" target="_blank"
rel="noopener noreferrer"> <img
src="productions/java/ide/tutorials/ide-tutorial-15-video.png"
alt="Tutorial part 13" />
</a></td>
<td id="Part16:"></td>
</tr>
</tbody>
</table>