Re: Progress re themes. Theme devs, pls read

> > How a new user would know about any of this is hard for me to see. At a > minimum, a menu item that offers to change the font size would be easy to > find and use. Changing the font is probably what many new users will want > to do soon after opening Leo. It's easy to think of ways this coul

Re: Progress re themes. Theme devs, pls read

On Saturday, December 26, 2020 at 9:10:39 AM UTC-5 gar wrote: > It's a matter of adding or changing a setting in *myLeoSettings.leo* vs >> changing a setting in a theme outline. Not much different. More of a >> difficulty is knowing what particular settings to change. >> > Great difference act

Re: Progress re themes. Theme devs, pls read

> > It's a matter of adding or changing a setting in *myLeoSettings.leo* vs > changing a setting in a theme outline. Not much different. More of a > difficulty is knowing what particular settings to change. > Great difference actually. When you setup a fresh computer - you need to copy not a sing

Re: Progress re themes. Theme devs, pls read

It's a matter of adding or changing a setting in *myLeoSettings.leo* vs changing a setting in a theme outline. Not much different. More of a difficulty is knowing what particular settings to change. In my case, I copied one of the dark themes and used that renamed copy to try to reduce the fo

Re: Progress re themes. Theme devs, pls read

On Sat, Dec 26, 2020 at 2:18 AM gar wrote: > But still, how can I reduce leo's font size with a theme applied w/o > modifying the theme outline itself? > You can't, because the setting is in the theme file. Yes, I know this isn't optimal. The question is, do we want to force everyone to change

Re: Progress re themes. Theme devs, pls read

But still, how can I reduce leo's font size with a theme applied w/o modifying the theme outline itself? Playing with `@string font-size`is still gives absolutely nothing. In my opinion the inability to change font size easily is the great miss of leo's styling. Cause default fonts are INCREDIBLY h

Re: Themes: What is the setting to change the gutter font size?

On Thu, Dec 24, 2020 at 8:33 AM tbp1...@gmail.com wrote: >> I suspect that your theme's stylesheet doesn't support gutter-font-size. >> My personal style sheet contained: >> >> QFrame#gutter { >> background: gray; >> } >> > > I did find that one, but didn't know what should be in there. I'm no

Re: Themes: What is the setting to change the gutter font size?

On Thursday, December 24, 2020 at 6:43:31 AM UTC-5 Edward K. Ream wrote: > On Wed, Dec 23, 2020 at 11:24 PM tbp1...@gmail.com > wrote: > > I haven't been able to find a setting for specifying the gutter font >> size. >> > > leoSettings.leo contains a "Gutter Fonts" node, with four settings,

Re: Themes: What is the setting to change the gutter font size?

On Wed, Dec 23, 2020 at 11:24 PM tbp1...@gmail.com wrote: I haven't been able to find a setting for specifying the gutter font size. > leoSettings.leo contains a "Gutter Fonts" node, with four settings, but you probably already know that. One of those settings is @string gutter-font-size = @sma

Re: Progress re themes. Theme devs, pls read

On Tue, Dec 22, 2020 at 11:21 AM tbp1...@gmail.com wrote: > I'm currently using > > @string font-family = Consolas, Droid Sans Mono, DejaVu Sans Mono > > I think that that Consolas comes with Windows and I like it better than > some of the alternatives. Apparently it can be installed on Linux in

Re: Progress re themes. Theme devs, pls read

I'm currently using @string font-family = Consolas, Droid Sans Mono, DejaVu Sans Mono I think that that Consolas comes with Windows and I like it better than some of the alternatives. Apparently it can be installed on Linux in some manner. I should probably move the DajaVu font ahead of the D

Re: Progress re themes. Theme devs, pls read

On Tuesday, December 22, 2020 at 5:46:37 AM UTC-6 Edward K. Ream wrote: 2. I have used the preferred names for settings in theme files. Settings > names have the form x-y-z rather than x_y_z. > Only in a few places. Style sheets refer to settings with underscores, and I'm not sure whether Leo's

Re: Progress re themes. Theme devs, pls read

