>My thought was to set up python, leo, and Qt in a single directory - the
>directory would then be installed by the "leo" installer, so that you end
>up with leo and its private copies of python/qt in c:\program
>files\leo\leo or somesuch. Dumb, inelegant, and the lowest possible
>barrier to the Leo experience from a user perspective.
In case this is the approach taken, and registry entries need to be
captured to create a "Leo" installer, this program does a pretty good
job of comparing copies of the registry to see what's changed:
http://sourceforge.net/projects/regshot/
Todd
--
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.
