On Wednesday, May 21, 2014 7:20:44 PM UTC+8, Terry wrote: > > I wonder if it would be sense for Leo's select body code to use a hook > or something similar to find the body widget, so that plugins could > change the meaning of "the body widget" more easily. Will make a note. > > I don't know if it's related but I've had this idea for a while now. What if you can have multiple body editors for different data like ordinary text, rich text, image, etc. There is a global dictionary that maps node directives to body editors. Plugins can add new node directives and select which existing body editors to use by just updating the global dictionary. Or plugins can add new body editors. So if create a plugin that introduces a @pdf node directive and a corresponding pdf viewer, I can just update the global dictionary and leo will know that nodes with headlines starting with the aforementioned directive will use my plugin's pdf viewer. The body editor may even be an external application.
Eric -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
