On Tue, Oct 25, 2011 at 10:07 AM, Edward K. Ream <[email protected]> wrote:
> On Tue, Oct 25, 2011 at 9:32 AM, Kent Tenney <[email protected]> wrote:
>
>> This thread has been over my head
>
> Well, parts of it are over my head as well, as Terry surely must have
> guessed by now :-)
>
>> However, I just tried Terry's script which cycled colors and realized that
>> if it was easy to specify different sets of colors it could add greatly to
>> Leo, at many levels.
>
> It's better than that. Stylesheets are about the entire range of look
> and feel, not just colors.
>
>> I would want a dead simple API
>
> We have a dead simple API::
>
> @data qt-gui-plugin-style-sheet
By dead simple I mean named sheets.
@data qt-gui-plugin-style-sheet solarize
or maybe the first line in the @data body is
name = solarize
So all I need to know is "solarize".
>
> True, in the past I've had reservations about using qt stylesheets
> directly, but for *this* discussion that's all we have, and there is
> no reason not to use this powerful tool.
>
>> All I need is something like: <alt-x> color-scheme solarize
>
> An interesting idea. It would be a useful command, and fairly easy to do.
>
>> Extra points if parameters are possible, shifting brightness and hue
>> <alt-x> color-scheme tropical.bright+2
>
> It is always easy to add parameters to commands: the commands simply
> call c.config.getX('command-param-x').
>
> Let me emphasize what I said in the other thread. Leo's commands and
> settings create an excellent (simple, flexible, general) framework for
> thinking about *any* set of capabilities that one might want to have
> for Leo.
You might be interested in this Tim O'Reilly talk, about the
importance of "platforms" in cognitive evolution. Leo matches
up well with Tim's description of platform characteristics.
http://max.couchone.com/cfapodcast/timoreilly/audio.mp3
>
> For example, on a recent walk I made the following notes::
>
> Think commands.
> Think tasks.
> Think design.
> Think tests.
> Think refactoring.
> Think kaizen.
> Think *permanent* views.
>
> It this too general? Not at all! Here are some commands that came to mind::
>
> move-to-bugs (moves node to the projects/bugs node)
> move-to-features (moves node to the projects/features node)
>
> clone-to-work (clones node and moves it to @work node)
> open-script-node (finds @button/@command node)
> open-command-def (finds node that defines x command)
> add-to-work (finds a node, adds it to @work node)
>
> refactor-rename-ivar
> refactor-rename-class
> refactor-rename-method
> refactor-convert-to-pep8
>
> etc. You get the idea :-)
>
> Edward
>
> --
> 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.
>
>
--
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.
