This being my first post since last night, I will attempt to explain what I am going to do.

I have decided that it will be too confusing to have 2 ways to say a command and it will divide the community as was seen this morning.  I had no idea how controversial this was, I thought it would not be such a big deal.  There are only 5 or 6 command spellings that would actually change and the rest would just be for new commands only.

That said, I will be going basically with a smooth transition to eventually make the new tokens the standard.  From now on, I will be removing the [alpha]+[vars] shortcut becasue its annoying and you might accidentally forget about enabling/disabling.  I already have automatic recognition working which only displays the new token name if it is part of an Axe source code.  But by default, this option will be disabled and just the normal tokens will be displayed.  Eventually, I will make the new tokens the default, and you will have to change the setting to display the old ones if you still want the original token names.  Then, I am hoping to remove this option and just make it on by default, but only if I see that everyone has adjusted to them and there are enough computer applications and things like that that support the new token sets.  Also, I will make sure the names I choose are all finalized before I do that so it doesn't change once again.

There will be a separate documentation that deals only with token names, their equivalences, how they work, how to use them, how to change the settings, etc.  But I will gradually transition the doc and commands list to the new spellings as people start getting used to them.  This processes will likely take more than a month becasue I want to make sure that everyone is adequately adjusted.  I hate sudden changes as much as everyone else and I know exactly how that feels.

So there is no need to change the old posts.  They are still valid even if they use the TI-BASIC spelling.  Its really not that hard at all to figure out most of the commands are referring to (like how "conj(" and "Copy(" sound almost the same).  I don't think it will be confusing at all, especially since even if they had no idea that an old command was used instead of a new one, they would go to the menu where they normally see that command in the program editor menus and realize that it does indeed have a new spelling.  If they were absolutely unsure they could use the conversion chart that would come with the documentation.  To think that some new coder can't figure this out on their own is completely ridiculous.

This decision is still not final, but this is what I'm leaning towards so I thought I would best let everybody know what's going on.  Also, someone else brought up the point that this is still a beta.  Please remember that.  I could have kept the entire project a secret until 1.0.0 came out so that there would be a single universal and unchanging standard with the syntax.  I decided not to do that becasue I wanted to share my progress with the community and I figured it would be useful even at its early stage.  I have already gotten emails and messages telling me how much people enjoy the Parser and how it has gotten them inspired to code again and I feel my decision to release betas was well worth the downside of instability that comes with it.  I'm really sorry if some of you got too used to the old spellings over the past few months, I never meant to give the impression that nothing would ever change.  I am hoping it will not be too much trouble to learn the 5 or 6 new ones.

The Tangent() command uses an OS bcall which is much slower than the 8x8 sprite drawing routines, but its still fast enough for most things and more convenient than drawing a bunch of 8x8s and it takes up hardly any memory in the program.  Because its an OS routine, they decide how the flags affect it so I really can't do anything about that other than tell you to change the flags with the Fix commands.

Also, I know it clips the sprites, but the documentation for that command (_DisplayImage) says that you cannot draw the image totally off the screen for some reason.  I don't know if that means it will corrupt ram or something so use with caution if you draw completely off screen.

Oh another thing, I should mention.  It uses Pt-Off() logic to draw the sprite.  That is, it erases behind it as it draws.

The actual doc is easy to do.  I can very easily "add another column".  But at the same time, I want to make things as simple as possible.  2 separate pdfs in the same zip file seems like its separating the Axe community in half and also there are probably only 1 or 2 commands in there that need changing at all.  Its not MY documentation that I'm concerned about becasue I have complete control over that.  Its how others will document their code and their tutorials, etc.  Should they really have to make 2 versions to appeal to 2 crowds is the question.

Not all the new tokens I'm keeping by the way.  "Repeat" I realize is best left alone since it functions very similarly to BASIC.  Others like "sign{" would likely be kept.

Correct

I can see your legitimate concerns, but I'm a little confused about that last part:

Leaving things as they were would also prevent potential issues with future TI-OSes and third-party APPS releases for short periods of time before Axe is updated.

Why would new TI-OSes or apps conflict with displaying a different spelling for the token?  Especially if its only during the program editor session with Axe source?

Is it possible you were just running a different program previously that might have changed the LCD settings?  See if ALCDFIX makes it work again.

Yes, except the commands list and stuff would be all the new token names and there might just be one additional chart for conversions.  But all other example code and documentation would be with the new tokens.