This is very cool indeed.
Cedric Vivier has made a LiveScratchpad that does live JavaScript evaluation in Firefox.
http://neonux.github.com/LiveScratchpad/
It would be cool to add the multiple function source to that!
Light Table - a new IDE concept
31–40 of 315 posts
Re: Light Table - a new IDE concept
#32- Smallest unit of code is the function. - Able to get instant feedback on code changes. - Multiple editors with just one function in it. Show code in an "area of concern" not just in a file. - The coding environment can show also results, app windows, graphics, other tools. - Can save the configuration of the above. Smalltalkers have been doing this in commercial projects since the 80's. If only we could have commun…
Yes, but our code was entirely in these utterly unusable changeset files that couldn't work nicely with the version control that everyone else in the entire world was using; his version still uses files under the hood. There's a team that's trying to back Monticello with Git, I believe by saving each method into its own file in part of a Git source tree; that looks promising as a compromise.
Re: Light Table - a new IDE concept
#33This looks really exciting. I also like the way that it is presented as enormously simplifying a somewhat complex space. Great stuff!
Re: Light Table - a new IDE concept
#34I really hope it's open source, I can't wait to give it a try.
Re: Light Table - a new IDE concept
#35Found a download! https://github.com/ibdknox/live-cljs/downloads
That's actually my live game editor - not the same thing, but also fun! I haven't decided what to do about my prototype quite yet, got too excited about sharing the idea :)
This is so cool, that I think you'd get plenty of funding to further develop this via a Kickstarter project.
Re: Light Table - a new IDE concept
#36This is pretty exciting stuff. IIRC ibdknox used to work on Visual Studio when he was at Microsoft.
I did indeed. I used to be the Program Manager for C# and VB in the IDE. :) A number of the ideas presented here started brewing during my time there, but it took me a bit to figure out what the overall abstraction should be. I really love the drafting table parallel - it's especially interesting when you start thinking about what we can do with touch...
This is great, I would love to try something like it. Making each code artifact living outside of the file paradigm should enable new way to develop, but in the past what I saw trying failed (at least for me). The drafting table look like the abstraction that can make this work. The interactivity would be key too.
I can't help but think of a drafting pad and drafting notebook to allow us to work on our system everywhere...
Re: Light Table - a new IDE concept
#37This is a great idea. I can almost see my development time going down by a big factor and writing much more robust programs.
I wonder, how hard it would be to do this in existing editors ?
Re: Light Table - a new IDE concept
#38Looks really nice! I'm wondering how you provide instant feedback on loops, where each iteration would replace the variables with different values?
Re: Light Table - a new IDE concept
#39- Smallest unit of code is the function. - Able to get instant feedback on code changes. - Multiple editors with just one function in it. Show code in an "area of concern" not just in a file. - The coding environment can show also results, app windows, graphics, other tools. - Can save the configuration of the above. Smalltalkers have been doing this in commercial projects since the 80's. If only we could have commun…
I immediately thought of Visual Age for Smalltalk when I saw this, but having been done is no reason to not try again.
Re: Light Table - a new IDE concept
#40This is great, however it glosses over the elephant in the room: what if a function is called multiple times, or what happens when code within a function is run multiple times? Which data do you display in the data flow view? What is really needed is an intuitive way to select a context or multiple contexts.
SubText's approach to this is to let you dig deeper in the call tree by clicking on function calls, but for a language like Clojure you also need a way to select a context for a piece of code nested within a function. For example suppose you have
(map (fn [x]
...
...)
xs)