On Fri, Oct 31, 2008 at 12:25 PM, Mike Crowe <[EMAIL PROTECTED]> wrote:
> As a returning user, I can offer some fresh insight, I think. I'm pumped > about Leo because I'm starting to see the deep power it has, which I wasn't > willing to find in prior experiences. Yes, there really must be an Aha moment where each new user sees what Leo is about. > Documentation: I agree that Leo's documentation could be improved. > I'm learning the joys of rst and writing documentation. We need a few > downloadable examples to help out. I found a lot from reading the > LeoDocs.leo. Yes, more examples would help, but LeoDocs.leo seems good enough for a start. > Edward is fantastic, but a vibrant community is critical to not drive people > away. We need more participation from people helping new people out. Quick > responses to n00b's asking for simple questions would be great. I'd be happy to have help. Are you volunteering :-) > Ability to collaborate on plugins, etc. This may be available, but it isn't > necessarily obvious. I groan to say this, but we almost need some wiki based > collaboration area where we can all contribute. I think bzr is a great tool. We have had lots of substantial collaboration on bzr branches this year. > IRC Channel. I think this would help, again, if we had a willing community. Again, I would be grateful for help, but this is not something I am willing to do myself. I value stretches of uninterrupted time, which is why I prefer email. > Languages: > > We need evangelists for each language. The python support is rock solid > (naturally). However, importing projects in other languages is not really > supported yet, nor easy. Huh? Leo has numerous importers, and numerous ways of importing directories of files. > I'm trying to tackle php and lua, but we need more > people within those communities expanding our support. Leo already has a php importer. See leoPy.leo, the node: Code-->Core classes-->@thin leoImport.py--><< scanner classes >>-->class phpScanner As you will see, almost all the work is done in the base class: Code-->Core classes-->@thin leoImport.py--><< class baseScannerClass >> so writing new importers should be easier than you might suppose at first. > I think qt might be the answer. Tk (though I run on windows) make it feel > old, somehow. Well, it's coming fast. > A true find/replace with regex support. I'm learning how to use the > existing support, but man, it's frustrating for new people. Leo has full regex support. > Shadow trees: IMO, this is the future. I think most will use this mode as > they develop. Especially for when using Leo to develop in environments for which making Leo a requirement is not possible. > Dynamic keyboard mapping: We all have different key choices, but I hate > searching for what I want to change, updating, exiting everything, then > going back to see if that was right. Currently, I was trying to remap F2 to > change the Headline. I put that in my myLeoSettings.leo, but got this > message: redefining shortcut F2 from edit-headline (all) > to find-prev (all). I have no idea why, but hate the process enough to not > bother with it. The print-bindings command will tell you where each binding comes from. > Vim: I'm not a programming novice by any means, but configuring things like > Vim keyboard emulation should be easy for new folks. I had so many problems > with it that I abandoned it and went back to the old keyboard binding. > OK, configuration: The more I think about what I don't like it really is > the configuration. Improving this is on the list. 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 -~----------~----~----~----~------~----~------~--~---
