Re: A Leo relative in the wild: Trilium Notes

Wow. I thought/hoped saying a couple words about Trilium would spark a few thoughts, but nothing like the way this thread is running. It's amazing. Thanks all! -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and

Re: A Leo relative in the wild: Trilium Notes

On Thursday, April 25, 2024 at 1:55:38 PM UTC-4 Thomas Passin wrote: On Thursday, April 25, 2024 at 1:25:21 PM UTC-4 Thomas Passin wrote: >From an architectural point of view, the current Leo editor widget could get replaced by a widget with several child widgets (a tabbed widget is one

Re: A Leo relative in the wild: Trilium Notes

On Thursday, April 25, 2024 at 1:25:21 PM UTC-4 Thomas Passin wrote: >From an architectural point of view, the current Leo editor widget could get replaced by a widget with several child widgets (a tabbed widget is one possibility), of which one is the current editor widget, and most keyboard

Re: A Leo relative in the wild: Trilium Notes

We are really on the same page here! On Thursday, April 25, 2024 at 12:39:33 PM UTC-4 Edward K. Ream wrote: On Thursday, April 25, 2024 at 6:57:17 AM UTC-5 Thomas wrote: Hmm, instead of rendering those nodes in a separate frame as VR/VR3 does, we could overlay the rendering frame over the

Re: A Leo relative in the wild: Trilium Notes

On Thursday, April 25, 2024 at 6:57:17 AM UTC-5 Thomas wrote: Hmm, instead of rendering those nodes in a separate frame as VR/VR3 does, we could overlay the rendering frame over the editing frame. We could switch in and out of rendering mode to allow editing. I bet that wouldn't be too hard.

Re: A Leo relative in the wild: Trilium Notes

Something like this, together with the 'paste a snippet as a file' feature I discussed a few weeks ago (and am still playing with) would go a long way to stopping me occasionally yearning for some of the features of Obsidian and/or Joplin, which I have tried recently. On Thursday, April 25,

Re: Leo 6.7.8 released to pypi

> > > When I using `pipx inject leo /Users/mac/Desktop/proj/leo-editor` for > newest code. it throws: > >error: package directory 'leo/doc/_static' does not exist > > > after `mkdir -p leo/doc/_static`, it works as before. > > Maybe we need an empty .gitignore file in that folder? > > Why

Re: A Leo relative in the wild: Trilium Notes

This sounds pretty much what I had in mind. The freewin plugin actually does the same (in its own separate window). VR/VR3 also replace the rendering widget type depending on what is to be rendered. Currently VR3 can optionally render to a tab in the log frame instead of to a new frame

Re: A Leo relative in the wild: Trilium Notes

I actually implemented something similar in a private 'leoapp' (app that lives in a .leo file) I wrote for myself a few years back. Pretty simple to get done, IIRC. My general pattern was to have a controller class that contained two 'view' widgets (a QTextBrowser for rendered HTML, and a

Re: A Leo relative in the wild: Trilium Notes

See new issue Allow VR/VR3-style rendering overlaid on standard editing nodes . On Thursday, April 25, 2024 at 8:10:51 AM UTC-4 Edward K. Ream wrote: > On Thu, Apr 25, 2024 at 6:57 AM Thomas Passin wrote: > >> Except that standard Leo nodes

Re: A Leo relative in the wild: Trilium Notes

On Thu, Apr 25, 2024 at 6:57 AM Thomas Passin wrote: > Except that standard Leo nodes don't render graphics and other non-text > items. That's a big difference. We get around it to a degree with VR/VR3. > Hmm, instead of rendering those nodes in a separate frame as VR/VR3 does, > we could

Re: A Leo relative in the wild: Trilium Notes

Except that standard Leo nodes don't render graphics and other non-text items. That's a big difference. We get around it to a degree with VR/VR3. Hmm, instead of rendering those nodes in a separate frame as VR/VR3 does, we could overlay the rendering frame over the editing frame. We could

Re: Leo 6.7.8 released to pypi

On Thursday, March 28, 2024 at 9:44:52 AM UTC-5 iamap wrote: > When I using `pipx inject leo /Users/mac/Desktop/proj/leo-editor` for newest code. it throws: >error: package directory 'leo/doc/_static' does not exist > after `mkdir -p leo/doc/_static`, it works as before. > Maybe we need an

Re: Current Devel Branch Fails To Start Using Python 3.9

On Wednesday, April 24, 2024 at 11:33:19 AM UTC-5 Edward K. Ream wrote: > PR #3885 ...moves *from typing import TypeAlias* into the range of *if TYPE_CHECKING*: ... > Even if the import fails, only mypy will be affected. At worst, mypy's type

Re: A Leo relative in the wild: Trilium Notes

On Thu, Apr 25, 2024 at 3:49 AM Christoph wrote: Of course, dealing with hierarchical data sooner or later requires a > mechanism that allows to put data in more than one branch of the > hierarchy so this seems to be a logical step. However, Leo has taken > this step more than 20 years ago and

Re: A Leo relative in the wild: Trilium Notes

I am under the impression that CherryTree (https://www.giuspen.net/cherrytree/) has implemented something similar recently: https://github.com/giuspen/cherrytree/issues/1222 Not sure if it is exactly the same or a variant. Also, Zotero has a similar mechanism. Of course, dealing with