Fennel web browser
https://gti.telent.net/dan/dunlin/src/branch/main/doc/index.md
1. When adding a button to flowbox, the flowbox widget interposes a flowboxchild between the two, which can receive events and so becomes part of the tab order. this is why our buttons weren't getting activated - they weren't focused even though they looked focused. So, use labels instead of buttons for completions 2. For some reason I don't understand, flowboxchild widgets receive :activate *only* on keyboard activation. So instead of using it, we connect to :child-activated on the flowbox. 3. Setting widget:on_foo *adds* a handler to the widget instead of replacing what was previously there. There is no nice way to remove handlers from a widget either. Because we need a new on_child_activated handler every time the completions change, the only way I can see to achieve this is to create the flowbox afresh on each keystroke instead of creating it once when the frame is created |
||
---|---|---|
doc | ||
test | ||
.dir-locals.el | ||
.gitignore | ||
.overmind.env | ||
buffer.fnl | ||
build.nix | ||
command.fnl | ||
COPYING | ||
default.nix | ||
dunlin.fnl | ||
frame.fnl | ||
history.fnl | ||
keymap.fnl | ||
lsqlite3.nix | ||
Makefile | ||
musing.md | ||
Procfile | ||
README | ||
repl.sh | ||
search.fnl | ||
shell.nix | ||
socket-repl.fnl |
See doc/index.md This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. You can find the full text of the License in the file COPYING in this directory