@rednelb: What he is suggesting is that a too tight grip when implementing with an MVC model leads to code over-engineering. Sometimes a simpler model works easier for developers or could involve a huge performance increase (in computation or space).
@carlcomplaint: As much as we like to innovate *now*, a good approach towards innovation often involves planning and architecture. During the construction of a new model oil-tanker, for example, parts of the once to be completed ship are already being ordered (leading to a chain of orders, going back all the way towards iron-ore), while other people are still drawing the designs of other parts of the ship. Surely, such an approach would not be possible without careful preparation on flows of goods and information. Therefore, a good architecture leads to a smooth development later on. Innovation is often in the planning and architecture, not in the eventual implementation (although the implementation is what people see).
@daves: You might be very right here, although I'm not a Windows programmer by heart. These event-driver MVC architectures have driven many applications so far. The reasons? They are relatively easy to grasp, they keep things seperated, they allow for easy replacement of parts and they can be easily tested. As an extra: they are very suited towards object-oriented languages (whereas other (older) models are less so).

I just read some of their chat history… they really have completely pulled blender apart and are putting it together from ground up. Which in all truth is exactly what Blender needed. I expect when they're are done that Blender will be faster, more stable and have a tonne more features! *CAN* wait till they're finished!

Absolutely stunned by the whole Blender community.

Happy New Year everybody, looks like it's going to be a good one!

In using Blender various versions - each has been a fairly decent improvement over the previous version.
I have used Blender on PII@350 running Linux, PIII@450 running Windows 98, and Linux, and currently run it on an AMD Athlon 64 2700+ (2.24GHz) - I don't remember the version I first used, but as I didn't have much of a clue about how it worked, it wouldn't have mattered anyway.

I have found that Blender 2.46 does use more of my memory than 2.41 did but the amount used is not signifacant enough to change my usage habits or reduce my creativity. I would suspect that according to the information given that the next version will take less memory and be more capable than the current version with a 'smoother' interface :D sounds good to me…

I am glad that some news is out about how the next version will work.

Other apps that have macro recording actually do not record mouse selection. Macros in Microsoft Word record the name of the object that was selected, as do Actions in Adobe Photoshop.

Still, recording a tutorial from the start of opening a file should always yield the same results, as the objects will have the same names. And carefully recorded macros can avoid selecting obects and start with the "active selection".

I looked at the model, and aside from the multi-pointer, remote input stuff people have been bandying about, I had one comment: Isn't this the Windows model? Event driven programming? (YES, I know this model is implemented by most other GUI OS's out there, each with its own nomenclature and methods) I just couldn't help but think "Welcome to MSWindows!!" while reading the log.