py drawing to 3dview (Re: [Bf-committers] User-defined Material Properties)

Campbell Barton cbarton at
Wed Oct 19 04:33:54 CEST 2005

Hi Greg, as Tom M pointed out- very little effort is going into the game 
engine at the moment,

About blenders design- okay, your a good C++ programmer who can see 
blenders internals and see how they could be a lot better.

There are probably many many badly designed things in this world, 
WindowsXP to start with, (I heared somebody look into SGI Irix source 
code and say the same thing), governments, corruption,  reasons behind 
If you knew all the crap that goes on behind the scenes, and understood 
it all, I'm sure you'd tear all your hair out with frustration.

The fact is that blender is in most cases fast, stable and doesn't break 
compatibility, it has a fairly stable and powerfull python plugin API..  
fairly big improvements are being made to fix design in spesific areas 
too. so its not a lost cause.

If you took a peek at WinXP source code and found it was badly designed, 
you wouldent say- "I wont put my job on the line be recommending WindowsXP"

You yourself sited 3dsMax as being badly designed, Im not saying bad 
design is good, just that imperfect design can be acceptable until 
something better comes along.

Also- theres nothing stopping you from adding material/datablock 
properties which is what you want in the first place isn't it??

Will you continue with your OpenFlight import export?

- Cam

MacDonald wrote:
> Hi Everyone,
> I assume you're directing these comments to me, because its under my 
> old thread name. I just wanted to inform you that someone else should 
> pick up the torch because I've decided not to contribute. I think the 
> most important thing Blender needs to do right now is replace the 
> internal data model with an extensible, object oriented design. I also 
> believe strongly that the game engine should not be a part of the main 
> Blender project. That people are devoting tons of energy to the former 
> and not the latter, indicates to me that the project is driven by 
> something other than the best interests of the end-users.
> Maya is fully extensible has a rock solid design because its been 
> rewritten multiple times, and it costs virtually nothing compared to 
> what my company currently pays for Creator. After seeing Blender's 
> internals, I can't put my career on the line recommending it.
> If Maya can be rewritten, Blender can too. And be done in a way that 
> all the old scripts still work the same. I know you paid a lot for 
> that C program, but now that you have everyone's attention you surely 
> can muster the troops for a rewrite. If I were to rewrite Blender, I'd 
> probably end up doing it from scratch and then porting pieces over to 
> the new framework. But I have a job and don't have time. Its really 
> not a one man project.
> This is my honest professional opinion. I offer it not to be mean, but 
> with the hope someone can do something constructive with it. If I 
> wanted to be mean, I would've said something like, "You can't polish a 
> turd." But fortunately for you I'm not like that.
> Best of luck.
> -Greg
> On 10/18/05, *Johnny Matthews* <johnny.matthews at 
> <mailto:johnny.matthews at>> wrote:
>     Space Handlers need to get on key up events too. They dont seem to
>     currently.
>     Johnny
>     On 10/18/05, *Willian Padovani Germano* <wgermano at
>     <mailto:wgermano at>> wrote:
>         antont at <mailto:antont at> wrote:
>         > i know there is this principle that windows are separate etc.
>         but such a
>         > script actually does not use the ScriptSpace, but is
>         scriptlinked. so in a
>         > way the 3d view is the space that is uses. is there a problem
>         with it? can we
>         > make it nice for 2.4?
>         Well, Ton devised space handlers for scripts to be able to get
>         events
>         from and draw to a given space type (3d view currently, but
>         it's easy to
>         add for others) in a way that fits with Blender's model.
>         But scriptlinks are also acceptable, afaik, so it's ok to use
>         them if
>         space handlers are not adequate for some task (feedback on
>         handlers is
>         always important to know if we can / should upgrade them, btw).
>         > also, such scripts suffer from the lack of Object.Changed
>         scriptlink event
>         > type, 'cause they currently have to listen to Redraw() and
>         check for possible
>         > changes in the object that they 'own' in python. so i think
>         we must add such
>         > a scriptlink event type.
>         Yes, there are missing events. "OnSelect" used to be
>         mentioned, as well
>         as "OnMouseClick", "OnKeyDown" (these two covered by event space
>         handlers), etc.  A coder mentioned he had success with a listener
>         (sockets) event, too, but we got no news from him after that.
>         Now that space handlers are in place being used, we can see
>         what's still
>         needed. Events for object changes, like you mention, and
>         selection are
>         good candidates.
>         --
>         Willian
>         _______________________________________________
>         Bf-committers mailing list
>         Bf-committers at
>         <mailto:Bf-committers at>
>     -- 
>     Johnny Matthews
>     johnny.matthews at <mailto:johnny.matthews at>
>     _______________________________________________
>     Bf-committers mailing list
>     Bf-committers at
>     <mailto:Bf-committers at>
> ------------------------------------------------------------------------
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at

Campbell J Barton

133 Hope Street
Geelong West, Victoria 3218 Australia

e-mail: cbarton at
phone: AU (03) 5229 0241

More information about the Bf-committers mailing list