New releases of KDE and Povray and a proposal

CARVALHO Luis Passos luis.passos at enabler.com
Tue Feb 3 19:50:41 CET 2004


Hello!

In 30th January Povray 3.6 beta1 was released. Anyone knows what's different? They refer mainly internal changes but I'm always curious.

Also KDE 3.2 was released today, so soon we will be able to start commiting again to head, right Andreas?

By the way, I'd like to propose, right now, for kde 3.3 if possible that we split PMPart. Here is my motivation: In order to create the object library, I had to instance an independent PMPart that keeps the scene inside the library object and holds it's own copy of the available plugins.

The problem I faced was that PMPart, aside from keeping that also has the work of maintaining the application's actions. I temporarily solved it by creating a second constructor that does not create the actions. However, this really feels like an ugly hack.

IMHO, a better design would be (the names could be better)
   PMDocument - Holds m_pScene and services needed by PMPart and other components to handle the scene
   PMDocumentRules -  Holds the prototype manager and the insert rules
   PMPartBase - inherits from PMDocument and PMDocumentRules just to collect both under the same roof as usually they will be used together.
   PMPart - Inherits from PMPartBase and provides all the actions needed by the interface, as well as creating the main widget.

That way, the part is never passed around and only a PMDocumentManipulator. Whenever we need to create a new/different scene view there is no need to create it from PMPart as that creates too many unnecessary things. We just create a new PMDocumentManipulator.

Am I missing something? What do you think? How do plugins fit in this?

Regards,
Luis


More information about the kpovmodeler-devel mailing list