RE: [Pythoncard-users] an IDLE clone (PythonCard IDE, wxIDLE...)

Editing Python Source Code
http://www.python.org/editors/

ka

> -----Original Message-----
> From: pyt...@li...
> [mailto:pyt...@li...]On Behalf Of Kevin
> Altis
> Sent: Saturday, January 19, 2002 8:09 PM
> To: pythoncard-Users
> Subject: [Pythoncard-users] an IDLE clone (PythonCard IDE, wxIDLE...)
>
>
> After listening to Guido's talk about Python and CP4E I got
> inspired to but
> together some background material links and topics relevant to an IDE for
> PythonCard. Please respond to this thread with other links or relevant
> issues. I don't know when we might pursue this, but it could certainly be
> done in parallel with some of the other work Rowland and I have
> been doing.
> If nothing else, this will make a good placeholder message to go back to
> when the motivation fairy visits one of us.
>
> There were a few threads back in August on wxPython-users about doing a
> wxPython IDLE (wxIDLE) program.
> http://aspn.activestate.com/ASPN/Mail/Message/722717
> Nothing seems to have come from that discussion; I think it ended up with
> people wishing Riaan would do a Boa-lite, but he is swamped and isn't even
> working on Boa as far as I can tell. Boa already has a lot of what people
> want, but a lot of extra stuff too. Anyway, there is probably
> enough wxIDLE
> interest that people not even interested in PythonCard would probably help
> with the effort.
>
> One Day of IDLE Toying
> http://hkn.eecs.berkeley.edu/~dyoo/python/idle_intro/index.html
>
> IDLE home page
> http://www.python.org/idle/
>
> The IDLEfork  Project
> http://idlefork.sourceforge.net/
> This is the place for IDLE developers.
>
> IDLE Documentation
> http://www.python.org/idle/doc/
> This is the most useful document I've seen for use as a spec.
> There is a lot
> to be said for just duplicating the features and key bindings of the
> tkinter-based IDLE, but using wxPython/PythonCard with wxSTC. The
> key would
> be to not deviate from the IDLE spec on the first pass, so that it is a
> straight coding effort without lots of design/redesign going on.
>
> We already have the Shell component, we just continue to use PyCrust.
>
>
> In the "six blind men describe the beast" thread, Neil Hodgson said:
>    "Writing a small editor isn't all that hard. I don't expect the initial
> version of an editor for PythonCard that handled the vast
> majority of needed
> features would take long at all. You can get tied up in details
> though. The
> biggest question to me would be how do you determine which files
> are part of
> a PythonCard project and where within those files are the event
> handlers? Do
> you do VB style file segmentation or just present the whole file to the
> user?"
>
> ka
>
>
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythoncard-users
>