Here is a live example of generator

[julientype]

You cannot teach HTML like this until 2 features are fix...

http://blocklyhtml.zgtm.de/

try it out and look at the render code window or HTML window.....
now move a block out and in..... the code still shows and it effects what the kid will see....
next is to pull out a child block from its parent......
if i pull the top child out the others pop out also....<-no good
it should pull out like the last child block dose....

you need a root render connected nodes......

HTML render for the child would remove a button and its gone. out of the view pop it back in and it shows up again thats how the child will learn how to code

[julientype]

let do a drag drop connect operation with a do loop .......
open live sample....
http://blocklyhtml.zgtm.de/
you will see a block call content ......
now go connect your do-loop from your script category and it pops in<---not good
this why you have xml tool file...... to govern to the output rights.....
can html category block accept a do loop under scripting category<----no
under tool box governing rule it would not plug in unless you have script block-tag
i dont do drag and drops Blockly does base on my programmable xml layout
before drop check what????? the target block category.... it dont fit....

like i said this is a grate sample to explain blockly generator code and its effect on rendered output
try moving the style tag around and see how the HTML window renders for kids to learn from......

[julientype]

to understand a a blockly type program you need to understand your objection...
html is ASCII to graphics your not html your graphics to ASCII
ias a user program for you i care about 2 things from you..... graphics to xml to ASCII
ok 3.... yet i need to see default values feed it data so we get 4 .... like drop down or check box within block it self......
its just a little error with my logic 3 ... 4 yet i ask for 2 to move data around to be corrected to produce what ASCII from a formatted xml file ....

Block.insert this block
value
value
ohh events to its block change....
feed it data... for what
to get the XML data ASCII text out.... your running a reverse dom xml phrasing engine
try to remake XML phrasing language it already been done successfully in 1998
you tone of people who can program the logic its not new its a standered ...
like getparent or nextchild i have sin-tax books from 1998 for xml phrasing
dont make up crazy new code logic where new programmers cant under stand what you did to object model .. they end up creating more errors
the foot print command is small to run a xml phrasing engine its been thought of hash out and it the best command foot print you can use to do any task you desire yet change foot prints and you get lost reverting redundant commands that cause errors and you get know one later to to understand how to fix it be cause you desided to make your own up....

[julientype]

category tool bar.....with a root node with 4 open slots how many tool bar blocks can be activated and filtered into position base on my ability to set up xml tool bar attributes
if you fave no open slots left what blocks can you feed the user.. none....
pull a block out what blocks do you grant.... i dont do this code nor should i other then setting up category index array that Blockly check in the xml tool structure ...
a circuit broad hand full of logic block to build a board you fave that logic....right now if you integrate with a category structure with on and off base on the task at hand then building blooks become easy .. all gov by the tool bar xml array its why xml is application development code and jason is boot file code it was develop later to create a small foot print for ascii text so its limited on char input where xml is not... all done and thought of back in 1998 ....

[RoboErikG]

@julientype I'm sorry, but I don't think any of us can help. If you find clear bugs in our implementation that you can provide simple steps to reproduce please let us know by filling out the bug template, but please stop filing long form issues like this, we will not look into them.