Components
Playground & Inspector
The Inspector lets you define custom presentations for each and every object. And then it enables you to navigate through them. Inexpensively.
The Playground powers up the inspector and makes the code part of the live inspection flow.
The Playground and Inspector can be molded in many ways. For example, for browsing the file system.
And they can be molded to become a browser for a code query.
Playground supports multiple snippets that can be evaluated independently.
Debugger
Debugger is a debugger. Go figure. Only, in true moldable fashion, it also lets you build custom debuggers that can be switched to during debugging time.
A Debugger opened on an exception. Inspecting a variable spawns an Inspector.
A Debugger showing the bytecode of the current execution.
Coder
Coder is for manipulating the static code. It's both standalone and integrated in the Inspector.
Coder opened on the class of an object in the Inspector. Evaluating code spawns the result.
A method viewed through Coder in an Inspector. Looking for implementors highlights the results.
The results of a code query shown highlighted in a Coder interface.
Transcript
Transcript is a stream of events. It's a live visual environment that enables in-place interaction with the logged events.
Transcript used to trace the steps of an animation.
Transcript used for teaching reflection. An exception can be expanded in place to show the stack.
Documenter
Documenter makes creating and consuming code documentation and tutorials a beautiful experience directly in the environment. And it transforms the environment into a data science tool.
Documenter opened on the Tour document. Clicking on a link spawns an Inspector.
Documenter showing a tutorial. The code changes are embedded as objects.
Documenter tranforms the class comment into a live document.
Visualizer
Visualizer makes visualization a first-class citizen in the environment. It contains a few programmable engines including Mondrian, for drawing graphs, and Connector, for identifying connections between various objects.
A Mondrian script showing a visualization of a directory structure.
The visualization is directly clickable: clicking on a node spawns an Inspector.
A Connector interactive visualization showing dependencies between examples.
Examples
Examples is a slim engine that lets you define examples throughout the code and use them for documentation or testing. Through Examples, a developer can switch rapidly from the static code to a live environment and program in the presence of objects. In essence, it enables example-driven development.
Examples can be fine grained and nested arbitrarily. The returned object offers immediate feedback.
Examples can be visualized with Connector, too.
Examples are executable. Connector allows us to explore how the overall result is obtained.
