>However, many times people have convinced me that I should want something more >:-)
or something less **cough (clones) cough** :-] On Tue, Aug 18, 2015 at 4:32 PM, Edward K. Ream <[email protected]> wrote: > On Tue, Aug 18, 2015 at 12:06 PM, Kent Tenney <[email protected]> wrote: > >> *checks pocket, finds 2 cents* > > > Or rather, several gold pieces :-) You and Terry seem to understand me and > my goals and motivations very well. I appreciate your comments. > > >> There's a tension between wanting Leo to gain widespread >> appreciation and making changes which Edward doesn't >> consider important. Understandable, Edward has a different >> relationship with Leo than others. > > > Yes. I have always done pretty much exactly what I wanted to do. However, > many times people have convinced me that I should want something more :-) > > >> >I wrote Leo for my own uses, primarily to aid the design, >> >construction and understanding of complex computer programs >> >such as Leo itself. It's great if other people use Leo for other >> > purposes, >> >but I feel no obligation to refocus Leo to such purposes. >> >> And he shouldn't feel an obligation, but maybe acknowledge that reaching >> a wider audience might involve some refocusing. > > > Maybe. Up until now I have been focused on programming and scripting. And > there is always something new to add. The new efc.compareTrees helper is an > example. > > There are several areas we could explore together. The first is Leo's > relationship with data bases. My brother Speed has done work in this area, > and I would like him to share with us what he has done. Separately, Speed > says that Sentences associative model is very much like a Leo acyclic > directive graph. So this could be something interesting. > > Another area is using Leo to render rST, markdown, etc. more powerfully. > This is the motivation for merging the vr and vr2 plugins. Perhaps all that > is really needed is a gallery of cool things that can already be done with > Leo. > >> >construction and understanding of complex computer programs > > >> >> Core to this is *clones*, Edward leverages their power brilliantly, >> I'd be curious how many others are as wed to them. >> I'm reminded of a developer opining against sophisticated IDEs, >> he thought they made it *too easy* to manage complexity, resulting >> in code which was too complex. Using an simple editor tends to >> enforce smaller files, simpler classes, shorter methods. >> The need for clones is one of those perennial debates, but I think >> it may be germane to this thread. > > > Managing complexity can never be too easy. I have been playing around with > the idea of creating new kinds of views into programs. Presumably, these > would be represented as Leo outlines, and rendered by Leo, but that's not > really the challenge. Is there a way, using Python classes, or some other > way, to represent how complex algorithms work? I doubt there is a general > solution, but this is a question that interests me. > > >> >> As far as branding, direction, that sort of thing, I see Leo as a >> tool to manage data: nodes, trees, graphs: reflecting the structure >> of the data whether a file or class (or method, if you're using sentinels) >> or another representation of structure as defined by a file type, or >> generated by the user in native nodes. >> (the degree of structuring is something I sometimes find bothersome, >> hence my interest in <alt-x>vim-edit-file) >> >> So Leo is brilliant at grokking data, wait a second, grokking data is >> all anyone talks about these days. >> >> From here on out it's pretty hand-wavy, pioneery, envisioning capability >> which doesn't really have an analogue. >> >> Put a database behind Leo, structured according to schemas defining >> node, file, tree, user, permissions, version etc. > > > Possible. It might be a meld of several ideas you and I have been > discussing. > > >> Make the database network accessible, not necessarily cloud, but available >> across machines. Allow me to view and or edit a subtree which Edward >> commited to the database. > > > I believe Jupyter has this, quite apart from rendering pages in a browser. > It's a significant piece of work. > > >> Allow me to generate a Leo file from the database resulting from a query, >> offering a structured view of the data I'm interested in. > > > If I understand correctly, this what Speed's Leopard (Leo something response > daemon) does. > > >> >> Maybe generate a file based on the wonderful APIs offered by >> http://sunlightfoundation.com/ where top level nodes would be >> 'Senate' 'House' 'Executive' and 'Judiciary', they would be populated >> (on demand) by the available stats. Create a node 'Tammy Baldwin' >> dclick, see her voting record, contributers etc. Given adequate >> perms, make a correction, addition: alerting the stewards of that content. >> >> Click to populate a Leo file with the available wifi networks, showing >> attributes of each in a subtree. > > > Interesting site. > > >> On and on. > > > Yes. Thanks for your ideas. > > Edward > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
