Nice
I'm also starting to wish I made an account back then (to beat Adriweb)

Very nice

I love the Sierpinski triangles

This topic has been moved to News.

http://ourl.ca/15093

Try not to focus on how the speaker works, but on sound.
Sound is a waveform, with different frequencies and some other stuff.
Our goal is to simulate a wave by output 1's and 0's since this will make the speaker move and create the wave.
But since we only got 1 and 0 we can not have a perfect smooth wave and won't have uber quality sound.
But you will have sound

What you need to focus on is creating the wave. You will need to know some details of the serial port in order to be able to create the frequencies you want.
The serial speed is 115200 baud, which is changes/sec. Its like bits/s, but not really.

So, how do we create our wave with 'x' Hz and playing 't' long?
First of all you need to know that Hz is cycles/second. To put this simple that means 500ms of 0's and 500ms of 1's.
Now lets first calculate how many bits we need to send to create one wave of 'x' Hz.
115200/x
That means we need 57600/x bits of 0 and 57600/x bits of 1.
Lets create some pseudo code for that
function wave(x){
  am = 57600/x;
  sendBits(0, am);
  sendBits(1, am);
}
Imagine that sendBits(bit, amount) sends 'bit' 'amount' times to the port.


Now, this is only one wave. To play it 't' long we need to repeat it x*t times
function wave(x, t){
  am = 57600/x;
  for (i=0; i<x*t;i++){
    sendBits(0, am);
    sendBits(1, am);
  }
}

But, actually we only can send bytes to the serial port.
Now its important to know that 1 byte is actually 10 because of some extra flag bits in the protocol.
Lets change the code for bytes
function wave(x, t){
  am = (57600/x)/10;
  for (i=0; i<x*t;i++){
    sendBytes(\x00, am);
    sendBytes(\xFF, am);
  }
}
I use \x00 as 0 and \xFF as 1.
Now, this should be enough to understand it (I hope)

Okay, first little comment about some code
Instead of
if something then
  --code
end

if not something then
  --code
endIts better to do
if something then
  --code
else
  --code
end


Now, your menu does get triggered when you press '1', but you don't invalidate the screen so it doesn't get drawn. Pressing the category button will trigger this, so only then you see the menu.
To solve this you need to add platform.window:invalidate() to your code (in on.charIn for example). This sets a flag which will make that the screen gets redrawn.

Hope this helps

I think the point is that its very badly documented, making it much harder to do something with it

Sadly enough not. But you could easily do it with C (Ndless).
I think you could get better quality too