Scratch

Magnie · 2012-02-29 14:44:01

roijac wrote:
http://nullpointer.ph/questions/3021/in-oop-what-is-so-important-about-information-hiding
^^
>>sourceforge forums

I can't access the forums for some reason. Can we just keep the discussion in here?

roijac · 2012-03-01 05:57:30

weird, can you still not access it?
and what command do i need to update the repo? hmm
edit: nevermind, i got it smile

Last edited by roijac (2012-03-01 05:58:55)

Magnie · 2012-03-01 09:41:08

roijac wrote:
weird, can you still not access it?
and what command do i need to update the repo?
edit: nevermind, i got it

Hmm, now I can. Over time, I'll end up forgetting about those forums. Scratch is the only site I've stayed on permanently. So if we just keep the discussion here, I'm less likely to abandon the project.

We'll go with importing. So how should we set up the program?

roijac · 2012-03-01 10:30:54

come on, it's funnier without planning smile
just add some code if you feel like big_smile

but maybe we should start with the language. like basic commands and that.

undefeatedgames · 2012-03-01 12:04:35

cool

roijac · 2012-03-01 12:37:41

thanks! smile

Magnie · 2012-03-01 12:59:27

Haha. Yeah, if we don't plan, it'll never even get done. tongue

I'm thinking of having the same syntax as the Scratch Forum Blocks. What are your thoughts?

roijac · 2012-03-01 13:16:10

that could sortof work, but i really don't like the endless ([<>]) hmm maybe just ' ' ftw? big_smile

Magnie · 2012-03-01 13:35:31

Yeah, we can change the ([<>]) to something else that's more reasonable.

roijac · 2012-03-02 03:13:36

but it's still unreadable, especially with nested blocks :S
maybe we should make it more like python functions...

Magnie · 2012-03-02 09:58:48

roijac wrote:
but it's still unreadable, especially with nested blocks :S
maybe we should make it more like python functions...

I write my Scratch Blocks like this:

Code:

when gf clicked
set [var v] to (1234567890)
forever
    if <touching [sprite v]?>
        say [How are you?] for (3) secs
    end

When ever I try to simplify it though, it gets confusing how [text] and (numbers) will end up working. So I think how it is right now is pretty good.

roijac · 2012-03-02 10:11:21

ok, i'm good with it smile
maybe hat blocks should be like this?:

Code:

greenflag:
some code
end script

clicked:
some code
end script

should i write a parser? big_smile

Magnie · 2012-03-02 10:15:12

roijac wrote:
ok, i'm good with it
maybe hat blocks should be like this?:
Code:
greenflag:
some code
end script

clicked:
some code
end script
should i write a parser?

Maybe ":end" should be used for the end of a script instead of "end script". And yes, a parser would be nice. smile

roijac · 2012-03-02 11:07:06

okay, i'll try to finish it till next week smile
you're going to work on UI?

Magnie · 2012-03-02 14:39:44

roijac wrote:
okay, i'll try to finish it till next week
you're going to work on UI?

Not sure. I have no idea how to use wx or tkinter. hmm

If you get a base up with a couple basic blocks, then I might be able to code everything else. If you have anything specific that isn't related to the GUI, I can probably work on it.

roijac · 2012-03-03 15:06:11

ok, what do you say about making the sprite and project dtd?

Magnie · 2012-03-03 22:13:38

Hmm, okay. I'll do DTD first.

Code:

