Stage {
    @green_flag{
        var count = 0;
        forever {
            count++;
            wait(0.5);
        }
    }
}

Sprite Cat {
    @key('right_arrow') {
        if x < 230 {
            x += 10;
        }
    }

    @key('left_arrow') {
        if x > -230 {
            x -= 10;
        }
    }
}

I now need to compy out the opcodes of all blocks into a dictionary and implement global variables.

-EmeraldThunder- wrote:

Ember is a programming langauge that I am currently working on that will allow users to compile their programs directly to .sb3. This means that they may have an easier time moving from the visual environment of scratch to more advanced text based languages.
The first releases will be released sometime form late December to mid January although you are always welcome to clone the files from the GitHub repo and test some of your code on it.

Currenly I've finsihed building up a lexer and am starting on the main compiler. I've got a few ideas for syntax although I would like feedback on what to change.

Stage {
    @green_flag{
        var count = 0;
        forever {
            count++;
            wait(0.5);
        }
    }
}

Sprite Cat {
    @key('right_arrow') {
        if x < 230 {
            x += 10;
        }
    }

    @key('left_arrow') {
        if x > -230 {
            x -= 10;
        }
    }
}

Please don't upload projects created with Ember to the website as it currenty violates the TOS.

What I'm currently working on:

I'm trying to implement variables and blocks. Some variables will be built into the sprite such as the position as shown above.

MagicCrayon9342 wrote:

what coding language is this coding language written in?

god286 wrote:

also isn't there yet another javascript framework called ember?

god286 wrote:

I've changed quite a bit of the source code for it to run on my computer. Does the version in the repository work for you? Which file do I run?
I got this as a result after doing my changes:

[KEYWORD : stage, SCOPE_OPEN : {, EVENT_REGISTER : @, KEYWORD : green_flag, SCOPE_OPEN : {, KEYWORD : var, KEYWORD : count, ASSIGNMENT_OPERATOR : =, NUMBER : 0, LINE_TERMINATOR : ;, KEYWORD : forever, SCOPE_OPEN : {, KEYWORD : count, PLUS_OPERATOR : +, PLUS_OPERATOR : +, LINE_TERMINATOR : ;, KEYWORD : wait, LBRACKET : ( , NUMBER : 0.5, RBRACKET : ), LINE_TERMINATOR : ;, SCOPE_CLOSE : }, SCOPE_CLOSE : }, SCOPE_CLOSE : }, KEYWORD : sprite, KEYWORD : cat, SCOPE_OPEN : {, EVENT_REGISTER : @, KEYWORD : key, LBRACKET : ( , STRING : right_arrow, RBRACKET : ), SCOPE_OPEN : {, KEYWORD : if, KEYWORD : x, LANGLE_BR : {, NUMBER : 230, SCOPE_OPEN : {, KEYWORD : x, PLUS_OPERATOR : +, ASSIGNMENT_OPERATOR : =, NUMBER : 10, LINE_TERMINATOR : ;, SCOPE_CLOSE : }, SCOPE_CLOSE : }, EVENT_REGISTER : @, KEYWORD : key, LBRACKET : ( , STRING : left_arrow, RBRACKET : ), SCOPE_OPEN : {, KEYWORD : if, KEYWORD : x, RANGLE_BR : >, MINUS_OPERATOR : -, NUMBER : 230, SCOPE_OPEN : {, KEYWORD : x, MINUS_OPERATOR : -, ASSIGNMENT_OPERATOR : =, NUMBER : 10, LINE_TERMINATOR : ;, SCOPE_CLOSE : }, SCOPE_CLOSE : }, SCOPE_CLOSE : }]

-EmeraldThunder- wrote:

Does anyone think constants are worth implementing? It would just raise an error at compile if you try to change the value, not in mainstream scratch but may be found useful by someone.

-EmeraldThunder- wrote:

Does anyone think constants are worth implementing? It would just raise an error at compile if you try to change the value, not in mainstream scratch but may be found useful by someone.

-EmeraldThunder- wrote:

I got this error when trying to push. What can I do?

To https://github.com/EmeraldThunder1/Ember.git
 ! [rejected]        main -> main (non-fast-forward)
error: failed to push some refs to 'https://github.com/EmeraldThunder1/Ember.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

-EmeraldThunder- wrote:

Would people prefer if each sprite plus the stage needed its own file or is everybody happy with the concept in the description?

NFlex23 wrote:

-EmeraldThunder- wrote:

Would people prefer if each sprite plus the stage needed its own file or is everybody happy with the concept in the description?

I like it the way it is: all the sprites in one file.

Scratch137 wrote:

NFlex23 wrote:

-EmeraldThunder- wrote:

Would people prefer if each sprite plus the stage needed its own file or is everybody happy with the concept in the description?

I like it the way it is: all the sprites in one file.

I second this; it's more accurate to the way that vanilla Scratch organizes the project.json file. It'd also help to fill the gap between it and a language like Python, where everything can more or less be handled by a single script.