stubbing KStartupInfo -- win32 feedback? (was Re: A little review of kdecore & kdeui)

[Thiago Macieira]

Benjamin Reed wrote:
>I started doing this, but realized I'd be re-implementing half of the
>"convenience" bits that are already in kstartupinfo.cpp, so I ended up
>just #ifdef'ing it instead.  I'd like some feedback from you and maybe
>anyone involved in the win32 port before I commit it, though.
>
>It basically chops out anywhere there are actual KXmessages passed
>around, but leaves things otherwise alone, including the
>state-tracking.

Which means the class becomes a big state-tracker. It doesn't do anything 
with that information nor does it receive any data from the external 
world.

>Could KXmessages perhaps be replaced by something qt-based
>(signals/slots or some other IPC mechanism)?  Or is it enough to just
>have the apps think they're able to track this basic state and be done
>with it for now?

No. It has to use X messages because the whole point here is to tell the 
Window Manager that the app is starting up / has finished starting up.

-- 
Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
  thiago.macieira (AT) trolltech.com     Trolltech AS
    GPG: 0x6EF45358                   |  Sandakerveien 116,
    E067 918B B660 DBD1 105C          |  NO-0402
    966C 33F5 F005 6EF4 5358          |  Oslo, Norway
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060411/eb05f91c/attachment.sig>