But that’s a bit unfair to people like Matt who do want their interface design to serve as many users as possible, not just his own design feel. Or theeth making widgets and other transform locking possible.
Their motivation might be internal, but that does not mean they don’t want to implement gui/ui that’s loved by their public.
Sure, a total GUI/UI makeover is very much wanted but very very difficult to realize… The obstacles are not difficult to invision. There are 2 possible ways: 1. revolution, 2. evolution.
-
revolution. Make a blender 3.0 from scratch…
This would need a very well organized production team. And unpaid open source projects don’t tent to be able to do things like this. That said Firefox is a good example that it can be done. Then again, rendering a html document is far easier then creating an html editor… Not even talking about a 3d animation suite.
-
evolution. Change blender is little steps.
That has dna/cancer pitfalls. Surgeons need to make sure growing lumbs are good lumbs and not bad lumbs. And some old postatics need to be removed. And some new postatics need to be made to fit better.
What does that mean for the documentation?
In an ideal world the documentation is written before the feature is implemented. Giving people with knolledge of blender the oportunity to comment on the concept, and help on how to implement the Gui (time is in frames not seconds in decimals, start and end frames are in the render window, please do not create new buttons with the same information, etc. )
This is not what we see alot. It’s or: “He you, write this feature” or “He you, I’ve made this feature”.
Lot’s of documentation is on micro level. Even made by the developers. More people are needed that show overview vision, and they need to get empowerment by the dictator. Ton’s been complaining for years now at the bconf that he needs more organisational power (meaning people who want to organize things for him), but I don’t think he’s ready yet to get those people in, because it’s to difficult for him to give them real empowerment. (Last time the empowered almost killed his creation, so no blaim there).
The best way to go, I think, is two ways:
Write documentation on macro level. Write about animation, modeling, styling, and o yes, btw, blender has this and this ui and gui concept, so you can do in this and this way. The “click here” and “press that” approach is not going to generate great artists… Great hobbiests, but not great artists. So maybe tell dummies to stick with their version might help to.
And,… now comes the hard part: New features need to be turned OFF by default in the official release. I don’t care about CVS, that can be full of nonsens and crashing and stuff, but people who want a new version with BUG FIXES don’t want there selection (for example) to be changed because some guy thinks his 120 hours of coding is worth more effort then the 12000 hours of users trying to figure out why they can’t select their verteces anymore. Don’t do revolution tactics on an evolution process!
just my 4 cents.
keep up the good work IamInnocent