On Fri, 3 Jun 2011 09:53:19 -0400 "Ville M. Vainio" <[email protected]> wrote:
> On Fri, Jun 3, 2011 at 9:45 AM, Terry Brown <[email protected]> wrote: > > > Picking a key for storing this info. in v.u and making the gui use it > > is fine, it seems like something the gui core should handle, but > > there's also the issue of task specific callback driven styling of tree > > node widgets. I think that will be useful, but I don't think it's > > incompatible with entries in v.u for coloring headlines. Also > > 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"). Just in case it helps Edward while he's doing the color thing, I have a vague recollection that the hook for the callback used by colorize_headlines is one line too early to manipulate some headline widget attributes (i.e. overridden by a later command), but I think it's trivial to move it. Cheers -Terry -- 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.
