-
Notifications
You must be signed in to change notification settings - Fork 28
Description
just another wishlist idea fwiw: doing the tutorial the hardest things for me go back to java itself, expanding the javafbp jar so the core classes were found, generating the code in the proper directories matching the package names and getting my classpath right and compiling the code from the proper directory and then when running again making sure my classpath and directory was right so the class for the subnet was found correctly...
these are some of the reasons I was drawn to groovy (and rhino) some years back before embracing node.js and javascript - these "scripting" type languages just have fewer of those headaches - they're just more fun!!
So this idea is really these related ideas (whoops just realized I've blurred the lines here between drawfbp and javafbp but I guess that's part of the idea):
a. Could the code generation steps be eliminated or at least hidden? (note that e.g. groovy feels to the developer like an interpreter but it's actually generating and compiling class files without the developer even knowing)
b. for creating custom processes could support be added for at least one of the JVM based scripting languages (groovy, rhino javascript, jython/python, beanshell), ideally with a little editor integrated into drawfbp so people could enter/edit and run right there without any explicit code generation/compilation steps needed.
c. Maybe ideally this would use the multi-language support provided by GraalVM so that javafbp would become "polyglotfbp"!!