Ah ok I see. I'm not sure how to help, then (I'm not tech savy when it comes to that stuff)

After some time (during which I've been busy, primarily with getting back to school...), another update. Window, finance, and graph format tokens have now been added. I just need to add the miscellaneous and the TI-84+ tokens (again, as defined by TI|BD, and then I'll release 0.3, which I plan on posting on ticalc.org as well.

Unfortunately, with such a large token file, the program will continue to get slower, which is why my goal for the version after that is to perform some optimizations. Slowness will be a result of three things:

-Parsing the token file (dependent on size of token file)
-My reverse-substring process to parse the input file (not dependent on token file size)
-Searching for a token in the collection of token infos (dependent on token file size).

I know I can make the first somewhat faster. The other two probably can be made faster, but I lack the knowledge to do it.

I've also decided I would like to eventually have the option to detokenize, to convert an *.8xp file into an *.89z file that can then be detokenized on the calculator. That gave me the idea for another project... with the assistance of X-Link and a z80 assembly program on the other end, it would become possible to use a 68k calculator to transfer z80 programs around! I don't think anything like this already exists- X-Link is the closest to it that I know of.

I like the ideas you got. It would be nice with the help of X-Link if there was a converter. Would the converter be on the 89 or the 83+? In the later case, would it have to be something in Axe/ASM?

I'm glad this is still progressing, btw

Well, due to the ability of Axe to manipulate data in memory, I guess it could very be possible to convert the 89 file to 83+ program format in Axe. Otherwise, ASM is another good option since it allows even more freedom

Cool to see new version out

As for the special tokens, are you planning to add them in future versions or are they out of the question?

So, another update. I've gotten the "compiled token files" working. The interface for the seperate program is shown in the screenshot.

I decided it might be a good idea to define the file type in each token file (that's what "File type" is), so a file compiled for, say, the 85 could say "85P" in the VAR-LINK menu instead of 8XP. But I haven't implemented that in code yet.

This causes token initialization times to be near instantaneous- under a second. The downside? The size of a compiled token file is about double the size of the text file. So I left the code to parse text files in Solar89, giving users a choice between the larger and faster files or the slower and smaller files.

The actual tokenization process is still slow- hopefully that can be rectified with additional optimizations.

nice update! In the VAR-LINK menu will the 85P part be .85P at the end of the program or just be part of the file name, not the extension? I'm glad this is still progressing

I wonder if this will make it much easier to port games accross calcs?

It will be the text in the second column- that says ASM, PRGM, TEXT, EXPR, STR, MATR, etc. I'm calling that the extension- not sure exactly what the technical term is.

Porting eventually might become easier using Solar89, but I'll need to write some other tools first (like an on-calc detokenizer and an on-comp 8xp-89y converter, not to mention a complete set of token files).