Right Click Select: Duplicates management proposal (UI Mockup/Improves feature request construction)
Hello guys. I would like to propose a small panel that displays the duplicate information of a specific post.
One good thing about duplicates are there could be a chance where it obviously is a duplicate but It has been explained much better or has much improvements compared to the original one.
There could also be newer features that the original proposal has missed and the new duplicate has proposed some details that would supposedly be the better option. I guess that would be considered brainstorming of ideas already. Teamwork can help create better results.
This feature will display the:
- Number of duplicates.
- Total upvotes of duplicates (Although this is not an accurate representation of the duplicate data, I guess it would be nice to see how many times this proposal has been upvoted already).
- Sort duplicates by number of votes, and date posted.
Mockup number 1 : The duplicate stats panel can be minimized for a cleaner UI.
Mockup number 2: This is how the duplicates panel looks when the user clicked the maximize button.
Mockup 3: The duplicates panel can also be place at the side when the UI is opened in center view mode (as an optional feature).
I am not sure if you guys would agree with the mockup but I would like to post this anyways. Maybe this can encourage some other users to create their own proposal about how duplicate information can be handled.
Thanks.
17 Comments
and yours is a duplicate of a post which was posted recently: blender.community/c/rightclickselect/j7dbbc/
* @pipeliner * That would be hilarious. I forgot to look if there are duplicates with this one. Thanks I will look into it.
* @johnpdelacruz26 * please search before you post.
* @pipeliner * I am not saying that my idea is better but the slippery slope here is that what if there is a specific duplicate proposal but it has some additional details and improvements that the original proposal have missed? Should we just ignore those confirmed properties that are technically better and has more details just because it is a duplicate?
Declaring something a duplicate is fine but sometimes the direction it is heading is not so realistic and helpful for creating a better idea regarding a certain feature that is being proposed. A supposed to be improvement of an old proposal will be deleted just because it has been generalized as a duplicate.
As for my own experience I have already duplicated some post multilple times but I have observed that most of the time the reason for being declared a duplicate is too general and the details are often different and the chance for the implementation steps to be similar is not always the same.
Lastly, preserving the duplicates can be also benefitial to those old proposals which haven't gained some votes for some specific reasons like being too messy, not presented the right way, the details are not what the users like, the implementations are not practical and more. If a new proposal has been made and it is seen as a duplicate to the original post that haven't gained some support, there is a chance that this feature might be well recieved this time because it has been presented and implemented in a much better way that many users support.
I would prefer to just kill duplicates
* @momotron2000 * You have a point. What about a vote button for duplicate posts so that the website host or handler(I forgot the name of that occupation) can easily determine if that post is a confirmed duplicate. This can be added in the development status drop down menu.
There are two things which I think can be a good solution:
a.) After a post has been declared a duplicate, the regular vote button for the specific duplicate can be now disabled and a link to the original can will be given.
b.) Another way would be just to allow the users to u[vote the duplicate post but the upvotes will be added to the original one and not the duplicate.
Regarding the downvote, A link will be given to the orginal one so that they can evaluate and determine if the said proposal would deserve a downvote.
* @momotron2000 * One good thing about duplicates are there could be a chance where it obviously is a duplicate but It has been explained much better or has much improvements compared to the original one.
There could also be newer features that the original proposal has missed and the new duplicate has proposed some details that would supposedly be the better option. I guess that would be considered brainstorming of ideas already.
* @momotron2000 * I agree. Just delete duplicates to keep this forum as clean as possible.
* @pipeliner * How about deleting the entire duplicates in the right click selectenvironment but placing ut insidw this kind of new panel which can be minimized to keep the ui clean?
* @johnpdelacruz26 * maybe but people should start to learn to search before posting. Maybe the duplicate can be added as a comment or something like that
* @momotron2000 * I have also thought of that but again the chance of this new proposal that would suppose to be the improvement of the old one will still be hidden under the guise of the old proposal that other users that have voted it down alaready and there could be a possibility that the new proposal will make them reverse their decision into an upvote.
* @momotron2000 *Also duplicates can sometimes act as indicator for the developers to determine the specific feature's demand among the blender community.
* @johnpdelacruz26 * a high vote count and detailed discussion in one thread helps a lot more than clicking in x single feature requests
* @momotron2000 * Higher vote counts is another topic what I am encouraging is the preservation of duplicates. Instead of being beneficial, deleting it permanently can hamper new ideas about a certain feature and may also slow down the things like we can consider as some significant enhancements/improvements or refinements.
Even in business, constant boatloads of ideas are helpful. This thing promotes further innovation.
* @johnpdelacruz26 * why are you defending that people should not use the search function in the beginning and add their feedback if the topic is already posted? Think about the Devs - they don't have time to go to multiple sites
* @pipeliner * You are missing the point that I am trying to explain. There would be case where some users might have already double checked if there is already a proposal that has some similarities with what they are planning to post but they just created their own instead because of some technical and artistic reasons and differences. This is not a case for having the same general idea but about the specifics/details regarding the subject which in result can create a better outcome for the said feature and may also develop and evolve to it's greater possibility.
That is why what I am trying to request that further review should be practiced and not instantly declare it as a duplicate and delete permanently. If it is a definite duplicate, without any new additions or presentations then by all means we can remove it indelibly.
* @johnpdelacruz26 * if it has some technical and artistic reasons and differences then it's not a duplicate