11–18 of 18 posts
Your landing page designs are sleek! Nitpicking about the package: is a not a valid HTML tag. You can use or
This component then inherit a shadow DOM where all the magic happen.
See https://developer.mozilla.org/en-US/docs/Web/Web_Components/...
Nice name. Inspired by Luna Park Sydney?
Basically, it's a very common name for amusement parks, and it has this 70s-80s vibe I love. It's also used as a term for "amusement park" in several languages (Italian, Greek, Polish, German...).
See: https://en.wikipedia.org/wiki/Luna_Park
I wanted the branding to feel "fun", not boring. The visual scripting editor also feels like a game, and I went full gamification for the tutorial: https://luna-park.app/challenge
Btw, kinda difficult to see, but the logo is a shadow of a rollercoaster on a ramp with the moon behind.
The source code itself doesn't seem to be available (eg for security scanning).
Is that correct?
If that's indeed the case, then with NodeJS/npm's ongoing problems with malicious packages... this seems like a problem. :(
Hang on, this doesn't appear to be Open Source. The source code itself doesn't seem to be available (eg for security scanning). Is that correct? If that's indeed the case, then with NodeJS/npm's ongoing problems with malicious packages... this seems like a problem. :(
But since it's an NPM package, the transpiled and minified code is of course available for automated security scanning (it's not uglified or obfuscated).
I don't think having the project open source will change a lot about security. It's a fairly complex project, and someone manually reviewing of all the code is unlikely.
Also, malicious packages is especially a problem for very common dependencies. And Luna Park is not gonna be a hidden dependency of a lot of packages.
On a side node, maybe the editor code will go Open Source someday, but since there's no way back to that decision, I'm taking time to reflect on this.
Just quickly scanned the page. As for VPLs in node, how does this compare to node.red?
So I'd say that Node-red is more of a workflow editor, not a visual scripting editor. You can create almost anything you would in code with Luna Park nodes. This is not the case with Node-red which is a bit higher level, and you do need to code the complex things you want to run.
Other than that, there are a lot of convenient features in Luna Park like:
- can be integrated withing any webapp (feels like Node-red needs a dedicated server to run)
- generate standalone JS code from the logic graph (to be run headless, with native performance)
- merge nodes into function that can be used as custom nodes
- type and value inspection at runtime
- a lot more nodes (generated from standard JS functions)
- and a few others features (integrated documentation, node customization, inspector, console, etc...)
Basically, Luna Park and Node-red might seem similar when looking at their UI, but they have a pretty different purpose. Node-red would be useful to automate workflows between systems. Luna Park would be useful to build those systems.
This is very cool. However, most our use cases would be in PHP apps. I see that you’re working on a code generation API. Would that be the step necessary for generating the PHP invokable code?
Thank you very much! For now, the generated code is in JS, so you'll need Node.js to execute it. Though, it could have other target languages. I keep in mind the PHP usecase, I'll see if/when I can implement this. In the meantime, you can create custom nodes that call PHP routes of your app. Not the most performant way of doing it, but it should work.
I'm thinking of various sites that need a "script" condition for domain logic. Like, "this coupon applies when your cart contains 5 items worth at least $5 each". If the client tried to write the logic for that they'd have no clue how. But a graph editor would be make that user-friendly.
There's just not a lot of FBP stuff for PHP, even though it's a popular language.