4 ms·

Thanks! No support for custom scripts yet. But the whole concept is that we're basically building a WYSIWYG editor on top of a node-based compositor on top of

by Keavon 2y ago

Thanks! No support for custom scripts yet. But the whole concept is that we're basically building a WYSIWYG editor on top of a node-based compositor on top of a visual programming language (so that's three products in one, lots of work ahead for us!). The result is that the whole thing is a programmatic data pipeline and you'll be able to write custom scripts in both node and code form, then compose them into reusable pieces and pipelines. But since we're building three products in one, we have only been able to focus on the parts that matter most to get things working. Your request hasn't yet been one of those, but worry not, that's very much a core feature.

WillAdams 2y ago
Is it possible to draw a Bézier curve, then decompose it in the Node Editor to a set of numeric nodes which input into a Bézier node? I couldn't figure out how to do that (mentioned it elsethread).
- Keavon 2y ago
  You could ask that in our Discord and we can give more advanced guidance, but that isn't something we specifically have nodes for yet. We are building a spreadsheet view for working with all the data in numeric form, and once we have that plus some nodes for interacting with the spreadsheet data, your use case will become more naturally represented.
  - WillAdams 2y ago
    This is a usage model which I would advocate for --- the ability to record series of actions and then edit them made using WordBASIC to automate Microsoft Word far more accessible/discoverable for me.
bschwindHN 2y ago
Do you think you'll use WASM as a target for the custom scripts in code form? Zed has an interesting WASM-based extension APIN that makes it really easy to write extensions in Rust, it might be worth checking out for this project.
- Keavon 2y ago
  Custom code will be compiled to Wasm so it's sandboxed for security purposes. First-party code that ships with Graphite, or perhaps trusted authors in the future, will be able to use non-Wasm native code on desktop. But Wasm is still a very high percentage of native speed.
  - bschwindHN 2y ago
    Makes sense, I think that will end up a solid approach.

by Keavon 2y ago

WillAdams 2y ago

Is it possible to draw a Bézier curve, then decompose it in the Node Editor to a set of numeric nodes which input into a Bézier node? I couldn't figure out how to do that (mentioned it elsethread).

Keavon 2y ago
You could ask that in our Discord and we can give more advanced guidance, but that isn't something we specifically have nodes for yet. We are building a spreadsheet view for working with all the data in numeric form, and once we have that plus some nodes for interacting with the spreadsheet data, your use case will become more naturally represented.
- WillAdams 2y ago
  This is a usage model which I would advocate for --- the ability to record series of actions and then edit them made using WordBASIC to automate Microsoft Word far more accessible/discoverable for me.

bschwindHN 2y ago

Do you think you'll use WASM as a target for the custom scripts in code form? Zed has an interesting WASM-based extension APIN that makes it really easy to write extensions in Rust, it might be worth checking out for this project.

Keavon 2y ago
Custom code will be compiled to Wasm so it's sandboxed for security purposes. First-party code that ships with Graphite, or perhaps trusted authors in the future, will be able to use non-Wasm native code on desktop. But Wasm is still a very high percentage of native speed.
- bschwindHN 2y ago
  Makes sense, I think that will end up a solid approach.