Re: ENB: studying code for credit

On Sunday, September 22, 2024 at 8:38:26 AM UTC-5 Edward K. Ream wrote: *Summary* Python's *-X frozen_modules* command-line argument bypasses all frozen modules, allowing me to step through all code. Converting projects in sitecustomize to personal repos allows me to get credit for my st

Re: ENB: studying code for credit

On Sun, Sep 22, 2024 at 9:42 AM Thomas Passin wrote: > Do you mean the sitecustomize folder on your computer? Yes. > why does this scheme make any difference so far as GitHub is concerned? I push any changes to my own (non-cloned, non-forked) repo over which I have full control. The official *

ENB: studying code for credit

This Engineering Notebook post tells how I plan to study projects like pylint and receive GitHub recognition for intermediate commits. *Aha! unfreeze modules!* Python's *-X frozen_modules* command-line argument bypasses all frozen modules, allowing me to step through all code. This argument ma

Re: Embedding An External Program In Leo - Proof Of Principle

On Sun, Sep 8, 2024 at 8:19 AM Thomas Passin wrote: > I have been able to embed an external (non-Leo, non-Python) application in > a Leo window. Thanks for this. I'll say more about this project later. Edward -- You received this message because you are subscribed to the Google Groups "leo-

Re: 🚀 LeoJS 1.0.6 & Website: Ready for Launch! 🌐

