Here, Julian is just enumerating, point by point ; what things system should respect, in his opinion.
That does not mean that interaction will be complicated.
The task is just about brush storage.
And in fact, it seems that brush storage will be handled by simple actions (click or double click in asset browser, right click menu on thumbnail).
That is what devs are focusing on but that is not really users main problem.
Users problem is brush access during a paint/sculpt session .
- Being able to specify shortcuts for several custom brushes of same category.
- Or only displaying a set of favorites brushes that is not relying on their category.
Like Pablo said, we don’t care about automatic previews.
Currently, I am experimenting crashes due to material previews.
I would like to avoid crashes related to brushes previews, too.
We asked devs to look at 2d software for UI of texture paint mode; and they took Photoshop UI default as an example.
Devs are focusing on storage because it is a critical point to handle hundreds of brushes.
But lack of quick access is the most critical point for users to handle a working session.
I don’t think that is a lack of communication. I think that is a misunderstanding that continues because of difficulty to maintain a discontinued discussion on a subject through months.
In a forum thread, posts accumulates quickly about different subjects.
Then devs read it, only retain a part of discussion, publish a task.
Then, comments on that task may deviate discussion on another subject.
Devs don’t know what is priority, anymore. They stop discussion to start on another task and reopen discussion after months.
I think there are misunderstanding happening on both sides. But mutual comprehension is probably happening a lot more often.
I think that paywalls will probably limit feedback and inspiration coming from community more than it would limit misunderstanding by limiting amount of participants to discussion.
There is a little bit of marketing in what Pablo Vasquez does. But he really is an experimented Blender User. If you have the feeling that there are many cases where he is not right ; it is because he is replying to a lot of questions in a period where Blender is evolving at light speed.
Anybody who tested an area, 3 days ago ; may have missed last changes that occurs, yesterday or today.
And I think that’s what happened to Pablo, several times.
But it is also true, that he can not be specialized in all fields. And he changed his show to include a guest that would be a specialist.
I agree. There is probably room for other people to help.
That is why there is a job offer for a blog writter.
https://www.blender.org/jobs/writer-editor-blogger/
On developer.blender.org, there are workboards per module triaging todos, bugs, design tasks.
In devtalk forums, thread title is supposed to bound terms of discussion.
That is up to users to stay on topic.
But probably sub-sections of user feedback section would help to avoid repeated threads on same subjects created by many users (users don’t use search before posting).
We already have developers coordinators trying to maintain coherence of module.
When they take decisions and share them to community through dev meeting notes or blog articles ; they are taking comments into account.
I don’t think that communication is bad. I think that is just really hard to content community of users that has an exponential growth about a development that has an increasing speed, too.
