You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to be able to run an application across several windows. At this point, the don't make me think magic style injections become a limitation.
I realise addressing this kind of outside context problem raises all sorts of other concerns - why not chuck in SSR and GTK native decorators while we're at it? - but for my part I'd be happy with what I think is a pretty modest proposal - a b.toString() method that returns the whole sheet as a string.
I think this would do a good job of preempting meta concerns down the road (multiple instances, stateless mode, etc) without complicating the API too much.
The text was updated successfully, but these errors were encountered:
There's currently an undocumented method called getSheet which is used for the tests. It'll clear any rules when being called, since that's relevant during testing, but I'm not sure it's desirable for something like this.
I'd like to make this thing into a documented option (but with the clearing part pulled out into it's own method), and I suppose that would be exactly what you need. (also what might be needed for SSR).
I'd like to be able to run an application across several windows. At this point, the don't make me think magic style injections become a limitation.
I realise addressing this kind of outside context problem raises all sorts of other concerns - why not chuck in SSR and GTK native decorators while we're at it? - but for my part I'd be happy with what I think is a pretty modest proposal - a
b.toString()
method that returns the whole sheet as a string.I think this would do a good job of preempting meta concerns down the road (multiple instances, stateless mode, etc) without complicating the API too much.
The text was updated successfully, but these errors were encountered: