[Idle-dev] mods?

[StephenM.Gava]

On Thu, 4 Oct 2001 03:59:am, Bruce Sherwood wrote:
> I'm not a registered developer for idlefork, so I'm not quite sure how best
> to submit the following changes. I gather that one mechanism is "patches",
> with which I'm not familiar. I'd be happy to submit this work in some other
> way, if someone would give me a microtutorial on how I should be doing
> this. Thanks!
>
> Bruce Sherwood

Hi Bruce.

Actually you don't have to be able to make real patches  (using patch) to 
submit 'patches', or more acurately, coding contributions, to idlefork. Just 
go to the idlefork home page ( http://idlefork.sourceforge.net/ )  and click 
on the 'submit patches' link in the 'IDLEfork at SourceForge' section of the 
sidebar. This will take you to the patches area of the idlefork sourceforge 
site where you will see a list of patches currently in the system.

When you get there click on the 'Submit New' link, which will take you to a 
page where you can enter your new patch.   Here you can eitther paste your 
changes, along with some explanatory notes, directly into the 'Detailed 
Description' box, or you can attach a file containig your code if you wish.

In either case please make sure you include some notes, or particularly 
comments in the code, to explain your modifications or additions and their 
purpose.

Thanks very much for contributing to the project. I meant to contact you 
earlier in response to your contribution of your 'spawn fix' patch for the 
windows platform, but I haven't regained reliable 'net access yet. Please 
post again if you have any further questions about submitting 'patches' or 
idlefork in general.

Thanks again,
Regards,
Stephen.

>
> ------------------------------------------------------------------------
>
> Attached is idlemods.zip, a zip file containing three modified files
> produced by modifying the files provided in idlefork-0.8.1.zip:
>
> 1) PyShell.py: outputs informative paragraph if Idle cannot run
> 2) spawn.py: corrects bug in Windows launch (no spaces around python.exe)
> 3) EditorWindow.py: invoke VPython.html if present in Doc, else index.html
>
> 1) The changes to PyShell.py move the creation of an on-demand window early
> enough in the process to be able to give an informative error message if
> Idle cannot run due to socket failure. This addresses the problem that Idle
> can fail silently.
>
> 2) A one-line change to spawn.py was needed because DOS-munging to 8-char
> names caused Idle to fail to start a run (on pressing F5) if Python was
> located in "Program Files" (which has a space in it).
>
> 3) The small change to EditorWindow means that if VPython is installed,
> pressing F1 invokes Doc\VPython.html, which gives you VPython
> documentation, Numeric documentation, and the usual Python documentation.
> If VPython.html is not installed, Doc\index.html is invoked, which just
> gives you Python documentation (VPython.html has a link to index.html).
> VPython users need the additional documentation. For info on the nature of
> VPython, see
>
> 	http://cil.andrew.cmu.edu/projects/visual
>
> My goal is that in the future all VPython distributions include the
> idlefork version of idle, rather than the older version originally due to
> Dave Scherer, from which idlefork development started.

-- 
Stephen M. Gava  <elguavas@users.sourceforge.net>
IDLEfork ( http://idlefork.sourceforge.net )  " just like IDLE, only crunchy "