![]() ![]() skip skip printing space after DATA and REMįrom the bottom up, going the other way, only the bare minimum so far. oneliner fake the offset and line number It's implemented as a bunch of utiliies using inotifywait, a python script to grab the AppleSoft program in memory from the AppleWin save state file, convert the hex to binary and pipe to fp2txt, and finally use xdg-open to open the text file.Ĭonvert Applesoft BASIC binary from standard input to text. When I press F11 in AppleWin, the current AppleSoft BASIC program opens in a text editor. Starting from the bottom up, I've implemented a few of the "easier" items. Sorry, the parts you are interested in have not been implemented. Hello mmphosis, can you provide an update on whether you went forward with the vision you laid out in your post? ![]() Press F11 (save state), and a daemon watching for the save state file to change, runs a script to detokenize, format, and open the source code the editor of my choice. send F12 (load save state) and enter key (open default save state file) to AppleWin.maybe even update the Program Counter (PC) to automatically JuMP to the RUN routine.Tokenize the output into the Applesoft Basic binary format.save a symbol table (of routtine & variable names), and optionally append the symbol table as comments in the Applesoft program.long variable names get converted to a pool of single character Applesoft variable names.use labels instead of line numbers (like Virtual BASIC does.).Parse the current source code text file, possibly with some features like.I press Command+R (or F5) to Run which runs a script which might do all of this. So in theory, I write code in an editor of my choice. I am looking into automatically writing tokenized Applesoft binary directly into this file. In the "Advanced" tab in AppleWin Configuration, there is a Save State section. I've been thinking about how to run code "hot" and "live" in memory within my own toy emulator. And, I am not talking just about Applesoft, but other languages CC65, 6502 assembly, PLASMA, and many others. It would be cool to edit code in a programming editor of our choice, hit F5 (or Command R) and run the code instantly in the emulator. ![]() There is the debugger in AppleWin, and I think there are commands to load files into directly into memory. I like AppleWin and run it even though I run it via Wine on Linux. I use a bunch of different Apple II emulators. Virtual Basic looks like it has a "ultra compact code" option that would do some of what I want. I try to avoid using GOTO, and write the code using FOR. I order the most frequently used routines to the beginning of the program, for example. I try to store values in single character variables rather than hard-coding the numbers. I compact as many statements onto a single line. I usually go the other way and make my code less readable to optimize for speed because Applesoft is slow enough already. From what I gather, you are trying to make your code more readable. It got me thinking about how to parse the source code, including automatically generating line numbers. I started creating a command line utility that converts text to Applesoft file format. I've been thinking about ideas for how to make this better. I know I can copy and paste code from a text editor to AppleWin, but that is hardly ideal. I'd found two very promising tools, but one (Virtual BASIC) still has its web page but apparently there are no download links (it's unclear if there ever was a version for Windows, as the screenshots apparently are from Ubuntu, but that would not be a major problem) and the other (WASP) does not seem to be working in conjunction with AppleWin (whenever I try to run the code in AppleWin within WASP I get an "emulator not running" error, maybe WASP was using some Windows API that can no longer be leveraged, or maybe it doesn't "talk" to the current version of AppleWin). I'm having trouble finding a working development toolkit. My goal is to work on Microsoft Windows, test the code in an emulator (AppleWin), and when ready, trasfer the program to a 5,25" floppy disk and to the actual hardware. I'm an Apple IIc owner and I would like to port a little BASIC project to the Apple II platform (so far I've done Commodore 64, Commodore VIC-20, Sinclair ZX Spectrum and Sinclair ZX81 versions).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |