I think it would be awesome to create a POTM award instead.  I think ticalc does a good job over the long run, but not too well in the short term.  Its the beginning of the month right about now anyway so its the perfect opportunity.  Maybe 3 or 4 people/programs get nominated every month (completed ones) and then the voting starts on the first of the following month and the winner is announced soon after.  It would be more exciting than a yearly award in my opinion becasue it is more frequent and current which I think is your main intention for suggesting this.  This award could even prompt ticalc to feature more programs since a highlighted program would be available every month.  A community vote would of course be used.

I've fixed the signing issue by the way.  Apparently, I had to add a dummy signature and update the size field of the app so you can now transfer from the calc to the computer and sign it there, its worked great for me so far.  Version 0.3.2 should be out either late tonight or tomorrow afternoon.

Is is not possible to just redraw the screen after the pop-up appears?  Especially becasue you say this is for a tile mapper, I would think it would be easy to call a "Redraw" subroutine that clears the screen and redraws all the tiles.  Then you don't need to worry about extra buffers.  Speed wouldn't be an issue becasue the redraw would only be needed when exiting the pop-up.

This entire thread is should ONLY be optimizations to the executable.  There would be no reasons to make source code "optimizations" becasue its irrelevant to the final product.  In fact, larger source code often leads to better readability and organization which is why I almost always cap my end parenthesis, leave comments, and sometimes indent when I've got a lot of nested blocks.

As far as I am aware, neither of those applications use the Token Hook so there should be no conflicts.  However, I may eventually use the Catalog Hook to rearrange the catalog which would of course conflict with any Language Localization apps.  Its possible I would need to use the App Change Hook as well which could cause other conflicts.  I will see if its worth all the trouble or not and if there is any simpler way to do it.

Okay, I've finished Axioms for the most part, I just have a few more things to tweak and more testing to do.  I updated the poll.  I won't go any higher than 4 options otherwise it will spread out the votes too much.  The "Update Documentation" idea would take me a long time to do, but it would involve writing a detailed commands list in the doc itself with examples and tips and stuff like that.  I would still keep the old one though just for reference and to have a "printer friendly" version.

The linking and port I/O would involve automated linking features that basically send and get bytes through the link port as well as raw data for perhaps microphones, IR controllers, sensors, advanced sound, accelerometers, electronic circuits, etc.

Little endian is only for reading and writing 2 bytes at a time.  Almost every sprite drawing routine I've ever seen reads 1 byte at a time so you will never have this problem.  In the rare cases where a routine reads 2 bytes at a time like for instance drawing an aligned 16x16 sprite super quickly, sometimes the programmer will compensate the reversing effect for you.  If they don't they would surely mention that the bytes should be reversed.