On Tuesday, December 22, 2020 at 5:46:37 AM UTC-6 Edward K. Ream wrote: 2. All theme files now specify font sizes in points (pt) rather than pixels > (px). Using pixels to specify font sizes is brain dead. I am responsible > for this, and I fear theme devs followed my lead. > How did I ever liv

Re: Progress re themes. Theme devs, pls read

On Tue, Dec 22, 2020 at 5:46 AM Edward K. Ream wrote: *Functional changes to theme files* > > When I started this project I said that I would make no "real" changes to > theme files. This is mostly still true, with the following important > exceptions: > I should emphasize that I made *zero* cha

Progress re themes. Theme devs, pls read

Yesterday saw breakthroughs and simplifications regarding Leo's theme files, .leo files in the leo/themes folders. This post summarizes yesterday's work, all contained in the ekr-theme branch. See #1792 . *Aha re testing themes* Leo loads t

Re: Themes documentation

On Mon, Nov 9, 2020 at 3:27 PM Thomas Passin wrote: I think underscore vs dash does not matter. When Leo imports the settings, > both of them are removed. > That's correct. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscrib

Re: Themes documentation

On Mon, Nov 9, 2020 at 2:22 PM Rob wrote: > Having trouble loading different themes, so checking the online > documentation here as > well as looking at the main LeoSettings.leo and other theme files, I'm > confused. > > Quoting from the web sit

Re: Themes documentation

On Monday, November 9, 2020 at 3:22:04 PM UTC-5, Rob wrote: > > Having trouble loading different themes, so checking the online > documentation here as > well as looking at the main LeoSettings.leo and other theme files, I'm > confused. > > Quo

Re: Themes documentation

Ignore the third question as I had the setting in the wrong place. On Monday, November 9, 2020 at 3:22:04 PM UTC-5 Rob wrote: > Having trouble loading different themes, so checking the online > documentation here as > well as looking at the m

Re: Themes

On Sun, Mar 11, 2018 at 6:06 PM, k-hen wrote: ​[I] ...​ > was just curious whether you envisioned people editing the regular > constants/defaults, like 'red' and/or 'leoRed' or whether these were best > kept separate. > ​Devs should not change the color definitions in leoSettings.leo: leoSe

Re: Themes

Edit: I guess what I'm saying here is that I prefer a 3-step approach, 1st the definition of the full color-palette, 2nd the assignment of the color-palette to the logical structural & syntax elements, 3rd the assignment of those logical elements to the physical components in the stylesheet, i.

Re: Themes

On Sun, Mar 11, 2018 at 5:47 PM, k-hen wrote: > > Just wanted to say thanks very much for this. It happens I was looking at > creating my own theme as a way of learning more about Leo and was really > struggling with the stylesheets myself. FWIW, the way I was going about > this was first defini

Re: Themes

Hi Guys, Just wanted to say thanks very much for this. It happens I was looking at creating my own theme as a way of learning more about Leo and was really struggling with the stylesheets myself. FWIW, the way I was going about this was first defining my full color palette in a section within

Re: Themes menu: status report 2

On Saturday, March 10, 2018 at 5:45:19 AM UTC-6, Edward K. Ream wrote: > I'll experiment with support for @data additional-style-sheet. > The body would be a style sheet that...would be tacked on to whatever stylesheet is *already* in effect. Hmm. Qt stylesheets do not cascade properly, and may

Re: Themes

On Sat, Mar 10, 2018 at 4:46 AM, Edward K. Ream wrote: > is there a different mechanism >> ​ [to generalize the] ​ >> path relative to leo/themes/? >> > ​This is tricky. We probably need a new setting for ssm.set_indicator_paths. Something like @string theme_base_directory, which would *itself

Re: Themes

On Fri, Mar 9, 2018 at 11:53 AM, Chris George wrote: > The second image is direct.png. It shows the total loss of triangles in > the tree. Here is the css. > > TreeView::branch:closed:has-children{ > > image: url(:dark/branch_closed.svg); > > } > The css passes the checks, the images simply

Re: Themes

A recent commit fixed the box problem. But I am still struggling with how to source images other than "open" and "close". It looks great with the correct boxes. Chris On Friday, March 9, 2018 at 9:53:31 AM UTC-8, Chris George wrote: > > > > > > > Where do I get to choose the boxes? >>> >> >> ​T

