[Bf-committers] Re: [Bf-blender-cvs] CVS commit: blender/source/blender/src header_view3d.c space.c

[Toni Alatalo]

On Apr 3, 2006, at 5:46 PM, Campbell Barton wrote:

> Was just thinking.....

(always that, he does!)

> (do we have this alredy?)

some of it, yes.

> A wikipage,

well there is stuff on the normal website too,
and not all of it is totally outdated.

it even has that Linux NVIDIA flip x11 driver setting info!
(but it did not know, untill Ton showed me - even then i did not care  
to change the setting of course, the flicker was fun to see :p)

UPDATE: i now see Ton posted the link so i dont have to dig it anymore..

> "Introduction to blender development"
> - a page somebody could read in 5min and link to usefull areas.

feel free to start this in the BlenderDev wiki

>
> With Sections (in brief)
> * Blender development team, how blender is developed irc meetings  
> mailing list and the way maintainers own parts of the software.  
> Links to Blender history, Who's Who of maintainers (Letterrip?),  
> Mail archives and irc page.
> * Blender Languages- small paragraph- C/C++/Python... explain where  
> each language fits in.
> * Compiling Blender- Have a link to a tutorial for each OS.
> * Brief overview of the source, and some files to look at.  
> creator.c, space.c
> * Editing the source- ways to find the area in the source that you  
> need to edit- through DNA_* or space.c,  Note on coding style and  
> links to editors and source code browsers.
> * explain DNA in brief- link to the Ton's full doc.
> * What its a patch? Link to patch tracker and tut for making a patch.
> * Give some examples of features  to write- realy small bite  
> size.   Link to IPO Tutorial and some more comprehensive tutorials.
>   Your first patch could be... 10 or so examples.
> * Areas in Blender not to touch (because of internal design/or  
> complexity?) - Probably note on changing Blenders DNA is not for  
> beginners.
>
> Worth adding, alredy exists?
> - Cam
>
>
>
>
> Toni Alatalo wrote:
>> On Apr 3, 2006, at 5:20 PM, Campbell Barton wrote:
>>> On the flip side, it would be nice for patch writers to know what  
>>> parts not to rely on. BEFORE they write a patch. (some comments  
>>> in the code alredy hint at this)
>>> Its never nice to have your patch rejected because "FooBar Will  
>>> be rewritten anyhow", Especialy if
>>
>> i often have fun quoting Ton's side/throwaway sentences about  
>> certain areas of Blender needing a rewrite.
>>
>> my current favourite is the IPO system, so if/when someone  
>> implements IPO modifiers (like a wave effect), well, i guess  
>> you'll notice why it is in the list ;)
>>
>>> - Cam
>>
>> just my stoopid 2cents,
>> ~Toni
>>
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at projects.blender.org
>> http://projects.blender.org/mailman/listinfo/bf-committers
>>
>
>
> -- 
> Campbell J Barton
>
> 133 Hope Street
> Geelong West, Victoria 3218 Australia
>
> URL:    http://www.metavr.com
> e-mail: cbarton at metavr.com
> phone: AU (03) 5229 0241
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers