[Bf-docboard] Bf-docboard Digest, Vol 46, Issue 1

[Roger Wickes]

Hey, great to have you back! I would like to be responsible for the Manual pages, (which just broached 1,250,000 hits!) and have the authority to control content changes. Skin changes I could care less about. I keep a list of what needs to be done in the To-Do list at http://wiki.blender.org/index.php/Wiki_Tasks as you awesome coders keep adding features. 

I have long wanted to beef up the Reference and keep doco on each panel updated in there. An example of that is the new Stamp panel. However, I have not really bothered with Reference as I think with 2.50 that whole panel organization will re-boot. 

At this time I am entering a very busy period for the next 3 months, with a book and video deal, so I will be in quiet mode and just build a list and concepts and sandbox any changes, rather than actually making changes. I also don't want to put alot into something that will need a drastic overhaul (reference manual). 

Tutorials has issues with organization, but I havent really spent any time on it. The issue is that Blender is an integrated, full featured tool, so many tutorial are not about modeling or just about texturing, but span many functional areas. I envision a venn diagram kind of presentation, with application/use on one side (architecture, game, outdoors, CG scenes, compositing) and functionality (modeling, animation, rendering, post-pro) on the other axis. 

I cannot comment on BlenderDev. I have read reference manuals on software internals for applications my company has developed, and api docs for applications like websphere. Both of those are something like 90% different from what we have for Blender, so I cannot even begin to compare or comment. 

Scripts are core to Blender's extensibility and contains a very rich set of functionality that is sadly overlooked largely because the doco is disperate and poorly advertised and scant. Migius and Meta have done an incredible job there getting from nothing to 1.0, and I will do what I can to help them get to 2.0 level. 

Game Engine wiki doco is sad, and as i have said earlier, people just need to buy the new book. I make the comparison to the wiki pre-my involvement to what we have now, where just whole entire concepts and topics need to be written. 

As a separate issue, everyone keeps saying 2.5, and not 2.50. oh well. If it is as dramatic as everyone says, you might want to consider 3 and be consistent. 

I am surprised at all the questions i get on the forums caused by old tutorials and such due to relatively minor UI changes that have occurred. The UV unwrap from edit mode, for example. I'm thinking we need to archive(?) the pre-2.50 info somehow, or have an active search, if the UI of 2.50+ will be drastically different, since that material is already out there to stay. 

 ----------------
Sent by Roger Wickes for intended recipient. If you are not the intended recipient, please delete this message and contact Mr. Wickes immediately.


Atlantica Investments, Inc.
PO Box 680310, Marietta, GA 30068 USA


   1. Docboard re-activation (Ton Roosendaal)
_______________________________________________
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/20081110/08385c12/attachment.htm