Suggestion:
Use Line(X1,Y,X2,) for horizontal and Line(X,Y1,,Y2) for vertical.

The empty arguments would tell the parser to use the optimized routines.

I agree with Quigibo.

In the far future, I would be nice to have the ability to have automated BGM.
Using the interrupts, perhaps?

Quote from: Quigibo on June 14, 2010, 10:18:55 pm

I think that might be a little confusing.  And also, that is currently valid syntax since empty arguments are filled with the last expression.  That is, your first example is parsed as Line(X1,Y,X2,X2) and the second one becomes Line(X,Y1,Y1,Y2) it can actually be a useful optimization occasionally.  This goes for all multi-argument commands.

I'm probably just going to use the horizontal/vertical tokens for fast lines with the syntax: "Horizontal X1,X2" since I can use the number of arguments to determine if its the line routine or the scroll routine.

You mean Horizontal X1,X2,Y1 or something like that, right?

* DJ Omnimaga hopes Quigibo was planning to actually let the user choose where to draw the line

I hope so too, otherwise it would be kind of like a BSOD/LCD Test Mode without the overload of electricity. O.o

Quote from: DJ Omnimaga on May 25, 2010, 07:58:47 pm

Keep in mind App compiling will take over 10 minutes on-calc, though.

@Raylin: lemme just explain why: the calc processor is too weak to handle all the cryptographic computations involving the signing of the app. (they still have to be signed, even when you already have them on your calc)

I thought they only had to be signed when transferring them to other calcs.

I will most likely sign them on the computer, personally. Much faster. That's providing it is even possible to send an unsigned APP from the calc to the computer, though. COuld anyone verify this? Also doesn't it require the app in .HEX format?

I really dislike the applications that do a process for 5 minutes with nothing to show for it but a blank screen.

Yeah I remember that about MirageOs sorting in version 1.1 with 100 programs it took 40 minutes and I thought my calc froze . IN 1.2 it's not as bad.

I don't know much about app signing, but the 10-15 minutes signing process thing came from BrandonW mouth so I guess he knows how that stuff works pretty welland there might not be other ways. As for archived appvars, do you mean to reduce the signing time (since the app wouldn't be multiple pages anymore)? Also I am not sure if Quigibo was planning to implement reading data from archive except if stored in an APP. We would probably still need to unarchive, read data, archive when RAM is running low, unarchive another appvar if needed, load other data, etc. SOmething that would cause a lot of loading times (and wearing off the Flash chip with garbage collections, probably)

DJ suggested a really cool idea.  I think If I use my hooks correctly, I can have the Axe Tokens automatically enabled whenever the basic editor detects the program it is editing is an Axe source file and then revert back to normal when you quit so that the tokens never get mixed up or confused when you're dealing with regular BASIC.

I'm just worried if I eventually want to switch to Axe Tokens as the default tokens, then computer coding might get more complicated since programs like SourceCoder only use the original tokens.