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

[Benjamin Reed]

On 4/10/06, Lubos Lunak <l.lunak at suse.cz> wrote:

>  Non-X11 platforms should implement their own KStartupInfo, with most
> functions being no-op I'd presume. Is there any problem with that?

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.

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?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kstartupinfo.diff
Type: application/octet-stream
Size: 8267 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060411/2921f764/attachment.obj>