On Thu, Sep 19, 2024 at 3:03 AM 'rengel' via leo-editor < leo-editor@googlegroups.com> wrote: > On my machine this works: From the menu on the home page ( > https://boltex.github.io/leojs/) select: > > *Advanced Topics -> Leo Scripting Guide* > At the top! Thanks! Edward -- You received this m

Re: Thomas, let's complete the new layout code

On Wed, Sep 18, 2024 at 8:14 AM Thomas Passin wrote: > Yes, let's zoom to make sure we're thinking of the same things and how to > incorporate them into the rest of Leo. Let's email separately about this. > Good. Edward -- You received this message because you are subscribed to the Google Gro

Thomas, let's complete the new layout code

The last unfinished piece of business for Leo 6.8.2 is fully integrating the new layout code into Leo's core. We could start by adding an official hidden Qt archive widget. And we must get the help commands working again. Thomas, what would you suggest? Would you like to propose a PR? I would b

Re: LeoJS vs. VSCode

On Wed, Sep 18, 2024 at 4:56 AM 'rengel' via leo-editor < leo-editor@googlegroups.com> wrote: > To put it succinctly: > > As far as programming is concerned, LeoJS is a general-purpose IDE within > another general-purpose IDE (VSCode). > That seems like an accurate description to me. Edward --

Re: 🚀 LeoJS 1.0.6 & Website: Ready for Launch! 🌐

On Tue, Sep 17, 2024 at 9:07 PM Félix wrote: I'd Like to also mention to the readers of this thread, that the new *documentation > website * has its example scripts > previously written in Python now meticulously translated into TypeScript. I don't see how to ac

Re: I just tried notebookLM! 🤯

On Tuesday, September 17, 2024 at 7:13:57 AM UTC-5 Edward K. Ream wrote: >> On Mon, Sep 16, 2024 at 9:52 PM Félix wrote: >> Google just released a new 'thing' called notebook LM... > > Here's the result: https://drive.google.com/file/d/15VLtEM2GPS52-Ja4W2Yfr4-2I

Re: Abridged summary of leo-editor@googlegroups.com - 24 updates in 2 topics

On Mon, Sep 16, 2024 at 3:16 PM Paul S. Wilson wrote: > Congratulations, Félix! > > And thank you! > > Besides extending Leo into the vastly wider world of millions of VSCoders; > painstakingly translating Leo into universal and virtually immortal > Javascript/Typescript (thus extending Leo's sc

Re: Need help with opening a Leo file

On Tue, Sep 17, 2024 at 6:59 AM 'rengel' via leo-editor < leo-editor@googlegroups.com> wrote: Confirmed! When using "@section-delims [[[ ]]]" the error disappears. > Thank you! > > Is there a way and/or place to define this language-specific? > Not yet. But an Erlang-specific special case in *ic.

Re: I just tried notebookLM! 🤯

On Mon, Sep 16, 2024 at 9:52 PM Félix wrote: Google just released a new 'thing' called notebook LM, I just tried it two > minutes ago. It's free and accessible like google-drive or google-docs. > > You give it some material on a subject: files, PDFs, text, URLs, etc. and > it helps you do documen

Re: Need help with opening a Leo file

On Mon, Sep 16, 2024 at 3:09 PM Jacob Peck wrote: Interesting. I’ve been using <> for 12 years now and have never > previously stumbled onto that limitation. I don’t see it documented, but > at the same time I’ve never been good at searching Leo’s docs. > Many languages have << and >> operator

Re: Need help with opening a Leo file

On Tue, Sep 17, 2024 at 1:35 AM 'rengel' via leo-editor < leo-editor@googlegroups.com> wrote: Reproducing the error is a little tricky, > so this is to clarify how the error can be reproduced. > > - My test file is at location "D:/Downloads/erlang_test.erl". > - From there I import this file with

Re: Need help with opening a Leo file

On Mon, Sep 16, 2024 at 12:34 PM 'rengel' via leo-editor < leo-editor@googlegroups.com> wrote: > So basically that means you can't reliably use Leo's @file nodes for > Elixir adn Erlang source code? > Yes, that's what I'm saying. @edit will usually be better than @asis. Edward -- You received

Re: Need help with opening a Leo file

On Mon, Sep 16, 2024 at 9:05 AM Thomas Passin wrote: Looking at the test erlang file, I see that the "<< ... >> " syntax seems > to be an essential part. I had at first thought they were symbols that had > not been escaped by the XML ingesting code, but I see that was wrong. I > wonder if the se

Re: Need help with opening a Leo file

On Mon, Sep 16, 2024 at 8:56 AM Thomas Passin wrote: > An @edit file is always considered to be a text file, isn't it? So we're > thinking that an @edit node was created when it should have been something > else, right? > It looks that way, but I can't be sure. Let's see if Viktor has any other

Re: Need help with opening a Leo file

On Monday, September 16, 2024 at 7:38:18 AM UTC-5 Edward K. Ream wrote: On Mon, Sep 16, 2024 at 5:41 AM 'rengel' via leo-editor wrote: BTW: Is there a safe way to include "<<...>>" structs in source code in the body pane? How can Leo be prevented from looki

Re: Need help with opening a Leo file

On Mon, Sep 16, 2024 at 7:40 AM 'rengel' via leo-editor < leo-editor@googlegroups.com> wrote: Given is the Erlang file 'erlang_test.erl' that I import in a fresh Leo > outline (first image, erlang_test1.png). > Then I change the '@auto' directive to '@file' and try to save the > outline. > That re

Re: Need help with opening a Leo file

On Mon, Sep 16, 2024 at 7:42 AM 'rengel' via leo-editor < leo-editor@googlegroups.com> wrote: > This is the Erlang test file: > Thanks. The .erl file contains several lines that look like section references. Leo should report problems when writing the enclosing .leo file. Neither of us seems sur

Re: Need help with opening a Leo file

On Mon, Sep 16, 2024 at 5:41 AM 'rengel' via leo-editor < leo-editor@googlegroups.com> wrote: BTW: Is there a safe way to include "<<...>>" structs in source code in the > body pane? How can Leo be prevented from looking for such structs in the > body pane? > <<...>> *always *means a section refe

Re: Need help with opening a Leo file

On Mon, Sep 16, 2024 at 5:38 AM 'rengel' via leo-editor < leo-editor@googlegroups.com> wrote: > Thanks for your suggestion! > > But this is the only node. In its body text it contains hundreds of othe > nodes wrapped in an xml file. So deleting that node would delete all the > contents of this Leo

Re: Need help with opening a Leo file

On Mon, Sep 16, 2024 at 12:56 AM 'rengel' via leo-editor < leo-editor@googlegroups.com> wrote: > I have a leo file stored in 'D:/dev/.leo/Dev.leo'. > > When I open this file with Leo (on Windows 10), I get > > '@edit D:/dev/.leo/Dev.leo' > Strange things happen. I would just delete the node. Edw

Returning to Leo

Tummy time is thankfully over. I'll be easing back to work on Leo soon. Thanks for the interesting discussions while I have been down. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emai

Re: A third vitrectomy on Friday, September 6. Leo 6.8.2 delayed?

On Friday, August 30, 2024 at 7:00:53 AM UTC-5 Edward K. Ream wrote: This vitrectomy will use a scleral buckle and will be done under general anesthesia. There will be yet another week of tummy time afterwards. The vitrectomy went well. I expect to be able to get off the floor on Thursday

Re: An Outline To Demonstrate The Script-based Layout System

On Wed, Sep 4, 2024 at 5:20 PM Thomas Passin wrote: > Here is an updated copy of the entire layout_script_cpmmands.leo outline. > It also has an added layout with VR. All layouts for VR now include the > version of the VR code that will work with both the new and the older > versions of Leo. I

Re: A third vitrectomy on Friday, September 6. Leo 6.8.2 delayed?

On Friday, August 30, 2024 at 7:00:53 AM UTC-5 Edward K. Ream wrote: This vitrectomy will use a scleral buckle and will be done under general anesthesia. There will be yet another week of tummy time afterwards. The 6.8.2 release will likely be delayed while we hash out the details of switching

Re: Engineering Notebook: A Script-based Approach To Leo's Layouts

On Sun, Sep 1, 2024 at 9:36 PM Thomas Passin wrote: > This Engineering Notebook discusses a script-based approach to changing > and restoring the arrangement of Leo's panes, including the body editor, > the nav pane, the Viewrendered and Viewrendered3 plugins' panes, and > potentially others. ...

Re: About layouts and their settings.

On Sat, Aug 31, 2024 at 8:36 AM Thomas Passin wrote: One thing to resolve is where these kinds of layout scripts should be > stored and managed. It's one thing for me to have a private collection of > scripts and commands, but another to make them usable and available to > other Leo users, and ye

Re: About layouts and their settings.

On Sat, Aug 31, 2024 at 6:56 AM Thomas Passin wrote: Short answer: yes, with a few quirks in the case of added widgets (ones > that are not VR/VR3 and RPCalc). These widgets may become lost but still > retain their resources and their event hooks. > Excellent. We can deal with event handlers la

Re: About layouts and their settings.

On Fri, Aug 30, 2024 at 11:27 PM Thomas Passin wrote: > Hmm, I've tinkered it down to this and it's just been working on my system: Thanks for your experiments. Bear in mind that this code doesn't add or change the layout setting. This > command would be executed after the layout setting had b

Re: About layouts and their settings.

On Friday, August 30, 2024 at 5:39:16 PM UTC-5 tbp1...@gmail.com wrote: I just discovered this. The shadow opened exactly on top of the other, so I didn't realize it was there. That should be fixable, I think. And if not, the previous version of the script works. The previous version does

Re: About layouts and their settings.

On Fri, Aug 30, 2024 at 2:16 PM Thomas Passin wrote: Reopening an outline even if it's the only one open turns out to be even > simpler" > > filename = c.fileName() > g.app.closeLeoWindow(c.frame, new_c=None, finish_quit = False) > g.openWithFileName(filename, old_c=c) > This code creates a shad

About layouts and their settings.

This Engineering Notebook post discusses issues relating to Leo's new layouts. As of today, the "devel" branch contains these PRs: - PR #4055 : Add "@string qt-layout-name" setting. - PR #4058

A third vitrectomy on Friday, September 6. Leo 6.8.2 delayed?

This vitrectomy will use a scleral buckle and will be done under general anesthesia. There will be yet another week of tummy time afterwards. The 6.8.2 release will likely be delayed while we hash out the details of switching between layouts. More on this topic later. Releasing 6.8.2 isn't urge

Re: PR #4033 (in devel) creates layouts

On Thu, Aug 29, 2024 at 6:29 AM Thomas Passin wrote: > The layout ASCII art (nice job on that, BTW) shows a VR panel so I > expected a VR panel to show up. Maybe asterisk the "VR" label to indicate > it's conditional. > I see the confusion. The layout diagrams show where the VR/VR3 will appear *

Re: PR #4033 (in devel) creates layouts

On Wed, Aug 28, 2024 at 12:05 PM Thomas Passin wrote: > "Layouts add VR or VR3 only if the user enables the corresponding plugin" > > I always enable them but I don't always want them on display when I open a > given outline. > I'm not sure what your complaint is. The VR/VR3 pane's won't become

Re: PR #4033 (in devel) creates layouts

On Wed, Aug 28, 2024 at 11:07 AM Thomas Passin wrote: I have some objections, but for right now I object to VR being forcibly > included in all these layouts. Layouts add VR or VR3 only if the user enables the corresponding plugin. Many times I don't want VR/VR3 at all on startup. And if I do

PR #4033 (in devel) creates layouts

PR #4033 creates six official layouts. Two layouts codify previous de-facto layouts. Four others are the result of recent requests. See the PR for a thorough description of all its features. The PR does not include everything that Thomas and

Re: PR #4047 merged into devel: body editors are gone

On Wed, Aug 28, 2024 at 7:03 AM Thomas Passin wrote: > Best wishes this time around from all of us. > Thanks. Edward -- 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 emai

PR #4047 merged into devel: body editors are gone

PR #4047 has been merged into devel. It has also been merged (with difficulty!) into PR #4033 , which adds new layouts. I have taken this step now because it seems likely I shall undergo yet

Re: Broken Add/Delete Body Editor

On Tue, Aug 27, 2024 at 5:55 PM Phil wrote: > As I am "at least one person" using (or had been using) this, here's more > about my usage of Add-Editor: > ... > I would not be upset if this feature went away. My alternative is to open > the example code in different text editor and just arrange

Re: Try A Tabbed Body Pane

On Mon, Aug 26, 2024 at 10:53 AM Thomas Passin wrote: > In the recent discussion about problems with the Add-Editor command and > its added editor, I floated the idea of making the body pane be a tabbed > widget instead of the current stacked widget. I found it was simple to > make this change i

Re: Leo 6.8.2 coming in a few weeks

On Sunday, August 25, 2024 at 12:34:03 PM UTC-5 Edward K. Ream wrote: Issue #4046 <https://github.com/leo-editor/leo-editor/issues/4046> must be addressed immediately. The add-editor command can easily create data loss. As a first step, rev 9683128 <https://github.com/leo-editor/l

Re: Broken Add/Delete Body Editor

On Sun, Aug 25, 2024 at 9:48 AM Thomas Passin wrote: > " Leo has been solid all these years because my supreme design goal has > been to minimize unwanted dependencies between unrelated modules." > > I don't think the body editor construction quite meets this goal. > The DynamicWindow class crea

Re: Broken Add/Delete Body Editor

On Sun, Aug 25, 2024 at 7:49 AM Thomas Passin wrote: We should wait a little to see if anyone responds, shouldn't we? We know at > least one person was interested enough to try using Add-Editor. Maybe > there are others who haven't been updating Leo all along. > I agree. There's no rush. The wo

Re: Broken Add/Delete Body Editor

On Sun, Aug 25, 2024 at 6:21 AM Thomas Passin wrote: > It looks like the colorizer might be getting the wrong position - the > position of the original editor rather than the newly focused position. > Might there be a p.copy() involved here? Anything is possible. I don't understand the code ve

Re: Broken Add/Delete Body Editor

irst bad commit commit a37e1eb2af74c8d53d325325d563a30f6dc100b3 Author: Edward K. Ream Date: Tue Apr 23 04:44:59 2024 -0500 Fix #3809 by adding jedit.Colorize(!!) leo/commands/commanderOutlineCommands.py | 5 - leo/core/leoColorizer.py | 11 +++ leo/core/leo

Re: Broken Add/Delete Body Editor

On Friday, August 23, 2024 at 11:01:36 AM UTC-5 Phil wrote: I am seeing that multiple body editors is broken. I see this too. This issue (#4046 ) means that Leo 6.8.2 will go out the door sooner than expected. It seems likely that this i

Re: 🚀 Announcing LeoJS 1.0 🦁

On Mon, Aug 19, 2024 at 9:43 PM Félix wrote: > Just a quick message added to this thread to let you know I've just > released LeoJS 1.0.5. > > *This release solves a problem when writing .md markdown files that > removed the leading newline inside sections. * Excellent. Keep up the good work ;-

Re: Help with PyQt6-WebEngine on linux

> > I'll soon create a PR that update's Leo's FAQ in LeoDocs.leo. I'll ask for > comments before merging. > See PR #4044 . Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe

Re: Help with PyQt6-WebEngine on linux

On Sun, Aug 18, 2024 at 6:41 AM Thomas Passin wrote: > Well Hallelujah! Finally. :-) I'll soon create a PR that update's Leo's FAQ in LeoDocs.leo. I'll ask for comments before merging. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To

Re: How The Mighty Have Fallen, Python Edition

On Tue, Aug 13, 2024 at 10:45 AM Thomas Passin wrote: https://chrismcdonough.substack.com/p/the-shameful-defenestration-of-tim Thanks for this post. I enjoyed reading about Tim's accomplishments. Today's identity-oriented politics are a mystery to me, but happily, a six-month ban is less sever

Re: Requirements For A New Layout System

On Wed, Jul 31, 2024 at 7:34 AM Thomas Passin wrote: > There will always be the main and secondary splitters. They should never be removed. Yes! I forgot to mention this "new" constraint. And their must always be a vertical layout. > "- Don't use settings to modify layouts." Yes, but settings *

Re: Requirements For A New Layout System

On Wed, Jul 31, 2024 at 2:56 AM Edward K. Ream wrote: > The main splitter corresponds to the longest vertical or horizontal line. Once this rule of thumb became clear, I saw that the "render-focused" layout must define its own QHBoxLayout widget. Otherwise, Qt will positio

Re: Requirements For A New Layout System

On Tue, Jul 30, 2024 at 6:53 PM Edward K. Ream wrote: > Some layouts are easy to provide. Some will be much harder. I was too pessimistic. An easy *rule of thumb* clarifies matters: *The main splitter corresponds to the longest vertical or horizontal line.* For example, I was having trou

Re: Requirements For A New Layout System

On Tue, Jul 30, 2024 at 3:04 PM Thomas Passin wrote: Here [are the requirement] I have come up with so far: > > A user should be able to: > 1. specify a default global startup layout using a setting. > 2. specify a per-outline startup layout using a setting. > 3. discover alternate layouts. > 4.

On vacation until August 7.

Rebecca and I will be attending a wedding in Copper Harbor, MI. Edward -- 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+unsubscr...@googlegroups.com. To

Re: Progress report 2: defining layouts with QtDesigner

On Monday, July 29, 2024 at 4:18:35 PM UTC-5 Edward K. Ream wrote: >> The PR will soon support code-based and QtDesigner-based layouts. > I'll aim for maximum compatibility. The define_qt_layouts will (where possible) define layouts with and without QtDesigner. c.frame.top is an i

Re: Progress report 2: defining layouts with QtDesigner

On Mon, Jul 29, 2024 at 2:17 PM Edward K. Ream wrote: *Summary* > > The PR will soon support code-based and QtDesigner-based layouts. > I'll aim for maximum compatibility. The define_qt_layouts will (where possible) define layouts with and without QtDesigner. Edward -- You

Progress report 2: defining layouts with QtDesigner

PR #4017 has passed several milestones: - The VR and VR3 plugins no longer know about layouts. - The *define_qt_layouts* plugin demonstrates that plugins can now define layouts. *Status* Layouts that can use Leo's two standard splitters are

Re: Progress report: new layouts

On Sun, Jul 28, 2024 at 1:41 PM Thomas Passin wrote: > If it's going to be a complete reload of an outline, it will need to be > the whole shebang - save outline if dirty, save selected node and any other > configuration items which will need to be saved to the database before > reload, just as i

Re: Progress report: new layouts

On Sun, Jul 28, 2024 at 1:07 PM Thomas Passin wrote: > The line between core code and plugin code has gotten somewhat blurred. > For example, the qt- plugins or quicksearch. And I think that's fine. > I agree. But we expect plugins to define all "local" layouts, so the line isn't too blurred in

Re: Progress report: new layouts

> > @button nodes can easily change layouts! Here are two tested examples: > This kind of button script can only select an "official" layout, including layouts created by plugins. The concept of layout-defining plugins is still unproven, but I expect success. Edward -- You received this messag

Re: Progress report: new layouts

On Sun, Jul 28, 2024 at 11:59 AM Thomas Passin wrote: > I don't think that restarting Leo is always called for. A user might > change the layout only for certain outlines. I do that all the time. If > there has to be a restart process, then if the default layout is in the > settings for a speci

Progress report: new layouts

PR #4017 has passed an important milestone. It contains working *layout-creation methods *for Leo's legacy and "big-tree" layouts. See the first comment of the PR for an overview of the changes. *Important: *the PR will *restart* Leo if the us

Re: A Script To Undo Many Layout Changes

On Sun, Jul 28, 2024 at 3:04 AM Edward K. Ream wrote: The PR will soon contain hard-coded methods that define all Jake's > suggested layouts. > > When that work is complete, I'll start work on *@data qt-layouts*. > @data qt-layouts is a wretched idea. The advantage of w

Re: A Script To Undo Many Layout Changes

On Sun, Jul 28, 2024 at 6:48 AM Thomas Passin wrote: It's not necessary that VR/VR3 be in their own separate splitter. I agree. Layouts are free to put the VR panes (plural) anywhere. Also, don't assume that a script will create a new layout only by inserting > an enabled plugin widget. My VR

Re: A Script To Undo Many Layout Changes

On Sun, Jul 28, 2024 at 3:12 AM Edward K. Ream wrote: > ...the PR will soon define an *empty layout*. This layout should help define @button nodes that define prototype layouts. Well, that idea quickly blew up. There are a *lot* of assumptions that an empty layout would violate. Edw

Re: A Script To Undo Many Layout Changes

On Sun, Jul 28, 2024 at 3:04 AM Edward K. Ream wrote: In the PR, dw.reloadSettings calls the new *dw.recreateMainWindow* method. > This method *restarts Leo* if the layout has changed. > > This approach solves one problem but creates another. How can we allow > users to define their

Re: A Script To Undo Many Layout Changes

On Sat, Jul 27, 2024 at 2:12 PM Thomas Passin wrote: This script will safely undo all the layout changes we have been discussing > recently. It will work for most layouts that include zero, one, or both of > VR and VR3. It does not solve the general problem. Thanks for this work. My experiments

Re: 🚀 Announcing LeoJS 1.0 🦁

On Sat, Jul 27, 2024 at 5:08 PM Félix wrote: > I am beyond thrilled to announce that after more than five years of relentless development, refinement, and passion, LeoJS has reached its 1.0 release! This milestone marks the beginning of a new era for Leo and VSCode, and I couldn't be more excited

Re: Leo 6.8.1 is here. LeoJS 1.0 coming soon!!

On Sat, Jul 27, 2024 at 1:38 PM Thomas Passin wrote: > Leo 6.8.1 installed and ran on Manjaro Linux (an Arch-based distro). Leo > had previously been installed on this machine so there were no problems > with those potential missing shared Qt libraries. > Thanks, Thomas, for all your testing.

Leo 6.8.1 is here. LeoJS 1.0 coming soon!!

Leo https://leo-editor.github.io/leo-editor/ 6.8.1 is now available on GitHub and pypi . Many thanks to all who have contributed to this release. This release: - Synchronizes Leo with LeoJS 1.0. - Consi

Re: WAT Inspector

On Fri, Jul 26, 2024 at 3:36 AM HaveF HaveF wrote: > [igrek51/wat: Deep inspection of Python objects]( > https://github.com/igrek51/wat) > Thanks for the link. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this gro

Leo 6.8.1 is code complete (for now)

The "devel" branch contains all changes scheduled for Leo 6.8.1. PR #4007 summarizes all the changes. The only possible changes will be fixes for last-minute "quirps" that Félix (or others) might find. The "6.8.1" branch contains those change

Improved tracking of issues and PRs

I am not receiving notifications of new issues and PRs. I'm not sure why, and I'm not sure that's even possible. As a workaround, I have created two new filters: - Pending issues : is:issue is:open no:miles

Re: ENB: More about layouts

On Sun, Jul 21, 2024 at 7:05 AM Thomas Passin wrote: > I think there should be a Layout class that contains > > 1. A description of a layout; > 2. A method that can create the layout from the description. > I agree. A Layout class would be part of what I described as "packaging". It will happen

Re: ENB: More about layouts

On Sunday, July 21, 2024 at 6:14:50 AM UTC-5 Edward K. Ream wrote: > This Engineering Notebook post will discuss the next steps. I have just opened #4016 <https://github.com/leo-editor/leo-editor/issues/4016> for this project. This issue contains a link to Jake's four propos

ENB: More about layouts

Experiments yesterday show that my undoer scheme is a failure. Changing an existing layout is significantly harder than creating a new layout. This Engineering Notebook post will discuss the next steps. *Starting from scratch* The only way forward is to try Jake's idea of deleting the exis

Re: Using multiple layouts

On Sat, Jul 20, 2024 at 3:28 PM Thomas Passin wrote: "But ideally, a layout undoer should preserve the *existing *VR/VR3 > controller and its gui. You would think it would be straightforward to > "relocate" the VR/VR3 pane, but I haven't discovered how to do that yet." > > I found with some of th

Re: Using multiple layouts

> On Sat, Jul 20, 2024 at 1:53 PM Jacob Peck wrote: > > The vr-related crashes are already happening in Leo, I reported a bug on it earlier this week: https://github.com/leo-editor/leo-editor/issues/4009 I'll turn my attention to #4009 first so it won't complicate the layout-related work. Edward

Re: Using multiple layouts

On Sat, Jul 20, 2024 at 1:53 PM Jacob Peck wrote: The vr-related crashes are already happening in Leo, I reported a bug on it > earlier this week: https://github.com/leo-editor/leo-editor/issues/4009 > Thanks for the link. I was not aware of the issue. I suspect it's the same bug, and nothing ne

Re: Using multiple layouts

On Sat, Jul 20, 2024 at 12:14 PM Thomas Passin wrote: > The most obvious way is to use try...except blocks. > > try: > vr_splitter.deleteLater() > except: > pass > I doubt that this would cure the real issue. The deleteLater seems to delete the controller itself. Edward -- You receive

Re: Using multiple layouts

On Sat, Jul 20, 2024 at 10:50 AM Edward K. Ream wrote: > I usually approach tricky tasks by writing specific code first. Heh. The example code wasn't specific enough. It used only QWidget methods, forgetting about QSplitter methods. It should be possible to move the VR/VR3 panes

Re: Using multiple layouts

On Sat, Jul 20, 2024 at 9:36 AM Jacob Peck wrote: > can't you [do something general :-)] I usually approach tricky tasks by writing specific code first. Here is a prototype undoer for the "quadrants" layout. It's in a separate node for prototyping: h = c.hash() pc = g.app.pluginsController gui

Re: Using multiple layouts

On Sat, Jul 20, 2024 at 9:36 AM Jacob Peck wrote: Sorry for my ignorance on the subject, but can't you: > > - find the top level frame, and destroy every child widget underneath it > (recursively if needed) > - rebuild the initial layout inside that top level frame (call some > c.buildGui functio

Re: Using multiple layouts

On Sat, Jul 20, 2024 at 9:25 AM Jacob Peck wrote: > Is there no way to simply call the code that creates the default layout in > the first place? If possible, it would obviate the need for any undoers at > all. Just call it as the first thing any layout script does. > That was the first approa

Re: Using multiple layouts

On Sat, Jul 20, 2024 at 7:51 AM Thomas Passin wrote: > I think there are two potential approaches to undoers: > > 1. Impose a specific layout regardless of the current layout; > 2. Reverse the changes made by the current layout. > Good point. I was thinking of 2. If done consistently, as I envis

Re: Using multiple layouts

On Sat, Jul 20, 2024 at 7:00 AM Edward K. Ream wrote: > We now have several scripts that change Leo's layouts. Let's call the > results of those scripts *alternate *layouts. > A few clarifications: This post should have been labeled as an Engineering Notebook post. It's

Re: Using multiple layouts

On Sat, Jul 20, 2024 at 7:19 AM Thomas Passin wrote: > I think the undoers should be pushed on a stack. My idea was that undoers always reverted to the original (default) layout. I still think this is a reasonable starting point. We can discuss this further after undoers are finished. Edward

Using multiple layouts

We now have several scripts that change Leo's layouts. Let's call the results of those scripts *alternate *layouts. Those scripts suffice if an outline only uses one layout at a time. But what if we want to switch between layouts? - How can we switch between *alternate *layouts? - How can we r

Re: On New-style Layouts And Their Scripts

On Fri, Jul 19, 2024 at 9:04 AM Thomas Passin wrote: > "1. Besides the original helper, g.app.gui.*find_widget_by_name*, we'll > want g.app.gui.*restore_layout*. This helper will use the "split > direction" setting. It should be straightforward to create this helper." > > I'm not so sure it will

Re: On New-style Layouts And Their Scripts

On Fri, Jul 19, 2024 at 7:32 AM Thomas Passin wrote: > I pictured a layout plugin doing it work by running one of those scripts... > The big picture is coming into focus: 1. Besides the original helper, g.app.gui.*find_widget_by_name*, we'll want g.app.gui.*restore_layout*. This helper will use

Re: On New-style Layouts And Their Scripts

On Fri, Jul 19, 2024 at 6:42 AM Thomas Passin wrote: > "Plugins that change layouts probably don't have to worry about > unexpected layouts." > > I don't see it. Many users will want to change from one layout to > another. If a plugin forces a specific layout at startup time, well and > good bu

Re: On New-style Layouts And Their Scripts

On Fri, Jul 19, 2024 at 6:21 AM Edward K. Ream wrote: > But [all the layout scripts] have a serious problem: they all assume they are starting from Leo's default layout. Aha. Changing layouts should be undoable! We can do that :-) Edward -- You received this message because

Re: How do I organize my panes, now that the 'easter egg' interface is gone?

On Thu, Jul 18, 2024 at 8:50 PM Jacob Peck wrote: Here's my go at a `quadrants` layout: > It works for me, provided that VR is enabled. Next, I'll make it work with either VR or VR3 (or both). Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" gr

Re: On New-style Layouts And Their Scripts

On Fri, Jul 19, 2024 at 6:10 AM Thomas Passin wrote: > We've been discussing how to create new layouts for Leo now that the old > nested-splitter system is gone - see > https://groups.google.com/g/leo-editor/c/nLfhTgnPcEc > > That thread includes a number of interesting scripts that can create ne

Re: How do I organize my panes, now that the 'easter egg' interface is gone?

On Fri, Jul 19, 2024 at 6:02 AM Thomas Passin wrote: >> Next, I'd like to replace the vx switch. Leo's plugins manager can tell us whether VR or VR3 is running. > Not if both are enabled, which I sometimes do. Our emails crossed in the ether. My version works for me if both VR and VR3 are runnin

  1   2   3   4   5   6   7   8   9   10   >