Oliver Buchtala
Oliver Buchtala
A totally different approach: allow for 'shifting' nodes via keyboard shortcut and drag.
Somehow `Rollup` is able to deal with the code. At the beginning we had to resolve real cycles such as `Selection.js` having a factory method depending on `PropertySelection.js` which apparently...
Ok, it's slow, because it really needs to analyse the whole library, and can not drop things on the fly.
Maybe it is an option for you to load `substance.js` via an extra `` and tell webpack to treat it as external located at `window.substance`? Edit: this is what we...
@michael @Integral what is ur opinion?
Ah, you are right. Am 19.06.2017 11:00 vorm. schrieb "Daniel Beilinson" < [email protected]>: > @oliver---- maybe i missed something, but > how to bind this observer to event handler (to...
@michael @Integral updated the proposal according to Daniels question. Alternatively we could do something like this: ``` appState.observe(this._onDocumentChange, this, { resource: 'document', stage: 'render', options: { path: [...] } })...
Not critical. Will be done in beta 5.
Hey @rquast, Thanks for collecting this information. The tenor in the thread seems to be either using physical keyboards or not relying on keyboard events at all when it comes...
Currently this implemented in a very naive way, creating a clone of the graph, and eventually applying the ops at once on the original graph. This should be optimized.