Coming soon...

[Félix]

... In a browser near you!

[Edward K. Ream]

On Saturday, January 17, 2026 at 6:12:32 PM UTC-6 Félix wrote:

... In a browser near you!

That's great news. Will there be a dark option?  

Edward

[alel...@gmail.com]

excellent!

+1 vote for dark mode!

On Sun, 18 Jan 2026 at 00:12, Félix <felix...@gmail.com> wrote:

... In a browser near you!

--
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+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/leo-editor/fb61dde0-d30c-4964-a787-1bfc0d467529n%40googlegroups.com.

[Félix]

>  Will there be a dark option?  

Of course! :P

It's basically the 'leo read-only browser' UI, which I did last fall, but with its 'read-only' simplified internals replaced with LeoJS core classes! :)

That UI replaces the vscode UI, and I've made it work local files on your computer although its enterily in the browser!

I'll put it online and give you a proper URL for all you guys to try it out as soon as I have finished hooking up the basic UI clicks and keyboard events to their specific Leo commands... If you're curious about its current state and development, here's the github repo for this project: https://github.com/boltex/leo-web 

Please dont hesitate to provide your comments and suggestions for this proper 'Leo in the browser' project!

Félix

[rengel]

Thank you! Great news. 
Will it be able to handle plugins (old and new widgets à la Trilium)?

[HaveF HaveF]

Félix, it is amazing...

 

That UI replaces the vscode UI, and I've made it work local files on your computer although its enterily in the browser!

 

And I'm a little confused, do you have any ideas about its usage scenarios?

[Viktor Ransmayr]

Hello Felix,

An impressive project /  web-app.

Am Mo., 19. Jan. 2026 um 02:33 Uhr schrieb Félix <felix...@gmail.com>:

>  Will there be a dark option?  
Of course! :P

To add to that, there already is one ;-) - See attached screenshot !

 

It's basically the 'leo read-only browser' UI, which I did last fall, but with its 'read-only' simplified internals replaced with LeoJS core classes! :)

That UI replaces the vscode UI, and I've made it work local files on your computer although its enterily in the browser!

I'll put it online and give you a proper URL for all you guys to try it out as soon as I have finished hooking up the basic UI clicks and keyboard events to their specific Leo commands... If you're curious about its current state and development, here's the github repo for this project: https://github.com/boltex/leo-web 

What's not clear to me is the state of the project: Should I already be able to open a dedicated file in / with the 'leo-web' app ? 

I did open a directory / workspace & allowed write access to it ...

With kind regards,

Viktor

[Viktor Ransmayr]

Hello Felix,

Am Mo., 19. Jan. 2026 um 02:33 Uhr schrieb Félix <felix...@gmail.com>:

>  Will there be a dark option?  
Of course! :P

Which web-browsers are you testing / using 'leo-web' yourself ?

I am currently using Chromium.

Is that OK / already supported ?

With kind regards,

Viktor 

[Robert-Felix]

@viktor....@googlemail.com  I've tested chrome and edge :



I've now implemented the menu and hooked file commands for now today, (the hamburger at top right toggles the 'zen mode' with hover buttons of the read-only viewer I had done prior to this.

I'll add the rest of the commands shortly (and then hook mouse clicks on nodes, etc.)

...Hopefully have full features before the spring! :)

Félix

--

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+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/leo-editor/CAAeSrG%2BN2rr3W-AonoZ_xY7%3DM1U_9FCOpY-W0uR-hTy2vfeQAg%40mail.gmail.com.

[Viktor Ransmayr]

Hello Felix,

Am Mi., 21. Jan. 2026 um 05:32 Uhr schrieb Robert-Felix <felix...@gmail.com>:

@viktor....@googlemail.com  I've tested chrome and edge :

...

I've now implemented the menu and hooked file commands for now today, (the hamburger at top right toggles the 'zen mode' with hover buttons of the read-only viewer I had done prior to this.

