- Details
- Hits: 2942
At the end of January, I delivered a 35-minute presentation about the Atari Video Computer System (VCS, Stella, 2600), its history and architecture, and how to code for it using WUDSN IDE. The live coding part was very appreciated by the audience. Changing a single line of code and seeing immediately what happens brings you as close as possible to the machine. The recording of the presentation is now available on my YouTube channel. The slides (PDF) and the sources can be downloaded from here. I recommend you open the slides parallel to read the content and code correctly. Thanks to Julien for the event and SvOlli for the slide templates.
- Details
- Hits: 2949
I've also received requests for a 32-bit version of the zero installation distribution. And after figuring out how I can do that without doing everything twice, it's ready for download: wudsn-ide-win32.zip
. I have no real 32-bit hardware to test it, so please provide feedback. Thanks also to Timothy, Kevin, and Fredrick for the feedback and for using WUDSN IDE on Mac OS X. I have extended the FAQs accordingly.
New FAQs:
- Why is the "Assembler" section not visible in the preferences?
If the WUDSN IDE-specific sections and features are not visible after a successful installation, you probably use an outdated Java version. This seems to be a common problem on Mac OS X. Make sure you have Java 1.7 installed and that Eclipse is started using that version. Java 1.6 has been out of maintenance since 2013/02. - Why do I get "Unable to read repository at ... Read timed out" when accessing the update site?
This error message indicates that 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, ensure that "Eclipse.exe
", "java.exe
", "javaw.exe
"or the corresponding program on your host platform cannot access the internet. Maybe you have to change the settings so you are prompted to allow access interactively.
- Details
- Hits: 3868
A new version of the IDE is available via the update site and has a zero installation download now. The main reason for this release is that I could finally track down the bug in creating the disk images for Apple II.
Fixes
- Automatic creation of ".DSK" disk images for Apple II works correctly.
- The dirty indicator in Graphics Editor is now updated correctly.
New detailed documentation section, "Annotations for Compiling".
- Add
com.wudsn.ide.asm.hardware
for compiling with different target platforms. - Add
com.wudsn.ide.asm.mainsourcefile
for compiling complex projects with included files. - Some more annotations are planned for the next release.
New and extended FAQs:
- How do I associate my source file extensions with the correct editor?
- Why do I have to put "
;@com.wudsn.ide.asm.hardware=...
" in the source file? - How do I compile into disk images?
- How can I use other emulators?
- Details
- Hits: 2740
One of the reasons why I created WUDSN IDE is to make it easy for people to (re)start working with 6502 assembly language for their beloved Atari, C64, or other machines. As you can see in Tutorial Part 1, the installation from scratch is easy and fast.
To make your initial steps even more accessible, I now provide a ready-to-run zero installation distribution named "wudsn-ide-win64.zip" for Windows 64-bit operating systems. It contains the Eclipse Platform, 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" link - That's all. Eclipse will open with the predefined workspace that contains "Hello World" examples for different platforms. You can adapt, compile, and run the samples with a single click.
- Details
- Hits: 2734
There have been many updates in the past two weeks. You can read the full details on AtariAge. Today, I have replaced the standard Java file chooser with its implementation, which uses the native dialogs of the underlying operating system. The main difference on Windows is that the context menu for files and folders works in the dialog window. The main difference on Linux is that the dialog looks like a real file chooser now, unlike some crap a teenager did as homework in the afternoon. In addition, the display of the banks now adapts better to the available screen size, so the bank blocks are displayed with larger blocks.
Windows: new versus old; click to enlarge.
Linux: new versus old; click to enlarge.