Hi,
On 26/04/24 16:36, Matt Wilkie wrote:
Leo is plain text first, and achieves rich text and media by
rendering. Trilium is rich text and media first, with the primary
entry mechanism through the 3rd party CKEditor which saves as html.
This is the foundational split behind the whole VR and multiple panes
/(pains? heheh)/ vs single pane thinking and attendant mitigation
machinery. Trilium doesn't have to think about rendering hardly at
all, since it's the embedded browser that does that.
Leo uses the file system for storage and Trilium uses sqlite. This
gives Leo its external files extended abilities very nearly for free.
For Trilium to adopt such features would be an exercise of some
effort. Otoh, being able to run sql queries across all nodes can't be
anything but powerful. (In Trilium access the SQL Console via |Alt-0|
or the flower logo at top left; yeah, speaks to lack of menu).
It's this db backend which enables syncing one's entire KB across all
devices in a pretty much set-and-forget manner. It's almost as good as
Fossil SCM in this regard. This is very, very attractive.
Another Trilium limit: there's only a single knowledge database. ALL
your Trilium work is one place. There is discussion on a future with
multiple db but nothing substantive that I've seen. I'm new to the
space and might be missing the action though.)
-matt
In Grafoscopio's case (Grafoscopio is becoming a distribution of several
extensions and customizations over Pharo/GToolkit) we are kind of in the
middle, maybe because we were inspired by Leo and Pharo/Smalltalk. For
example:
1. our default UX/UI uses GToolkit's Lepiter to combine several
representations (prose, code, data, graphics),
2. our storage format kind of inverts what we had previously with the
early Grafoscopio version: instead of Markdown inside a STON[1], which
give us a pretty light and readable textual format (see the source code
of Grafoscopio manual[1a], now we have STON metadata inside Markdeep,
which keeps the readability, while providing a format that can be
rendered in almost any web browser.
3. For storage, sharing, versioning and publishing of our notebooks we
use Fossil.
Cheers,
Offray
[1]
https://book.huihoo.com/smalltalk/pharo/enterprise-pharo/book-result/STON/STON.html
[1a]
https://mutabit.com/repos.fossil/grafoscopio/file?name=Docs/En/Books/Manual/manual.ston&ci=tip
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/80580625-b770-4d5d-9839-98d73d6d006c%40riseup.net.
