LoginLogin
Nintendo shutting down 3DS + Wii U online services, see our post

Smilebasic tutorial program?

Root / Talk About Programs / [.]

DefaultioCreated:
It's in the name, is it possible to make something like it? It should be interactive and the finished code during each lesson should be in slot 1. It will be saved up to the point of the last lesson you did. Your welcome.

what about my welcome Something like this seems pretty doable, really. Especially when most people just need to memorize command syntax and be exposed to the proper commands, you could work most into a one-line input.

Even though someone is actually doing something like this in miiverse.

A programming tutorial isn't exactly easy to do since you have to teach the basic commands and also the programming logic (that's way more important).

There is tutorials on YouTube by petitprofessor I learned everything I know from him

There is tutorials on YouTube by petitprofessor I learned everything I know from him
Yeah but he repeats his code a lot.

That's because when he repeats its because he's adding to existing code in New video Can't show changes without existing code

That's because when he repeats its because he's adding to existing code in New video. Can't show changes without existing code
Wat? I mean he does stuff like (For an example of repeating, he might not be this redundant)
BGPUT 0,0,0,103
BGPUT 0,1,0,103
BGPUT 0,2,0,103
BGPUT 0,3,0,103
BGPUT 0,4,0,103
BGPUT 0,5,0,103
BGPUT 0,6,0,103
BGPUT 0,7,0,103
BGPUT 0,8,0,103
BGPUT 0,9,0,103
When he can do:
FOR X=0 TO 9
 BGPUT 0,X,0,103
NEXT
That was just an example. I actually looked at his Dax shooter thingy game and had a looooad of code in it. [EDIT] I found a real example. In dungeon dax at line 19:
GCLS:CLS:SPCLR 3:SPCLR 4:SPCLR 6:SPCLR 7:SPCLR 8
When he (If he still wants to repeat, but with less code) could do:
FOR SP=0 TO 8
 SPCLR SP
NEXT
But then, he does not even need to do that. His line at 19 could simply be:
GCLS:CLS:SPCLR
I'm only replying because it gets a little annoying when people post programs (Even if they are good) with messy code.

Wat? I mean he does stuff like (For an example of repeating, he might not be this redundant)
BGPUT 0,0,0,103
BGPUT 0,1,0,103
BGPUT 0,2,0,103
BGPUT 0,3,0,103
BGPUT 0,4,0,103
BGPUT 0,5,0,103
BGPUT 0,6,0,103
BGPUT 0,7,0,103
BGPUT 0,8,0,103
BGPUT 0,9,0,103
When he can do:
FOR X=0 TO 9
 BGPUT 0,X,0,103
NEXT
It would be even better to use BGFILL, don't even need a loop and it's a lot faster execution wise.
BGFILL 0,0,0,9,0,103
But you are right, and I find myself going back to a lot of my code that has expanded over time and needing to do some refactoring. It's a good practice in general to be thinking of these things from the start, instead of just copy/pasting from tutorials.

Whoops I meant if he changed characters like
FOR X=0 TO 9
 BGPUT 0,X,0,103+X
NEXT

When you're trying to teach children programming you have to lay it all out there and be redundant. Besides, It's just a retro revival app on 3DS. Being efficient isn't really that important here.

When you're trying to teach children programming you have to lay it all out there and be redundant. Besides, It's just a retro revival app on 3DS. Being efficient isn't really that important here.
Actually, when we consider the limitations on the platform and the expectation that your code should work on both O3DS and N3DS (not even considering the factor of Wii U), being efficient is the most important thing. Yes, you have to spell it out, but you also have to challenge them. Pick up the pace when the time it right. Teach them that FOR loop. Without a challenge and a diverse skillset, there's no problem-solving ability. Programming is problem-solving. The platform isn't an excuse for sloppy code.

