github
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/simonw/datasette/issues/690#issuecomment-644987083 | https://api.github.com/repos/simonw/datasette/issues/690 | 644987083 | MDEyOklzc3VlQ29tbWVudDY0NDk4NzA4Mw== | 9599 | 2020-06-16T20:11:35Z | 2020-06-16T20:11:35Z | OWNER | Twitter conversation about drop-down menu solutions that are accessible, fast loading and use minimal JavaScript: https://twitter.com/simonw/status/1272974294545395712 I _really_ like the approach taken by GitHub Primer, which builds on top of HTML `<summary>` `<details>` tags: https://primer.style/css/components/dropdown | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
573755726 | |
https://github.com/simonw/datasette/issues/690#issuecomment-596296955 | https://api.github.com/repos/simonw/datasette/issues/690 | 596296955 | MDEyOklzc3VlQ29tbWVudDU5NjI5Njk1NQ== | 9599 | 2020-03-09T01:49:19Z | 2020-03-09T01:49:19Z | OWNER | Once I've defined what these are they can be implemented using the existing `pluggy` mechanism. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
573755726 | |
https://github.com/simonw/datasette/issues/690#issuecomment-596296745 | https://api.github.com/repos/simonw/datasette/issues/690 | 596296745 | MDEyOklzc3VlQ29tbWVudDU5NjI5Njc0NQ== | 9599 | 2020-03-09T01:48:04Z | 2020-03-09T01:48:53Z | OWNER | Maybe there are a few things here: * A mechanism for adding **actions** - essentially menu items - to tables and rows and queries and the index page * A way of defining blocks on the page where a plugin can add an entire block of custom HTML - above and below the table, or at the top of the index page for example. Anything fancier than this can be achieved using JavaScript - provided there are documented blocks with IDs that JavaScript code can then manipulate in sensible ways. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
573755726 | |
https://github.com/simonw/datasette/issues/690#issuecomment-596275489 | https://api.github.com/repos/simonw/datasette/issues/690 | 596275489 | MDEyOklzc3VlQ29tbWVudDU5NjI3NTQ4OQ== | 9599 | 2020-03-09T00:55:29Z | 2020-03-09T00:55:29Z | OWNER | I just hacked around this again in `datasette-search-all`, which abuses the `description_source_license` block to add a search for to the top of the `index.html` template: https://github.com/simonw/datasette-search-all/blob/f9b2a9c3328f35021a4744205d862c108f8f08eb/datasette_search_all/templates/index.html | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
573755726 | |
https://github.com/simonw/datasette/issues/690#issuecomment-593247614 | https://api.github.com/repos/simonw/datasette/issues/690 | 593247614 | MDEyOklzc3VlQ29tbWVudDU5MzI0NzYxNA== | 9599 | 2020-03-02T06:49:12Z | 2020-03-02T06:49:12Z | OWNER | The answer may lie in a plugin hook which returns a list of HTML fragments to be added to the page in a particular place. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
573755726 |