search

raspigam / vector-scratch-blocks

Extending the work found at http://scratched.gse.harvard.edu/resources/vector-scratch-blocks
1 stars 0 forks source link

SVG to contain plain text, in order to make translations #1

Open tpfuhl opened 7 years ago

tpfuhl commented 7 years ago

Hello, this is a very useful project, many thanks ! I want to use it in my neighborhood with interested children, but would prefer a localized version. The SVG files do not contain plain text (e.g. "if then else") only paths. Is there a possibility to make SVG files that use plain text for the commands ? Best, Thomas

robvandenbogaard commented 7 years ago

Hello Thomas, great to hear you're interested. I will have a look at it, it should not be too hard to convert it to text nodes. I'd say we should make the path-version a branch and the text-node version the master. The path-version is nice if you don't like to have "font-hassle" ;) Would you be able to collaborate with me on this, editing part of the svgs and committing them? I'm not sure yet how much time I can allocate and how long it will take to convert all of them.

tpfuhl commented 7 years ago

Hello robvandenbogaad, Thanks for your quick feedback. Yes, I would like to collaborate. Meanwhile I found the site scratchblocks.github.io which provides svg export with text nodes. This might do the job.

robvandenbogaard commented 7 years ago

Hi Thomas, sorry for the late response; did scratchblocks.github.io work out for you?

tpfuhl commented 7 years ago

Hello Rob, thank you for asking. Yes, it worked but it must be done by hand, I think. Did not figure out how to script it. The other thing is that , of course, we do not have dynamoc length for em bedding fileds, e.g. conditions. Best would probably be to provide a set of placeholders with different lengths.

2017-09-25 11:06 GMT+02:00 Rob van den Bogaard notifications@github.com:

Hi Thomas, sorry for the late response; did scratchblocks.github.io work out for you?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/raspigam/vector-scratch-blocks/issues/1#issuecomment-331821519, or mute the thread https://github.com/notifications/unsubscribe-auth/AJztzCPtnMe_N9KgydrfiwEgXnfxK0Slks5sl20ugaJpZM4O9XB_ .

robvandenbogaard commented 7 years ago

Indeed I was also wondering about that; how to deal with field sizes and code in e.g. loops. Another solution could be to provide separate top and bottom parts for enclosing instructions. You could also split up the instruction which have fields. The downside is that that quickly gets into a pile of fragments you loose overview of..

So maybe if you stick hook&loop (velcro) tape on the back of the parts anyway you could provide pieces of hook&loop cloth (loop front, hook back - to stick to the background medium) keeping the parts together and if you'd like to make the fields bigger you can take the separate parts and place them more apart on a bigger piece of cloth or directly on the background medium. I'm not sure it is a really practical approach.

For the time being we will probably only do very simple assingments with the printed scratch blocks (without needing wide fields), but yeah it remains an issue. Requiring any complex opration to be put into a variable so it always fits (as a reference to the variable) in the fields might get annoying ;)