On Wed, 16 Apr 2008 05:29:06 -0700 (PDT) bobjack <[EMAIL PROTECTED]> wrote:
> (One thing that puzzles me is the difference between 'Code Archetypes' > and 'Node Types'. Are they just different names for the same thing?) > > I would like to define my own Node Types, and also I would like to set > colors for my own and predefined Node Types. Perhaps this could be > done through @settings? Perhaps as well as colors, a Node Type could > have an optional user-icon associated with it (to show in the > headstring not the cleo icon position?) Is it possible to set fonts > for individual headlines? If it is, then perhaps each Node Type could > have a font attribute also? The Code Archetypes and Node Types are an ancient part of cleo from before I started working on it, so I can't explain their derivation. But I do think it would make sense to generalize the way cleo automatically colors things, and make it user configurable. I realized this when Edward was asking about a setting to turn off the @file coloring. So yes, I'll try and switch to user configurable coloring, and perhaps the icon thing as well. Not sure about the fonts. > It would be nice if cleo's features could be accessed via scripts and > minibuffer commands. Not an area of Leo I've looked at, but I'll see what the deal is, I think there's some mechanism for that. > I think it would be good if there was a general purpose way of setting > cleo attributes on a headline independently from Node Types. > > Temporary Attributes. I would like a way of setting cleo attributes > and icons (including user icons) on a temporary basis. ie. do not > save them when the file is saved. Perhaps there could be a 'temp' > attribute of a Node Type, just like color, font, etc. That's doable, I think it would be particularly easy for icons, a plugin (maybe cleo :-) could use the save callbacks to strip all icons tagged as temporary. Color and font not quite so easy because they're not dicts so you'd have to find somewhere special to put the temp tag. > For instance, I would like to be able to write a search script that > would highlight found nodes by setting a particular Node Type, and I > don't want these saved with the file. > > >But I'm wondering if there are broader issues here, and if a general > >rather than cleo specific solution might be useful. > > I think there should be more generalization, but this should be a > matter of cleo making its solutions available for general use by other > scripts and plugins rather than asking the core to provide these > features. It seems natural that cleo should be the central provider > for these tree related matters. Perhaps, I still think foreground / background color at least should be in the core, but some of this node display related stuff is certainly what cleo's done historically. I'll definitely look at these points soon. 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 -~----------~----~----~----~------~----~------~--~---
