On Fri, 5 Aug 2011 12:45:28 +0300 "Ville M. Vainio" <[email protected]> wrote:
> Leo itself would not deal with "classes" apart from UI level. More complex node rendering is something I've wanted to try for a long time, using rules to add icons and change foreground / background color and perhaps have summary instead of full headline text displayed (but switch to full when editing of course). I.e. I'd rather see [auto-icon] views.py than @auto /mnt/usr1/home/tbrown/Desktop/Proj/GLRI/data/siteweb/siteweb/siteapp/views.py for some reason :-) I'd like to try reasonably open ended rules for the rendering, in terms of text content and uA values, and the colors / font / style / text changes they can map to. Basically equivalent to CSS for node styling. Not really sure how this would relate to a blessed class attribute, I guess I'm not sure what, beyond special rendering, you'd want to drive with the class attribute? Prior to this, the Leo way to designate a nodes type is with @directives. I assume you'd want an space separated list of classes a la CSS, so a node could have multiple classes. Cheers -Terry 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.