Re: Themes menu: status report

On Friday, March 9, 2018 at 5:33:48 AM UTC-6, Edward K. Ream wrote: *Changing settings* > > This is unexpectedly tricky. After computing the local settings, we want > to use *all and only* those settings when computing the stylesheets. How > to do this? > Oh joy. It appears that we can just

Re: Themes

On Thu, Mar 8, 2018 at 11:18 AM, Chris George wrote: > Where do I get to choose the boxes? > ​There are two settings: For the Leo Dark setting they are: @string tree-image-closed = nodes-dark/triangles/closed.png @string tree-image-open = nodes-dark/triangles/open.png I think these paths are r

Re: Themes

Where do I get to choose the boxes? SInce this morning (Rev 5e3976b) I get the white box images in the tree with both Breeze Dark Theme - KDE Plasma.leo with myLeoSettings.leo disabled and with settings enabled and the theme in myLeoSettings.leo. I deleted both sets of white boxes in leo/Icons

Re: Themes

On Thursday, March 8, 2018 at 4:49:42 AM UTC-6, Edward K. Ream wrote: > > > I see by your rev 0924e4f that you have joined the dev team. Thanks! > Rev 5e3976b adds the @color log_note_color setting. Be sure to pull this before making any more changes. I'm hoping this is the last "jiggle" in th

Re: Themes

On Wednesday, March 7, 2018 at 5:08:24 PM UTC-6, Edward K. Ream wrote: Instead of sending an attachment, please push your work. > I see by your rev 0924e4f that you have joined the dev team. Thanks! Edward -- You received this message because you are subscribed to the Google Groups "leo-edit

Re: Themes

On Wed, Mar 7, 2018 at 4:06 PM, Chris George wrote: > Changed by CG > > - Finished button styling. > - Replaced all hacks by moving "Widgets: general" node to top of > stylesheet and styling appropriate widgets. > - Added hover effect to menus to match buttons and tabs. > ​Instead of sending an

Re: Themes

Changed by CG - Finished button styling. - Replaced all hacks by moving "Widgets: general" node to top of stylesheet and styling appropriate widgets. - Added hover effect to menus to match buttons and tabs. Still researching how to fix the glitchy "contextmenu". Chris -- You received this me

Re: Themes

Mainly I thought it might be handy to have a reference available to show the relationships in the hierarchy in order for themers to make sure they get the inheritance right. For example the relationships between LeoQtx and Qtx aren't clear to me at all. Chris On Wednesday, March 7, 20

Re: Themes

On Wed, Mar 7, 2018 at 11:48 AM, Chris George wrote: How hard would it be to generate a tree showing Qt widget inheritance from > Leo's source? > ​Not sure what you mean. w.parent() is the containing widget. w.__class__ is the widget's class, which can be inspected with Python's inspect module

Re: Themes

How hard would it be to generate a tree showing Qt widget inheritance from Leo's source? Chris -- 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 leo-editor+unsub

Re: Themes

On Wed, Mar 7, 2018 at 10:08 AM, Chris George wrote: It looks like inheritance and position in the css tree matters. > ​Thanks for this detailed report. Imo, the behavior you report is a serious bug in the Qt stylesheet mechanism. Adding css for QWidget, no matter where added, should not affec

Re: Themes

It looks like inheritance and position in the css tree matters. eg. Look at the buttons in the Breeze Dark theme. They are surrounded by a lighter border. When I went to style them, no matter what I did in the "Buttons" node, the lighter border persisted. So I got to thinking. Many widgets inhe

Re: Themes

> > Thank-you for the print-style-sheet command. That is going to save s >> much time. >> > > I copy the output into a Leo node so I can see it more clearly. Be sure > to search for "@". That will tell you if there are unexpanded @ > constants. These can do real mischief. > > I will pol

Re: Themes

> > As of rev 9f30f16, Breeze Dark Theme - KDE Plasma.leo seems to work fine > with the newly updated leoSettings.leo. > > - Added solarized-black/white to leoSettings. > - Completed the transition from @solarize[d]-base to dark-base. > > Recent revs also added definitions of "logical" colors so

