I remain confused, due to my lack of basic knowledge/experience with bazaar; it is likely I did something wrong and didn't follow the directions, since my understanding is that following the directions did not result in there being any launchLeo.py (or anything at all other than .bzr) in the leo-editor folder.
When I have time I'll run through it again and keep a detailed log.
In the meantime I still believe that if we want non-programmers to run from trunk rather than arbitrary releases, the user-level installation docs need clarification to support people that may have never heard of version control, much less bazaar.
I am happy to contribute to such docs if there is a clear and efficient path to do so.
In my getting to know Leo, it seems that DokuWiki's data structures (plain text in a dirstruc) would be a trivial publishing target for Leo to generate. This would allow a developer-maintained "master source" to be kept authoritative, as well as a completely open and easy-to-contribute-to wikiweb for user edits and contributions - simple difftools could be used to periodically update the master source, wipe that part of the wiki with a new authoritative "version" available for further feedback.
I remain confused, due to my lack of basic knowledge/ experience with bazaar; it is likely I did something wrong and didn't follow the directions, since my understanding is that following the directions did not result in there being any launchLeo.py (or anything at all other than .bzr) in the leo-editor folder.
When I have time I'll run through it again and keep a detailed log.
In the meantime I still believe that if we want non-programmers to run from trunk rather than arbitrary releases, the user-level installation docs need clarification to support people that may have never heard of version control, much less bazaar.
I am happy to contribute to such docs if there is a clear and efficient path to do so.
In my getting to know Leo, it seems that DokuWiki's data structures (plain text in a dirstruc) would be a trivial publishing target for Leo to generate. This would allow a developer- maintained "master source" to be kept authoritative, as well as a completely open and easy-to- contribute- to wikiweb for user edits and contributions - simple difftools could be used to periodically update the master source, wipe that part of the wiki with a new authoritative "version" available for further feedback.
Sorry, just thinking out loud. . .