Jump to content

X16 Edit - a text editor 0.5.1

   (2 reviews)

1 Screenshot

About This File

X16 Edit is a text editor for the Commander X16 platform.

Design goals:

  • Use plain text files
  • Store text buffer in banked RAM (512KB to 2 MB) 
  • Handle large text buffers efficiently
  • Simple modeless user interface inspired by GNU Nano
  • Implement basic editing functions well - refrain from making the program too feature-rich
  • Support both ISO and PETSCII modes

Emulator and Kernal requirements:

  • X16 Edit versions 0.0.1-0.3.6 are tested with the official R38
  • X16 Edit versions 0.4.0-0.4.5 are tested with an emulator and Kernal compiled from the Github master branch (Kernal commit 7bfa81a to f62e25a).
  • X16 Edit version 0.5.0 is tested with the official R39 and R40

Run with the following command:

  • x16emu -sdcard sdcard.img -prg X16EDIT-x.x.x.PRG -run (rom version < R40)

where x.x.x is the program version.

The above method doesn't work in ROM version R40. Instead you need to store the X16EDIT-.x.x.x.PRG file on the SD card. Start the emulator with x16emu -sdcard sdcard.img. In the emulator type LOAD"X16EDIT-x.x.x.PRG" to load the program, and then RUN to start it.

Please read the attached file romnotes.pdf if you want to try the ROM version.

Source files available at https://github.com/stefan-b-jakobsson/x16-edit

Released under GNU General Public License v 3 or later.

 

 

 

logo.png

 

 

manual.pdf

 

romnotes.pdf

Edited by Stefan


What's New in Version 0.5.1   See changelog

Released

This release adds support for block based reading of text files using the Kernal function MACPTR. This significantly speeds up the time it takes to read a text file into memory. The old byte wise reading is still supported as a fallback method, should the storage device not support MACPTR. Writing text to a file is still done byte by byte, and is not affected by this change.

This release also changes the prompt to confirm overwriting a file. Previously, the application would always ask the user to confirm overwriting a file, including the currently open file. This was a bit annoying if you worked on a file and wanted to save it from time to time not to lose changes. The new behavior is to overwrite the current file name without prompting the user. The confirmation is still needed if you overwrite another file.

Finally, there is a new build script that let's you build a RAM version of the program that is loaded and run at $6000. This version of the program does not contain an executable header, and must be started with a SYS command.


try_it

Yes

try_it_start_prg

X16EDIT-0.4.2-R38.PRG

try_it_license

GNU General Public License v 3 or later
  • Like 8
  • Thanks 1
 Share


User Feedback

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest

Jakebullet70

   2 of 2 members found this review helpful 2 / 2 members

This could be the beginning of a REAL built in BASIC  programming editor. Very nice work.

Response from the author:

Thanks!

A text editor is a programmer's tool. If the X16 is to become something more than a games console, you must be able to use it for native program development.

The editor could be used for any programming language. A version of Forth (Volksforth) is already published on the site, and it reads source code from text files. The same person is also working on a C compiler that runs natively on the X16, which sounds promising. An assembler that takes text files as input is at the top of my own wish list, much like the Commodore macro assembler I once purchased and used as a teen in the 80s. Editing Basic files is of coarse also very interesting.

Maybe someone out there is interested in writing any of these. If you have a solution, I'm very interested in integrating it with the editor, so that the programs play nicely together.

The new version published today is mostly focused on that kind of integration. The zero page and lower RAM usage has been minimized. The ROM version lets the user set what banks of the banked RAM is used by the editor. And the editor now takes a snapshot on startup of the zero page and lower RAM it uses, so that those memory locations can be restored on program exit.

  • Like 2
Link to review
evlthecat

   1 of 1 member found this review helpful 1 / 1 member

Outstanding editor!  I have been using nano on the command line for years when developing, and this like solution is so intuitive and natural to use.  I will be working on the ROM integration next so

it can be coupled with the cc64 compiler being developed.  Thanks so much for porting to the x16.

  • Like 2
Link to review
×
×
  • Create New...

Important Information

Please review our Terms of Use