Axe Parser

[Runer112]

I would like to improve line drawing, but I need your help! I want to add horizontal and vertical line commands, and then also allow modifiers to all line and other drawing commands to allow white or inverted drawing. The question is, what syntax for these features looks best and/or is easiest to use?

I have added a poll to get your input on this question. Really this is two polls in one:
[1] What should the command for horizontal and vertical lines be?
[2] What should the syntax for white and xor drawing be?

So please look over all the options, and then pick ONE in the [1] category and ONE in the [2] category. Please consider the pros and cons of each; for instance, Horizontal seems like a great choice, but it might cause confusion with the existing Horizontal+ comamnd; and tokens like LinReg(a+bx) can be turned into much better names with the token hook, but without the token hook, they may look confusing.


I would like to note that, for specifying white and xor drawing modes, something like WhiteLine(X1,X2,Y1,Y2) is very much a possibility as well. But then the question is, what tokens should be replaced to be White and Xor? I don't see any obvious choices, but if you have an idea about it, pick the "other" option for [2] and post what your idea is.

[willrandship]

I've never been a big fan of overloading functions. It makes code less readable. I also don't see a need to use new tokens, especially since we're getting to the point where those tokens are in more and more obscure sub-menus.

I rather like the W<command> syntax, but I'd also be okay with the !. It's a little misleading, but not too bad. Also, HLine(), etc. is faster to type than LinReg()

If typing on the calc wasn't so slow I'd advocate pure-ASCII compiling. Actually, I would like that anyway, at least as an option.

[Builderboy]

I am in favor of preceding the commands with the letter modifiers.  This allows the same syntax to be used for both the horizontal/vertical lines, as well as the different drawing modes for the drawing commands, which would help keep the syntax more consistent.  Additionally, adding more and more extra tokens for new but similar commands can get annoying when they start being spread out over multiple menu's, with the letter modifiers we only ever have to look towards a single token.   

[Deep Thought]

I thought ! would be great because it means "not" in terms of !If already.

I doubt there'd be more than two of these "prefixes," so W and X out of the entire alphabet feels a bit weird to me. ! and i are characters anyway (so they're more like prefixes), and as I said, ! is already used for something close to that meaning.

Also what would happen if you did something like this?

→XLine(,Y,X+3,Y+3)

[Freyaday]

Also what would happen if you did something like this?

→XLine(,Y,X+3,Y+3)

You'd get a syntax error.

[leafy]

Yeah, but I think what he's trying to get at is loading a value into X, then using that value in HL as the first argument for the Line() command, which should make sense. It's easier to modify values outside of the command block.

[Matrefeytontias]

Then just add a newline between X and Line and it will work.

[Runer112]

So I just released a new version of Axe about 4 hours ago... and I managed to screw up the flagship feature. So I have quickly fixed it and replaced the bad 1.2.1 with 1.2.1a!

If you were one of the five who downloaded Axe 1.2.1 already: go get the fixed version.

For everybody else: what crippling bug? I would never make such a silly mistake, what are you talking about? I don't see it anywhere.

[Freyaday]

The error message for a too-large app is "ERR:MEMORY". It really should be something more descriptive, like say, "ERR:TOO BIG FOR ONE PAGE" or something.

And that is too big for one error message. Anyways this isn't really a bug, and you still knew what it meant so it seems like it's descriptive enough. Maybe you won't even see that error eventually.

Does this mean we might be able to have two-page Axe apps in the future?

[Runer112]

The error message for a too-large app is "ERR:MEMORY". It really should be something more descriptive, like say, "ERR:TOO BIG FOR ONE PAGE" or something.

And that is too big for one error message. Anyways this isn't really a bug, and you still knew what it meant so it seems like it's descriptive enough. Maybe you won't even see that error eventually.

Does this mean we might be able to have two-page Axe apps in the future?

Eventually I hope so, yes. But as I've mentioned in previous posts, it's a logistical nightmare so don't expect it any time soon.

[Freyaday]

The error message for a too-large app is "ERR:MEMORY". It really should be something more descriptive, like say, "ERR:TOO BIG FOR ONE PAGE" or something.

And that is too big for one error message. Anyways this isn't really a bug, and you still knew what it meant so it seems like it's descriptive enough. Maybe you won't even see that error eventually.

Does this mean we might be able to have two-page Axe apps in the future?

Eventually I hope so, yes. But as I've mentioned in previous posts, it's a logistical nightmare so don't expect it any time soon.

Alrighty, then!

[Sorunome]

The error message for a too-large app is "ERR:MEMORY". It really should be something more descriptive, like say, "ERR:TOO BIG FOR ONE PAGE" or something.

And that is too big for one error message. Anyways this isn't really a bug, and you still knew what it meant so it seems like it's descriptive enough. Maybe you won't even see that error eventually.

Does this mean we might be able to have two-page Axe apps in the future?

Eventually I hope so, yes. But as I've mentioned in previous posts, it's a logistical nightmare so don't expect it any time soon.

Let's party!
I've been waiting for this feature long
But it would still give error memory if there isn't enough ROM
And wouldn't you need to like write page to page and swap a lot between ROM and RAM because the calc doesn't have enough RAM?

[Matrefeytontias]

Bump,

At school, I'm in a project that requires the linking abilities of my Ti-83+, and since I'm too lazy to make it in assembly (), I wondered : what's the protocol you're using with the Send( command ? My goal is to catch the bits sent with an Arduino in a byte.

Also, since these functionalities had been added to the latest version of Axe, I think you should remove the current poll and make a new one

[Keoni29]

I usually write my own link routines. Toggle one pin in the port. This is your clock. Every time want the bit to be 1 you toggle both pins off. Every time you want it to be a 0 only turn the clock pin off. Now for receiving data you send thearduino 8 bits to tell it the calc is in receive mode. Then toggle the clockpin 8 times. On the arduino side you run a bit of hardware interrupt code on the clock pin. Put bits on the data pin.

[Matrefeytontias]

In fact it's ok, I've already wrote my routine thanks