Omnimaga
Calculator Community => Other Calc-Related Projects and Ideas => TI Z80 => Topic started by: Juju on June 17, 2011, 01:05:11 am
-
I heard some people wanted a wiki about Axe, much like all the other wikis out there about TI-BASIC, the Prizm and stuff. I'm wondering if anyone is interested, I could host it if you want.
-
Sounds like a good idea. Then we can share routines, etc. and access them more easily. Would there be a way to have an Omni topic for each page or something of that sort?
-
Probably, although you could just use the discussion page of that page. And you would have a page about each command with it's extensive documentation. I intend the main goal of the wiki to document each feature of Axe, their axioms and projects made in Axe in detail.
-
I'd be in on this. Maybe I could help a bit with designing it? We could use the Wikimedia template.
Then we can share routines, etc. and access them more easily.
...or entire source codes. ;D
-
As an alternative to the pain in the butt that is Mediawiki, I've heard some good things about Dokuwiki (http://www.dokuwiki.org/dokuwiki).
-
Hmmm I like MediaWiki (even if it's a pain in the butt). Oh well I already installed one, I'll link it as soon as I'll finish configuring it.
EDIT: Done, have fun. http://wiki.axeparser.co.cc/
-
I'm actually surprised that their hasn't been one made yet. I think this will be a great additional resource for Axe programmers. :)
-
I have a feeling this will be absolutely fantastic for Axe programmers.
We should probably get some initial pages set up so people can easily start expanding on it. What kinds of pages would be good to have to start?
-
It would be nice indeed. Just be sure to put a link to the Axe sub-forums and WikiTI for those who need extra help. We definitively need an Axe wiki, that'S for sure.
-
I have a feeling this will be absolutely fantastic for Axe programmers.
We should probably get some initial pages set up so people can easily start expanding on it. What kinds of pages would be good to have to start?
Same, that's why I set it up in the first place.
Also you can start editing it now :)
-
I have a feeling this will be absolutely fantastic for Axe programmers.
We should probably get some initial pages set up so people can easily start expanding on it. What kinds of pages would be good to have to start?
Same, that's why I set it up in the first place.
Also you can start editing it now :)
Yes, but my question is just about what kinds of pages would be good? We should probably have some general index pages. I just made a 'Routines' page, but it still has no content of course.
Edit: Added List_of_Commands, too. Should there be links to these other pages on the main page? Or do you want another index of all these pages? I'm thinking another index might be good so the main page can contain just general information and not be too cluttered.
-
Well, you can create a page for each element then put these elements in categories.
-
Yeah, I see that now. So should each command have its own page within the Documentation category? Maybe have them alphabetized with subcategories for different command types (i.e. Math, Graphics, Text, Data Manipulation).
-
Yeah, subcategories, good idea. Also I made a page which is much like the html page included with the Axe zip but it will include wikilinks.
-
Phew, how do I create a new wiki page / category?
-
Just go on the page you want to create, then click create.
-
The List of Commands page needs lots o' formatting. I've started, but I don't think I'm gonna do it all tonight...
EDIT: Also, I'm honestly not sure exactly how to do all this formatting, so I don't really know what I'm doing. I'm just using what was already there. If someone could give me some documentation on how it all works that would probably be incredibly useful.
-
Would you mind installing the Code Box template, Juju? Also, you should secure your front page. It's probably not a good idea to leave it editable by unregistered people.
-
Okay, now the List of Commands page is at least readable. Hope that's sufficient formatting there.
The only thing I see left to do would really be coloring and borders on the table cells, because they're kinda hard to read as-is.
-
The List of Commands page needs lots o' formatting. I've started, but I don't think I'm gonna do it all tonight...
EDIT: Also, I'm honestly not sure exactly how to do all this formatting, so I don't really know what I'm doing. I'm just using what was already there. If someone could give me some documentation on how it all works that would probably be incredibly useful.
I could help formatting per command...
plus I'll create a page about optimizing.
-
I edited the whole routines category, do you like it?
-
Whoever wrote this (http://wiki.axeparser.co.cc/wiki/Routine_template) should try to be more specific and scientific. This is programming (science) we're talking about, and vocabulary such as "whatever" and the "r1,r2,etc" should be more objective and precise.
Thank you
-
Like it this way?
-
Like it this way?
Nice :)
-
Here's the doc on page editing. (http://www.mediawiki.org/wiki/Help:Contents)
-
I know, I used that
-
yeah, Scout++, try to keep it very professional. I refuse to read non-professionally written informative pages.
-
I'll make a page on the different Axe releases.
-
Yeah, you can name it Changelog or something.
-
Should I contact Quigibo before making the ChangeLog? Considering that I'm pretty much just copying http://ourl.ca/4060 (http://ourl.ca/4060)?
-
I'll make a page on the different Axe releases.
That's a great idea.
Perhaps a warning of the problems with some of the releases (bugs)?
-
Maybe. Well I copied the [axe]List of commands[/axe] from the .zip file too. You can complete the [axe]Changelog[/axe], would be nice to have it in wiki form, I think there wouldn't be any problems, you just have to cite your source (like Wikipedia lol).
-
wow juju, that is NIIICE, did you parse it with some regexp?
-
wow juju, that is NIIICE, did you parse it with some regexp?
What? Also you might notice I already added the [axe]/[!axe] custom BBcodes.
-
Regular expressions. On the commands page, some of the stuff is too mushed together for my tastes. Great work, though ^^
-
Nice so far, but
The Axe bbcode is bugged. It misses the top line of the border ???
Also change axeparser.co.cc to axe.omnimaga.org and omnimaga.org to www.omnimaga.org. Those are the official URLs.
-
Done. You could had did it yourself, but Qwerty.55 told me to protect the page so it won't get vandalism and stuff.
For the BBCode, hm that's weird. Maybe something with line height.
-
You should copy the code I used for the other bbcodes, because it worked fine with them ???
And yeah I agree about vandalism, especially that Axe is quite popular and Omni attracts lots of traffic X.x.
-
I did copied the code O_o... or maybe i did it wrong? Oh well I'll check.
And the protect feature of MediaWiki is kinda nice for vandalism :P
-
Hehe, I was actually creating this a while ago, but lost time due to much busyness IRL. :P
A couple of suggestions...
1) The command list page should later be revised to have the monospaced font, but not be placed in a dashed line box. It should also link to the command's own page, where further explanation, examples, and information can be found about it.
2) Oh, and here's the old wiki that failed... and the Axe command template that was being made. You should install the Infobox template for this to work. This also uses "hidey boxes" as well, which may require a thing or two (maybe not) to work.
http://withg.us.to/axewiki/index.php?title=AxeCommandTemplate
EDIT: You should also poke Runer112 as well... he has a good idea of what he wants to put in. :P
-
Hehe, I was actually creating this a while ago, but lost time due to much busyness IRL. :P
A couple of suggestions...
1) The command list page should later be revised to have the monospaced font, but not be placed in a dashed line box. It should also link to the command's own page, where further explanation, examples, and information can be found about it.
2) Oh, and here's the old wiki that failed... and the Axe command template that was being made. You should install the Infobox template for this to work. This also uses "hidey boxes" as well, which may require a thing or two (maybe not) to work.
http://withg.us.to/axewiki/index.php?title=AxeCommandTemplate
EDIT: You should also poke Runer112 as well... he has a good idea of what he wants to put in. :P
Was thinking of exactly this. Each command in the list of commands should be linked to its own page with an infobox like on Wikipedia. And each page should be placed in the appropriate (sub)category.
-
You should also add a link to the tutorials on Omni for those who needs some more info by the way.
-
Runer, about the instant quit which uses sp, what is the $ED56 for? Can't you just do:
ld sp ($83E3)
ret
?
I like the progress!!
-
I finished the changelog page. Feel free to mess around with the formatting.
-
Runer, about the instant quit which uses sp, what is the $ED56 for? Can't you just do:
ld sp ($83E3)
ret
It sets IM 1 before quitting, killing any active custom interrupt. But it doesn't reset the interrupt ports, though Axe may or may not do anything to those. It should be removable. You can clean up your interrupts on your own.
-
What about including Runer112's Command List and Cycle Speed?
-
Why not. You can go ahead and add it.
-
There are a lot of new spam pages up on the Wiki since the last month or so and there might be more before. Also I noticed that guests can still edit pages. You definitively need to require admin approval or something for account creation and usage.
Thankfully, the Axe pages seems intact, though.
-
This seems to be quite out of date and lacking a lot of great possible articles, though :\