Some inline comments >>I find reading and navigating >>> Leo's docs inside Leo more cumbersome (maybe I just haven't tried hard > enough).
> I agree they're nicer to read in a browser. HTML browsing is already builtin in some sense through the viewer and @url, but could be easier turn on and control. >> One requirement would be to avoid >> forcing the user to set up bzr / ssh / launchpad. That part could >> probably be handled by Leo itself. > > see something to fix or add to, and click the [edit] link in the > > sidebar. The browser calls Leo, which opens that file and outline > > location. I make my changes, save, and push "email to launchpad" > > button. I agree on these points. I think it would be a big step forward in encouraging both code development and documentation improvement to have a Leo Developer version that has these as built in functionality --create Launchpad lp:leo-editor account with push capability for new users (I recall setting up keys for ssh is complicated) --authenticate lp account --both bzr push and bzr pull (with auto reload) One potential hangup would be integrating lp authentication and bzr access in Leo and retaining platform independence. Not sure of relying on the python bzr library is necessary, vs the more reliable command line method. -- 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.
