On Mon, Sep 7, 2009 at 7:47 AM, David Szent-Györgyi <[email protected]>wrote:
> Your proposal -- putting all the boilerplate in a .txt file -- would > allow me to maintain all the code in one place. It would still mean > editing the boilerplate in the .txt file and the calls to the > boilerplate in a Python script elsewhere in the Leo outline. This seems to me to be a reasonable plan: - Rather than reading the boilerplate, the script generator script could simply generate an !include line. - leoDist.leo could contain @thin nsi.boilerplate.txt tree. This scheme would allow all aspects of the final .nsi script to be written in leoDist.leo. 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 -~----------~----~----~----~------~----~------~--~---
