Dennis Hackethal
@dennis-hackethal·Member since June 2024
Activity
#1790·Dennis HackethalOP revised about 2 months agoFeature to collapse all criticized ideas of a discussion? Useful for todo lists.
Or each discussion could have a search/filter form to filter ideas not just by criticized or not but also content and potentially other attributes.
Feature to collapse all criticized ideas on a page? Useful for todo lists.
Feature to collapse all criticized ideas of a discussion? Useful for todo lists.
Feature to collapse all criticized ideas on a page? Useful for todo lists.
#1786·Dennis HackethalOP, about 2 months agoCycling through the revisions of a leaf reveals its gutter, which should be hidden since it’s a leaf.
Fixed as of 76b7ab4.
#1786·Dennis HackethalOP, about 2 months agoCycling through the revisions of a leaf reveals its gutter, which should be hidden since it’s a leaf.
Make sure cycling between a leaf revision with children and a leaf revision without children properly toggles the gutter.
Cycling through the revisions of a leaf reveals its gutter, which should be hidden since it’s a leaf.
#1780·Dennis HackethalOP, 2 months agoHaving features to both collapse an idea and hide all its comments seems like an opportunity for unification. Why not just go with collapsing and remove the ability to hide all comments?
Sometimes you just want to hide the comments without collapsing the parent idea.
Because that would mean hiding each comment individually if you ever do want to hide all comments of an idea. And sometimes you just want to hide the comments without collapsing the parent idea.
Because that would mean hiding each comment individually if you ever do want to hide all comments of an idea.
#1781·Dennis HackethalOP, 2 months agoBecause that would mean hiding each comment individually if you ever do want to hide all comments of an idea. And sometimes you just want to hide the comments without collapsing the parent idea.
Bulk
#1780·Dennis HackethalOP, 2 months agoHaving features to both collapse an idea and hide all its comments seems like an opportunity for unification. Why not just go with collapsing and remove the ability to hide all comments?
Because that would mean hiding each comment individually if you ever do want to hide all comments of an idea. And sometimes you just want to hide the comments without collapsing the parent idea.
Having features to both collapse an idea and hide all its comments seems like an opportunity for unification. Why not just go with collapsing and remove the ability to hide all comments?
#1775·Dennis HackethalOP revised 2 months agoInclude (preview of) content in idea URLs: '/ideas/123-first-30-or-so-chars-of-idea-here'.
Done as of fcf578c.
#1771·Dennis HackethalOP revised 2 months agoFetching the idea is not necessary if the feature is backwards compatible. Can still just use /ideas/123.
As noted in #1777, fetching the idea actually helps. Well worth the overhead.
#1769·Dennis HackethalOP, 2 months agoThat would mean fetching an idea to compute the path for each hashtag. Overhead?
This actually helps to prevent rendering links with IDs that don’t point to any existing idea.
Use friendly IDs for ideas? A ‘mixture’ where URLs say '/ideas/123-first-30-or-so-chars-of-idea-here'.
Include (preview of) content in idea URLs: '/ideas/123-first-30-or-so-chars-of-idea-here'.
#1763·Dennis HackethalOP, 2 months agoUse friendly IDs for ideas? A ‘mixture’ where URLs say '/ideas/123-first-30-or-so-chars-of-idea-here'.
Wouldn’t even need friendly ID for that since the URL would contain the ID. Would only need to override to_param to concatenate the idea’s ID and content.
#1769·Dennis HackethalOP, 2 months agoThat would mean fetching an idea to compute the path for each hashtag. Overhead?
Seems like minor overhead. It’s not like there are tons of user-generated hashtags everywhere.
Elaborate/clarify
Not if the feature is backwards compatible.
Fetching the idea is not necessary if the feature is backwards compatible. Can still just use /ideas/123.
#1769·Dennis HackethalOP, 2 months agoThat would mean fetching an idea to compute the path for each hashtag. Overhead?
Not if the feature is backwards compatible.
#1763·Dennis HackethalOP, 2 months agoUse friendly IDs for ideas? A ‘mixture’ where URLs say '/ideas/123-first-30-or-so-chars-of-idea-here'.
That would mean fetching an idea to compute the path for each hashtag. Overhead?
#1764·Dennis HackethalOP, 2 months agoThe way IG solves this is by rendering the form in a fixed position. It’s still on the bottom but always remains visible.
Facebook does it this way, too.
#453·Dennis HackethalOP revised about 1 year agoThe more ideas there are in a discussion, the further the form for top-level ideas is pushed down. Then people don’t know how to submit a new idea and comment on an existing one instead, even if it’s unrelated, as happened with #448. So I need to make this clearer.
Reddit is a bit different because they have multiple subreddits/communities, but each community has top-level posts which people can then comment on. They have a completely separate page/UI for top-level posts. And then directly underneath a top-level post, there’s a textarea saying “Join the conversation”.
#1765·Dennis HackethalOP, 2 months agoThat would make idea URLs more meaningful, but there’s something simple and beautiful about the shorter URLs that only have the numeric ID.
Could have backwards compatibility for the short version and continue using the hashtag in the UI. Best of both worlds?
#1763·Dennis HackethalOP, 2 months agoUse friendly IDs for ideas? A ‘mixture’ where URLs say '/ideas/123-first-30-or-so-chars-of-idea-here'.
That would make idea URLs more meaningful, but there’s something simple and beautiful about the shorter URLs that only have the numeric ID.
#453·Dennis HackethalOP revised about 1 year agoThe more ideas there are in a discussion, the further the form for top-level ideas is pushed down. Then people don’t know how to submit a new idea and comment on an existing one instead, even if it’s unrelated, as happened with #448. So I need to make this clearer.
The way IG solves this is by rendering the form in a fixed position. It’s still on the bottom but always remains visible.