3 ms·
Wow thanks for the videos. In the first video, you're right its confusing that the new node jumps to the top left. What's happening is that you create a new nod
by escot 5y ago
Wow thanks for the videos. In the first video, you're right its confusing that the new node jumps to the top left. What's happening is that you create a new node that has no connections, then the layout algorithm re-runs and places your node in the top left since it has no upstream dependencies. I should probably just disallow editing an empty cell that doesn't have any adjacent nodes or something, there isnt really any use case for it.
The |+| button is only activated if you have multiple nodes selected. Clicking it will add a new node thats placed inbetween the other nodes. Like A->B, (then click), will result in A -> new -> B. There's a html title on that button but you have to hover for a second to get the details.
Sorry for the json bug :/. That probably happened when serializing to the url. I'll have to try to reproduce it. Maybe I allowed you to introduce a cyclic connection or something.
For Scaffoldly:
How do you see it as compared to Netlify or Github pages for folks like myself just deploying a static site? At some point I'll build a backend but I don't need it yet.
Is there a way I can give some feedback without altering my aws/github accounts?
Thanks again for the detailed feedback.
- cnuss 5y agoLet me know when you have a new release and I'll try it out some more! Scaffoldly+Knotend: - Compare with Netlify/GH Pages: Big bonus is that you get Nonlive and Live out-of-the-box (e.g. app-dev.knotend.com and app.knotend.com for examples) and CI+CD+Releases in GH Actions to run it all. I have a "Generic CDN" template (not yet documented) that will push a public_html/ directory to S3+CloudFront too, here's an example repo: https://github.com/scaffoldly-demo/demo-web-cdn https://github.com/scaffoldly-demo/demo-web-cdn, in your case, you'd update the GitHub action to compile whatever into the public_html directory - Feedback w/o altering AWS/GH: Everything is contained to A) a new GH organization and B) an AWS sub-organization. If you want to "edit-undo" any changes Scaffoldly did, it should be as simple as (1) delete the github org and (2) terminate the AWS sub-org account. - I presume you're eventually going to need a backend, which is where Scaffoldly will help, wires up APIs + Swagger Docs for you, and takes care of all that CORS stuff too. Let me know what you think!