Huh, that's a really weird tokenizing error.  I confirmed on my linux box: I'll go ahead and take a look at it (although it may take a week or so before I have time push the fix out).

Erm, could you clarify what you mean by 'fixed color'?

If you're referring to how grayscale usually has a flickering/diagonal effect in real calculators, I'm probably not going to in the near future because I'm not really sure how to code something like that. 

*Michael_Lee is shamed into posting

I don't know if somebody brought this idea up yet, but one idea apart from internal events such as contests and whatnot would be to try to raise awareness of calculator coding outside of places like Omnimaga.  For example, the main reason I joined Omnimaga was because of a video of Axe I saw on youtube -- perhaps more youtube videos might attract people who are willing to stick around?

Necropost!

Here's a shiny new youtube video:
<a href="http://www.youtube.com/watch?v=i2cjxqMY4bg" target="_blank">http://www.youtube.com/watch?v=i2cjxqMY4bg</a>
(it comes out a bit small, so try going to the actual video?)

...and the download link:
http://dl.dropbox.com/u/10645749/axe-interpreter_v0.3.zip

So, here are a list of changes since the last official version!

• The parser and interpreter have been completely remade so it can handle goto statements
• Grayscale
• Almost anything related to memory has been finished

...and the things I need to work on:

• Adding constants
• Adding sprites
• Working on speed

The list of all supported tokens can be found here:
static.michael0x2a.com/commands.html

Wow, this looks really cool.  I don't have the technical skill to really give this a thorough run, but I do have one suggestion -- try adding an option to change the font size?  It's a tad too big for me.

I revamped how I handle memory and graphics.

Full pointer madness is working, along with graphics (including grayscale and sprites).  I still have to implement all the different sprite variations (which should be easy), and redo scrolling (Horizontal/Vertical +/-).

On the lexing/parser side, I've been procrastinating and still haven't rewritten it to compensate for those blasted gotos

Does anybody know where I can get the font used for the TI-84?  (both the small one and the homescreen one?)

You could try making a virtual PC (using something like VirtualBox) and installing Windows XP on it.

Progress report:

So, I essentially have to rewrite a chunk of my program.  Basically, the story is, I'm first converting text into a sort of tree -- lists containing lists containing lists.  Unfortunately, that format won't allow me to easily code in goto statements -- there are ways to hack out a solution, but they're all slow and brittle. 

So I'm rewriting my code to first create a tree then convert it into a single flattened list so I can easily jump to a line number.  Which is a pity, since I thought my whole recursive scheme for running the tree was cool (I like recursion). 

I'm also angsting over whether or not I should turn my tree into objects containing objects or just keep them as nested lists.

You know, gotos are generally seen as evil, but I never realized they were diabolical to implement too

Currently, strings aren't supported.

A .axe  file is the same as a .txt file.  You can use either -- the extension doesn't matter.

^ That.  It could also eventually let you port your Axe games to be playable on the computer.

Do you know where I can find an official copy of what Wabbitemu uses for key mappings?  This should be pretty trivial to change. 

Another release!

getKeys, scrolling, a few more pxl-commands, rudimentary pointers and constants (using L1-L6 for lists, mostly), a bunch of math commands, and a few more control structures were added.

Download here: http://dl.dropbox.com/u/10645749/axe-interpreter_v0.2.zip
Executables for Linux and Windows along with source code should be included.  (Tested on Windows 7 (64 bit) and Linux Mint 11 (32 bit))

I then whipped up a quick tunnel game below, which you can watch below

<a href="http://www.youtube.com/watch?v=xscgq5-lwkw" target="_blank">http://www.youtube.com/watch?v=xscgq5-lwkw</a>

(Hmm, the embedded youtube video is a bit too small.  Is there a way to make them bigger?)
(Edit: Weird, you can't see the mouse.)

Additional notes:
By default, a few keys are mapped to getKey -- for example, pressing backspace maps to 'getKey(15)', for example.  Included in the folder should be a file named 'keybindings.config' which can be edited to change which keys maps to which getkey.  That file has to be in the same folder as the exe.

You can use the '{ }' brackets and L1-L6 for lists and pointer stuff, but currently changing L6 or L3 doesn't change the buffers yet.

Using @OPEN "filename" (you have to include the quotation marks) can open files directly inside the interpreter.  If you use those commands inside files, I guess that would work as a sort of substitute for imports/subroutines, at least until I have legitimate imports, subroutines, labels, etc. working.

You have a config file, and you assign whatever computer key you want the appropriate computer key.  So to make GetKey(15) equal the backspace key, you would edit the config file so the appropriate line reads

^ That.

Note: Later today, I'll upload another version.  GetKey has been implemented, along with pointers, so you can have legit lists.
I'm having some trouble integrating the screen with manipulating memory, so writing to L3 or L6 won't currently effect the screen.

Does anybody know how you can use a bytearray or a list (in python) to manipulate or create a pygame Surface?

Oh, that's intentional.  To turn that off, type '@DRAW 0' and to turn it back on, type '@DRAW 1'.  I thought that constantly having to type 'DispGraph' was a bit annoying.


Thanks for the suggestions!  I ended up using multiple processes instead of threads, but the final effect was the same.  Never mind.  Should have tested on Windows.  Got threads working now.

I'll look into the other suggestions, thanks.

Really?  What do you mean?