Hey, its taken care of now.  Don't worry about it.

I'm also going to say this frankly.
Stop the bullshit, guys.  I will not tolerate a single negative comment towards either of these people.  Keep in mind that Axe isn't even an official release yet.  Stop making any negative comments, period.  You do not want to test me.

happy forum is happy

my 2 cents:

I think that, while the original goal of Axe was to provide a similar style to TI BASIC programmers, this is kind of necessary. Commands like Tangent( do not share any similar syntax between Axe and BASIC, and so it's fine to have the token hook replace this with Bitmap(.
Like DJ said somewhere, i think that many of the tokens that share similar syntaxes, like Repeat and possibly conj( should be switched back.
In other words, practice moderation when changing token names. If, Quigibo, you really are running out of possible intuitive commands, then by all means use the token hook to "make" new ones. At the same time, however, previously established commands should retain their original token.

I feel like this will provide a way for newer members to see less "replaced" tokens, as well as not intro'ing too much of a change for longer-time Axe users. I mean, I always just do "Math" "1" when I think "command to display ASCII," so...yeah

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.

I think the automatic token change described in your 3rd paragraph might be the best solution. When you open an Axe program in the PRGM editor (or SourceCoder/Cooliojazz editor?), I think it would be good if those tokens automatically changed, both in menus and the CATALOG.

Also, a few hours ago, SirCmpwn suggested a SMF mod that would allow us to use the Censorship feature of the forums per individual sub-forum instead of having it set global. I will use that bad word filter to change old tokens to new ones in people source code, so people won't need to fix all the old code. IMHO, those old snippets should be preserved in a as useable way as possible and preferably not requiring way too much work from their authors (or staff).

In Cooliojazz/Kerm cases, they could simply set their respective editors so when a program starts with a dot, it's parsed as an Axe program.

I also think the version/change history, including new tokens, should be included in a plain text file or in the PDF with Axe Parser releases. What I mean is the content of every post in the downloads topic (except the screenshots)

As for the forums themselves, I have taken precautions to make sure what happened this morning won't happen again in the future. I will also be taking a break from some stuff soon, too, I think. I've done way too much lately.

I am also sorry for having blown this way out of proportion. I am still trying to figure out what made me overeact this much at such thing, when I normally overeact only if somebody intentionally annoys me for a while (worse when ppl supports his action). The only thing I could find out is having burned myself out by devoting too much time on the site in many ways despite my increased real life work schedule/load, but I still wish that did not happen. I agree with the small quote located in Quigibo profile under his avatar.

int() (changed to sign{ )
i n t ( ) (not changed to sign{ )
people would figure it out rather quickly.

eh, i don't think it's so bad. regardless, anyone who's bothering to switch from BASIC syntax to Axe syntax definitely has enough determination to figure out how different token names work. all you need is about 2 sentences of documentation to explain the feature, how to toggle them and that there is no difference between Conj( and Copy(