Here are some comments on some recent posts that I make to help (hopefully) the dialogue, plus what I think are 2 new ideas.
* Fixing the broken search on home page is very important, in terms of keeping new users of LEO interested in the project. Search at http://webpages.charter.net/edreamleo/search.html?q=help&check_keywords=yes&area=default does not work, and has not for sometime, plus it next to impossible to find unless you know how the web site is organizes. It is very hard to find the right help documents without a good search utility—or at least new users would think so. Maybe a completely new, different and more robust search utility should be used. * A redesign of the LEO website would help as well, but what might provide greater value added is a better user contributed Wiki. I know there is one but most of the entries are ‘dead’. Pruning the dead branches or maybe just highlighting the living ones would help. Also there is few clues on how to contribute or edit. * Ed – how about adding an open letter to new users on the web site, stating what you think LEO offers and why contributing to the group is worthwhile, plus state the best way to contribute and get involved. And it would be important to update this regularly. What I am thinking is a summary of what you write to the group -- all in one place. * It seems that there is a temptation to have LEO do almost anything and everything, such as managing BLENDER projects, replace SCITE or WORDPRESS (pardon to Ed if I am misinterpreting). I think a better overall goal is to have LEO manage and organize almost anything through trees, cloned nodes, @file links and python scripting power. In this regard I suggest a @open node concept where clicking on or hitting enter on a @open node opens another program with given inputs (much like a desktop shortcut) based on the underlying sub-tree headlines and bodies. I know this is not very hard to do with a button that runs a script, but something built-in for python neophytes would help. This way you fully harness the power of other program, versus trying to replicate or better them. To make this concept work to its full potential for new users, setting up the @open would have the option of a dialogue box – much like a desktop shortcut (or alternatively a website management program or bzr project GUI interface). And to complete the circle, the @open anticipates the other program will ‘talk’ back to the LEO outline both through files and directly. Of course the @open name is open for debate. * In the end, no one has time to do everything they desire or dream up (given our paying day jobs). I suggest that regular Leo users contribute $5, $10, $50 or as much as $100 to a fund that Ed manages to hire contract programmers. There are numerous sites where programmers across the globe can bid on a job and Ed is very skilled at describing the tasks, understanding what is feasible and where resources are best spent. If I had my druthers, I would use the fund to first fix or replace search, prune the WIKI and make it easier to add to, update and manage, and then remake the web site. My @open idea surely needs more thought, debate, feedback and protyping before it would be ready to 'task' out. Hope my 2 cents is worth at least that -- 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.
