SWIG worked for me ages ago...
http://www.swig.org/
-->Jake
On 4/1/2014 11:05 AM, Edward K. Ream wrote:
On Tue, Mar 25, 2014 at 10:59 PM, F.S. <[email protected]> wrote:
Anyway I still think
the core of Leo is a gem that shouldn't be buried inside just Python. If
there were a libleo that handles parsing of leo files, serialization, and
core outline manipulation API then it could get integrated with editors for
other languages where Python is not the first class citizen. A back end
leo-qt API would be a bonus.
Thanks for the complement :-) Wouldn't it be great if there were a
way to make Python code available to C programmers, and vice versa,
merely by using some common-format library.
I am not aware of such a thing. Are you?
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 post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
