My 2ยข: If something like this **is** done, it should IMO be packaged as an alternative to the normal installation procedure.
You would definitely get marketing exposure by getting the specs from PortableApps.com and let them host it there as "Portable Leo", tracking the "official" Portable Python (currently 2.7.2) as a dependency, obviously including QT etc as well. But it would need to be kept up to date. . . Most Windows users would be better served by following the normal installation procedure and ending up with a registry-and-environment-variables-complete install of Python et al which they can use for other things beyond Leo. Ending up with multiple instances of Python to maintain is likely to cause more problems. And the normal Windows install just isn't that hard, really! Improving the current instructions, by providing a step-by-step "cookbook" with direct links to the download packages etc might make it a **little** easier (IMO only for the clueless), but then of course that would be a doc that would need pretty frequent updates, which if I may be so bold doesn't seem to happen too quickly on the doc side. (for which topic I'll start a new thread) -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/uJxbe8iqgzwJ. 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.
