{"html_url": "https://github.com/simonw/datasette/issues/596#issuecomment-1238790634", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/596", "id": 1238790634, "node_id": "IC_kwDOBm6k_c5J1nHq", "user": {"value": 9599, "label": "simonw"}, "created_at": "2022-09-07T00:55:52Z", "updated_at": "2022-09-07T00:58:41Z", "author_association": "OWNER", "body": "Or there's this recipe on StackOverflow that does the same thing without jQuery - there's an interactive demo on that page if you click \"Run code snippet\": https://stackoverflow.com/a/47038108/6083\r\n\r\nAll sorts of other potential solutions in that thread too.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 507454958, "label": "Handle really wide tables better"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/596#issuecomment-1238790158", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/596", "id": 1238790158, "node_id": "IC_kwDOBm6k_c5J1nAO", "user": {"value": 9599, "label": "simonw"}, "created_at": "2022-09-07T00:54:55Z", "updated_at": "2022-09-07T00:54:55Z", "author_association": "OWNER", "body": "The jqDoubleScroll plugin is interesting: https://github.com/avianey/jqDoubleScroll/blob/master/jquery.doubleScroll.js\r\n\r\nHere's a demo: https://6317eba21040d42c0228aab9--tiny-tarsier-c1f294.netlify.app/example.html\r\n\r\nWouldn't be too hard to port that to work without jQuery.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 507454958, "label": "Handle really wide tables better"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/596#issuecomment-1238383171", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/596", "id": 1238383171, "node_id": "IC_kwDOBm6k_c5J0DpD", "user": {"value": 562352, "label": "CharlesNepote"}, "created_at": "2022-09-06T16:27:25Z", "updated_at": "2022-09-06T16:27:25Z", "author_association": "NONE", "body": "Perhaps some ways to address this.\r\n\r\n1. Add a **horizontal scrollbar at the top of the table**. There are some solutions here: https://stackoverflow.com/questions/3934271/horizontal-scrollbar-on-top-and-bottom-of-table\r\n2. Use a **fixed table header**. It would be useful when you're lost in the middle of a very big table. Pure CSS solutions seem to exist: https://stackoverflow.com/questions/21168521/table-fixed-header-and-scrollable-body\r\n3. Maybe a possibility to resize columns. Not sure about that because it would more work not to lose it after each reload.\r\n4. A way to keep **favorite views for each user**. The process would be: I select the column I want or not (with existing \"settings\" icon of each column); then I select a \"favoritize view\" option somewhere; then I can recall all my favorite views from a menu. These data could be hosted on the browser.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 507454958, "label": "Handle really wide tables better"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/596#issuecomment-720741903", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/596", "id": 720741903, "node_id": "MDEyOklzc3VlQ29tbWVudDcyMDc0MTkwMw==", "user": {"value": 132978, "label": "terrycojones"}, "created_at": "2020-11-02T21:44:45Z", "updated_at": "2020-11-02T21:44:45Z", "author_association": "NONE", "body": "Hi & thanks for the note @simonw! I wish I had more time to play with (and contribute to) datasette. I know you don't need me to tell you that it's super cool :-)", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 507454958, "label": "Handle really wide tables better"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/596#issuecomment-720689653", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/596", "id": 720689653, "node_id": "MDEyOklzc3VlQ29tbWVudDcyMDY4OTY1Mw==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2020-11-02T19:53:36Z", "updated_at": "2020-11-02T19:53:47Z", "author_association": "OWNER", "body": "In #998 I implemented a horizontal scrollbar for these tables, which is a big improvement - demo here: https://global-power-plants.datasettes.com/global-power-plants/global-power-plants", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 507454958, "label": "Handle really wide tables better"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/596#issuecomment-647893140", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/596", "id": 647893140, "node_id": "MDEyOklzc3VlQ29tbWVudDY0Nzg5MzE0MA==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2020-06-23T03:59:51Z", "updated_at": "2020-06-23T03:59:51Z", "author_association": "OWNER", "body": "Related: #862 - a time limit on the total time spent considering suggested facets for a table.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 507454958, "label": "Handle really wide tables better"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/596#issuecomment-567226048", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/596", "id": 567226048, "node_id": "MDEyOklzc3VlQ29tbWVudDU2NzIyNjA0OA==", "user": {"value": 132978, "label": "terrycojones"}, "created_at": "2019-12-18T21:43:13Z", "updated_at": "2019-12-18T21:43:13Z", "author_association": "NONE", "body": "Meant to add that of course it would be better not to reinvent CSS (one time was already enough). But one option would be to provide a mechanism to specify a CSS class for a column (a cell, a row...) and let the user give a URL path to a CSS file on the command line.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 507454958, "label": "Handle really wide tables better"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/596#issuecomment-567225156", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/596", "id": 567225156, "node_id": "MDEyOklzc3VlQ29tbWVudDU2NzIyNTE1Ng==", "user": {"value": 132978, "label": "terrycojones"}, "created_at": "2019-12-18T21:40:35Z", "updated_at": "2019-12-18T21:40:35Z", "author_association": "NONE", "body": "I initially went looking for a way to hide a column completely. Today I found the setting to truncate cells, but it applies to all cells. In my case I have text columns that can have many thousands of characters. I was wondering whether the metadata JSON would be an appropriate place to indicate how columns are displayed (on a col-by-col basis). E.g., I'd like to be able to specify that only 20 chars of a given column be shown, and the font be monospace. But maybe I can do that in some other way - I barely know anything about datasette yet, sorry!", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 507454958, "label": "Handle really wide tables better"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/596#issuecomment-542462126", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/596", "id": 542462126, "node_id": "MDEyOklzc3VlQ29tbWVudDU0MjQ2MjEyNg==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2019-10-16T00:45:45Z", "updated_at": "2019-10-16T00:45:45Z", "author_association": "OWNER", "body": "This means moving away from `select *`. I've been thinking this would be worthwhile anyway, since that way when you click \"Edit SQL\" you'll get a more useful SQL statement to start hacking away at.", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 507454958, "label": "Handle really wide tables better"}, "performed_via_github_app": null}