Replies: 6 comments 2 replies
-
|
There would need to be a way to switch the redirects off, probably with a flag, and maybe also opt-in via a |
Beta Was this translation helpful? Give feedback.
-
|
related: srid/emanote#121 |
Beta Was this translation helpful? Give feedback.
-
Yes, I too thought of this idea in the context of Emanote. We should do it for sure. Perhaps Ema can provide a "frontend API" that talks to the web browser through websocket, with a single API entry in it for now called "switchRoute". Then Emanote can call We should also consider this in terms of #55 (and vice-versa) as well as srid/emanote#84. But maybe for initial rough version we can just expose |
Beta Was this translation helpful? Give feedback.
-
|
I see the current websocket endpoint is pretty simple: path up (and a second path up to change route), html fragment down. Would you rather change the current impl to support some message type specifier (at least down, but might as well be both ways) anticipating future features, or add another endpoint for the server->client switchRoute messages? Alternatively, the current endpoint could be changed so the server always sends a route before the html fragment, and the client updated to support setting the route from the server. This seems like the minimal change needed. How about it? |
Beta Was this translation helpful? Give feedback.
-
|
We have @lucasvreis asked for this here: #70 (comment) |
Beta Was this translation helpful? Give feedback.
-
Vivaldi has split view, which in conjunction with something like running vim over gotty, can be interesting to achieve this workflow other way (ie. editor in web browser, rather than web browser in editor).
|
Beta Was this translation helpful? Give feedback.
-
I'm using emanote with Obsidian (and Vim, Emacs, etc) and have been thinking about ways of enabling side-by-side preview without requiring explicit navigation when switching pages. There are plenty of possible approaches:
<link rel=edit...and either a browser extension or some browser-based editor.I'm more interested in the second class of solutions, but there is another option that I wanted to put up for discussion: in hot reload (server) mode, Ema is watching source files for changes, updating its model and sending reload commands down the websocket. What if it also learned to send redirect commands to the slug for whatever file changed most recently? Some aggregation would be necessary for bulk updates (maybe redirect to the first change event right away, then wait a bit and redirect to the last one, so max 2 redirects per batch). This is just one idea, but I like that it completely decouples from the editor and uses filesystem updates for signaling (i mean, monitoring FS updates is super difficult and edge-casey, but since ema is already doing it, it probably wouldn't add too much overhead or code complexity, i guess)
Beta Was this translation helpful? Give feedback.
All reactions