Dev talk:Py/Scripts/Guidelines
"Object.Get() to get all objects is only to be used in cases where getting objects from the current scene with Scene.GetCurrent().getChildren() is not appropriate."
While I understood everything else in this document, the above passage went right over my head, and I'm sure only (very) experienced Blender python programmers are going to understand it. There are probably hundreds of examples of where "XXX is better than YYY", if Object.Get() is very common / special, then an explanation would be nice to see here. Mike --Mstram 12:35, 15 August 2006 (CEST)
<quote>Constant variable</quote>
interesting formulation that underlines Python lack of real constants.
These guidelines are coming along nicely : they're more than rules and are giving helpful tips. A positive slant can only make them better respected.
Thanks --Iaminnocent 09:37, 4 August 2006 (CEST)
gui
We've got to say something about the gui of scripts. I would prefer that all scripts look like the Button Window. With charts for preferences, auto shrinking, scrolling through the charts with mouse wheel, fixed button positions, minimize functions...
But because its much work to do in each script, I would prefer to have a module for that.
I don't think every script needs this whole flexibility, but the user is much faster when they all look and act similar. The script I'm working on uses up to ten preference charts to control visualization of some physical simulations and to interact with these external programs. There I need the flexibility.
--Hugen 11:18, 5 August 2006 (CEST)
- The BPy Draw module doesn't directly support GUI scaling, paning and pannelling, so it's a bit harsh to request it from script writers, unless we provide a higher level library to ease the pain (which wouldn't be impossible, mind you). --Theeth 01:17, 11 August 2006 (CEST)
--Ideasman42 01:18, 16 August 2006 (CEST) Not much we can do about the gui stuff right now, at some point we will improve the pygui but until then well make do with whats available.
