Axiom Requests

[Quigibo]

This is the place to make requests for specific assembly commands you might need in your Axe programs as well as to show off or improve existing Axioms. In case you're not familiar with the lingo, Axioms are assembly libraries that extend the Axe language.  They can be linked into your Axe programs by using the command: #Axiom(AXIOMNAME).  To write your own Axioms, check out the AxiomSDK in the "Tools" folder of the latest version of Axe Parser (assembly knowledge required!).

As another feature of this thread.  I have more space for custom Axiom tokens.  If you can think of some token names which have no near-substitutes and are general enough for many possible uses, I will definitely consider adding them.

Here is a list of current Axioms (mods, please update):
LCDKit: Control many features of the LCD screen - By Runer112
Pucrunch: Efficiently Compress/Decompress your program data - By Iambian
Crabcake: Allows you to turn your Axe program into a larger-than-8-KB ASM program - By Hot_Dog
SpeedKey: Optimized Getkey for just the arrows - By Binder News
Aiming Utility: Returns an angle that can be used to aim at targets given a delta X and Y - By Iambian

[ZippyDee]

There has been conversation about advanced graphics features, such as floodfill (with grayscale support) and masked LCD sprite display, which could probably make a fairly decent Axiom. Though masked LCD sprite display would probably go better in Runer112's LCDKit, and he was talking about doing it eventually anyway.

[Freyaday]

Something that would allow the font to be edited on-calc.

[ZippyDee]

That would be nice. Large or small font? Or both? I guess an axiom could include routines for both...

[Darl181]

Pucrunch: Efficiently Compress/Decompress your program data - By Iambian

Wait, I thought it could only decompress...

[Happybobjr]

It includes compression tools.

[Darl181]

Ok I guess that's what I get for only reading the first page

[Broseph Radson]

Graphscreen input with custom coordinates, allow/disallow lowercase, max length, word wrap, and custom prompt would be kickass. Something like gInput(x,y,[0 for no lowercase, 1 to allow],[max length],["prompt" or Str# to use as prompt]

[Builderboy]

An elaborate drawing Axiom would be nice, with:

Lines
Circles
Rectangles
FloodFill

Lines circles and Rectangles would all have draw, clear and invert modes, possibly with a numerical argument instead of multiple r's.  Recangle and Circle would also have options to fill black, fill white, or fill invert.  FloodFill would have to be limited to fillBlack or FillWhite, as fillInvert doesn't make much sense

And all of the commands would be able to be drawn onto the front, back, or both buffers.

[Freyaday]

FloodInvert makes sense iff the target image has two colors.

[Builderboy]

ooooh i see what you mean, yeah I guess that could work

[Freyaday]

Some way to prevent access to the Catalogue during input or have char input instead of tokens. Also, perhaps a token editor, too?

[ZippyDee]

Graphscreen input with custom coordinates, allow/disallow lowercase, max length, word wrap, and custom prompt would be kickass. Something like gInput(x,y,[0 for no lowercase, 1 to allow],[max length],["prompt" or Str# to use as prompt]

That sounds like a fantastic idea!
Maybe it could also have support for character sets. Like...a pointer to the starting address of a 16 byte character set.

It would be really nice if Axiom commands could support optional parameters. Maybe the header could have something like one byte for "# of arguments expected" followed by one byte for "# of optional arguments." Then it would have another byte somewhere that is set each time the axiom is called containing the number of optional arguments supplied. I know that's complex, but I think it could end up being useful. Though it would add an extra 2 bytes per routine to your Axiom.

Ehh, just a thought.

[Freyaday]

I really need to learn Asm.

[FinaleTI]

CalcNet and gCn Axioms would be super-fantastic.