If you hit 'reply' it opens the window for typing a reply (but doesn't reply to the post you click it on, just replies to the thread at large) If you change your mind, it would be nice to have a 'Cancel' button next to the 'post' button to close out the edit window.
Also, the forum pages start to ignore input if you have a reply window and try to click something else, and I have to reload the page to get it moving again
I agree with you DxJxC, I wish replies would either nest below the comment you're replying to, or automatically append the message with something like "Replying to X"
Your browser will warn you when you leave the page after not sending a reply, because it's considered an active field after you've written in it, taking an extra act to continue browsing. I get that you don't see this as important, but adding a cancel/close button is a small effort for a developer and will make the user's experience more smooth.
No effort by a developer is a small effort. Firstly, you're assuming their forum is bespoke software made in house and not a white label suite made by another developer.
I'm assuming it's an open source one. But sure, if it's closed source white label, it might not be possible, then it is what it is. But if they do have control, it is a small effort, comments like "no effort by a developer is a small effort" are pretty dishonest.
I work in development and "no effort is a small effort" is very much true. Even a minor change requires testing, deployment, rollback strategies, downtime etc. It's not dishonest, it's the honest truth.
Oh, you're being like that... I know, I work in development too and I've worked in each of the roles involved in the pipeline. I was saying it from a developer point of view, but let me restate it then to make you happy, the change is a relatively small effort.
No need to be condescending, I was just responding to you calling me dishonest and I was highlighting the fact that I wasn't just pulling my point of view out of nowhere. I have personal experience (as a QA manager specifically) of a 'small change' causing big issues, on multiple occasions, so I found being called dishonest for referring to my own personal experience somewhat insulting.
I didn't intend to imply you were being purposely dishonest, my apologies. I was merely attempting to convey the statement itself has an inherit dishonesty and I didn't take the time to properly elaborate, my bad.
Yes, development of any feature takes multiple steps (and usually people) to get to production safely. However that can be said about many things outside of development too, using that to say a change is never small is unfair and ignores any proportionality to the overarching scope. With a project this size it could have issues multiple times and still be a minor effort compared to other features in development.
As for being condescending. I thought it was warranted (just a bit of banter, not being mean spirited). 😉 <-- I should use these more.
Now to get back to the actual subject. Assuming it's even possible to change, is this something DDB would want to allocate resources to at this point? Probably not. Is it something they might want to tackle later on? I would think so. And even if not, any improvement to the user experience should at least be considered, which is why I wanted to add my two cents to a thread that felt a bit dismissive.
As for the reply window, it takes up space and makes the experience more cluttered. Plus it's really easy to get the wrong box when scrolling around for reference.
Plus, the same issue is in the discussion section under all the monsters.
No effort by a developer is a small effort. Firstly, you're assuming their forum is bespoke software made in house and not a white label suite made by another developer.
This isn't true at all. They could bother to take the small effort of updating their change or defect tickets, or unit testing, or commenting their code and they often don't do these small things that lead to huge time expenditures for other people with code maintenance problems, making the rest of the team delay due to having to resolve audit findings, and a host of other small tasks that take devs a couple of minutes, but when they skip it costs people downstream to waste multiple hours in tracking it down or resolving audit findings during reviews. Sometimes they forget to hit 'commit' or include required verbiage in their checkin comments, etc. So yeah there's a lot of small actions taken by develoeprs.
And out of the box forum software is customizable. Likely there's a setting already there that just has to be activated, esp for something like this.
If I hit 'reply' but meant to hit 'quote' I would like to be able to switch to 'quote' mode. As it is, it's a hassle to say 'oops, forgot the quote button' So yeah this makes the interface cumbersome sometimes.
Now to get back to the actual subject. Assuming it's even possible to change, is this something DDB would want to allocate resources to at this point? Probably not. Is it something they might want to tackle later on? I would think so. And even if not, any improvement to the user experience should at least be considered, which is why I wanted to add my two cents to a thread that felt a bit dismissive.
The success of a public facing product hinges very heavily on UX design. If a product is amazingly featured and powerful and robust and high-performing, but the UI is a hassle, then an objectively functionally inferior competitor with a great UI will blow them out of the water in the market. So yeah, none of these kinds of updates are glamorous, but an annoyed customer is a lost customer, and too many irritating quirks in a UI can and will drive them to a competitor. In this case, they may just choose not to use the forums, and their contributions may never happen. That's a soft factor, but it's a factor.
The success of a public facing product hinges very heavily on UX design. If a product is amazingly featured and powerful and robust and high-performing, but the UI is a hassle, then an objectively functionally inferior competitor with a great UI will blow them out of the water in the market. So yeah, none of these kinds of updates are glamorous, but an annoyed customer is a lost customer, and too many irritating quirks in a UI can and will drive them to a competitor. In this case, they may just choose not to use the forums, and their contributions may never happen. That's a soft factor, but it's a factor.
I absolutely agree, knowing DDB I'm just not so sure they would want to allocate a developer to it at this point. As for their reasoning, I do not know, but will assume it is sound.
If, however, it's a feature that just needs enabling, as you suggested a few posts up. They'd do good to enable it soon to not annoy users any longer than need be.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
If you hit 'reply' it opens the window for typing a reply (but doesn't reply to the post you click it on, just replies to the thread at large) If you change your mind, it would be nice to have a 'Cancel' button next to the 'post' button to close out the edit window.
Also, the forum pages start to ignore input if you have a reply window and try to click something else, and I have to reload the page to get it moving again
You can just leave the page or ignore the reply field, I don't see why a cancel button is needed?
As for your other issue, what browser are you using? I'm not getting that problem
Find my D&D Beyond articles here
I do wish the reply option would indicate itself as such within the post.
But besides that, it works fine. I ignore it if I change my mind, and it doesn't mess with the page.
I agree with you DxJxC, I wish replies would either nest below the comment you're replying to, or automatically append the message with something like "Replying to X"
Find my D&D Beyond articles here
Your browser will warn you when you leave the page after not sending a reply, because it's considered an active field after you've written in it, taking an extra act to continue browsing. I get that you don't see this as important, but adding a cancel/close button is a small effort for a developer and will make the user's experience more smooth.
No effort by a developer is a small effort. Firstly, you're assuming their forum is bespoke software made in house and not a white label suite made by another developer.
Find my D&D Beyond articles here
I'm assuming it's an open source one. But sure, if it's closed source white label, it might not be possible, then it is what it is. But if they do have control, it is a small effort, comments like "no effort by a developer is a small effort" are pretty dishonest.
I work in development and "no effort is a small effort" is very much true. Even a minor change requires testing, deployment, rollback strategies, downtime etc. It's not dishonest, it's the honest truth.
Find my D&D Beyond articles here
Oh, you're being like that... I know, I work in development too and I've worked in each of the roles involved in the pipeline. I was saying it from a developer point of view, but let me restate it then to make you happy, the change is a relatively small effort.
No need to be condescending, I was just responding to you calling me dishonest and I was highlighting the fact that I wasn't just pulling my point of view out of nowhere. I have personal experience (as a QA manager specifically) of a 'small change' causing big issues, on multiple occasions, so I found being called dishonest for referring to my own personal experience somewhat insulting.
Find my D&D Beyond articles here
I didn't intend to imply you were being purposely dishonest, my apologies. I was merely attempting to convey the statement itself has an inherit dishonesty and I didn't take the time to properly elaborate, my bad.
Yes, development of any feature takes multiple steps (and usually people) to get to production safely. However that can be said about many things outside of development too, using that to say a change is never small is unfair and ignores any proportionality to the overarching scope. With a project this size it could have issues multiple times and still be a minor effort compared to other features in development.
As for being condescending. I thought it was warranted (just a bit of banter, not being mean spirited). 😉 <-- I should use these more.
Now to get back to the actual subject. Assuming it's even possible to change, is this something DDB would want to allocate resources to at this point? Probably not.
Is it something they might want to tackle later on? I would think so. And even if not, any improvement to the user experience should at least be considered, which is why I wanted to add my two cents to a thread that felt a bit dismissive.
Chrome
As for the reply window, it takes up space and makes the experience more cluttered. Plus it's really easy to get the wrong box when scrolling around for reference.
Plus, the same issue is in the discussion section under all the monsters.
This isn't true at all. They could bother to take the small effort of updating their change or defect tickets, or unit testing, or commenting their code and they often don't do these small things that lead to huge time expenditures for other people with code maintenance problems, making the rest of the team delay due to having to resolve audit findings, and a host of other small tasks that take devs a couple of minutes, but when they skip it costs people downstream to waste multiple hours in tracking it down or resolving audit findings during reviews. Sometimes they forget to hit 'commit' or include required verbiage in their checkin comments, etc. So yeah there's a lot of small actions taken by develoeprs.
And out of the box forum software is customizable. Likely there's a setting already there that just has to be activated, esp for something like this.
If I hit 'reply' but meant to hit 'quote' I would like to be able to switch to 'quote' mode. As it is, it's a hassle to say 'oops, forgot the quote button' So yeah this makes the interface cumbersome sometimes.
The success of a public facing product hinges very heavily on UX design. If a product is amazingly featured and powerful and robust and high-performing, but the UI is a hassle, then an objectively functionally inferior competitor with a great UI will blow them out of the water in the market. So yeah, none of these kinds of updates are glamorous, but an annoyed customer is a lost customer, and too many irritating quirks in a UI can and will drive them to a competitor. In this case, they may just choose not to use the forums, and their contributions may never happen. That's a soft factor, but it's a factor.
I absolutely agree, knowing DDB I'm just not so sure they would want to allocate a developer to it at this point. As for their reasoning, I do not know, but will assume it is sound.
If, however, it's a feature that just needs enabling, as you suggested a few posts up. They'd do good to enable it soon to not annoy users any longer than need be.