Nice work.
I do agree with you that, for someone that is experienced in using a Python console, the textarea looks closer to the normal Python interpreter than the simple input box that Crunchy uses. However, I do find that it leaves the impression that we ought to be able to go back and edit some previously entered lines - whereas the simple input box is not misleading in this regard. I think that a textarea with line numbering and a history mechanism (similar to IPython) might be the way to go.
The visual aspect, as you noted, is important. We've been busy working on this for Crunchy but it's nowhere near as nice as others (as we've spent much more time on adding new functionality.) Thanks for bringing attention to the other sites. 
I do wish I had more time so that I could try to incorporate your approach within Crunchy. Perhaps this will happen in a few months...
I'd like to build on Crunchy (and be able to reuse the tutorials already available for it) - but I wonder how much time it would take. I suspect quite a long time to do a proper job and I would rather spend my time working on the tutorials.
Going back and editing previous lines *should* be possible and is one of the features I would add to Python in the Browser. I would probably base it on [some of...] the console features of PyCrust. I expect Dan would be willing to add it to Silvershell as well.
Please remember that Silverlight is Windows only. Might be "visually appealing", but I'll never know. Yeah, I know about Moonlight, but this is alpha software. It also comes with a warning about Microsoft patents and a really scary "convenant not to sue" (Linux distributions are excluded, and even end-users are only protected if they paid some money to Novell).
@Baptiste
Silverlight is *not* Windows only. It is already Windows and Mac OS X (I do all my demos and Silverlight development on the Mac).
Your patent comments are pure FUD regarding Moonlight.
> Your patent comments are pure FUD regarding Moonlight.
That's disappointing, Michael. Trying to paper over the issues does not make them go away.
You made your choice, others made theirs, and we should be able to talk about it without being labeled as FUDdders without any explanation.
@Nicola
As regards *Moonlight* they are pure FUD though Nicola. As regarding Mono they would be *mainly* FUD (if Microsoft wanted to get rid of Mono they have had every opportunity) but I understand genuine patent questions exist. I don't believe that situation is the same for Moonlight - Microsoft have provided codecs, test suites, technical knowledge and even sourcecode for the standard set of controls. They *need* Moonlight to exist and work.
Given that Moonlight can't exist without Mono it puts Mono in a stronger position - for MS to attack Mono on patent grounds really would be shooting themselves in the foot now (far more than ever before).
For those who are ideologically already against Microsoft - and anything they might do - this will never be enough of course...
OK, I should have provided a more complete information. On the moonlight web page ( http://www.mono-project.com/Moonlight ), the last link in the "Licensing" sections leads here: http://www.microsoft.com/interop.../
moonlight.mspx , and the definitions are here: http://www.microsoft.com/
interop...efinitions.aspx . As you can see, the definition of "Intermediate Recipients" is written in such a way as to exclude Linux distros other than Novell. (I was wrong, though, about having to pay Novell: this is from the more general Novell-Mocrosoft agreement: http://www.microsoft.com/
interop..._agreement.mspx ).
Then, as you mention, Microsoft needs moonlight to exist. For now. But they also need to cripple Linux with patent royalties, so you can't be so sure about the future.
Interesting and relevant interview with Miguel de Icaza.
http://derstandard.at/?url=/?
id=...d=1216918402134
Commenting by HaloScan
