New releases of KDE and Povray and a proposal

CARVALHO Luis Passos luis.passos at enabler.com
Wed Feb 4 13:44:41 CET 2004


Hello!

> From: Andreas Zehender [mailto:zehender at kde.org]
> 
> PMPart should contain only the core functionality. All 
> actions will move into 
> the povray plugin.
> 

There still is the issue that the PMPArt, if I'm not mistaken, also creates the main widget.
I presume that will not move to any plugin. If we want to use some part of PMPart (no pun intended) elsewhere, this creation of the widget must go. That is also another reason why I want to split both.

> I'd like to split the sources, too. A core library and a 
> plugin directory. I 
> just want to wait for the release of KDE 3.2 to contact the 
> cvs maintainer to 
> move the files. I hope I have enough time this weekend. At the moment 
> everybody is busy to release KDE
> 

Great. Good to hear that. I'll just backup my files so I don't have a lot of dificulty merging afterwards.

> 
> Not sure at the moment.
> Plugins need always a PMPart because of the KDE plugin 
> architecture. And the 
> object library will need plugins to create and handle 
> objects. The only 
> optimization that would be possible is to disable action 
> creation for plugins 
> if no gui is needed.
> 
> Will have to think about that.

The plugin "scanner" is part of the functionality provided by KParts. What if the PMPart is a factory for PMDocumentRules?
That way, PMPart scans the plugins and registers them in it's own internal PMDocumentRules. Then, whenever we need a PMDocumentRules, we just ask the Part to clone one for us or give us a reference to it's own manager (depending on whether we implement this by inheritance or composition).

My main objective in proposing this change is to make PMObject and it's descendents, as well as the views, as independent as possible of the visual aspects of the part. But I believe you already know that and at heart agree with me. ;).

Aditionally, I think that some crashes I'm experiencing in my latest developments have been caused by not instantiating a complete part and instead creating a "crippled" one. I'm having crashes in a "delete m_pPart". I'm still investigating, but this somewhat bad hack I did keeps nagging me.

Regards,
Luis


More information about the kpovmodeler-devel mailing list