On Dec 9, 8:09 pm, mdb <[email protected]> wrote: > I think your SOP to give headlines titles that are just Dates+Time -- > - versus using descriptive titles -- would not help most people better
Yes, perhaps I should have just used "node A" "node B". In my case I'm also planning a "journaling" tree, which will basically clone the "canonical" tree, but only include that subset of the nodes that fall into "talking to myself / misc analysis / stream of consciousness" that I'm currently doing with RedNotebook. > Leo lets you embed custom created attributes to each node, besides the > title and body text, but this takes some programming and LEO > experiences. Trying to get around the programming by embedding > attributes or tags in the title is probably a dead end -- at least for > developers that want greater power and flexibility. Data 'stored > (ideally discreetly) in my plaintext content' is inferior to data > stored internally that can be displayed and accessed anyway you want > it. I.e. you will have a had time convincing a programmer to use the > less-than-the-best tools available for the job. Of course everything you say is true - but relevant to programmers. It's obvious that Leo is primarily targeted to that context, but I would argue that its potential is no less revolutionary out in the end- user world, and that is where my interest lies. For example, I am a teacher, and would love to have my students learn to organize their thoughts for essay writing in Leo, getting beyond the usual outlines method I learned from Mrs Arbuckle in the third grade. And my own use-case, managing single-source lightly-marked-up plaintext for output to various publishing formats, while more technical, is also not an area limited to programmers only, and Leo seems (so far to me) to have the potential to be a best-of-breed tool in that arena as well. > I suggest working through a python tutorial. It sounds like what you > need are programming scripts to pull out and re-use/re-format data > from '20K+ bookmarks currently hostage to the vagaries of > del.icio.us'. Sounds like a perfect job for a program-- not manual > manipulation. I wasn't planning on doing anything manual with that data set believe me. On the other hand I **don't** want it to end up stored in yet another opaque format. I intend the end result to be lightly-marked-up plaintext files in a dirstruc, most likely OPML. Of Leo is just one possible element of the toolchain, the data is stored as XML and also in SQLite DBs, so more mainstream import/export/ reporting/data conversion tools exist - the only difficult piece I see is if I decide to try to preserve my "tag bundles". As with any such project, if I can accomplish what I'm trying to do without having to become a programmer I will, as unfortunately my current situation doesn't give me that much free time. Thanks very much for the learning Python resources, and I'm sure if I stick it out with Leo I'll continue to be nudged in that direction, and maybe before I get too old and doddery I'll have the time to dig in. . . > Another option is to 'contract' out the work. You just need to describe the > job well and be very specific about the output you expect. There are numerous > sites devoted to freelance programming. If I had the money to pay someone to do it for me, I'd invest it in "free time" to learn how to do it myself. In my introductory thread I ended with > If I were rich I'd learn to become a programmer To Terry - believe me I'd already got excited by that post, it's been tagged as 2followUp in delicious, which I will do once my basic Leo knowledge is in place. Thanks much for the encouragement to me, as well as of course all your contributions to the community. -- 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.
