Well, not much progress.

I've been really busy with a bunch of projects lately (large essay, piano recital, trying to learn javascript (currently fail), trying to organize + make website for robotics club, somehow taking over said robotics club, large math assignment, mandatory school project (unless I don't want to graduate), etc..., all nearly at once)

The detokenizer that I've posted already should be pretty good to use, you should just be able to add it in without much modification (although it's really ugly...).

I'm going to go ahead and give you guys what I have right now, with the understanding that it doesn't work yet + might be overly complicated + is extremely different from previous versions + is written in Python 3.1 and might not work in older Python versions due to differences in how bytes are treated.

I think tokenizing in theory works, but I haven't had time to add in making checksums + generating metadata, and never really completed it.  Detokenizing should also work.

I'll probably resume development in about two weeks to a month (or I might just have to wait until summer).

I'm not too worried about licenses -- this project informally uses the Academic Free License 3.0, but really, I don't care too much about licensing as long as you don't go around claiming you wrote my code, or doing other weird stuff.

I have now the need to use this program since it's cross-platform and I need to write Axe files in Linux.

The version 0.2 seems to be in .exe and I'm not sure if I can use it the same way as the last one.

I got this when running:

david@David-PC ~/Documents/Calculators/TIConvert $ python main_v0_3.py
Traceback (most recent call last):
  File "main_v0_3.py", line 107, in <module>
    (input_path, target_path) = command_info.ReturnPaths(suffix = "_out.txt")
  File "main_v0_3.py", line 67, in ReturnPaths
    input_path = self.arg[0]
IndexError: list index out of range
david@David-PC ~/Documents/Calculators/TIConvert $

Python 2.6.6, Linux Mint 10

This goes from Axe source to ASM files and other way around?

I know for a fact it can do 8xp source to text file.

I don't think I finished text file to 8xp source, though you could give it a shot.

And I don't even want to try text or source to compiled 8xp (that's what Quigbo's working on, after all )

I know the latter doesn't work obviously. I need the second one.

Michael, I really think you should try and finish this

I finished!

Changes:
> You can convert .txt to .8xp now!
> Switched from Python 3.1 to Python 2.7
> Rewrote everything
> Switched to MIT license
> Fixed some bugs.


Edit:
I don't feel like making another post, so here's a short update.
Changes:
> A bunch of minor code fixes
> The parser can handle broken code a little better
> You can now have the .txt files have fancy output!  (characters like → and λ)
> TI-Basic tokens in .txt files will still compile normally into .8xp files.
> All .dll and other similar files have been compressed into a single .exe file for portability

I'm going to work on support for TI-Basic tomorrow.

Sorry, I didn't take the time to read any other posts, but what do you mean by "it probably wouldn't be able to compile" in the OP?

--EDIT--
I have "fancy output" in TBEXE implemented, too (a pain in the butt to find which characters were accounted for, though)! Great minds think alike, I guess

Ah.  Back then, tokenizing text was very mysterious to me, and I wasn't sure if I was capable of programming such a thing.  Converted text files should have no problem compiling now

I just started a Python TI-BASIC implementation a few weeks back. It's actually doing pretty well.

My parser/tokenizer implementation is here
I'm using a list of tokens and simply comparing each token (sorted from longest to shortest) against my position in the text until I find a match, then incrementing my position by the length of the match. It's worked perfectly so far with many tests, and it's extremely fast (5000 lines / 70k characters took <1s to tokenize). If you take away the cruft for expressions and bracket parsing, it might be useful for your purposes

This commit has the raw token lists, the current version is all dynamic. The full parser from that commit might actually be useful, as it's the raw version with just string output.

AFAIK, calccrypto doesn't have an account on omnimaga.