Re: Terry: replace SubProject label with Summary items?

On Sun, Mar 11, 2018 at 9:01 PM, Terry Brown wrote: I'm not fussed one way or the other ​Neither am I. It's just a suggestion. They are your items. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To

Re: LaTex to PDF workflow using Leo

On Thursday, March 8, 2018 at 10:48:28 AM UTC-6, Arjan wrote: Reviving this old topic. I made a crude attempt, hard-coded etc., to just > rewrite the section definitions via regex search and replace... > > How would I add Undo to this? Any other obvious improvements to make? > Here is a version

Re: Terry: replace SubProject label with Summary items?

On Sun, 11 Mar 2018 15:54:35 -0700 (PDT) "Edward K. Ream" wrote: > Imo, you will likely find creating summary items, with "Summary" > label, quite useful. This will allow us to retire the SubProject > label. > > Edward I'm not fussed one way or the other - to me Sub

Re: Gitlab

On Tue, Mar 6, 2018 at 4:25 PM, Kent Tenney wrote: > I see references to gitlab, never knew it's story. > > Here is an interview with it's creator, it's quite compelling stuff > https://twit.tv/shows/floss-weekly/episodes/473 > > As advertised, it's dead simple to install

Re: Autocomplete

On Sat, Mar 10, 2018 at 9:06 AM, Arjan wrote: I happened upon Python auto-completion somewhere in the docs (nice > feature!). Upon first trying it, I got an exception: > ​This uncovered a can of worms ;-) Rev 6d95fe6 makes many changes to leo/external/codewise.py. How

Re: Atom might be Leo's future

On Sat, Mar 10, 2018 at 8:04 PM, Thomas Passin wrote: > 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

Re: Summary info items

On Sunday, March 11, 2018 at 3:54:10 PM UTC-5, Edward K. Ream wrote: We can regard labels as the top-level of the organization, summary/info > items as the second level, and individual labels as the bottom layer. > Summary items typically consist of bullet lists of other items: - Item 1 - Item

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

Re: Python 2?

On Sat, Mar 10, 2018 at 6:52 PM, Terry Brown wrote: Bottom line I think pickle's a bad format for anything except transient > serialization > ​Let's google "python alternative to pickle": First hit: Don't Pickle Your Data

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,

Re: Styling Plugins

On Sun, Mar 11, 2018 at 3:44 PM, Chris George wrote: GammaRay requires PyQt 5.10 to work. I can build it and use it to load Leo > and it works great. Very useful. > ​Thanks for this info. ​ > But PyQt 5.10 breaks my stylesheet. Qt Designer validates the stylesheet > just

Re: ENB: Simple design principles for style sheets

On Sun, Mar 11, 2018 at 4:05 PM, Chris George wrote: Would it be possible to program a button to "Reload Stylesheets", > close the current file, and then reopen it? I must do this a hundred > times a day manually. :-) > ​Why do you want to reload Leo if you reload

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

Terry: replace SubProject label with Summary items?

Imo, you will likely find creating summary items, with "Summary" label, quite useful. This will allow us to retire the SubProject label. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving

Re: Summary info items

On Sun, Mar 11, 2018 at 3:18 PM, Edward K. Ream wrote: > #796: Summary of installation items > , contains links to > all installation-related items. I have closed all these items so as not to > obscure the info items page

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: ENB: Simple design principles for style sheets

Hmmm, I was considering asking for how to do something similar. Would it be possible to program a button to "Reload Stylesheets", close the current file, and then reopen it? I must do this a hundred times a day manually. :-) Chris On Sun, Mar 11, 2018 at 11:02 AM, Edward K. Ream

Re: Summary info items

On Sunday, March 11, 2018 at 3:18:33 PM UTC-5, Edward K. Ream wrote: > #796: Summary of installation items , contains links to all installation-related items. The info items page

Re: Styling Plugins

