Ether lession #0: Introduction and pseudocodes

[JoseskVolpe]

Introduction
¡Welcome to your first programming logics lession!
Get ready for a lot of pain, headache and to get spanked by a lot of f****ing compiling errors or some... dangerous memory manipulation mistakes you will probably make
¡LOL look at your faces reading that! *laughing out loud and acute as a fox*
Chill, i'm just kidding... Partly... Yeah, that's not a lie you'll crack your heads sometimes, but you'll get used to it.

Anyway, let's begin. You'll need Alchemy OS to do the next lessions, if you haven't, don't lost your time install it already
Download Alchemy OS: http://dedomil.net/forum/showthread.php?tid=5865
Alternative download (JAD): http://alchemy-os.sourceforge.net/get.php?type=jad
Alternative download URL 2 (Choose a version): https://sourceforge.net/projects/alchemy-os/files/

Talking to your phone

Developing a game involves a lot programming. You have to pass instructions to the machine to make anything on your game. You'll basically "talk" to your phone.
You'll say "phone, i need you to load this sprite and show it on the screen". But instead, you'll say it on a language it can interpret
A computer (any computer, including mobile phones) needs to be told in a very literal way exactly what it have to do, step by step. That's why you need to know programming logics.

Programming logics is awesome because after learnning how to communicate to a machine, how they interprete codes, you'll be able to learn ANY programming language without much difficulty
That's why FOR OUR LUCKY Alchemy OS exists, and i've choosen Ether language for that

¡Pseudocode! Example

Before beggining the next true first lession, when you'll finally crack your head, we'll begin with something that does not involves any coding at all

Let's do a setp-by-step procedure for something randomly.
In front of you, there's a desk. On the desk, there's a phone to the left and a unplugged charger to the right. Above the desk, there's a wall socket.
There's no battery in the phone. ¿How do you charge it step-by-step?

1. Lift right arm
2. Move right hand front
3. Close right finger 1, 2, 3, 4, 5 //Hold charger
4. Move right hand up
5. Move right hand left
6. Move right hand front //Insert charger on wall socket
7. Open right finger 1, 2, 3, 4, 5 //Release charger
8. Move right hand back
9. Rotate right hand x_angle 90º
10. Close right finger 3, 4, 5
11. Move right hand down
12. Close right finger 1, 2 //Hold charger's plug
13. Lift left arm
14. Move left hand front
15. Close left finger 1, 2, 3, 4, 5 //Hold phone
16. Move right hand left
17. Rotate right hand y_angle -90º
18. Move right hand left //Insert charger's plug into phone's USB
19. Open right finger 1,2,3,4,5 //Release plug
20. Open left finger 1,2,3,4,5 //Release phone
    

Yup. That's what a machine needs to receive to do something like that
¿Dumb, right?
Now imagine you could face some problems: The robot's hand could not move enough to reach the wall socket, and release the charger in the air, for example. Or it could just push the phone outside of the table and break it. Etc etc etc
To be sure everything is going fine, we make some tests in our code. We call that "Debug". We can ask the machine to communicate with us. "Hey phone, tell me if you could load this sprite and why". We'll see it on our very first code pretty soon

¡Now, let's begin the activity!

Activity

I'll let you be less way literal than the example to facilitate for you. But be as literal as possible
Choose any of these and write a step-by-step procedure to:

• How to tie a shoelace
• How to open a door
• How to write a big "A"
• How to turn on a phone that is on a desk in front of you
• How to undress yourself (¿Because why not? x3 hehehehhe)
• Free.... Imagine a situation and write a procedure for that