Last meeting I agreed to work on some python introduction page since
the API reference. here is a first pass.
Id appreciate if people want to read through and make edits or suggest
areas to improve.
http://wiki.blender.org/index.php/BlenderDev/Blender2.5/PyAPI_Intro
I made this page as a wiki so
Hi, now that introductory tutorials and howto's-like documentation is
starting to be written down I'd suggest we bring up again the topic of
naming. I understand this could be seen as topic hijacking, but well...I
have a bomb!
Although pretty much settled all over the API there are still some
+1 for operators adopting dot syntax (idnames not C functions ofcourse).
If anyone didnt follow - this would mean naming all operators
identifiers "OBJECT_OT_select_all" into "object.select_all" in C.
This should also be done for panels and menus too.
On Sat, Jan 23, 2010 at 8:14 PM, Elia Sarti
eak, if it was renamed to e.g. "selection"?
> Datum: Sat, 23 Jan 2010 18:52:12 +0100
> Von: Campbell Barton
> An: bf-blender developers
> Betreff: [Bf-committers] Blender 2.5 Python API Introduction.
> Last meeting I agreed to work on some python introduction page sin
> - Renaming section "context" to e.g. "User selection (Context)" might help
> new users find/understand it faster, as "context" could mean anything if
> you're not so familiar with the API.
Hmm... I think that the idea of context is too important to link it to just
selection. It's important t
@Lars.
"integrate links" - This is mostly for other people to edit for a bit,
I intend to move this into sphinx eventually so wasnt interlinking
types much.
"break in flow" - Agree, I was getting impatient, it was late and I
was thinking of things people might want to know about the python api,
add
Campbell,
I haven't dived into the python api deep enough yet, but I like the
format you give here, which is:
* a specific objective/concept
- overview and blender objects
- how to connect from python (with working example)
- where to find more info
can we stick to this format all through th
> @Lars.
> "context" - This definitely needs more of an explanation but confusing
> with selection is not good IMHO.
Seems like "context" is more than just selection. You need to describe what it
includes, what you are supposed to do with it.
If you change some values in a mesh, it's clear what w
Spent some time making the sphinx intro page nicer and added Mathutils docs.
http://www.blender.org/documentation/250PythonDoc/
Also updated wiki docs on context and types.
On Mon, Jan 25, 2010 at 8:03 PM, Lars Krueger wrote:
>> @Lars.
>> "context" - This definitely needs more of an explanation
very cool. good job Campbell!
From: Campbell Barton
To: bf-blender developers
Sent: Wed, January 27, 2010 5:27:30 PM
Subject: Re: [Bf-committers] Blender 2.5 Python API Introduction.
Spent some time making the sphinx intro page nicer and added Mathutils
Would it be possible to add PDF/HTML bundle export or
at least autogenerated PDF/HTML as in
http://docs.python.org/3.1/download.html
for offline viewing?
On Shhinx page they say "Output formats: HTML (including Windows HTML
Help) and LaTeX, for printable PDF versions"
Thu, 28 Jan 2010 00:27:3
Heres PDF generated from sphinx 6.4
http://www.blender.org/documentation/250PythonDoc/250PythonDoc.pdf
if anyone would like to help out, these descriptions would be very
nice to be updated since they are closely related to writing your own
operators and panels.
http://www.blender.org/documentatio
Campbell Barton wrote:
> Heres PDF generated from sphinx 6.4
> http://www.blender.org/documentation/250PythonDoc/250PythonDoc.pdf
>
Wow, thats a great fat book!
If you are the Blender-Python-Pope this is our bible ;-)
Carsten
___
Bf-committers mail
Thu, 28 Jan 2010 12:53:31 +0200, Campbell Barton :
> Heres PDF generated from sphinx 6.4
> http://www.blender.org/documentation/250PythonDoc/250PythonDoc.pdf
Thanks :)
A link to the PDF at http://www.blender.org/documentation/250PythonDoc/
and maybe generation date in the name would be nice also
The PDF is more an example of what we can get closer to the release,
since I like to keep these docs updated every week or two its a hassle
to build both and upload. Eventually I'll automate this process.
Ill add build-info (date & revision) into the docs soon.
On Thu, Jan 28, 2010 at 3:43 PM, I
Campbell,
What are we going to do with the usability aspects of developing
scripts in 2.5? following our talk in IRC is there some kind of a
proposition for a well defined workflow?
Thanks,
shul
On Thu, Jan 28, 2010 at 10:38 AM, Campbell Barton wrote:
> The PDF is more an example of what we can
Hi Shul, (on IRC clarified that 'usability aspects of developing'
means context problems with operators not running).
There are 2 main problems
1) Running from the console/text editor wont work for many operators.
2) When an operator wont run there is no message to say why.
For 1, many operators
17 matches
Mail list logo
