KIO: separating the API from the implementation

[Thiago Macieira]

nf2 wrote:
>i wonder if the public API of KIO could be made more "abstract" for KDE4
>(to be able to plug other VFS implementations, but also to make
>innovation easier for KDE). i believe there are many classes, members,
>methods and enums in the KIO namespace, which should not be exposed to
>the "library user". For instance, what's the point of having Slave or
>SlaveInterface, Scheduler, enum Message... in the public API... ?
>Perhaps such things should be moved to a KIO::KDEImpl:: namespace...

I want to do some work there, but given my current amount of free time 
available and the upcoming freeze dates, I don't think we can pull it 
off.


-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070320/2c7608a6/attachment.sig>