On Fri, Jun 3, 2011 at 5:02 PM, Terry Brown <[email protected]> wrote:
>> Callback driven mechanism is implemented already, colorize_headlines.py is an
>> example of that.
>
> True - I'm thinking of more extensive use of that approach, perhaps
> where a user can specify pairs of pattern/action rules in @settings
> which are applied looking for matches on v.u contents, v.h and v.b, and
> then manipulating fore/background color, font styling, icons, and maybe
> even the text shown in the tree node widget. I.e. the idea of showing
> the text the user cares about ("foo.py") and then switching to the
> actual text when you enter edit mode ("@file foo.py").
All of this (including changing the text displayed!) should be
already possible with the callback driven approach. I don't like the
idea of adding more "policy" to colorizing than just promising that a
function will be called, and the function can do whatever it wants.
--
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.
