Improving Code Editor in PyKata

[Abhishek Mishra]

Hi everyone,

I just came across Bespin from Mozilla Labs - https://bespin.mozillalabs.com/

Looks like we can embed it into our own projects. I'll give it a shot
as soon as I'm ready with Idea list for PyKata which is of more
priority to us right now.

Let me know your opinion/experience on Bespin if any. Looks pretty
good to me :)

Also would it be okay to release the PyKata idea list to Edu-Sig for
more brainstorming after posting on PyWhip mailing list?
I'm just starting with ideas.

Thanks,
Abhishek

[Abhishek Mishra]

Allright Bespin is cool, but would lack browser support, a good way
would be to fall back to edit area if Canvas is not available, and
fall back to text if JS is not available.

http://robertnyman.com/2009/04/03/mozilla-labs-online-code-editor-bespin/
^^ only supported by modern web browsers currently.

Another good thing I came across with web2py is -
CODE(open('yourfile.py','r').read(),language='python')
^^ gives back a code editor :)

On Mar 25, 8:22 pm, Abhishek Mishra <ideam...@gmail.com> wrote:
> Hi everyone,
>

> I just came across Bespin from Mozilla Labs -https://bespin.mozillalabs.com/

[Abhishek Mishra]

Another option - Coding Mirror http://marijn.haverbeke.nl/codemirror/

A very simple interface - http://marijn.haverbeke.nl/codemirror/contrib/python/index.html

At this time, the following browsers are supported:

* Firefox 1.5 or higher
* Internet Explorer 6 or higher
* Safari 3 or higher
* Opera 9.52 or higher
* Chrome

On Mar 25, 8:37 pm, Abhishek Mishra <ideam...@gmail.com> wrote:
> Allright Bespin is cool, but would lack browser support, a good way
> would be to fall back to edit area if Canvas is not available, and
> fall back to text if JS is not available.
>

> http://robertnyman.com/2009/04/03/mozilla-labs-online-code-editor-bes...

[David MacQuigg]

Let's discuss these ideas first within our group. Time is short, and I
want to avoid long, less useful discussions. A final review involving
[edu-sig] would be OK, but let's not let it slow us down in getting a
good proposal for GSoC.

-- Dave

[Abhishek Mishra]

Alright, I'm putting down an idealist right now, would be here soon.

Abhishek

> --
> You received this message because you are subscribed to the Google Groups
> "PyWhip" group.
> To post to this group, send email to pyw...@googlegroups.com.
> To unsubscribe from this group, send email to
> pywhip+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/pywhip?hl=en.
>
>

[David MacQuigg]

I'm not seeing the benefit of a sophisticated code editor integrated
into PyKata.

The EditArea widget we are currently using seems to do everything we
need, even some nice syntax coloring. Remember, these are simple
functions that students are entering, not huge programs that would
benefit from a more full-featured code editor.

Let's be sure the benefit to our users justifies the time and energy of
not only our current developers, but also the future maintainers of
PyKata, who may be students also.

These same concerns apply to the choice of Web2py vs Django.
Professional web developers seem to love Django, but they do acknowledge
a steep "learning curve". What we need is code that a student web
developer can understand and make simple fixes. You might even need to
write a document explaining how everything works.

-- Dave

[Abhishek Mishra]

I suggest we go for web2py. From the experience with sahanapy
developer community, I observe that entry as an contributor was pretty
easy once little bit of web2py was explained to me by them.
Besides there are 4-5 student contributors to sahanapy who work on web2py.
I believe that's a good proof to choose web2py as our framework :)

Thanks,
Abhishek