[IPython-dev] Camera widget

[Doug Blank]

On Thu, Feb 27, 2014 at 11:28 AM, Jason Grout
<jason-sage at creativetrax.com>wrote:

> On 2/27/14 9:09 AM, Doug Blank wrote:
> > (I just realized that we could have some magics that handle these
> > cases... run cell in a thread, return the thread id, cancel a thread,
> > etc. You would effectively say: run this cell in the background. I could
> > think of some use cases for that (we program a lot of robots). I guess
> > you could do this in the IPython Python kernel too by just manually
> > creating threads).
> >
>
> That would be interesting to explore doing this using magics.  I don't
> know how the notebook handles multiple simultaneous kernel executions.
> It seems like you could make it work so that the message header on
> return messages was local to the thread, so different thread's messages
> would be routed to different handlers in the notebook.
>

In order to route a language's standard output, we have redirected all
output to whatever the current cell is. There may be some manner to
associate output to its thread, and then route that to the proper cell. But
I don't see a lot of use for the complexity just yet.


> > It would be cool someday to have Calico as a viable kernel in Sage. (Of
> > course, there are a lot of good kernels under development. We just got
> > F# working as one of our languages, and some people might be interested
> > in that reason alone.)
>
> Does Calico work on unix (maybe via mono)?
>

Yes :) In fact it works on Windows via mono. And OS X via mono. I smile
because it is a common assumption if I mention something like C# or F# that
we have some Windows bias. But ain't so.


> Sage doesn't work well on Windows natively because many of the component
> programs don't support Windows very well.
>

I, personally, do all of my development on Linux, but we make sure that
whatever we create works on the major operating systems. It is quite a nice
system in that we only have one set of "binaries" that work everywhere.

Calico as a IPython kernel is interesting because it allows programming in
Java, Ruby, F#, Scheme, assembly (and 15 other languages) as first class
IPython languages (eg, not running via a process or shell). Thus, you
should be able to use our CameraWidget directly in all of those languages.

-Doug


>
> Jason
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20140227/ce482451/attachment.html>