I'll add the rest of the commands shortly (and then hook mouse clicks on nodes, etc.)

And as of today I can report that I'm able to open a file in 'leo-web' using Chromium on Fedora Linux as well.

See attached screenshots.

When I try to select the node an exception is triggered - but - I assume this is just related to the current implementation status of the project.

I was asking the question, since I was worried that my setup (Fedora 43 distrobox, Chromium, etc.) was a problem - and - prevented me to see the 'real' state of the project

Luckily I was wrong ...

With kind regards,

Viktor

 

[rengel]

Ref "zen-mode": There might be misunderstandings. The hamburger menu toggles the Leo-specific zen-mode. Besides that, there is still the F11 zen-mode of the browser itself (I tried Chrome). Both zen-modes can be combined: So F11 gives you a very clean, Leo-only screen.

[rengel]

Leo-web, Chrome: When I click the vertical/horizontal toggle in the upper-right corner, my mouse cursor vanishes in the log and body panes.

[rengel]

I cannot toggle between the vertical and horizontal layout if the tabbar and the menubar are shown.

On Wednesday, January 21, 2026 at 5:32:25 AM UTC+1 Félix wrote:

[Félix]

@rengel I'm not able to reproduce the behavior : when I click the vertical/horizontal toggle, my mouse cursor and focus stays in the body or log pane respectively. Maybe I dont understand the precise issue - What browser are you using?

 Lets see if this persists in the next few days/weeks as I develop and add features. I'll keep an eye opened for this specific behavior and re-test it as I go along.

I'll fill up more items in the menu, and I'll hook up more commands shortly for the menu and other UI / clicks / keyboard shortcuts.

Many thanks for testing stuff out ! 

[rengel]

@Félix I'm using Chrome on Windows 11. The error is transient. On my machine it is reproducible. In horizonal mode: I click on the toggle and then move the cursor from the log pane to the body pane. As soon it crosses the border between the two panes, the cursor disappears. Moving it between the two panes several times, the cursor reappears. The analog happens in vertical mode. But if I try to capture it in a video (using SnagIt) the cursor is always visible (as it should be). I'll keep an eye on this.

[Edward K. Ream]

On Saturday, January 17, 2026 at 6:12:32 PM UTC-6 Félix wrote:

... In a browser near you!

Here is the report of my experiences:

Environment

Windows 11. Mozilla as my default browser. All my experiments are with MS-Edge.

Leo-web: rev 6a862d1b on master. (Latest pull).

Readme.md

The readme says:

> This [`npm run dev` or `npm start`] will start the webpack dev server and automatically open the application in your browser at http://localhost:8080.

`npm run dev` does not seem to open the page.

`npm start` starts http://localhost:8080 in my *default* browser (Mozilla).

Using MS-Edge

Opening http://localhost:8080 in Edge works as expected.
leo-web prompts for a folder, remembering the previously-given folder.

I give permission to edit the directory.
I chose the leo-web directory.

I have to click the pancake menu to see Leo's menu. I would like that menu to be visible by default.

Opening leo-web.leojs works! I see the top-level @clean files.

Trying to expand the Leo outline (by clicking) crashes:

