UNPKG - Some components missing

[heliacer]

I've tried out implementing the lexical variables using the unpkg sourcecode
It did surprisingly work, but only partially. I have a testing demo here
Only the procedures category and the loops category pick up the components of lexical variables.
the rest, including the main variables category just stays on its default.

Does anyone know why? Could it be because i'm using the new JSON layout?
Thanks for letting me know!

Regards, heliacer

[mark-friedman]

@heliacer Please note the following from the "Usage" section of the README file:

Note that unlike with standard Blockly, you should not use a custom toolbox category for your variables, as this would interfere with the way that variables are declared and used with this plugin. Just create an ordinary Variables category, if you want, and place the lexical-variable-get and lexical-variable-set blocks in there.

[mark-friedman]

Hey there, Thanks for writing back. I did read all prerequisites and am aware of that. If im correct the variables category is named as its default, so it shouldn't really interfere.

What my quoted text was trying to say is that it does interfere. You shouldn't use the standard custom variables category.

Do i have to place the blocks manually? If thats the case then it would make sense on why the variables didn't appear.

Yes. Please take a look at toolbox definition in the demo repo for some more guidance.

[mark-friedman]

Turns out its possible to add them manually to the toolbox category of "Variables". I managed to find those blocks ( excluding the mutators ) but i didn't manage to find the public variable initialising block on the unpkg source code.

        {
          kind: 'block',
          type: 'lexical_variable_get'
        },
        {
          kind: 'block',
          type: 'lexical_variable_set'
        },
        {
          kind: 'block',
          type: 'local_declaration_statement'
        },
        {
          kind: 'block',
          type: 'local_declaration_expression'
        }

All the blocks and their types should be specified in the README file for the plug-in. For example, here's the global variable definition block.

[heliacer]

Thanks a lot for the help!
I was a bit confused at first,
but i think i get it now.

Have a nice day,
Regards
Heliacer

[mark-friedman]

👍

…

On Mon, Mar 18, 2024, 9:29 AM heliacer ***@***.***> wrote: Thanks a lot for the help! I was a bit confused at first, but i think i get it now. Have a nice day, Regards Heliacer — Reply to this email directly, view it on GitHub <#49 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANJWSQ2DKGDALCDLH53OLTYYX4IZAVCNFSM6AAAAABEZT2MPWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DQMRQHEZTK> . You are receiving this because you commented.Message ID: ***@***.***>