Re: Themes

Leo Log Window Leo 5.8 devel, build 20180306071523, Tue Mar 6 07:15:23 CST 2018 Git repo info: branch = devel, commit = 3d0a5d349ef9 Python 3.6.4, PyQt version 5.6.2 linux isPython3: True On Tuesday, March 6, 2018 at 11:33:48 PM UTC-8, Edward K. Ream wrote: > > > > On Tue, Mar 6, 2018 at 6

Re: Themes

On Tuesday, March 6, 2018 at 6:03:39 PM UTC-6, Chris George wrote: Thank-you for the print-style-sheet command. That is going to save s > much time. > I copy the output into a Leo node so I can see it more clearly. Be sure to search for "@". That will tell you if there are unexpanded @ co

Re: Themes

On Wednesday, March 7, 2018 at 1:38:01 AM UTC-6, Edward K. Ream wrote: > ​Rev e28a220 adds it to leo/themes with *very important* modifications... As of rev 9f30f16, Breeze Dark Theme - KDE Plasma.leo seems to work fine with the newly updated leoSettings.leo. - Added solarized-black/white to le

Re: Themes

On Tue, Mar 6, 2018 at 9:45 PM, Chris George wrote: > Attached is a solid first draft. > ​Thanks for this. Rev e28a220 adds it to leo/themes with *very important* modifications: 1. Put the theme in a @settings node, so it becomes active when loaded. 2. Changed @solarized-base to @dark-base eve

Re: Themes

On Tue, Mar 6, 2018 at 6:03 PM, Chris George wrote: > I have ferreted out the problem. > > Under the @data qt-gui-plugin-style-sheet node in the "Tree" node, I had > to change the first "QtreeView" to "LeoQTreeWidget#treeWidget" to get the > font size and colour to work for me. > ​That should no

Re: Themes

Attached is a solid first draft. No matter what I do, I cannot change anything about the log pane text. I will work on sorting that out, but it seems to me that this was a showstopper last time I took a run at theming. What would be really, really helpful is to have a list of all of the things

Re: Themes

I have ferreted out the problem. Under the @data qt-gui-plugin-style-sheet node in the "Tree" node, I had to change the first "QtreeView" to "LeoQTreeWidget#treeWidget" to get the font size and colour to work for me. Similar to changing QTextEdit to QTextEdit#richTextEdit to get both font size

Re: Themes

On Tue, Mar 6, 2018 at 4:21 PM, Chris George wrote: > I loaded the new @theme. > > I cannot change the font size for the resting tree by choosing a different > size in the Fonts node. I cannot change the font colour of the resting tree > or the body using their parts of the css. > ​ > ​I have be

Re: Themes

I loaded the new @theme. I cannot change the font size for the resting tree by choosing a different size in the Fonts node. I cannot change the font colour of the resting tree or the body using their parts of the css. I can change the font size for the resting tree using the QWidget found in "

Re: Themes

On Tue, Mar 6, 2018 at 3:13 PM, Chris George wrote: ​> ​ If I change the tab bar section (see the following example), my tree does not style correctly at all (see screenshots of before and after). This usually indicates a syntax error in the css. Be wary of @constants inside comments. Change @w

Re: Themes

On Tue, Mar 6, 2018 at 12:45 PM, Chris George wrote: > I am working on a theme for Leo to match the "Breeze Dark" desktop theme in KDE Plasma. Glad to hear it. > I started using Edwards newly simplified layout and discovered a typo. That ​ ​ may have been ​ ​ fixed awhile ago. Your report has

Re: Themes

Oh, I found it expedient to simply copy the "Color definitions (Do not change)" node to myLeoSettings.leo and then change the colours as the easiest way to get what I wanted. It makes it easy to change things globally. It took me a bit to figure out where the solarized definitions were coming f

Re: themes

On Saturday, June 20, 2015 at 4:39:52 PM UTC-5, Terry Brown wrote: > > ...if themes are to be implemented > in part by a stylesheet appended to a core universal stylesheet, I > think there should be three: core, theme, and user, with user being > blank and entirely for personal use of the user,