[patch] KApplication

Jaroslaw Staniek js at iidea.pl
Fri Oct 15 01:00:24 BST 2004

>>>I'd later (because it's not yet tested) come with generating other_qt.pot
>>>file for translators. At least win32 could load other_qt.po (explicity,
>>>in KApplication_init_windows()).
>>   With QFileDialog, not only will users lose the advanced features of KFD,
>>one of the big benefits of using KDE, but they will also lose the ability
>>to use KIO properly.
> Isn't Jaroslaw working on a native KDE port on Windows, i.e. not cygwin ?
> I guess kiolsaves don't work at all there, so this doesn't matter.

Mostly right. But my work is on native KDElibs/win32 port, not KDE 
Desktop/win32. So the goal is not to again-and-again patch win crap (C API, 
non-posix behaviour of kernel), but integrate KDElibs API with it, using 
native OS capatibilities. File dialogs are example of such thing. And most 
probably there's more value in keeping win32 feature-set as-is (maybe with 
exception for DCOP/DBUS) and improving KDE/unix target. Otherwise..  we'd end 
up with the same "toy" as KDE/Cygwin is from end-suer point of view.

And btw, kiolsaves work quite well, it's just K*Socket not ported - IIRC, I 
used gzip filter within KWord/win32. I also plan to patch QFileDialog later 
(for myself) to have it more "native". After all, a bit different typical GUI 
elemnets have not so much to do with, say, KIO API, which can be equally 
usable on win32.

regards / pozdrawiam,
  Jaroslaw Staniek / OpenOffice Polska
  Kexi Project: http://www.kexi-project.org, http://koffice.kde.org/kexi
  KDElibs/Windows: http://wiki.kde.org/tiki-index.php?page=KDElibs+for+win32

More information about the kde-core-devel mailing list