[Bf-docboard] Bf-docboard Digest, Vol 62, Issue 2
Ivan Paulos Tomé
greylica at gmail.com
Fri Mar 5 15:50:03 CET 2010
I've e-mailed before, but my mails didn't appeared in the list, I don't know
what
exactly happened, or I don't know how to mail fro the list.
I'm sending again the first Text.
From: Ivan Paulos Tomé. A.K.A. Greylica !
Hi Ton, Hi Friends, Good Vibes !!!!
About Big Manuals.
I agree with the Idea of a big Manual, since I've learned Blender from the
2.3 Reference Guide.
There are some tutorials, but the technical resources is what I'm looking
for every time
I read the book, and they are well organizated.
Our colleague Ira said that the noobs to Blender won't use those books, OK,
OK.
Some noobs prefer Video Tutorials, some other prefer Manuals,
And some prefer 'osmosis' like things..... kkk (kumbaia related ???).
But the main thing, I see, is the fact that when we have a big Manual, full
of
engineering resources, it serve as a basis for another books, wikibooks, and
so on.
For me, a 2.6 Reference Guide (I guess it will took 2 volumes, 400~600
pages), with a 2.5 Python Guide
(300~500 pages), will serve as the main basis for everything starting from
scratch or not.
It's a must have, noob or pro.
Noobs -> use other resources to start using Blender.
They can start looking in the net, there are plenty of Blender resources,
buy the book to study !
Pros -> use those to create content for noobs, and related works, Wiki based
or not.
When you learn how to fly with an airplane, you have to learn (at least
some)
technical resources, someone created those. I'd prefer a full printed Manual
with
those blender software engineers explaining what they did...
I guess we should put energy helping coders/software engineers to explain
how those
features work, and ask them help to better explain those.
About Organization:
I'd think Ton is sseking ways or new Ideas to facilitate to readers to
absorb knowledge.
And then he is open to new Ideas about how to write a new Reference Guide.
I have one:
We can change the reading behavior of the fisrt Reference Guide a little,
for example,
we could do three sections to every issue and a fourth, Techincal resources,
example:
Noob, Average, Pro. (Iconified...)
Noob: Basics about tools/features
Average: Using tools/features
Pro: Examples of the interaction between tools/features explained and
another Blender resources
Technical Resources:
As the name implies, this is a section explaining the numeric limits of the
tool/feature,
How the buttons work, etc, etc.
Course, this will turn out to be a BIG BIG BIG challenge to write, but, it's
only an Idea...
Thank's
Ivan Paulos Tomé - Greylica - Brazil.
2010/3/5 <bf-docboard-request at blender.org>
> Send Bf-docboard mailing list submissions to
> bf-docboard at blender.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.blender.org/mailman/listinfo/bf-docboard
> or, via email, send a message with subject or body 'help' to
> bf-docboard-request at blender.org
>
> You can reach the person managing the list at
> bf-docboard-owner at blender.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Bf-docboard digest..."
>
>
> Today's Topics:
>
> 1. Re: Blender books -> official reference (Mike Belanger)
> 2. Re: Blender books -> official reference (Ton Roosendaal)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 4 Mar 2010 20:31:29 -0600
> From: Mike Belanger <mikejamesbelanger at gmail.com>
> Subject: Re: [Bf-docboard] Blender books -> official reference
> To: Blender Documentation Project <bf-docboard at blender.org>
> Message-ID: <CB26058B-39A3-4162-80CF-4AD7EA813105 at gmail.com>
> Content-Type: text/plain; charset="us-ascii"
>
> I think both books and wikis can coexist. The Wiki should focus on
> documenting
> features, sort of a glossary of tools, settings, etc. It'd be generic,
> just tells you what's what.
> But it should be complete, and consistent.
>
> Books on the other had, could have specific tutorials, with specific steps,
> and settings.
>
> That way, people have a consistent, reliable online source for features,
> but can get
> more specific tutorials if they buy a book.
>
>
>
> Mike Belanger ( Mikahl )
> www.watchmike.ca
>
>
>
>
>
> On 2010-03-03, at 7:55 AM, Ira Krakow wrote:
>
> > Hi Ton,
> >
> > Your idea about a Reference Guide is an excellent one. The problem,
> however, is that one size doesn't fit all. Everyone has a different level
> of Blender knowledge, so that something one person might think is too self
> evident might be new information for someone else.
> >
> > For example, how should Blender 2.5 Python be documented? If someone
> already knows the principles of OOP, classes, methods, attributes,
> inheritance, and so on, and knows Python, then the current API
> documentation, which lists the classes and methods, is just fine. If
> someone doesn't understand OOP, or, for that matter, is new to programming,
> the current documentation is insufficient and a reference guide would have
> an entirely different look.
> >
> > This principle works with other parts of Blender. Do we expect users of
> the animation reference to be seasoned 3D animators, or do they need a
> reference to animation basics as well? The same goes for rigging, lighting,
> texturing, etc., etc.
> >
> > I think we need, instead of one comprehensive reference guide, a series
> of guides for different aspects of Blender, geared for different levels of
> user. The "Noob to Pro" book is an excellent first step to get beginners up
> to speed, but we can't really expect everyone to be expert in all aspects of
> Blender. So perhaps I'm suggesting a series of reference guides?
> >
> > These are just some preliminary thoughts, to start the conversation. The
> goal is a very worthy one.
> >
> > Best wishes,
> > Ira
> >
> >
> >
> >
> >
> >
> > On Wed, Mar 3, 2010 at 8:14 AM, Ton Roosendaal <ton at blender.org> wrote:
> > Hi all,
> >
> > Writing Blender books for (commercial) publishers is already a good
> > and common bizz nowadays. I can only recommend anyone who is
> > interested in this to contact publishers with good plans!
> >
> > Blender Foundation is also publisher, we did this initially also to
> > open up the market for Blender in bookstores. That's not really needed
> > anymore. :)
> >
> > What would be useful though is still:
> > - have about one book published per year to get additional income
> > - support the current active documentation volunteers
> > - have good quality, open and free docs in wiki.
> >
> > I'd like to get two projects running for this.
> > One is for an updated "Blender Essential 2.5" book, for that I'll
> > first work with the team who has done the first Essential book.
> >
> > Another project is to check on the feasibility for a good (annual?)
> > printed reference guide. Check for example how the 2.3 guide reference
> > was done, I still think a good example of useful reference content for
> > users (includes screenshots etc).
> > Would there be a useful and efficient way to organize this? To get
> > both a great printed book as content for wiki? How? Who? :)
> >
> > Thanks,
> >
> > -Ton-
> >
> > ------------------------------------------------------------------------
> > Ton Roosendaal Blender Foundation ton at blender.org www.blender.org
> > Blender Institute Entrepotdok 57A 1018AD Amsterdam The Netherlands
> >
> > _______________________________________________
> > Bf-docboard mailing list
> > Bf-docboard at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-docboard
> >
> >
> >
> > --
> > Watch my Blender 3D videos:
> > http://www.youtube.com/irakrakow
> >
> > Subscribe to my Blender 3D forum:
> > http://forum.irakrakow.com
> > _______________________________________________
> > Bf-docboard mailing list
> > Bf-docboard at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-docboard
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.blender.org/pipermail/bf-docboard/attachments/20100304/2dcd9f2c/attachment.html
>
> ------------------------------
>
> Message: 2
> Date: Fri, 5 Mar 2010 11:04:53 +0100
> From: Ton Roosendaal <ton at blender.org>
> Subject: Re: [Bf-docboard] Blender books -> official reference
> To: Blender Documentation Project <bf-docboard at blender.org>
> Message-ID: <0EC2F648-D848-4273-AC85-8AEF29EAF42A at blender.org>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
> Hi Ira,
>
> All valid points, but following your reasoning leads to the conclusion
> that specialized, clearly targeted books make most chance in a market.
> We know that already, and most publishers do that.
>
> If we take Python and the game engine separate, I think that what's
> left is quite comprehensive and interesting for a very solid
> reference. But we might also conclude that this reference, if
> presented well, already gives you a phonbook size volume that's not
> interesting anymore to print. :)
>
> So... instead of targeting on user interests or level, we can do a
> "series" of references based on logical separated features and modules
> in Blender.
>
> - UI configuration (screens, preferences, menus, hotkeys, etc)
> big subsection for Python ui scripts
> - Modeling, modifiers
> - Animation system
> - Material, lights, textures, uv, paint
> - rendering, composite, sequencer
>
> And of course
> - python api generics (operators, importers, integrating, etc)
> - Game engine
>
> Hrm... need to think this over too :)
>
> -Ton-
>
> ------------------------------------------------------------------------
> Ton Roosendaal Blender Foundation ton at blender.org www.blender.org
> Blender Institute Entrepotdok 57A 1018AD Amsterdam The Netherlands
>
> On 3 Mar, 2010, at 14:55, Ira Krakow wrote:
>
> > Hi Ton,
> >
> > Your idea about a Reference Guide is an excellent one. The problem,
> > however, is that one size doesn't fit all. Everyone has a
> > different level of Blender knowledge, so that something one person
> > might think is too self evident might be new information for someone
> > else.
> >
> > For example, how should Blender 2.5 Python be documented? If
> > someone already knows the principles of OOP, classes, methods,
> > attributes, inheritance, and so on, and knows Python, then the
> > current API documentation, which lists the classes and methods, is
> > just fine. If someone doesn't understand OOP, or, for that matter,
> > is new to programming, the current documentation is insufficient and
> > a reference guide would have an entirely different look.
> >
> > This principle works with other parts of Blender. Do we expect
> > users of the animation reference to be seasoned 3D animators, or do
> > they need a reference to animation basics as well? The same goes
> > for rigging, lighting, texturing, etc., etc.
> >
> > I think we need, instead of one comprehensive reference guide, a
> > series of guides for different aspects of Blender, geared for
> > different levels of user. The "Noob to Pro" book is an excellent
> > first step to get beginners up to speed, but we can't really expect
> > everyone to be expert in all aspects of Blender. So perhaps I'm
> > suggesting a series of reference guides?
> >
> > These are just some preliminary thoughts, to start the
> > conversation. The goal is a very worthy one.
> >
> > Best wishes,
> > Ira
> >
> >
> >
> >
> >
> >
> > On Wed, Mar 3, 2010 at 8:14 AM, Ton Roosendaal <ton at blender.org>
> > wrote:
> > Hi all,
> >
> > Writing Blender books for (commercial) publishers is already a good
> > and common bizz nowadays. I can only recommend anyone who is
> > interested in this to contact publishers with good plans!
> >
> > Blender Foundation is also publisher, we did this initially also to
> > open up the market for Blender in bookstores. That's not really needed
> > anymore. :)
> >
> > What would be useful though is still:
> > - have about one book published per year to get additional income
> > - support the current active documentation volunteers
> > - have good quality, open and free docs in wiki.
> >
> > I'd like to get two projects running for this.
> > One is for an updated "Blender Essential 2.5" book, for that I'll
> > first work with the team who has done the first Essential book.
> >
> > Another project is to check on the feasibility for a good (annual?)
> > printed reference guide. Check for example how the 2.3 guide reference
> > was done, I still think a good example of useful reference content for
> > users (includes screenshots etc).
> > Would there be a useful and efficient way to organize this? To get
> > both a great printed book as content for wiki? How? Who? :)
> >
> > Thanks,
> >
> > -Ton-
> >
> > ------------------------------------------------------------------------
> > Ton Roosendaal Blender Foundation ton at blender.org
> > www.blender.org
> > Blender Institute Entrepotdok 57A 1018AD Amsterdam The
> > Netherlands
> >
> > _______________________________________________
> > Bf-docboard mailing list
> > Bf-docboard at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-docboard
> >
> >
> >
> > --
> > Watch my Blender 3D videos:
> > http://www.youtube.com/irakrakow
> >
> > Subscribe to my Blender 3D forum:
> > http://forum.irakrakow.com
> > _______________________________________________
> > Bf-docboard mailing list
> > Bf-docboard at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-docboard
>
>
>
> ------------------------------
>
> _______________________________________________
> Bf-docboard mailing list
> Bf-docboard at blender.org
> http://lists.blender.org/mailman/listinfo/bf-docboard
>
>
> End of Bf-docboard Digest, Vol 62, Issue 2
> ******************************************
>
--
Drogas são coisas que não se pode nem se deve compartilhar.
Que tal compartilhar Linux ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20100305/6729c281/attachment-0001.htm
More information about the Bf-docboard
mailing list