Native mode for KFileDialog API on Windows (again)

Jaroslaw Staniek js at
Mon Jun 9 12:46:11 BST 2008

I am looking (again) for the finest way to wrap native file dialogs support 
for Windows in KFileDialog API.
In a such QFileDialog mapping, getOpenFileName() would be mapped to 
QFileDialog::getOpenFileName(), etc.

The goal would be that both KDE and Native mode would be available in the same 
KDE installation, easily switchable in a "Integration" page of the system 

KFileDialog inheriths KDialog, so we would still keep its instance allocated 
even if it's not displayed, and we could display native dialogs instead.

- we want to avoid any changes in the applications code, so no #ifdefs;
   devs that do not even think about windows/mac builds of their could would
   not be disturbed by any requirement

- we agree on that functionality of the native mode is degraded, e.g. no KIO
   support, and only native mimetypes/associations support

- in KDE 3 I've been using such mappings implemented as application's level,
   e.g. in Kexi, but now we have hundreds of apps and want fine level of

- perhaps Mac OS X port would benefit from the native mode too

Any hints? Notes?

PS: This is a technical question, not a request for comments on what mode to 
use. Given developers using kdelibs would just #ifdef things in their code if 
there is no support for the native mode in kdelibs.

regards / pozdrawiam, Jaroslaw Staniek
  Sponsored by OpenOffice Polska ( to work on
  Kexi & KOffice (,
  KDE Libraries for MS Windows (

More information about the kde-core-devel mailing list