The fact that an Axe source file starting with two periods (a subprogram/library) doesn't show up in the compile menu is intentional. That way, you don't have subprograms and libraries cluttering up the compile menu, since it doesn't make sense to compile either as a standalone executable.


Just include prgmLIBNAME as a line in your main program and the library will be included and compiled with your main program.

As I have been going throughout this forum I see a major difference between the forum for TI-BASIC & Axe. The key is in the way people have responded to the different types of programming problems.  Now I'm not saying axe parser is anything like the syntax of ti-basic, its not. What happens is the forum for tibasic need only be searched to find out how to do something.  But in this forum I see a common problem with the answers people give....
1) read the manual
2) a link to something that may not even be in axe, with the promise its similar

I can't say I've noticed this. If people do this, then they're being somewhat rude. I certainly try not do it myself, or if I do tell the asker to look at an external resource, I tell them exactly what part relates to your problem and how. I generally see others providing helpful answers as well.

What I find even worse than that is when someone responds with the irc chatbox and doesn't put the solution on the topic.

I know I tend to try to provide programming help over IRC a lot more than on the forums. That's usually because I can quickly and interactively solve the problem with the person experiencing it, working out any issues that may arise as they come. But if you'd prefer a solution be posted on the forums, just ask! I'm sure most people would be happy to oblige.

Why if the syntax for a simple command such as bitmaps not even mention that you need a header... I dont think that thats good documentation for a command.

It certainly does:

Draws a bitmap to (X,Y) on the main buffer, back buffer, or specified buffer respectively. The bitmap data should have in order: width (1 byte), then height (1 byte), then the rows of the image padded with zeros to the nearest byte. Mode 0 is "Pt-On" logic and Mode 1 is "Pt-Change" logic. Mode 0 is used if unspecified.

Now I'm certain that the command list has no single mention of what you have to do to make tilemapping work...

As others have said, tilemapping is an algorithm that a coder must implement, not a built-in feature of the language. Therefore, I wouldn't expect it to be described in the language's documentation. Also as others have said, basic tilemapping implementations are described and provided in a number of tutorials on the site. Finding them now is just a bit trickier, since the new site removed its explicit index of tutorials, which I agree is not a great situation.

and on top of that most of the tutorials never even say that you have to use hexadecimal notation for your tilemap declaration pointer.

You don't have to use a hexadecimal string to include data, but it's certainly an easy way. The hexadecimal data inclusion syntax is present in the command list, and it appears in numerous fully-explained code examples in the documentation (Documentation.pdf). Also included and documented in both is another common way to include data, Data().

I think that when we do have such a small community of axe users we should maximize the potential for understanding how it works. As ive thought about this alot... how about a more verbose command list.

What kind of verbosity are you looking for here? As far as I'm concerned, the Commands.html file does exactly what it's supposed to do, providing succinct but complete explanations of what each individual command/operator/syntactical element does.

Is there any way to add some sort of "suspend" to the program editor? Press a button and you're at the homescreen, where you can math out that constant you need, and then press it again and you're back where you were.

Now that's an idea I could really get behind.

Quote from: Runer112 on March 13, 2014, 08:42:21 pm

Quote from: TheCoder1998 on March 13, 2014, 02:34:34 pm

if thepenguin can make a 2-page app, he can make a 3- or 4-page app too right?

What's the point, then? It seems like all it would do is get rid of two physical applications and their menu entries without saving any archive space, which seems like a lot of work for not much benefit. And then things would start getting messy with multiple versions of zStart for people who do and don't want Omnicalc, people who do and don't want Symbolic, etc.

But everyone wants MirageOS libs, no ? It allows to run every single program (except maybe 20).

If there's leftover space in a two-page version of zStart, I can definitely see the point of adding MirageOS libraries. I just wouldn't be in favor of adding a page primarily for it (in that case, just use the original app!). But I believe TheCoder1998 was asking about consuming Omnicalc and Symbolic, which would in all likelihood need most of two pages for themselves, which I'm not as keen on and is what that quote was supposed to address.

I'm not sure about the whole gray comments thing. You'd need to be constantly updating the screen for the gray to look solid, which means allocating about 2/3 of CPU time just to grayscale updates. Not only would that result in a pretty noticeable slowdown of the editor, but it would probably have a large (negative) impact on battery life, as well.


And then there's the implementation difficulty, too.

This emulator only emulates original Game Boy games, as in the original 4-color grayscale ones (although they can be colorized with fixed palettes).

It's certainly doable. But I'm guessing that most people aren't too concerned with integrating such features natively, as they already work fairly well as simple parser hooks and MathPrint is a decent enough replacement for Symbolic. Finding someone with the intersection of motivation and OS patching/hooking skill (unless that someone is you) could be tough.

I would love this feature. How impossible would it be to import something like MathJax? Some guy seemed to know how to do it.


Or just pick something that's already designed for SMF2.