On Wed, Dec 4, 2013 at 8:43 AM, Kent Tenney <[email protected]> wrote:
> I seem to recall a couple suggestions for a layer between Leo's
> settings machinery and the UI.
This is the way, regardless of details. It's an example of "separation of
concerns", probably the most important design guideline there is. There is
*nothing* wrong with Leo's basic settings machinery: the problem is making
use of it.
> A menu item which took
> you to the correct node in the @settings tree, possibly putting
> documentation in the log window. Or a font size widget which
> knew just where in the @settings tree to change a number.
>
Or @button nodes. All these are feasible. Not sure which is best.
BTW, Terry's recent addition of @data qt-gui-user-style-sheet is a
*spectacular* improvement. It is *so* much clearer to specify diffs from
leoSettings.leo. Here is mine:
/* Headline edit widgets */
QTreeWidget QLineEdit {
background-color: pink;
selection-color: white;
selection-background-color: blue;
}
QLabel#minibufferLabel {
font-size: 14pt;
}
QLineEdit#lineEdit { /* minibuffer */
font-size: 14pt;
}
For the very first time I can see at a glance what my particular
preferences are.
Of course, this isn't a complete solution, but it's much better than before.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/groups/opt_out.
