Hello, world:

I am going to start my prizm development legacy by making a simple game -- snake!

This will be essentially the original snake with a few added features like beautiful graphics and many modes of play!

Since I haven't even started coding it yet (still getting used to managin prizm projects) I'll just show you my first step, which was to create a SELECTED and UNSELECTED bitmap for each mode -- for your convenience I condensed the two together in a PNG file for you guys to see:

So is this C or asm code. Either way it will be better than the Prizm snake I made in BASIC back in January. The problem with that was that drawing commands were way too slow and difficult to use.

btw you will want to remove the text at the bottom of the menu icons because the OS automatically adds the the name of the app. Or you could just wait for me to finish my asm shell, but that could take anywhere from 2 weeks to 1 month to finish

So is this C or asm code. Either way it will be better than the Prizm snake I made in BASIC back in January. The problem with that was that drawing commands were way too slow and difficult to use.

btw you will want to remove the text at the bottom of the menu icons because the OS automatically adds the the name of the app. Or you could just wait for me to finish my asm shell, but that could take anywhere from 2 weeks to 1 month to finish

I'm making it in C right now, and thanks for the icon suggestions thanks all for support

Or if you prefer you're own text, you could just leave the program name field blank. This isn't the name of the file, but just the text contained within the header that the OS uses. And don't worry to much about the getkey() call. Because the keys are memory mapped (you can view this in insight) it's really easy to make your own call that doesn't need any bloated OS call to work. Seriously getkey() is an overly bloated call that draws the screen, will run the screen receiver, does getkey duh, will exit your apps, and draw the status bar if shift or alpha is pressed. But then again getkey() is the only way I know of so far to exit apps

z80man, a way to exit apps:

sts.l pr,@-r15
...
stc @r15+,pr
rts
nop

The OS jumps to the program as if it's a subroutine, so you can just rts without generating any serious errors.

So Ashbad, how's this going?

Quote from: Qwerty.55 on May 02, 2011, 06:15:28 pm

The OS jumps to the program as if it's a subroutine, so you can just rts without generating any serious errors.

Are you sure about that? I've seen discussions on IRC where people have said that it's not like that...

Why don't we check what's in the PR when staring programs? We can check the code around the returned address and see how apps are initiated. And I did see how the code is loaded. As we know apps are ran from flash, but how it is done is the physical address of the app is mapped to virtual memory at 0x30000000. This would suggest that 0x30000000 is not a static address, but is remapped every time an app is ran.

@Qwerty you had a minor error in your code. fix'd it for ya

sts.l pr,@-r15
...
lds.l @r15+,pr
rts
nop

Ah ok. I hope you finish this, Pyrix, TanF and the others at one point too. I can't wait for screenshots too.