Re: ENB: Simple design principles for style sheets

On Monday, March 5, 2018 at 9:14:00 PM UTC-6, Edward K. Ream wrote: > *Corollary 2: Avoid two-level @constants* > There is one benign exception to this rule. All themes will likely define @color constants in terms of @ constants for solarized or other colors. No confusion or maintenance

ENB: Simple design principles for style sheets

It's easy to create a stylesheet that quickly becomes overwhelming. This week, for the first time ever, I have created a style sheet this is easy to understand and will be easy to change in the future. And today, also for the first time, I see clearly the principles involved. Several Aha's and

Re: #768-new-tree branch ready for preliminary testing

On Mon, 5 Mar 2018 12:45:47 -0800 (PST) vitalije wrote: > Making vnodes able to emit > notifications to all interested parties about what exactly has > changed will greatly reduce amount of unnecessary redrawing and that > is where I expect greater speed boost to come.

Re: #768-new-tree branch ready for preliminary testing

Ok. I'll look at it on Thursday. On Monday, March 5, 2018 at 9:41:53 PM UTC+1, Edward K. Ream wrote: > > On Monday, March 5, 2018 at 1:25:10 PM UTC-6, vitalije wrote: >> >> New branch 768-new-tree >> , related to >> issue #768 is

Re: #768-new-tree branch ready for preliminary testing

> Probably minor, but I see todo.py icons aren't rendering, and > multi-node selection isn't enabled. > > Thanks for the report, I didn't use neither todo.py nor multi-node selection. I'll try to fix it. Comparing Outline -> Expand All on LeoPyRef.leo on 768-new-tree and > master I

Python console: equiv for Ctrl-B execute-script?

So happy to discover the python console! (courtesy of "show what Leo already has" thread). Does it have an equivalent of the Ctrl-B command, to send from body pane and/or outline to the console? Copy-paste doesn't work because of line-feeds. matt -- You received this message because you are

Re: #768-new-tree branch ready for preliminary testing

On Monday, March 5, 2018 at 1:25:10 PM UTC-6, vitalije wrote: > > New branch 768-new-tree > , related to > issue #768 is ready for testing. > All of the following must be fixed, at a minimum: - In the new code, moving a cloned node

Re: #768-new-tree branch ready for preliminary testing

On Mon, 5 Mar 2018 12:12:39 -0800 (PST) vitalije wrote: > Comparing to Leo's current implementation. After expanding large > outline, Leo becomes less responsive. With new code it is not the > case. Hmm, I gave it a quick try. Probably minor, but I see todo.py icons

Re: #768-new-tree branch ready for preliminary testing

Comparing to Leo's current implementation. After expanding large outline, Leo becomes less responsive. With new code it is not the case. On Monday, March 5, 2018 at 8:57:30 PM UTC+1, Terry Brown wrote: > > On Mon, 5 Mar 2018 11:25:10 -0800 (PST) > vitalije wrote: > > >

Re: #768-new-tree branch ready for preliminary testing

On Mon, 5 Mar 2018 11:25:10 -0800 (PST) vitalije wrote: > Browsing LeoPyRef.leo outline with more than 10.000 nodes is breeze. Was it a problem before? Not saying it wasn't ;-), just curious what you're seeing performance wise. Do you mean with all nodes expanded? I know

#768-new-tree branch ready for preliminary testing

New branch 768-new-tree , related to issue #768 is ready for testing. All but 2 unit tests pass. Those two that fail are not related to the new tree code (something about docutils and script controller). All commands that I can think

Re: #766: Creating a themes menu

​​ On Mon, Mar 5, 2018 at 12:46 PM, Terry Brown wrote: I think it's only moot if we decide we don't want to allow users to > adjust things via @settings, and that editing stylesheets is required > for tweaking themes. > ​Lot's of settings still remain. The ones that I

Re: #766: Creating a themes menu

On Mon, 5 Mar 2018 12:25:08 -0600 "Edward K. Ream" wrote: > ​This will always be a judgement call. However, this question is > *almost* moot because in the new scheme my first stop is *always* the > relevant css node in the @data qt-gui-plugin-style-sheet tree. This > ends

Re: #766: Creating a themes menu

​On Mon, Mar 5, 2018 at 10:42 AM, Terry Brown wrote: A reason to retain single use @ constants would be allowing users to > change things by editing a single setting, rather than having to grok a > Qt stylesheet. > ​This will always be a judgement call. However, this

Re: #766: Creating a themes menu

On Mon, 5 Mar 2018 10:42:10 -0600 Terry Brown wrote: > A reason to retain single use @ constants would be allowing users to > change things by editing a single setting, rather than having to grok > a Qt stylesheet. Although I think we can also legitimately ask if making

Re: #766: Creating a themes menu

On Mon, 5 Mar 2018 02:51:57 -0800 (PST) "Edward K. Ream" wrote: > 2. With a few exceptions, I eliminated settings used in only one > place. Now the value of the setting used directly in the css, in the > proper node. This value might still be an @ constant, but this >

Re: #766: Creating a themes menu

On Monday, March 5, 2018 at 4:51:57 AM UTC-6, Edward K. Ream wrote: This a progress report on #766 Create a Themes menu and simplify theme > settings . > And it was also an update on #764: Improve the screen shot on Leo's home page

#766: Creating a themes menu

This a progress report on #766 Create a Themes menu and simplify theme settings . This post discusses two topics: - How to create a Themes menu. - How to make developing themes easier for devs. I have just partially fixed #780: @tabwidth -2

Re: How to make Outlines which contains images and can display those images?

On Sun, Mar 4, 2018 at 4:16 AM, Pal Csanyi wrote: > I want to write in Leo editor Outline which will be contains images too beside text. > Moreover, I want to can see those images. ​​ This is already possible, in a number of ways. ​ - You can put images of various kinds in

Re: my 2 cents to embedding Leo into other editor or vice versa

On Sun, Mar 4, 2018 at 10:56 PM, Matt Wilkie wrote: ​> ​ My conceptual solution to this was/is "What If Topics Were Folders?" ​I always liked the MacOS scheme of allowing folders to be treated as files with attributes. But Linux and Windows don't do this, so Leo has to have

Re: Unable to push or pull from devel

On Sunday, March 4, 2018 at 4:21:36 PM UTC-6, Edward K. Ream wrote: > I'll back up recently changed files and do a clean clone. Done. It was straightforward. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this

Re: How did I came across Leo?

On Sun, Mar 4, 2018 at 9:18 PM, Matt Wilkie wrote: >> ​ ​ @root and Leo's tangle and untangle commands will remain "forever". ​>>​ They are, on purpose, no longer documented, [...] > ​ ​ I would hope they are documented somewhere though? Perhaps within the code if no place