Working on *Stand-alone distro for leoAst.py* #1532
<https://github.com/leo-editor/leo-editor/issues/1532> I've been
semi-successful. The structure of
https://github.com/leo-editor/ast-token-tools is approximately correct but
I've run into difficulty cleanly importing the commit history. It's okay
for the first import but attempting to merge or import subsequent
development yields disconnected branches and/or duplicate commits with
different IDs. There's probably a way to do this using git magic but I
don't know it.
Pondering this has me wondering if it's this hard to maybe the approach is
wrong. Maybe the long term way would be to make it a stand alone package
for Leo too, ie. a dependency, and handle it the same as black or pyflakes
or any of the other 3rd party requirements. This got me thinking about
plugins. Maybe they too could independent packages, and maybe they'd even
be happier that way. (I'm continually cautious/nervous whenever I make
changes as most of Leo is way over my head.)
It's relatively easy to make a new python project and make it available to
the world via `pip install {thing}`. What I don't know is how to integrate
with something like Leo if a person wants to do more with it than `import
leo-plugin-foo`. For instance: how would I access the plugin's
"Leo-Docs-plugin-foo.leo" or "Leo-Settings-plugin-foo.leo"? (how does the
plugin inform and register with Leo their location.)
Does anyone have thoughts on the topic? Know of other python projects with
independent plugins we could learn from?
-matt
--
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/dd5e03fb-67d6-4f6b-a495-98726c510228%40googlegroups.com.