Uncaught runtime errors:
ERROR
Cannot read properties of null (reading 'length')
TypeError: Cannot read properties of null (reading 'length')
    at LeoController.handleOutlinePaneClick (webpack-internal:///./src/LeoController.ts:131:59)

Clicking the back arrow brings me back to the MS-Edge home page.
Clicking the bookmarked leo-web link, http://localhost:8080, again prompts me for a folder.

Summary

A great start.

Edward

[Thomas Passin]

I hope the port can be easily changed from 8080 to something else. On my computer, 8080 is already spoken for.

[Félix]

@Thomas yeah the port can be specified like this by adding "--port=xxxx":
npx webpack serve --mode=development --port=9000

add --open to open a browser automatically (that's the difference between the 'dev' script and the 'start' script in package.json)
npx webpack serve --mode=development --port=9000 --open

Thanks to all for trying out this very early version and reporting those details, suggestions and issues. (This helps a lot!)

 I'll make another post when I've got something more usable with the basic functionality all implemented :D 

Félix

[Félix]

@Edward Indeed, the 'show menu' toggle should be saved between refreshes just like the pane ratios, the theme and other options that survive a refresh. 

I will also save the chosen 'workspace' folder and offer a 'reset workspace' command in the files menu to change it when needed.

I know its a bit early in the project, but the suggestions really help at that stage of developement, so thanks again to all who pitched-in in this thread! :) 

Félix

[Viktor Ransmayr]

Hello Felix,

Félix schrieb am Freitag, 23. Januar 2026 um 04:45:37 UTC+1:

@Edward Indeed, the 'show menu' toggle should be saved between refreshes just like the pane ratios, the theme and other options that survive a refresh. 

I will also save the chosen 'workspace' folder and offer a 'reset workspace' command in the files menu to change it when needed.

I know its a bit early in the project, but the suggestions really help at that stage of developement, so thanks again to all who pitched-in in this thread! :) 

Did you perform any tests on Chromium & a Linux distro from your side already ?

I'm asking, because I fail to get a usable version of 'leo-web' using Chromium on Fedora 42 as well as Debian 13 !

That is, I can open 'leo-web.leojs' & the outline is opened - but - NO body content is displayed :-(

Or is it still to early in your implementation of 'leo-web' ?

With kind regards,

Viktor

[Félix]

Hi Viktor - First of all, thanks so much for your consistent beta testing and support!

Yeah I've tested a bit on linux on my other machines but I've only now (tonight) finished the UI and integrating the LeoJS core into it, but the body pane (and headline editing) is yet to be implemented. 

So totally normal that all commands can be performed via mouse, keyboard-shortcuts and menus, but no proper body pane nor headline editing.

to recap,  so far, I've taken the "Leo read-only HTML viewer" (Thanks to Brian for launching that series of events BTW!) that I did last fall, and added a menu system and some more 'UI' machinery in order to hook most of Leo's functionality - somewhat similarly to how VSCode exposes its menu and interface buttons and controls, but a bit simpler.

So I've updated the readme. Here's the part about what is done so far:

## Limitations

To keep Leo-Web light and fast, it does not support .db files.

Absolute paths (such as C:/myFile) are not supported with the browser's file api. Use relative paths exclusively. (supports ../ if within workspace)

`Ctrl+N` and `Ctrl+T` are reserved by the browser for opening new windows or tabs.

## Current Features

- Complete UI implementation with outline, log, settings, and find panes

- Leo's core integrated with menu system, keybindings, and mouse controls in the outline

- Full outline pane with node selection, expansion/collapse, marking, and hoisting

- Multiple document support with tabbed interface

- Theme and layout customization

- Drag-to-resize panes with persistent preferences

- Context menus and keyboard shortcuts

### Not Yet Implemented

- Headline editing in the outline pane

- Body pane text editing

- Find/replace functionality

I'm now going to start on the last 3 items remaining: allow changing headlines, and hooking up the body pane and find pane. (Still hopeful to have a fully working 1.0 version before march!!)

Many thanks again to you guys for playing with it early in the development and pointing out problems!

Félix

[Viktor Ransmayr]

Hello Félix,

Félix schrieb am Mittwoch, 11. Februar 2026 um 05:45:15 UTC+1:

... 

So totally normal that all commands can be performed via mouse, keyboard-shortcuts and menus, but no proper body pane nor headline editing.

...

I'm now going to start on the last 3 items remaining: allow changing headlines, and hooking up the body pane and find pane. (Still hopeful to have a fully working 1.0 version before march!!)

Thanks a lot for your clarification & project update.

With kind regards,

Viktor