I just wanted to check in again before going on to the next step for me in GSoC. I need to start polishing work on my code very soon--the firm pencils down date is in two weeks--and I would like some confirmation as to whether or not my project could be feature in the version of IDLE released with Python. If it could be, I would really appreciate some input about how to proceed. Otherwise, I appreciate all of the work you have contributed to IDLE and Python in general, I couldn't have done this project without it.<br>
Chas<br><br><div class="gmail_quote">On Mon, Jul 26, 2010 at 11:47 PM, Chas Leichner <span dir="ltr"><<a href="mailto:chaoslichen@gmail.com">chaoslichen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I posted on this list at the start of the summer about my Google<br>
Summer of Code project. I've made a lot of progress and want to bring<br>
it to the community for some feedback. For people who missed a<br>
description, I am working on an extension to IDLE which will allow<br>
tutorials to be more interactive. It works by accepting specially<br>
annotated Python files which describe their own annotations. It then<br>
generates a trace of the execution, along with annotations and<br>
variables, storing it as a JSON file. I then made another type of<br>
window for stepping through the traces like a debugger and displaying<br>
the annotations at the appropriate lines. I have gotten to the point<br>
where I have a working prototype for my project and would like to know<br>
where the IDLE developers see it fitting in with IDLE. I don't know<br>
if it would fit in better as a built in additional feature, an<br>
optional extension, or somewhere in between. I would also appreciate<br>
any advice on how to integrate it better with the current class<br>
hierarchy (it is currently rather awkwardly grafted on) so I could get<br>
user interface issues addressed as soon as possible.<br>
<br>
If you want to take a look at what I've done so far, this is my repo:<br>
<a href="http://code.google.com/p/idlecarpentry/source/checkout" target="_blank">http://code.google.com/p/idlecarpentry/source/checkout</a>. The .json<br>
files in the examples directory will bring up a trace window directly<br>
when you open them and the .py files will bring up the editor, as<br>
usual. Traces can be run from the editor window by selecting Run ><br>
Create Trace, annotations are pulled from any line starting with #><br>
and applied to the first line of Python code which follows. I would<br>
love to hear any about any bugs you find or UI friction you encounter.<br>
<br>
I have been keeping a blog here <a href="http://cleichner.blogspot.com/" target="_blank">http://cleichner.blogspot.com/</a>, and<br>
will be posting a screencast to it tomorrow.<br>
<br>
Thanks,<br>
<font color="#888888">Chas<br>
</font></blockquote></div><br>