... and while I realize that the answer(s) to my question(s) seem to be somewhere near the first page of the homepage, maybe at: http://leoeditor.com/testimonials.html yes, I read those, and I trust them; but there's a lot of opinions there, and few examples. Examples like: I needed to do this little thing, and I did it this way; and that other little thing, and I did it that way. I don't mean that I'm entitled to this kind of hand-holding; it's more, I think that this would be the kind of information that would draw many more Python programmers, and potentially other programmers to Leo. Thanx again; Nenad
Am Dienstag, 5. Juli 2016 19:46:21 UTC+2 schrieb Propadovic Nenad: > > Hello Ed and everybody, > I'm writing inspired by Eds post "Wanted: students for the Leo Code > Academy" of today, but I'm carrying this question with me since, well, > February, when I started using Leo, again, after a pause of maybe ten years. > And yes, I recognize that Leo helps me organize my thoughts and code and > texts once in a while, but there seems to be a big gap between those who > dig it and those who don't, and I seem to be on the don't-dig-side. Not the > fact that it can be useful, but the fact that ut can be useful to extents > that it has some fanatic fans. > I tried using Leo for tasks that jumped at me, like, translating some code > from Perl to Python. I did it by analyzing the (very poor) structure of > that code in Leo, and it still took me a week; afterwards I realized I > would have been better of, if I had just translated it to Python - command > by command - , *without* understanding the structure, and *then* tried to > force structure upon it; so decomposing and analyzing seems not be the > right method for this kind of task. > Now, again, another task: I'm analyzing some Python code, much better > structured. Still, it's quite complex, the state-machine it contains has > multiple rather unclear transitions and conditions of changing > transitions... Leo helped me only so much, but just the implications of > this and that changing value in the code at runtime... is just not yet > clear to me. Trying to analyze seems to be less useful than adding log > entries to see the runtime values. > So, after seriously trying to use Leo for tasks that came along my way, > and finding it nice, but not so useful that I'd say it's indespensable, may > I ask: what are you guys using Leo for? > I realize that writing code of the size and quality of Leo itself is a > huge task, and would be hard without a good tool; but are there smaller, > but also very useful things you can do with Leo, which would be much harder > without it? > (Yes, I have read the documentation; not I have not *studied* it). > I'd appreciate examples which *show* me why Leo is great. I really want to > love it, honestly. I *tried* to find it extremely useful ten years ago, > when I stumbled upon it after reading about the greatness of outlines > (articles from Steve Litt). Yet by now I have the impression that it's most > useful in a greenfield environment, when you have control of structure, > anyway. Being a contractor, hopping from project to project, I almost never > do such development. > Thoughts? Answers? I'd really appreciate them. > Regards, > Nenad > -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