When you're trying to teach children programming you have to lay it all out there and be redundant. Besides, It's just a retro revival app on 3DS. Being efficient isn't really that important here.
Actually, when we consider the limitations on the platform and the expectation that your code should work on both O3DS and N3DS (not even considering the factor of Wii U), being efficient is the most important thing. Yes, you have to spell it out, but you also have to challenge them. Pick up the pace when the time it right. Teach them that FOR loop. Without a challenge and a diverse skillset, there's no problem-solving ability. Programming is problem-solving. The platform isn't an excuse for sloppy code.
Actually, I kind of have to agree with PetitProfessor here. Even when I taught COLLEGE students, we wrote inefficient code just to get the concepts across. The smarter students would pick up on it and tell us how stupid we were, but even doing things the naive way, many students still didn't get it. Efficiency should NOT be the first thing you try to teach new programmers, regardless of what platform it's on.

Oh yeah I probably should have been more clear. It's fine to write bad code early on if you have to make a point. You just have to get to that point where you start to move things along more quickly eventually. You taught compsci too? Gee have you done everything?

Oh yeah I probably should have been more clear. It's fine to write bad code early on if you have to make a point. You just have to get to that point where you start to move things along more quickly eventually. You taught compsci too? Gee have you done everything?
You flatter me too much lol. Yes, I taught extended lecture hours for the introductory programming course and for the senior level programming language concepts course. Sorry I didn't catch what you were trying to say. I agree with that point about moving on eventually.

Oh yeah I probably should have been more clear. It's fine to write bad code early on if you have to make a point. You just have to get to that point where you start to move things along more quickly eventually. You taught compsci too? Gee have you done everything?
You flatter me too much lol. Yes, I taught extended lecture hours for the introductory programming course and for the senior level programming language concepts course. Sorry I didn't catch what you were trying to say. I agree with that point about moving on eventually.
No it's fine, I was a little too impassioned. I just don't like the thought of "it's SB, it doesn't matter." And yeah, maybe we should praise you less before you become an egomaniac. You smell!

No it's fine, I was a little too impassioned. I just don't like the thought of "it's SB, it doesn't matter." And yeah, maybe we should praise you less before you become an egomaniac. You smell!
‧º·(˚ ˃̣̣̥⌓˂̣̣̥ )‧º·˚

When you're trying to teach children programming you have to lay it all out there and be redundant. Besides, It's just a retro revival app on 3DS. Being efficient isn't really that important here.
Actually, when we consider the limitations on the platform and the expectation that your code should work on both O3DS and N3DS (not even considering the factor of Wii U), being efficient is the most important thing. Yes, you have to spell it out, but you also have to challenge them. Pick up the pace when the time it right. Teach them that FOR loop. Without a challenge and a diverse skillset, there's no problem-solving ability. Programming is problem-solving. The platform isn't an excuse for sloppy code.
It's only one more thing to teach, saves time and it's more efficient. Quite honestly, this is a habit you want them to get used to doing because it's fairly quite simple to do. A for loop mini tutorial I guess. FOR loops are loops that start from a designated number set to a variable("I" in our case) to another set number. This can only be achieved from a lower to a greater value unless you configure the step to -1 to decrease by one. SYNTAX: FOR(Indicates you are about to start the loop) I(The variable we want to increase/decrease in this loop)= 0(The starting value) TO 6(The ending value) STEP 1(The amount that the variable I increases by everytime you hit a NEXT)
FOR I=0 TO 6 'The current loop will continue until the variable "I" reaches the second designated number
PRINT I 'Each time the loop is passed, the variable "I" increases by the value you set to your step. If not stated, one is default; this will print I
NEXT 'This will increase I by the value you set to the step. This will only be bypassed if the variable "I" reaches the second designated number
END 'You would only reach this point if the variable is greater than the value of the ending value
Correct me if I'm wrong about above ^

When you're trying to teach children programming you have to lay it all out there and be redundant. Besides, It's just a retro revival app on 3DS. Being efficient isn't really that important here.
Ah, sorry. I thought it was supposed to be advanced tutorials.

When you're trying to teach children programming you have to lay it all out there and be redundant. Besides, It's just a retro revival app on 3DS. Being efficient isn't really that important here.
And I'm one of those kids.....