[IPython-user] Cocoa frontend for ipython1

[Ville M. Vainio]

On Wed, Mar 12, 2008 at 10:26 PM, Barry Wark <barrywark@gmail.com> wrote:

>  I've started working on a Cocoa (OS X) front-end for ipython1. I'm
>  struggling a bit with bzr at the moment (bzr branch
>  http://bazaar.launchpad.net/~ipython/ipython/ipython1-dev  gives me a
>  ipython1-dev directory with a .bzr folder, but no other contents...)

Weird, works for me.

And now, without any real ipython1 background:

>  2. I propose an additional IEngineInteractive interface consisting of
>  deferred wrappers for ipython1.core.interpreter.Interpreter's
>  feed_block and complete methods. This allows interactive frontends to
>  do propper line continuation and tab completion. I propose that we

Why not compile in the frontend? Just to see whether the command is
complete, that is...

Regarding completion - I don't think we need to make anything special
for this. Why not just ask for the engine to execute
_ip.complete('os.pa') or somesuch, and get the return value list in a
pickle?

>  3. Have folks thought about how we're going to handle the equivalent
>  of the ThreadedInterpreter in the new model (i.e. how should I think
>  about handling matplotlib plotting)?

I don't think we need to be afraid of threads on ipython1, because the
user won't be pressing ctrl+C in the engine. We could even make the
default shell like the current MTInteractiveShell, i.e. whoever
chooses to run it's 'runcode' once will always be forwarded the next
code execution requests. Then, it's just a matter of instantiating
something that will grab the code execution pipeline
(MTInteractiveShell.runcode() responsibility).

-- 
Ville M. Vainio - vivainio.googlepages.com
blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio'