[Bf-gamedev] Refactoring BGE code (to accomodate a new design)

[pgi]

Thank you for the answer.

Well, if the thing is already planned (and I mean it will happen, just 
we're not sure when) then the entire process I propose is unnecessary. 
It will be done anyway, just in the right way from the start - instead 
of discussing here a design that may or may not survive the later 
integration.
Let's be clear, I'm more than happy with that, the more I look at the 
code the more I say to myself "you're gonna be in deep troubles..." :D.


On 01/02/2015 21:47, Sybren A. Stüvel wrote:
> On Sun, Feb 01, 2015 at 09:06:10PM +0100, pgi wrote:
>> I'd like to have some feedback, resoucers or articles to check for,
>> ideas and and (mandatory) agreement on the new layout of the engine.
>> Or a slap in the face, I might very well be wrong on my assumption
>> that the current design is a mess. But I could point out that it has
>> been probably a data driven design because I see the logic of it and
>> its typical problems.
>  From my point of view, it is hard to give feedback on your ideas. I
> think your overall idea is good. However, it is written in such
> generic terms that it's hard to disagree with.
>
> I think that unification between Blender and BGE is one of the aspects
> where we can really improve the BGE. This would cover the viewport,
> mesh data, materials, physics, etc. Unification would also mean that
> there is less (or no) need for an asset manager any more, no separate
> renderer, etc.
>
>
>
>
> _______________________________________________
> Bf-gamedev mailing list
> Bf-gamedev at blender.org
> http://lists.blender.org/mailman/listinfo/bf-gamedev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-gamedev/attachments/20150201/8e0eaf83/attachment.htm