[Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender  trunk/blender/source/blender: More logical ordering of Empty draw types.
Jason van Gumster
jason at handturkeystudios.com
Wed Feb 2 05:50:20 CET 2011
No doubts. I hope that there's no misunderstanding here. Blender is by far one
of the most documenter-friendly environments around. In fact, I'd go so far as
to say that we're pretty spoiled if things like this are all we have to
complain about. I'm well aware that defaults have changed before and I've
ridden the wave with those as well. My comment was that it's sometimes nice to
have a touch of warning when it comes to the more visible changes. Whether or
not that actually happens, I'll deal with it... and I'll probably deal with it
with a smile on my face.
The silver lining here is that the issue has been raised and addressed. In
other development communities, we might not even get that much. :)
Tony Mullen <tony.mullen at gmail.com> wrote:
> My $0.02:
> I'm with ZanQdo here. And I know very well how a last minute default
> change can screw up documentation. Large portions of my second book
> were seriously borked by the change to add objects in Object mode
> rather than Edit mode, which was a decision made after the first or
> second test build of the version had already been released. I got a
> lot of 1 star reviews on amazon over that! :(.
> For situations like that, at the stage of debug builds, I think
> changes should be as strictly as possible limited to debugging, and
> changes that affect workflow at that late stage should be seriously
> (re)considered and communicated.
> But we're not at that stage now, we're at beta, and at beta all kinds
> of things can change. And if the changes don't affect workflow (like
> the default draw of Empties) then I don't see much of an issue.
> Redoing screenshots isn't even necessary. Unless the book has already
> gone to press then one line of text can explain the different draw
> type. And if the book has gone to press, well, that's what happens
> when you write about beta software.
> Documenters (and learners) just need to live with that. A book isn't
> obsolete just because an icon looks different or an empty is drawn
> differently, and anybody who thinks it is should probably stay away
> from Blender books.
> > OK guys, no matter what, blender will not look the same in the future.
> > That is why you documenters always have new stuff to show right?
> > Greater changes are being made all the time, it's your job to keep up.
> > Of course I could have told about it in this list but I do believe
> > this is getting out of hand. Blender is continually being changed all
> > over the place. What I changed is only a default, I didn't remove the
> > draw option. I've changed tons of stuff like this in the past,
> > defaults and limits for settings everywhere, added options on the UI..
> > and all of them based on my experience working on blender everyday. I
> > don't think documentation has to be *perfectly* up to date either. You
> > are not teaching robots are you? With all that said, I will try to be
> > more communicative in the future but hope this doesnt become a
> > considerable limit for my efforts in blender
> > cheers
> > Daniel Salazar
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers