4 ms·

I look forward to writing (essentially vim-) plugins for light table in javascript. Some day soon? Extensions were mentioned on the blog about a year ago (http

by jiaaro 13y ago

I look forward to writing (essentially vim-) plugins for light table in javascript. Some day soon? Extensions were mentioned on the blog about a year ago (http://www.chris-granger.com/2012/04/15/light-tables-numbers/ http://www.chris-granger.com/2012/04/15/light-tables-numbers...), but as far as I can tell, they're still not here yet :(

ibdknox 13y ago
The plugin architecture is something we have to be deliberate about given that it allows you to do literally anything we can do. I talk a little bit about the plan moving forward at the bottom of the post, but gist is that there's going to be one more public release, and then the private beta (for KS folks) is going to focus on really hammering out how we expose LT to plugins.
- Meai 13y ago
  Is there a way to preorder in order to get into the private beta as well? I wasn't with the Kickstarter crowd. If plugins are as powerful as you say they are, I'm very interested.
  - smweber 13y ago
    Yeah, I found myself visiting the Kickstarter page today hoping there was some way I could fund the project months after it completed. Needless to say I couldn't. Seems like it would be a useful feature for projects like this - I doubt they couldn't find a use for more money.
  - Cogito 13y ago
    The Double Fine Adventure guys are doing that, for an example of how it could work. They call the second round supporters 'slacker backers' [0]. I would also pre-order now if I could. [0] http://www.doublefine.com/dfapay/ http://www.doublefine.com/dfapay/
- mheathr 13y ago
  Can you comment in generalities on the scope of changes to LT's behaviour end users can expect to be possible by design, e.g. the entire stack is modifiable to the extent that Emacs (even the underlying elisp interpreter) is modifiable, only via a limited API like Sublime Text 2 has (which results in end users being reliant on major changes coming from the top down), or something else entirely?

by jiaaro 13y ago

ibdknox 13y ago

The plugin architecture is something we have to be deliberate about given that it allows you to do literally anything we can do. I talk a little bit about the plan moving forward at the bottom of the post, but gist is that there's going to be one more public release, and then the private beta (for KS folks) is going to focus on really hammering out how we expose LT to plugins.

Meai 13y ago
Is there a way to preorder in order to get into the private beta as well? I wasn't with the Kickstarter crowd. If plugins are as powerful as you say they are, I'm very interested.
- smweber 13y ago
  Yeah, I found myself visiting the Kickstarter page today hoping there was some way I could fund the project months after it completed. Needless to say I couldn't. Seems like it would be a useful feature for projects like this - I doubt they couldn't find a use for more money.
- Cogito 13y ago
  The Double Fine Adventure guys are doing that, for an example of how it could work. They call the second round supporters 'slacker backers' [0]. I would also pre-order now if I could. [0] http://www.doublefine.com/dfapay/ http://www.doublefine.com/dfapay/
mheathr 13y ago
Can you comment in generalities on the scope of changes to LT's behaviour end users can expect to be possible by design, e.g. the entire stack is modifiable to the extent that Emacs (even the underlying elisp interpreter) is modifiable, only via a limited API like Sublime Text 2 has (which results in end users being reliant on major changes coming from the top down), or something else entirely?