<!DOCTYPE meow_project [
    <!ELEMENT meow_project (meow_settings, project_settings, project_sprites)>
        <!ELEMENT meow_settings (version)>
            <!ELEMENT version (#PCDATA)>

        <!ELEMENT project_settings (author, name)>
            <!ELEMENT author (#PCDATA)>
            <!ELEMENT name (#PCDATA)>

        <!ELEMENT project_sprites (#PCDATA)>
            <!ELEMENT sprite (name, costumes, sounds, scripts)>
                <!ELEMENT name (#PCDATA)>

                <!ELEMENT costumes (costume)>
                    <!ATTLIST costume id CDATA #REQUIRED>

                <!ELEMENT sounds (sound)>
                    <!ATTLIST sound id CDATA #REQUIRED>

                <!ELEMENT scripts (script)>
                    <!ATTLIST script id CDATA #REQUIRED>
]>

What do you think?

roijac · 2012-03-04 05:12:18

project notes missing, but everything else is good smile
parser will have to wait a bit, too many tests sad

bendad · 2012-03-04 12:54:58

Hi guys!
Great work so far, sorry for not being around.

I'm not exactly a coding master, but I know a few things. I'd love to help out with syntax ideas, art for the GUI, and website management.

Sorry for not getting the site up, I've been really busy lately and I keep on meaning to but life gets in the way.

I can't check out the sourceforge site because it's blocked on my school laptop (Which I'm on right now tongue ). I'll see it when I get home.

So what have we decided on the site, sharing files, and other things?

roijac · 2012-03-04 13:50:00

hi, nice to c u smile
are u good with wx?

bendad · 2012-03-04 15:49:54

no. I know the basics of python but I could learn wx.

Magnie · 2012-03-05 09:19:41

Code:

<!DOCTYPE meow_project [
    <!ELEMENT meow_project (meow_settings, project_settings, project_sprites)>
        <!ELEMENT meow_settings (version)>
            <!ELEMENT version (#PCDATA)>

        <!ELEMENT project_settings (author, name)>
            <!ELEMENT author (#PCDATA)>
            <!ELEMENT name (#PCDATA)>
            <!ELEMENT notes (#PCDATA)>

        <!ELEMENT project_sprites (#PCDATA)>
            <!ELEMENT sprite (name, costumes, sounds, scripts)>
                <!ELEMENT name (#PCDATA)>

                <!ELEMENT costumes (costume)>
                    <!ATTLIST costume id CDATA #REQUIRED>
                    <!ATTLIST costume name CDATA #REQUIRED>

                <!ELEMENT sounds (sound)>
                    <!ATTLIST sound id CDATA #REQUIRED>
                    <!ATTLIST sound name CDATA #REQUIRED>

                <!ELEMENT scripts (script)>
                    <!ATTLIST script id CDATA #REQUIRED>
]>

I'm still trying to figure out how we should implement images and sounds all into a single file.

roijac · 2012-03-05 10:46:04

http://stackoverflow.com/questions/3715493/encoding-an-image-file-with-base64^^

roijac · 2012-03-11 07:53:01

parser development is active smile

Code:

#Only proof of concept
import re
class ParseError(Exception):
    def __init__(self, message):
        self.message = message
    def __str__(self):
        return repr(self.message)
specs = [ r'move %n steps',
        r'turn %n degrees',
        r'point in direction %n',
        r'go to %n:%n',
        r'set x to %n',
        r'set y to %n',
        r'change y by %n',
        r'change x by %n',
        r'stop script']
for i in range(len(specs)):
    specs[i] = specs[i].replace('%n', r'([0-9.]*)')
    #Another symbols come here :)

def getinputs(block):
    for spec in specs:
        if re.match(spec, block):
            print 'Found block spec!\n' + block + ' is ' + spec
            print 'Inputs are ' + str(re.match(spec, block).groups())
            break
    else:
        raise ParseError('Block not recognised!')

if __name__ == '__main__':
    block = 'turn 12.43 degrees'
    getinputs(block)

roijac · 2012-03-11 14:12:50

do you think we should allow different spellings/writing of blocks?
for example goto instead of go to, etc.?

Scratch

archived forums

#76 2012-02-29 14:44:01

Re: The Return Of M30W

roijac wrote:

#77 2012-03-01 05:57:30

Re: The Return Of M30W

#78 2012-03-01 09:41:08

Re: The Return Of M30W

roijac wrote:

#79 2012-03-01 10:30:54

Re: The Return Of M30W

#80 2012-03-01 12:04:35

Re: The Return Of M30W

#81 2012-03-01 12:37:41

Re: The Return Of M30W

#82 2012-03-01 12:59:27

Re: The Return Of M30W

#83 2012-03-01 13:16:10

Re: The Return Of M30W

#84 2012-03-01 13:35:31

Re: The Return Of M30W

#85 2012-03-02 03:13:36

Re: The Return Of M30W

#86 2012-03-02 09:58:48

Re: The Return Of M30W

roijac wrote:

Code:

#87 2012-03-02 10:11:21

Re: The Return Of M30W

Code:

#88 2012-03-02 10:15:12

Re: The Return Of M30W

roijac wrote:

Code:

#89 2012-03-02 11:07:06

Re: The Return Of M30W

#90 2012-03-02 14:39:44

Re: The Return Of M30W

roijac wrote:

#91 2012-03-03 15:06:11

Re: The Return Of M30W

#92 2012-03-03 22:13:38

Re: The Return Of M30W

Code:

#93 2012-03-04 05:12:18

Re: The Return Of M30W

#94 2012-03-04 12:54:58

Re: The Return Of M30W

#95 2012-03-04 13:50:00

Re: The Return Of M30W

#96 2012-03-04 15:49:54

Re: The Return Of M30W

#97 2012-03-05 09:19:41

Re: The Return Of M30W

Code:

#98 2012-03-05 10:46:04

Re: The Return Of M30W

#99 2012-03-11 07:53:01

Re: The Return Of M30W

Code:

#100 2012-03-11 14:12:50

Re: The Return Of M30W

Board footer