| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This snapshot was demoed at https://archive.org/details/akkartik-teliva-2022-02-10
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We also made render dynamic, showing zettels in the first place it
encounters them in depth-first order.
Open question: how to show a collapsed outline view with the data model
I'm experimenting with. Not even clear 'outline' has meaning in the
presence of cross-links. Outliners privilege one view of the network.
Zettelkasten also does so; changing child/sibling relationships is a lot
of work. However, reading between the links it seems to try to provide
an escape hatch for rethinking connections using cross-links. I'm trying
to lean into that -- at the cost of providing outlines. We'll see if
this is a good trade-off.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Conundrum:
I want the app to provide some sample data for people to interact with.
However, I also want them to be able to delete it to make it their own.
BUT I'm not yet convinced the app should allow deletion in general.
Besides, deleting stuff robustly and reliably is a whole other level of
programming.
Solution:
Make people edit the app to clear the initial sample zettels.
This has the "beneficial" side-effect of getting them editing apps on
Teliva.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This will eliminate some spurious git diffs I keep having to clean up.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Still won't show up in view mode for now. Soon we'll be able to adjust
zettel dimensions.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The problem I'm running into is that apps might want to perform their
own editing. So I can't take up prime estate like the ctrl-e hotkey or a
menu name of 'edit'.
I'm still prioritizing rendering Teliva's edit and permissions menu. If
the window is too narrow the app's settings will be overwritten and
Teliva's hotkeys will be preferentially displayed. Seems safer.
|
| |
|
| |
|
|
|
|
| |
https://fosdem.org/2022/schedule/event/lastmilesandboxing
|
|
|
|
| |
Also a minor edit in doc:main.
|
| |
|
|
|
|
| |
Now we can be sure apps can't call `require`.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Just like with `require`, we don't we don't know how to sandbox it.
(Though we still have `require` because standard libraries outside apps
need it. I need to make sure apps can't invoke `require`..)
|
| |
|
|
|
|
|
| |
How many levels of macros do we need. Also stop lying that we're using
Linux in BSD.
|
|
|
|
|
|
|
|
| |
I've never tested with it, and it is likely broken after all my changes
to base Lua 5.1. Might as well be transparent about that.
If you care about this platform, please let me know:
http://akkartik.name/contact
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://merveilles.town/@akkartik/107742821323590471
What we have so far:
a representation (see 'zettels')
parent/child
next/prev sibling
(todo: misc cross-links)
ability to render zettels in multiple columns based on 'view_settings'
all zettels render with same size
alternate backgrounds between zettels for legibility
skip rendering duplicates (if we ever hit cycles)
a highlighted 'current zettel'
ability to move current zettel
by screen location (arrow keys)
by network structure (h/j/k/l)
Still can't edit zettels or load/save from/to disk.
|
| |
|
|
|
|
|
| |
It's not clear to me where my Linux gets strlcpy and strlcat from
¯\_(ツ)_/¯
|
| |
|
|
|
|
| |
Submitted upstream at https://github.com/antirez/kilo/pull/81.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'd already dropped the variant without a filename. But even the variant
with a filename is very easy to use in a way that is confusing to use in
the presence of sandboxing:
* call io.lines()
* Sandboxing saves an error, io.lines() returns nil
* Caller (usually a loop) raises an error.
* We show the error and not the sandboxing failure.
* Worse, there's no way to adjust permissions from within Teliva,
because we can't ever get to that menu while there's an error.
Best solution I can come up with: encourage a separate step for
translating filename to file handle. That way it's more obvious that we
need to check for errors.
|
| |
|
| |
|
|
|
|
|
| |
This will help people cross-correlate when the app performs specific
calls.
|
| |
|