The installer at rev 2369 of the trunk can now install Leo. As noted below, the remaining tasks are determining what boilerplate code the script should emit. It is here that help with installer guru's would be appreciated.
The commit log: QQQ Use rootDir to specify path to source files. Leo now can create a script that installs Leo. The following do not work: - The .onInit function has been disabled. I need help finding Python 2.5 or later. - The uninstall script appears to work, but does nothing. Perhaps it is deleting the wrong stuff??? QQQ It's now time to improve the generated leo.nsi script. - I'll work on fixing the uninstall script. It may be a simple blunder. - To create the leo.nsi script in the top-level leo directory, execute the script in the node "create leo.nsi" in leoDist.leo. - The script contains lots of "boilerplate" code in the "boilerplate" subtree. There are problems with messages that are due to the put function is not handling indentation properly. I'll fix this asap. - As noted above, I disabled the .onInit function. See the node putOnInit for the string that defines this function. I suspect that finding Python (making .onInit work) will be the hardest remaining task. Here is where help from an installer guru would be appreciated. Thanks. Please feel free to ask questions about the script. To repeat, I suspect that installer guru's will be able to ignore most of the guts of the script. Instead they would just modify the triple-quoted strings that define the boilerplate. Edward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