A big caveat: GammaRay requires PyQt 5.10 to work. I can build it and use it to load Leo and it works great. Very useful. But PyQt 5.10 breaks my stylesheet. Qt Designer validates the stylesheet just fine. Drop back to PyQt 5.6.2 and the stylesheet renders correctly in Leo. All things

Re: Styling Plugins

Thanks for the motivation. I am now running GammaRay and Leo native (no Anaconda). I will have to rebuild a few things, but no big deal. Leo Log Window Leo 5.8 devel, build 20180307231313, Wed Mar 7 23:13:13 PST 2018 Git repo info: branch = devel, commit = 0a733e0506cd Python 3.6.4, PyQt version

Summary info items

#796: Summary of installation items , contains links to all installation-related items. I have closed all these items so as not to obscure the info items page

Re: ENB: Simple design principles for style sheets

On Sun, Mar 11, 2018 at 12:45 PM, Edward K. Ream wrote: > > @button load-ekr @key=F5 > > @language python > # Open ekr.leo in a separate process. > import os > os.system("e") > > On Windows, F5 will execute e.bat, which opens ekr.leo. The command runs > in the same console

Re: ENB: Simple design principles for style sheets

On Sun, Mar 11, 2018 at 8:56 AM, Thomas Passin wrote: I didn't have too much trouble finding color constants per se. > ​...​ > But colors look different depending on their surroundings, and I had to do > a lot of trial and error to hit on ones that worked *and* were distinct

Re: Styling Plugins

On Sun, Mar 11, 2018 at 9:04 AM, Chris George wrote: What is going to be the convention for styling plugins? > ​Good question.​ So far to accommodate the bookmarks plugin, heroic theming is required. > Will it be up to the theme developer to load, inspect and style every

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

On Sun, 11 Mar 2018 07:05:54 -0700 (PDT) Thomas Passin wrote: > I haven't worked on anything much in-browser since before html5 came > out. So I didn't know anything about "~=", for example. Even then I > tried to only work with the simpler constructs (both javascript and >

Re: Using Holoview in @Jupyter Nodes

On Sun, Mar 11, 2018 at 8:45 AM, Thomas Passin wrote: > I have only done this for a notebook located on my own computer. You have > to use "file:///" and I changed the backslashes (I'm on Windows) to forward > slashes: > > file:///C:/Users/tom/holoview_tests.ipynb >

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

I haven't worked on anything much in-browser since before html5 came out. So I didn't know anything about "~=", for example. Even then I tried to only work with the simpler constructs (both javascript and css), so I probably wouldn't have used that particular construct anyway. On Saturday,

Styling Plugins

What is going to be the convention for styling plugins? So far to accomodate the bookmarks plugin, heroic theming is required. Will it be up to the theme developer to load, inspect and style every plugin? It took a bit for me to figure out how to style the Tags Tab, for example. The good news

Re: ENB: Simple design principles for style sheets

I didn't have too much trouble finding color constants per se. I would do a web search for, say, "color #553399", and that would show me the color. There are also on-line color pickers. But colors look different depending on their surroundings, and I had to do a lot of trial and error to

Re: Using Holoview in @Jupyter Nodes

I have only done this for a notebook located on my own computer. You have to use "file:///" and I changed the backslashes (I'm on Windows) to forward slashes: file:///C:/Users/tom/holoview_tests.ipynb The right syntax for a file URL seems to confuse people. I think the RFCs aren't too

Re: ENB: Simple design principles for style sheets

On Sat, Mar 10, 2018 at 7:06 PM, 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? > ​These map directly to the constants

Re: ENB: Simple design principles for style sheets

On Sat, Mar 10, 2018 at 7:19 PM, Thomas Passin wrote: 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 >

Re: Using Holoview in @Jupyter Nodes

On Saturday, March 10, 2018 at 8:26:21 PM UTC-6, Thomas Passin wrote: > Run the code in Jupyter Notebook. Let it finish and display the graphic, then save the notebook... > ViewRendered will be able to show the graphic in the @jupyter node. Many thanks for this. I had completely forgotten that