Thanks for your answers!

Ton gave kind of a reason about this issue at the “Blender conference” but I’m sure there is a solution somewhere

And this is awesome, don’t get me wrong ! every single application should be like that. It got a wonderful “internal” API now.
I’m more talking about an external api though. Like for example if you would like to develop an external application which interact with Blender, as you would do with Max or Maya. If it’s possible now, then I misunderstood something.
The only C plug-in you could develop as far as I know was image plugin and filter plugin (for sequencer).
But let say you want to do a “FumeFx” or “Krakatoa” kind of program which bind with blender, I don’t see any way to do that except by getting your hands dirty into Blender code and recompiling the entire thing everytime.
Which in basics it’s not a big deal, but still if you had to recompile maya or Max each time your company is doing a proprietary plug-in your engineer would get crazy by the end of the day.
The only kind of things that the Py API allow you today (and once again this is my understanding of it, I’d like to be proven wrong) is creating an export for an external render which get a better integration into Blender UI and internal functions. Which is actually really good ! but the other way around is not possible.
Maybe a Py blender lib would do it. so in maya you would be able to do something like “import blender”, but even that would limit the dev to py.

Do you get my point ? Anyway, I don’t think that such a thing would come any time soon…

(ou alors j’ai pô compris la private joke )

Now the question is how hard is it to implement it?

—-

About plug-in development in Blender: I wonder what you mean by “making it more easy”?

I am not used to blender’s python development and I’m curious about your thoughts about it. What is your main complaint about it? The way the internal python API is organized and the freedom it gives you (or not) to script anything (I thought Blender 2.5 was now “full python-scriptable”)? The way you can (or can not…) share plug-ins?

This last point interests me more. For example, I know that in Houdini you can package your scripts/shaders/models/etc. into “digital assets”: something you can easily share with others. In Softimage XSI, plug-ins can be shared through the “workgroups”: a directory where external plug-ins are referenced.

Are there such easy plug-ins sharing mechanisms in blender?