It would be nice if the same code that begins with `using Interact` can run in multiple environments. But this arrangement is cool too. Right now, all IJulia specific stuff is in Interact/src/IJulia. It was initially a separate package, then we put it inside Interact for convenience. The main thing the IJulia specific part does is override writemime(::IO, ::MIME, ::Signal) and writemime(::IO, ::MIME, ::Widget) to set up communication and invoke IPython widgets.
This highly dated document https://github.com/JuliaLang/Interact.jl/blob/master/DESIGN.md describes some of the initial ideas about separating environment specifics from widget models. On Sun, Sep 7, 2014 at 12:15 PM, Shashi Gowda <shashigowd...@gmail.com> wrote: > This is very cool! > > I really love how there is no lag in the example and things seem so > responsive. Added a link in the Interact.jl README. > > One of Interact's goals is to make such adaptions hassle-free. Please do > file issues if you think some change to Interact can make your code neater. > > > On Sun, Sep 7, 2014 at 11:41 AM, Iain Dunning <iaindunn...@gmail.com> > wrote: > >> Don't think I need this personally, but just wanted to say - looks cool! >> >> On Saturday, September 6, 2014 4:35:33 PM UTC-4, j verzani wrote: >>> >>> The new Interact.jl package allows you to use interactive widgets such >>> as sliders, dropdowns and checkboxes to play with your Julia code within an >>> IJulia session. It is pretty neat, in particular the `@manipulate` macro. >>> For those times where IJulia is not convenient, but the console is, I've >>> made a small wrapper package GtkInteract.jl that creates these widgets in >>> Gtk with the expectation that Winston will be used for graphics. If you are >>> interested in such a thing, you can try it out by cloning the package: >>> Pkg.clone("https://github.com/jverzani/GtkInteract.jl.git";). >>> >>> >
