The time has come!  Yes, I need to actually start making a manual and/or tutorial for how to use Axe Parser.  I need at least a small one so I can release the beta next week or else new coders will have no clue how it works and this subforum is getting way too large to find that type of information.  I'd like to have a very clean format.  HTML is okay, but I'd really prefer a pdf instead so I can have more control with the formatting and it just looks nicer in general.  So does anyone know a good free program that can do the job?  Or if someone is really good with this kind of stuff and would be willing to put the articles together, that would be great too.

Which brings me to my next point.  I think I'll need a lot of help writing this since there's already over 100 commands and I'd like to eventually have a little paragraph about each one with an example or two.  If you're already experienced with the language and you have a little time to volunteer, let me know so I can put this together this week.  Even if you aren't an Axe expert, you can still help with formatting, reviewing, and writing the general stuff.  And yes, everyone that helps gets credited.

I'm not actually going to start writing this until after the next update which should be tomorrow, but I just want to see who can help.  I'll get everyone's email via PM and partition the load depending on the situation.

This community has already helped with the project enormously with all your feedback and motivation for me to continue at this pace.  Thanks so much!  

I can basically do any part of helping with this, and would really like to. The only things I can't really help with is creating example codes and explanations for the codes and I wouldn't be able to do things relating to the code. But I can proofread, expand, edit, etc. everything others write and I can organize everything. I can also most likely put it into a PDF file. If I start working with Axe soon and get the hang of it and what the commands are I can then start helping with the things I said I couldn't. But would love to help anyway I can

I'm up for it.
Just tell me what to do.

I would love to help, I understand the syntax pretty well so I could do documentation on them.

Mmmmm i don't know if i am familiar with Axe syntax enough to be of any help... X.X

lolz

Okay, I downloaded openoffice and I think I get the hang of it.  I'll post a list of articles that need to be written.  Don't feel pressured to write something you don't want to becasue I'm going to be writing whatevers left over anyway.  And I'll be rewriting or rewording the articles to make them transition between each section better so don't worry about that, its the core content that's most important.

If you want to do one, post your request here.  First post first pick to avoid duplicates:

• What is Axe Parser?  What can/can't it do?  Advantages/Disadvantages Quigibo
• How syntax looks/Differences with TI-BASIC Quigibo
• How to use the Parser Quigibo
• Numbers (hex vs decimal, signed vs unsigned, 1 byte vs 2 byte)
• Labels, Subroutines, and program flow.  Order of operations.
• Pointers 101 What are they? How do they work?
• Data, Memory, how to read and write to them.  Making sprites/strings/maps.
• Reading/Writing/and creating Save Files.  How to archive/unarchive
• How to optimize/neat tricks.
• Writing a simple game: A tutorial. SirCmpwn

Plus there are the Individual commands.  Each one should have 1 or 2 examples and a short paragraph sized explanation.  Some commands might need more or less though depending on how complicated they are.  I'll put the list of done commands right after this:

N/A

I have to write the "Using the parser" one becasue its changing next version with new options like shell support.  When you finish one, just upload it here as an attachment.

People could actually use parts of my news article regarding Axe Parser for the description, altough some stuff might need to be changed if not accurate, since Axe got updated a lot since then. Some grammar mistakes in my description could be done too, if any.