At present, the only remaining item to do for the installer is to determine the location of Python. This is what the now- disabled .onInit function does.
On my machine, regedit contains entries for all all my Python folders. For example: HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\2.5 HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\2.5\InstallPath I am thinking that will be enough to make the shortcuts generated by the installer fully functional. As an alternative, it is possible to generate a so-called installer "page" that will prompt the user for the location of Python, but I see no real need to do this. At present, the only two valid Pythons are 2.5 and 2.6, so trying 2.6 first, then 2.5 seems like a straightforward solution. Anyone see any problems with this approach? Edward P.S. The script is almost, but not quite, ready to be used for any bzr application. That is, it can be modified for other apps simply by changing top-level (Python) defines in the script. The only glitch is that at present the script hard-codes the value of the "leo" directory. It was an impatient hack for some problem or other. I'm hoping I'll be able to get rid of it, but Leo 4.6.3 can go out the door without changing it. EKR --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
