Hi all, It's good to see these paths ahead. I particularly like the priority 3 as it resonates a lot with my approach with Grafoscopio (my Pharo powered outliner, inspired by Leo, Jupyter, TeXmacs, Smalltalk among others) development and its grassroots communities involvement solving "real life" problems (in my case it became quickly priority 1). I would suggest a little bit of lateral inspiration by using other outliners and tools. In my case, the old inspiration with the afore mentioned tools has been improved by the recent exploration of Doom Emacs[1] and Lepiter[2]. Maybe such lateral exploration would seed the interesting and powerful Leo+LeoInteg bridge.
[1] https://github.com/hlissner/doom-emacs [2] https://lepiter.io/feenk/introducing-lepiter--knowledge-management--e2p6apqsz5npq7m4xte0kkywn/ Also good to know that your sabbatical is over. Of course you can extend it as you like, but is always good to have you here Edward and to see the energy you imprint in this place. Cheers, Offray On 18/08/21 10:53 a. m., Edward K. Ream wrote: > Ending the sabbatical has clarified my goals. > > *Priority 1: Support the release of leoInteg 1.0* > > Félix and I will take as long as necessary. 1.0 may happen in a week > or two. If it takes longer, so be it. Still, I expect that leoInteg > 1.0 will go out the door in a month or two at most. > > *Priority 2: Unit testing* > > Using `@test` nodes has become an embarrassment. I'll give priority to > those Leo features that leoInteg uses. So most editing commands do > /not/ have to be tested. However, there are proper (traditional) unit > tests for most of those commands anyway. > > *Priority 3: Solving new problems in Leonine ways* > > Innovation never happens in a vacuum. Instead, innovation is the > result of solving juicy problems. So I'll be looking for those problems. > > *What I won't do* > > I'll continue to ignore the majority of feature requests. I'll > consider "petitions," but the surest way of getting an issue done is > to do it yourself. > > I am unlikely to put substantial effort into projects such as "Leo in > language X." Python is deeply privileged in Leo for several good > reasons. Yes, the situation is different in leoInteg, and dealing with > that difference is likely to be the source of innovation. > > *Summary* > > Leo and leoInteg will likely keep me busy for the rest of my life. > > All comments are welcome. > > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/1f236520-c6cc-4180-bb78-6e6884c2bbf3n%40googlegroups.com > <https://groups.google.com/d/msgid/leo-editor/1f236520-c6cc-4180-bb78-6e6884c2bbf3n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/84ef99e0-9871-f9bb-a254-7f9cc3845f93%40riseup.net.
