Point
Points are referencable units with a granularity smaller than a webpage, so a single webpage could contain multiple points.
Points manifest as <point url="/some-unique-point-name"/> tags within webpages.
Ideally points would be implemented by the browser, but currently you can poly-fill them on your webpage by including <script src="https://braid.org/point.js"></script>
Here is a point: This is a point.
Example:
I claim points are easy to use.
As a bit of evidence, every use of a point has been easy.
Hi dan!
todos in the pipe
- saw some echo/overwriting/feedback in "type" input box
- server sometimes has an issue/becomes unresponsive
- points don't do well when wrapped.. when you click to open dialog, it is very small
- https://wickie.invisible.college/point-test gets a lot of CORS erros..
- Also appears in: -- seems to follow the urls (like the other sections) but this one doesn't need to
- make points display with "type" (as they appear within the popup)
try it and see what it looks like..
recently done
- DONE 9/15: "Type:" not lined up with dropdown, in point popup
- DONE: points inherit bold in popup, and probably shouldn't -- other styles also seem worse after fixing issue with reflowing page text
- DONE: clicking a point in this page slightly alters the text layout
- are the points down? -- yes, rebooted server
- fixed dom monitor so there is no need to call pointify manually -- also added listeners to unmount points when they go away
- DONE: debug why the point-monitor doesn't work for the wickie (and instead we call pointify manually whenever rendering new markdown)
- make it so points, when they don't have an id, say so (so people know that's what needs to be fixed)