On Fri, Apr 8, 2011 at 3:09 PM, Edward K. Ream <[email protected]> wrote:
> And another thing :-) I'd like to create a plugin controller for this
> plugin. This will allow more flexibility, for example for options.
Have a blast :). I wrote it knowing I only have a bit of time for
implementation, so I didn't bother making it "modular" or whatnot.
Just promise one thing - avoid subclasses :). I personally dislike
subclassing in Python, it makes the code more complex than it needs to
be.
> At present, the plugin uses print statements to report "Lets".
> Options to send to the log or a file would be useful.
I think we can just comment that stuff out when we don't need them
anymore. They are for debugging.
> In other words, it would be good to make extending this plugin as easy
> as possible. I have the feeling we are going to be doing that a
> bit :-)
Let's hope so :). I plan to add at least @cl nodes from ILeo, i.e. if
you have something like this
@= foo
---body---
@cl MyData
blah blah
blah
What it gets translated to is:
g.vs.foo = MyData("blah blah\nblah")
Also see "@cl definitions" from
http://mail.python.org/pipermail/python-list/2008-February/530134.html
(ah, that mail brings me back; valuespace is spiritual successor of
ILeo work, a more "mature" and conservative implementation of the
ideas, if you will)
Or
http://webpages.charter.net/edreamleo/IPythonBridge.html#cl-definitions
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
