[PATCH] A KJob jobtracker that uses kuiserver, or falls back to dialogs.

Rob Scheepmaker r.scheepmaker at student.utwente.nl
Thu Sep 11 13:50:29 BST 2008

On Thursday 11 September 2008 12:05:08 Rafael Fernández López wrote:
> wrong myself, we should keep the KDEUI_EXPORT and just mark the class as
> internal.
> I also meant having it as @internal, so it's API is not "exposed" (well,
> only for libkio reasons). We have this on lots of places
> /**
>    * @internal
>    * For kio/global.cpp use only.
>    */
> or something like that.
> Seems that having some trackers on kdeui/jobs and this one on kio is not a
> very nice hierarchy.
> Anyway, if you think having it on kio is better, just let it be there.

I agree that having all trackers in kdeui/jobs has it's advantages. But 
effectively it's still public in that case. What is usually done in kdelibs in 
comparable situations? I'm new to contributing to kdelibs so I haven't really 
got a feel for how this should be done. Kevin, what's your opinion on this?

Rob Scheepmaker

More information about the kde-core-devel mailing list