On Mon, Dec 9, 2013 at 6:56 PM, gatesphere <[email protected]> wrote:
> The following is all the *real* functionality I need: > > commander: > c.all_positions() > c.all_unique_positions() > loading + saving (ignoring *all* external files, i.e., @file, @auto, etc.) > c.config -- *just* the getBool, getString, etc. methods, and scoped only > to the local file... could be implemented completely around > c.all_unique_positions() > > positions: > p.h, p.b, p.v, p.u > p.insertAsNthChild() > > vnodes: > v.h, v.b, v.u > v.insertAsNthChild() > > Leo itself would be a full-blown GUI option, but just as a file format, > .leo outlines with a minimal API would provide a *lot* of groundwork. > Perhaps I can hack something together that wouldn't depend on Leo's core... > Given this list, I would suggest using the leoBridge module as it is. If you rolled your own init sequence you would probably gain (lose) very little, and you would be setting yourself up for crashes due to uninited ivars in the commander and subcommanders. EKR -- 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/groups/opt_out.
