that feeling when your code works the way you want it to. so i filled the touch screen with random doodles.

Just don't load everything in one function call so that you can optimize FPS and Memory. Some debug information like FREEMEM function can also help you so that you can have a general idea of how much resource your program is using.

There is no "correct" way or standard in doing a certain program. It is up to the programmer to develop his/her own style and be comfortable with it. Choose a sample program and look at the way the code is organized. Some games I looked at are arranged by: Initialization, Main Program, Functions (input and output), Graphics (map and sprite), Sound, Data Arrays. Just don't load everything in...

Is it in Japanese? I saw one on youtube. 7ANYN3H4

if you want to save the program you are making in EDIT mode, hold L or R then click SAVE

6. loading maps created using smile tool

The last line of code seems to crash SmileBasic. Just put a comment tag on it. (also, GOTO @EXIT)

i think you will need to use SPLINK. will post one later.

5. animate a sprite

sure I can spend some free time

4. basic graphics commands

3. playing with button inputs.

2. more variable i/o. string variables end with $

going through the basics. 1. basic variable i/o.

have you tried INPUT instead of PRINT for getting var A?