Earlier quoted context omitted.
+1 for Emacs keybindings
(+ 1 1)
(partial (+ 1))
A new Light Table experience
131–140 of 152 posts
Re: A new Light Table experience
#132I'd absolutely love to see ruby in Light Table, how are plans looking for this? If there was a kickstarter for adding ruby I'd pony up in a flash. I realise manpower is probably going to be the main issue though...
Manpower is an issue, but we've gotten a lot of requests for Ruby in the future. When and where Ruby support will come is still unknown, but do know that we hear you! :)
I think this would be the right place to bring this up: Is language support backed in or can everyone write a plug-in for his language? Implementing highlighting, completion and repl for all the different languages users could want seems like an enormous task. At the same time this is where Emacs shines: supporting a new language rudimentary is easy to do, adding more advanced support isn't too hard either. Will users be able to define new language modes?
Re: A new Light Table experience
#133It is absolutely gorgeous, but it is also looking a lot more like a traditional text editor from what i can gather. I'll download and play with it a bit anyway, to see what i get from it.
It is, but that's because we have to have a solid editing experience for the "simple" stuff before we can do the more interesting things. What good is it to have these awesome function oriented editors when you can't even modify a file efficiently? :) We use tabs as a simple way of wrapping up a context. In the future they will include all sorts of neat things - and they aren't limited in any way. If we want, we can…
+1 for strong editing features. All the fancy stuff came after Emacs became an OS for editing text. Nail that, the rest follows.
Re: A new Light Table experience
#134I know python support is planned, but will it be integrated alpha/beta or will we have to wait until after the 1.0 release?
It'll definitely be before 1.0, but I'm not exactly sure when. Right now it's still just me on the code side, so it depends a bit on how hiring goes.
How many people are working on this project ?
Re: A new Light Table experience
#135Does anyone know what Light Table is programmed in? It seems to be cross platform, how does it achieve that? I assume some kind of mix between Clojure and using browser technology as a UI, but does anyone know specifics?
In addition to node-webkit, I believe the app code itself is written in ClojureScript (a compile-to-js dialect of Clojure.)
Yep, mostly ClojureScript and a bit of Javascript for boot and setup.
Re: A new Light Table experience
#136Re: A new Light Table experience
#137I can't wait for this to support Java so I can at least have some beautiful tools to get me through the soul sucking days of Spring development :-)
Re: A new Light Table experience
#138Looks really nice. I want to use it. I also like vim.
BUT could do with some more documentation.
Re: A new Light Table experience
#139You gotta be kidding on the sideways text as an important part of the UI. Also adding the vim integration is a waste of time as long as you don't have buffers, registers, ranges and can't parse my .vimrc nor use my modules you might as well not do it.
> You gotta be kidding on the sideways text as an important part of the UI.
I don't think he ever actually says it is. Also, "... if your preference is for something else, you have complete freedom when writing your own skin."
Re: A new Light Table experience
#140What going back over the old demo and looking at this post did was remind me of how nice jsfiddle is when it isn't insanely slow, which then led me to wonder how hard it would be to create something like jsfiddle that lived on top of github would be, or something like jsfiddle that lived inside my favorite editor, or just in a static html page on my desktop.
I used to be a huge proponent of JSFiddle but it's got so slow and temperamental recently that I've started moving over to codepen.io. It gives instant results (every change is evaluated in real time), supports LESS and SASS on the CSS side, and CoffeeScript on the scripting side. And it's got a nicer UI, giving more space to the output pane and allowing quick switching/expanding of the code panes