Dennis Kobert
Dennis Kobert
> It might be worth moving the type exporting code into the startup of the application if possible when doing a debug build so that you don't need to run...
> * Splitting all of your types into a different crate than the one with the `build.rs` so it can import the types as a build dependency. Yeah, was thinking...
We just need to reexport the specta types static global from the editor so we can consume in then the wasm crate but that is easy to do
I'd be interested to take a look at this to get familiar with the code structure. I assume we would use the inotify api? Afaik it provides both a blocking...
This is unrelated to #2802
Could we make pulling in time optional? We are currently thinking about adding Rhai support to graphite: https://github.com/GraphiteEditor/Graphite/pull/2460 but in our case we don't need time support at all so...
Should be fine to do now, will probably become obsolete when we add automatic type conversions
Alternatives considered: Using Caching to hide the bad performance during rendering
 After fixing the mutex errors, this seems to be related to the image serialization.
This might actually be a memory issue as the in memory representation takes 384mb which is quite substantial