Another small glitch (recurring icon problem)

Thank you very much to EKR for immediately fixing my previous issue (Internet Explorer kept popping up, trying to connect to sites that my firewall reported were unsafe). That has not happened again, and I'm very happy! However, I've had a stubborn new problem for a while now.

Re: Proposal: simplify style sheets for Leo 5.6, or maybe 5.5b1

Hope you don't mind me voting for copying one node, and then executing a 'Reload Styles' command, or something similar. Compliments to you both for tackling this issue. Regards Lewis On Wednesday, March 8, 2017 at 11:14:10 AM UTC+11, Terry Brown wrote: > > > [snip] Theme installation can be as

Re: Proposal: simplify style sheets for Leo 5.6, or maybe 5.5b1

On Tue, 7 Mar 2017 15:19:20 -0800 (PST) "Edward K. Ream" wrote: > Maybe we can make the css comments do the heavy lifting, as you > suggest.  In that case, maybe not much new really is required. But it > must be a lot easier to discover and use than at present. I'm not

Re: Proposal: simplify style sheets for Leo 5.6, or maybe 5.5b1

On Tuesday, March 7, 2017 at 4:44:44 PM UTC-6, Terry Brown wrote: > > On Tue, 7 Mar 2017 16:13:49 -0600 > "Edward K. Ream" wrote: > > > The present (accurate) comment is the following: > > > > In order for theme settings to take effect, you may need to disable > > >

Re: Proposal: simplify style sheets for Leo 5.6, or maybe 5.5b1

On Tue, 7 Mar 2017 16:13:49 -0600 "Edward K. Ream" wrote: > The present (accurate) comment is the following: > > In order for theme settings to take effect, you may need to disable > > existing `@color` and `@data qt-gui-plugin-style-sheet` nodes in > > myLeoSettings.leo.

Re: Proposal: simplify style sheets for Leo 5.6, or maybe 5.5b1

On Tue, Mar 7, 2017 at 3:04 PM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: > To be honest I don't remember the motivation for supporting parsing values > from comments in CSS. > ​I don't think it was ever a conscious thing. The present code just does it. ​ > The use of

Re: Proposal: simplify style sheets for Leo 5.6, or maybe 5.5b1

To be honest I don't remember the motivation for supporting parsing values from comments in CSS.  The use of regular @settings nodes seems more Leonine to me.   But that also seems to require iterative substitution.  When the system was working, it supported both. Although I disagree with your

Re: Proposal: simplify style sheets for Leo 5.6, or maybe 5.5b1

On Tuesday, March 7, 2017 at 2:02:37 PM UTC-6, Edward K. Ream wrote: This button will replace StyleSheetManager.expand_css_constants and helpers. > Alas not. expand_css_constants is needed to handle legacy style sheets. That's too bad, because it's way too easy to corrupt a style sheet by

Re: Proposal: simplify style sheets for Leo 5.6, or maybe 5.5b1

On Tuesday, March 7, 2017 at 2:20:02 PM UTC-6, Edward K. Ream wrote: The code that scans the lines above maintains a dict of name/value pairs. > A non-constant must already be in the dict. No more loops. > Or maybe the code will assume that a RHS that isn't in the dict is, in fact, a

Re: Proposal: simplify style sheets for Leo 5.6, or maybe 5.5b1

On Tue, Mar 7, 2017 at 12:59 PM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: > I would resist removing @setting expansion > from stylesheets. > ​On second thought, I agree with you. But I am convinced that we need, *right now*, a better

Re: Proposal: simplify style sheets for Leo 5.6, or maybe 5.5b1

p.s. if you like I can try taking a look at it and improving the flow / docs. / comments to make it easier to follow - I know the theme issue was originally assigned to me and I didn't get to it.  Just as long as we're not working in opposite directions on the same code - let me know. Cheers

Re: Proposal: simplify style sheets for Leo 5.6, or maybe 5.5b1

I would resist removing @setting expansion from stylesheets. It's a major pain maintaining CSS without such a mechanism. CSS3(?, maybe 2) has variables, but that doesn't help with Qt-CSS.If the @setting expansion is hard to understand, let's blame docs., comments, and code layout, not the

Proposal: simplify style sheets for Leo 5.6, or maybe 5.5b1

This is a revision of this comment to #350 . Today's escapades with themes convinces me that Leo's stylesheet machinery is on the verge of being impossible to

Re: HTML 5 Leo Viewer

Last time I used Atom this was one of my big complaints, though these days I feel like most editors have performance issues in one way or another. On Tuesday, March 7, 2017 at 11:46:09 AM UTC-5, Arjan wrote: > > Regarding Atom, it might be interesting to take a look at Visual Studio > Code as

Re: Well Kent, your vision for Leo is becoming clearer

On Monday, March 6, 2017 at 11:41:26 AM UTC-5, Kent Tenney wrote: > > I'm not sure if my periodic outbursts qualify as 'vision' but in terms > of where my characterization of Leo might differ from the norm, it > would be my seeing Leo as a hierarchal data store rather than an > editor, the D3

Re: HTML 5 Leo Viewer

Regarding Atom, it might be interesting to take a look at Visual Studio Code as well https://code.visualstudio.com. Very similar, also an Electron app, but much faster opening of large files, and more snappy in general (unless Atom improved a lot recently). Arjan -- You received this message

Re: #350: Themes are ready for serious testing

When I tried themes last night the dark themes didn't seem to be working, background color wise, even with color definitions. Also, I'd just include all settings needed by a theme in the theme node and not make users copy two things. I don't think the duplication is a problem. Cheers -Terry

Re: #350: Themes are ready for serious testing

On Tue, Mar 7, 2017 at 5:39 AM, Edward K. Ream wrote: > > On Mon, Mar 6, 2017 at 10:01 PM, 'Terry Brown' via leo-editor < > leo-editor@googlegroups.com> wrote: > >> >> Hi Jon. I'm using the "@solarized-" names, and they're working ok, I >> don't think that part of the theme

Re: #350: Themes are ready for serious testing

On Mon, Mar 6, 2017 at 10:01 PM, 'Terry Brown' via leo-editor < leo-editor@googlegroups.com> wrote: > > Hi Jon. I'm using the "@solarized-" names, and they're working ok, I > don't think that part of the theme machinery is damaged. But note that > those names aren't built into Leo, they have to