Light Table 0.4 released
111–120 of 193 posts
Re: Light Table 0.4 released
#112I'm not near any machines of mine that aren't Chromebooks. Does anyone know if the libudev.so.0 stuff is fixed? I don't see any mention of it in the change log, but I was really hoping they would have a fix for those of us not on Ubuntu so we don't have to symlink the new libudev.so.1 to so.0 just to use light table (yes other hacks exist, this was the most prevalent one...)
unforunately no. It's an issue carried over from node-webkit[1] and I'm not really a Linux guy :/ Someone could work on a fix for node-webkit, though and I'd pick it up in a heartbeat [1]: https://github.com/rogerwang/node-webkit
Re: Light Table 0.4 released
#113I 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... ), but as far as I can tell, they're still not here yet :(
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.
Re: Light Table 0.4 released
#114Re: Light Table 0.4 released
#115I hoped ST3 would replace Emacs, but Light Table seems more like it now...
Re: Light Table 0.4 released
#116Earlier quoted context omitted.
1. make a new lein project 2. fill in the dependencies in project.clj 3. open your src/core.clj (or whatever) in LT 4. start coding LT will automatically launch a client and connect to it. In between lein will have seamlessly fetched the dependencies for you (this happens automatically each time you launch or relaunch a client). You can do manual (C-Enter) or live (Instarepl) inline evaluation in any of your project…
Would you then recommend focusing development around some unit tests and eval-ing them as you do work? (that's what I am trying so far, seems ok)
It is also pretty nice to have an Instarepl where you can see live changes, either in your source files or in a separate repl. Don't forget that if your paths and namespaces match you can require your namespaces at will.
Re: Light Table 0.4 released
#117It looks pretty nifty! It's kind of like what Subtext and Bicicleta wanted to do, but never did (or haven't done yet). You get live update of the code and, apparently, live inspection of all the values in the code. The missing piece would be inspecting values inside a function call. But it sounds like it's proprietary software? Why do you need that if you're getting funded through Kickstarter? Either way, it looks li…
What happened with Bicicleta? I love the premises I saw listed in response to Perlis. LT will be open source, just want it to get a bit more stable first.
Re: Light Table 0.4 released
#118I am really amazed with how well codemirror emulates basic vim key bindings [3], as I prefer to use ctrl-c rather than escape and I often find that vim emulators either do not support ctrl-c or do not support it well.
[1]http://www.chris-granger.com/2012/04/15/light-tables-numbers... [2]http://codemirror.net/ [3]http://codemirror.net/demo/vim.html
Re: Light Table 0.4 released
#119Earlier quoted context omitted.
Would you then recommend focusing development around some unit tests and eval-ing them as you do work? (that's what I am trying so far, seems ok)
Precisely. This is at least how I do it. It is also pretty nice to have an Instarepl where you can see live changes, either in your source files or in a separate repl. Don't forget that if your paths and namespaces match you can require your namespaces at will.
Re: Light Table 0.4 released
#120alert('foo');
Produces 'SyntaxError: Unexpected identifier'. I'm looking forward to the kinks being ironed out.