Veritula – Meta
#1892·Dennis HackethalOP, about 2 months agoThat would mean the revise button would be at the top of the idea. But presumably, people would typically want to revise an idea after they finish reading it. Meaning after they reach the bottom.
It could go both ways. Someone may have already read an idea and just wants to revise it, in which case having to scroll to the bottom is cumbersome.
#1891·Dennis HackethalOP, about 2 months agoI could turn the ‘Revise…’ button into an icon button that lives next to the collapse icon button. It could just have a pencil for an icon.
That way, the button wouldn’t need to be hidden anymore.
That would mean the revise button would be at the top of the idea. But presumably, people would typically want to revise an idea after they finish reading it. Meaning after they reach the bottom.
#1888·Dennis HackethalOP, about 2 months agoThe ‘Revise…’ button is hidden when the comment form is open. It makes sense to hide it because it doesn’t belong in that context. But once hidden, the user has no quick way to revise an idea. Maybe the first thing they want to do after opening
ideas#showis not comment but revise.
I could turn the ‘Revise…’ button into an icon button that lives next to the collapse icon button. It could just have a pencil for an icon.
That way, the button wouldn’t need to be hidden anymore.
Should I be showing the comment form by default on ideas#show?
Should I be showing the comment form by default on ideas#show?
To avoid scrolling past content, I could remove the autofocus on the textarea unless a certain query parameter is given.
#1886·Dennis HackethalOP, about 2 months agoShould I be showing the comment form by default on
ideas#show?
The ‘Revise…’ button is hidden when the comment form is open. It makes sense to hide it because it doesn’t belong in that context. But once hidden, the user has no quick way to revise an idea. Maybe the first thing they want to do after opening ideas#show is not comment but revise.
#1886·Dennis HackethalOP, about 2 months agoShould I be showing the comment form by default on
ideas#show?
Then the autofocus on the textarea would force a scroll basically to the bottom of the page. For sufficiently long ideas, that means scrolling past content the user wants to see.
Should I be showing the comment form by default on ideas#show?
#1877·Dennis HackethalOP, about 2 months agoThat would probably be stretching the capabilities of Stimulus…
Could probably use Turbo frames instead.
#1869·Dennis HackethalOP, about 2 months agoThe red ‘Criticized’ label could be clickable and filter the displayed comments ‘in place’.
That would probably be stretching the capabilities of Stimulus…
#1865·Dennis HackethalOP, about 2 months agoThe red ‘Criticized’ label shows how many outstanding criticisms an idea has. For example ‘Criticized (5)’ means the idea has five outstanding criticisms.
But if there are lots of comments, including non-criticisms and addressed criticisms, it’s hard to identify outstanding criticisms.
There should be an easy way to filter comments of a given idea down to only outstanding criticisms.
There could be a separate button to filter comments down.
#1865·Dennis HackethalOP, about 2 months agoThe red ‘Criticized’ label shows how many outstanding criticisms an idea has. For example ‘Criticized (5)’ means the idea has five outstanding criticisms.
But if there are lots of comments, including non-criticisms and addressed criticisms, it’s hard to identify outstanding criticisms.
There should be an easy way to filter comments of a given idea down to only outstanding criticisms.
The red ‘Criticized’ label could be clickable and filter the displayed comments ‘in place’.
The red ‘Criticized’ label could be clickable and lead to a filtered version of ideas#show.
The red ‘Criticized’ label could be a link leading to a filtered version of ideas#show.
#1865·Dennis HackethalOP, about 2 months agoThe red ‘Criticized’ label shows how many outstanding criticisms an idea has. For example ‘Criticized (5)’ means the idea has five outstanding criticisms.
But if there are lots of comments, including non-criticisms and addressed criticisms, it’s hard to identify outstanding criticisms.
There should be an easy way to filter comments of a given idea down to only outstanding criticisms.
The red ‘Criticized’ label could be clickable and lead to a filtered version of ideas#show.
The red ‘Criticized’ label shows how many outstanding criticisms an idea has. For example ‘Criticized (5)’ means the idea has five outstanding criticisms.
But if there are lots of comments, including non-criticisms and addressed criticisms, it’s hard to identify outstanding criticisms.
There should be an easy way to filter comments of a given idea down to only outstanding criticisms.
#1845·Dennis HackethalOP revised about 2 months agoThere should be a feature similar to the ‘single comment thread’ feature Reddit has, where you start with some deeply nested child idea and render all of its deeply nested parents above it:
G /|\ P1 P2 P3 \|/ IThis feature would be great for seeing an idea in its proper context without having to scroll past a bunch of potentially unrelated ideas.
For parent ideas, cycle only through revisions that lead to the target idea. Communicate accordingly in the UI. For the target idea, its children, and any of its siblings’ children, cycle through all revisions.
Every idea should have a link to a separate page with the single comment thread. This could just be ideas#show. That page should also scroll the target idea into view in case its preceded by too much context that would otherwise push it below the viewport.
This feature would also allow me to remove the buggy ‘context’ feature.
Implemented as of 632c0d7.
There should be a feature similar to the ‘single comment thread’ feature Reddit has, where you start with some deeply nested child idea and render all of its deeply nested parents above it:
G
/|\
P1 P2 P3
\|/
I
This feature would be great for seeing an idea in its proper context without having to scroll past a bunch of potentially unrelated ideas.
For parent ideas, cycle only through revisions that lead to the target idea. Communicate accordingly in the UI. For the target idea, its children, and any of its siblings’ children, cycle through all revisions.
Every idea should have a link to a separate page with the single comment thread. This could just be ideas#show.
This feature would also allow me to remove the buggy ‘context’ feature.
There should be a feature similar to the ‘single comment thread’ feature Reddit has, where you start with some deeply nested child idea and render all of its deeply nested parents above it:
G
/|\
P1 P2 P3
\|/
I
This feature would be great for seeing an idea in its proper context without having to scroll past a bunch of potentially unrelated ideas.
For parent ideas, cycle only through revisions that lead to the target idea. Communicate accordingly in the UI. For the target idea, its children, and any of its siblings’ children, cycle through all revisions.
Every idea should have a link to a separate page with the single comment thread. This could just be ideas#show. That page should also scroll the target idea into view in case its preceded by too much context that would otherwise push it below the viewport.
This feature would also allow me to remove the buggy ‘context’ feature.
#1841·Dennis HackethalOP revised about 2 months agoThere should be a feature similar to the ‘single comment thread’ feature Reddit has, where you start with some deeply nested child idea and render all of its deeply nested parents above it:
G /|\ P1 P2 P3 \|/ IThis feature would be great for seeing an idea in its proper context without having to scroll past a bunch of potentially unrelated ideas.
For parent ideas, cycle only through revisions that lead to the target idea. Communicate accordingly in the UI. For the target idea, its children, and any of its siblings’ children, cycle through all revisions.
Every idea should have a link to a separate page with the single comment thread. This could just be ideas#show.
This feature would also allow me to remove the buggy ‘context’ feature.
The target idea should be scrolled into view. Otherwise, it might not always be visible, which could cause confusion. See eg #1811, which is preceded by a long idea and thus not visible on page load at the time of writing.
#1841·Dennis HackethalOP revised about 2 months agoThere should be a feature similar to the ‘single comment thread’ feature Reddit has, where you start with some deeply nested child idea and render all of its deeply nested parents above it:
G /|\ P1 P2 P3 \|/ IThis feature would be great for seeing an idea in its proper context without having to scroll past a bunch of potentially unrelated ideas.
For parent ideas, cycle only through revisions that lead to the target idea. Communicate accordingly in the UI. For the target idea, its children, and any of its siblings’ children, cycle through all revisions.
Every idea should have a link to a separate page with the single comment thread. This could just be ideas#show.
This feature would also allow me to remove the buggy ‘context’ feature.
Implemented as of 55d02a7.
There should be a feature similar to the ‘single comment thread’ feature Reddit has, where you start with some deeply nested child idea and render all of its deeply nested parents above it:
G
/|\
P1 P2 P3
\|/
I
This feature would be great for seeing an idea in its proper context without having to scroll past a bunch of potentially unrelated ideas.
Cycling through revisions on the parent level might hide the idea but that in itself isn’t a big deal: the user can just refresh the page anytime they quickly want to find their way back to the idea.
Every non-top-level idea should have a link to a separate page with the single comment thread.
This feature would also allow me to remove the buggy ‘context’ feature.
There should be a feature similar to the ‘single comment thread’ feature Reddit has, where you start with some deeply nested child idea and render all of its deeply nested parents above it:
G
/|\
P1 P2 P3
\|/
I
This feature would be great for seeing an idea in its proper context without having to scroll past a bunch of potentially unrelated ideas.
For parent ideas, cycle only through revisions that lead to the target idea. Communicate accordingly in the UI. For the target idea, its children, and any of its siblings’ children, cycle through all revisions.
Every idea should have a link to a separate page with the single comment thread. This could just be ideas#show.
This feature would also allow me to remove the buggy ‘context’ feature.
#1837·Dennis HackethalOP revised about 2 months agoThere should be a feature similar to the ‘single comment thread’ feature Reddit has, where you start with some deeply nested child idea and render all of its deeply nested parents above it:
G /|\ P1 P2 P3 \|/ IThis feature would be great for seeing an idea in its proper context without having to scroll past a bunch of potentially unrelated ideas.
Cycling through revisions on the parent level might hide the idea but that in itself isn’t a big deal: the user can just refresh the page anytime they quickly want to find their way back to the idea.
Every non-top-level idea should have a link to a separate page with the single comment thread.
This feature would also allow me to remove the buggy ‘context’ feature.
Every non-top-level idea should have a link to a separate page with the single comment thread.
Might as well go with top-level ideas, too. That way, when there are other top-level ideas, they get filtered out. Good for zeroing in.
#1837·Dennis HackethalOP revised about 2 months agoThere should be a feature similar to the ‘single comment thread’ feature Reddit has, where you start with some deeply nested child idea and render all of its deeply nested parents above it:
G /|\ P1 P2 P3 \|/ IThis feature would be great for seeing an idea in its proper context without having to scroll past a bunch of potentially unrelated ideas.
Cycling through revisions on the parent level might hide the idea but that in itself isn’t a big deal: the user can just refresh the page anytime they quickly want to find their way back to the idea.
Every non-top-level idea should have a link to a separate page with the single comment thread.
This feature would also allow me to remove the buggy ‘context’ feature.
Cycling through revisions on the parent level might hide the idea but that in itself isn’t a big deal: the user can just refresh the page anytime they quickly want to find their way back to the idea.
During testing, I realized this behavior is more confusing than I had initially thought.
There should be a feature similar to the ‘single comment thread’ feature Reddit has, where you start with some deeply nested child idea and render all of its deeply nested parents above it:
G
/|\
P1 P2 P3
\|/
I
Cycling through revisions on the parent level might hide the idea but that in itself isn’t a big deal: the user can just refresh the page anytime they quickly want to find their way back to the idea.
Every non-top-level idea should have a link to a separate page with the single comment thread.
This feature would also allow me to remove the buggy ‘context’ feature.
There should be a feature similar to the ‘single comment thread’ feature Reddit has, where you start with some deeply nested child idea and render all of its deeply nested parents above it:
G
/|\
P1 P2 P3
\|/
I
This feature would be great for seeing an idea in its proper context without having to scroll past a bunch of potentially unrelated ideas.
Cycling through revisions on the parent level might hide the idea but that in itself isn’t a big deal: the user can just refresh the page anytime they quickly want to find their way back to the idea.
Every non-top-level idea should have a link to a separate page with the single comment thread.
This feature would also allow me to remove the buggy ‘context’ feature.
There should be a feature similar to the ‘single comment thread’ feature Reddit has, where you start with some deeply nested child idea and render all of its deeply nested parents above it:
G
/|\
P1 P2 P3
\|/
I
Cycling through revisions on the parent level might hide the idea but that in itself isn’t a big deal: the user can just refresh the page anytime they quickly want to find their way back to the idea.
Every non-top-level idea should have a link to a separate page with the single comment thread.
This feature would also allow me to remove the buggy ‘context’ feature.
#1813·Dennis HackethalOP, about 2 months agoFor example, I had to manually notify Edwin in #1811 of a revision I had made to address a criticism of his. Without this notification, he might miss the revision. If he disagrees that the revision addresses his criticism, that’s a potential error that might not get corrected.
good idea!
#1812·Dennis HackethalOP, about 2 months agoWhen you revise an idea to address a criticism, its author should get a notification so they get a chance to verify that the revision really does address the criticism.
For example, I had to manually notify Edwin in #1811 of a revision I had made to address a criticism of his. Without this notification, he might miss the revision. If he disagrees that the revision addresses his criticism, that’s a potential error that might not get corrected.