Assorted questions ...

[Andreas Pakulat]

On 18.06.07 11:37:33, Sandro Andrade wrote:
> Hello,
> 
> I would be grateful for some explanation about the kdevelop code aspects
> below:
> 
> 1) Why does the Core class (and others classes) in shell directory contain a
> CorePrivate struct ? Why the controller attributes weren't declared directly
> in the Core class ?

Because its easier to keep BC with that. See 
http://techbase.kde.org/Policies/Library_Code_Policy
http://techbase.kde.org/Policies/Binary_Compatibility_Issues_With_C++

> 2) Where is the Core::setDocumentController method declared ? The Core class
> contains just a documentController() accessor method !!!

Thats right. There is no setDocumentController, the documentcontroller
is setup during initialization

> 3) Why to setup a new DocumentController if the initialize() method on
> CorePrivate already creates a DocumentController ?

I don't see that happening. CorePrivate::initialize creates the
document controller, Core::initialize just calls
CorePrivate::initialize()

> 4) In main method the loadingPlugin signal from pluginController is
> connected to the splash slot AFTER the invocation of
> pluginController()->loadPlugins(). Is this useful ? No messages are
> exhibited in the splash !!!

Right, none of this is actually working at the moment. This will be
fixed "some day".

Andreas

-- 
You may be gone tomorrow, but that doesn't mean that you weren't here today.