0 Members and 4 Guests are viewing this topic.
The app could also handle loading a save file and copying the main program to RAM and running it (thus protecting the user from RAM clears making them lose the game and having to redownload it to their calc.).
Okay so I'm deciding how the team work will be organized since it looks like I'm recognized as lead dev. -All the (re)source, build scripts, etc. will be hosted on Github.-Shmibs's tok8x will be used to tokenize Axe code which will be stored in raw text files with .axe as extension.-SPASM will be used for all Asm code (which will e compiled as Axioms) and resource file generation.-Sprites should be stored as 8x8 or 16x16 BMPs since we use SPASM.-Code formatting conventions should be established.-When working on something, contributors would do their thing in a new branch which I'll approve before merging to master.-I'll write some scripts (GNU make based) to compile Axe code in an emu (tilem2) and then run it either in emu or on an attached hardware calc. This will make testing easy and convenient for everyone.-Every contributor shall be able to build binaries in order to test (including spriters and mappers). This means that at least a Linux virtual machine is required. I can cook up a VirtualBox image with all the dev environment set up if needed.Anything to add / ammend ?
Quote from: Xeda112358 on September 12, 2013, 10:09:28 am The app could also handle loading a save file and copying the main program to RAM and running it (thus protecting the user from RAM clears making them lose the game and having to redownload it to their calc.).Not sure what you mean by that, could you explain a bit further ?