Re: The design of Leo+Ipython+Jupyter+Lit-computing

On Sat, 10 Mar 2018 18:46:12 -0800 (PST) Thomas Passin wrote: > Do you happen to know if it's feasible to use QML widgets in Leo? I > don't know either Qt or QML, but much of the PyQt code I see in Leo > looks very painful, a steep learning curve to climb. I remember when

Re: The design of Leo+Ipython+Jupyter+Lit-computing

Do you happen to know if it's feasible to use QML widgets in Leo? I don't know either Qt or QML, but much of the PyQt code I see in Leo looks very painful, a steep learning curve to climb. I remember when I wrote my Matplotlib graphics plotting and calculator program, finding out how to do

Using Holoview in @Jupyter Nodes

I have been playing with Holoview, which may be a good system for graphing and plotting, as a replacement fro pyplot. It uses more declarative and less procedural progamming, which is usually a good thing. It already integrates with Jupyter Notebook, and so I decided to see if the

Re: Atom might be Leo's future

It seems to me that many python-based systems could be run in a Leo process, which would give access to their internal APIs. The challenge would be to get their input and output into Leo cells. For non-python systems, in some cases there could be a python wrapper that handles communication

Re: The design of Leo+Ipython+Jupyter+Lit-computing

On Sat, 10 Mar 2018 17:41:47 -0800 (PST) Thomas Passin wrote: > If I could step in here some months later, and move to a higher level > of conversation, I think that there are several levels of engagement > with Jupyter that we could contemplate. I have a long term goal of

Re: The design of Leo+Ipython+Jupyter+Lit-computing

If I could step in here some months later, and move to a higher level of conversation, I think that there are several levels of engagement with Jupyter that we could contemplate. For example, we could display a notebook, graphics output and all, in a separate pane. ViewRendered does that

Re: ENB: Simple design principles for style sheets

On Sat, 10 Mar 2018 17:06:24 -0800 (PST) Thomas Passin wrote: > One more reason I found it hard to adjust the colors is that so many > of the syntax colors have those JEdit names, like "literal2_color". > What the heck does that map to? If I could have made a change, >

Re: ENB: Simple design principles for style sheets

PyScripter displays a small code example that contains most of the code structures that get touched by the syntax colorer. If you click on one of them, a picklist scrolls to that element, and the color chooser gets populated with the corresponding color, including its symbolic constant name,

Re: ENB: Simple design principles for style sheets

On Saturday, March 10, 2018 at 1:18:38 PM UTC-5, Terry Brown wrote: > > On Sat, 10 Mar 2018 06:58:42 -0800 (PST) > Thomas Passin wrote: > > in 5.7, LeoSettings has (at least) four dark themes: "base dark", "windows ekr dark", "leo_dark theme 1", and "leo_dark theme 2". I

Re: Python 2?

Yes, although it seems to have been worse since Vitalige's cache related work. Python 2/3 pickle protocols aren't compatible by default. It's possible that there's some relatively new code that should be changed to use an older protocol, not sure about that. Bottom line I think pickle's a bad

Python 2?

This is the first time in years I have loaded python2 and tried to run Leo. Is this normal? Chris Leo Log Window Leo 5.8 devel, build 20180307231313, Wed Mar 7 23:13:13 PST 2018 Git repo info: branch = devel, commit = a31ff9cc5543 Python 2.7.14, PyQt version 5.10.0 linux2 isPython3: False

Re: ENB: Simple design principles for style sheets

On Sat, Mar 10, 2018 at 8:58 AM, Thomas Passin wrote: > I just went through a really painful experience when I adopted a dark > theme. > ​I agree with Terry, this is excellent feedback. Here are some ideas. *Color samples directly in Leo* Understanding colors is always

Re: ENB: Simple design principles for style sheets

On Sat, 10 Mar 2018 06:58:42 -0800 (PST) Thomas Passin wrote: > I just went through a really painful experience when I adopted a dark > theme. I think this is good feedback. Although I wonder if you're talking about one of the old themes or one of the new ones, for

Re: ENB: Simple design principles for style sheets

I just went through a really painful experience when I adopted a dark theme. The existing ones that are in leoSettings were unusable, because too many of the syntax colors were unreadable against the dark background. I've gotten it working more or less to my satisfaction (there's one color

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

2018-03-10 17:45 GMT+01:00 Terry Brown : > On Sat, 10 Mar 2018 17:11:17 +0100 > Csányi Pál wrote: > >> I have not the command `edit-pane-test-open` in Leo editor. Why not? > > Hmm, are you starting from a console and do you see any error messages >

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

On Sat, 10 Mar 2018 17:11:17 +0100 Csányi Pál wrote: > I have not the command `edit-pane-test-open` in Leo editor. Why not? Hmm, are you starting from a console and do you see any error messages there? Cheers -Terry > I have installed QtWebKit. > > 2018-03-10 16:28

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

I have not the command `edit-pane-test-open` in Leo editor. Why not? I have installed QtWebKit. 2018-03-10 16:28 GMT+01:00 Terry Brown : > On Fri, 9 Mar 2018 23:55:52 -0800 (PST) > Pal Csanyi wrote: > >> This is an image >> >> >> The

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

On Fri, 9 Mar 2018 23:55:52 -0800 (PST) Pal Csanyi wrote: > This is an image > > > The following does not work. Why not? > >  Try the command `edit-pane-test-open`, which should open a split edit/view pane.

Autocomplete

I happened upon Python auto-completion somewhere in the docs (nice feature!). Upon first trying it, I got an exception: autocompleter On Traceback (most recent call last): File "/home/username/bin/leo-editor/leo/external/codewise.py", line 563, in cursor return self.dbconn.cursor()

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

Themes menu: status report 2

Excellent progress yesterday. Significant work remains. *Yesterday's work* 1. These two @button nodes now work properly, seemingly in all respects (but see below). @button open-light-theme c.styleSheetManager.load_theme_file('EKRLight.leo') @button open-dark-theme

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

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