My first reaction was to say no, don't retire working code. And I think some people use *add-editor*, even though it's fairly unworkable for me personally. My second thought was to realize that there could be a change to a future version of Qt that makes the code stop working. Who is going to want to maintain that? So now I lean towards removing it. Is there a way the removal can be scheduled for a future release, and a deprecation warning given in the meantime?
I wonder if leoJS has the *add-editor* command working. I imagine that it would not be hard to recreate Freewin in leoJS, and I think it would be worth doing once the plugin mechanism is working. On Saturday, December 23, 2023 at 8:26:41 AM UTC-5 Thomas Passin wrote: > As a bonus Freewin can render ReStructuredText bodies. > > One point to remember is that Freewin's editor is not a full-fledged Leo > body editor. It only gives you key shortcuts that the underlying Qt widget > gives you, for example. I find that is plenty good enough for the intended > purpose. > > On Saturday, December 23, 2023 at 4:20:41 AM UTC-5 Edward K. Ream wrote: > >> Thomas has just posted a discussion of the freewin plugin >> <https://groups.google.com/g/leo-editor/c/PRW9Aoa1rVM/m/arg63qSAAAAJ> >> and its use for comparing nodes and taking notes. >> >> As Thomas says, this plugin is more convenient and easier to use than >> using multiple body panes within Leo itself. >> >> Is it time to retire Leo's add-editor command? Your comments please. >> >> 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/a14a5355-b9e2-4dae-a364-ef424a84bf5en%40googlegroups.com.
