|
|
nemesis wrote:
> Exactly. Blender feels to me closer to vi than anything else. You just
> press regular keys and contextual commands are issued.
Yeah. Some of the abbreviations are kind of unintuitive, along with the
linking between items and such. I need to link my ME: to my MA: or
something, and I spend an hour figuring out wtf that means. :-)
> Blender's official user-level documentation
> is a wiki so it may simply not have catched up with source modifications.
Yes. That's what boggles my mind - that you'd start coding some changes
without first writing down anywhere what the changes are supposed to
accomplish. If you add a new button to the interface, is it hard to write
three sentences describing what the button does? It doesn't have to be
complete professional-grade documentation, but at least tell people what the
abbreviations on the buttons stand for so someone else can write the
documentation. :-)
If users have to read the code to figure out what it does, you're doing it
wrong. But of course, this is pretty much SOP with free code - why would
you document it if you wrote the code yourself to be used by yourself? It's
a strange world, popular complex software developed for free by the whim of
volunteers.
--
Darren New, San Diego CA, USA (PST)
"Ouch ouch ouch!"
"What's wrong? Noodles too hot?"
"No, I have Chopstick Tunnel Syndrome."
Post a reply to this message
|
|