It’s quite a nice way to write your code if you’re working on an application in one of the supported languages. Light Table’s REPLs are typically in Live mode - where you’ll get inline evaluation without performing any commands to eval your code. Those familiar with Emacs will appreciate the fact of being able to fire up REPLs on the fly.
You can also include additional connections from the plugin manager or write your own for your favorite runtime. Some of the defaults include an embedded or external browser, a local or remote Clojure REPL, the Light Table UI itself, Node, or Python. The connections allow you to bind to different runtimes and environments to your REPLs or watches, as previously mentioned. I personally had an issue with this working reliably in testing, but it was likely something I was doing wrong.
#CONSOLE.LOG NOT WORKING IN LIGHTTABLE UPDATE#
Choose a connection (what runtime you want to evaluate your watches/code), Set a watch, start making changes or run your application and the watchers will update the values as they run. Light Table has watchers available in JavaScript, ClojureScript, and Python to track values in real time. Despite being largely popular in, and targeted for, the Clojure community, the only component still written in Clojure is the set of bindings to load up a Clojure REPL. As such, it does a really good job of providing an interactive environment for ClojureScript, JavaScript, and Clojure. Light Table is almost entirely written in ClojureScript. It uses the node-webkit library as a foundation for the interface/application, and uses CodeMirror as the editor. While initially rough around the edges and requiring boot from a Java jar file, Light Table is continuously being polished up and has a pretty solid UI. Light Table was initially developed by Chris Granger in 2012 - receiving over $316K in a Kickstarter program. I’ve enjoyed a number of things about this editor and the plugins I’ve picked up, but we’ll get to the pros and cons in a bit - let’s start with basic information about the editor. It’s not my first experience with the editor by a long shot, but this was the longest continuous streak I’ve spent exclusively editing with it (okay, technically I edited git messages in Vim because I forgot to assign EDITOR to the command line light app to launch the GUI). My text editor journey began with Light Table.
Light Table Part 1: An Introduction JContinue to Part 2: A Retrospective Light Table
#CONSOLE.LOG NOT WORKING IN LIGHTTABLE SOFTWARE#
Matt Machuga: Software Engineer / Engineering Manager / Educator
0 kommentar(er)
