On Sunday, May 15, 2011 02:03:32 Stefan Majewsky wrote:
> On Sat, May 14, 2011 at 10:18 PM, Parker Coates
>
> wrote:
> > Also note that KPixmapCache is now deprecated and that KImageCache is
> > just a thin convenience wrapper around KSharedDataCache. So really,
> > KSharedDataCache is KDE's only
On Sat, May 14, 2011 at 10:18 PM, Parker Coates
wrote:
> Also note that KPixmapCache is now deprecated and that KImageCache is
> just a thin convenience wrapper around KSharedDataCache. So really,
> KSharedDataCache is KDE's only current caching system.
Michael Pyne, if you're reading this, pleas
On Sat, May 14, 2011 at 15:51, Christoph Feck wrote:
> On Saturday 14 May 2011 21:42:18 Mark wrote:
>> Why is KDE having it's own image/pixmap caching classes
>> when the Qt lib also has them (QPixmapCache and QCache).
>
> KDE's cache classes are on-disk caches and cross-application, while Qt's cac
On Sat, May 14, 2011 at 9:51 PM, Christoph Feck wrote:
> On Saturday 14 May 2011 21:42:18 Mark wrote:
> > Why is KDE having it's own image/pixmap caching classes
> > when the Qt lib also has them (QPixmapCache and QCache).
>
> KDE's cache classes are on-disk caches and cross-application, while Qt
On Saturday 14 May 2011 21:42:18 Mark wrote:
> Why is KDE having it's own image/pixmap caching classes
> when the Qt lib also has them (QPixmapCache and QCache).
KDE's cache classes are on-disk caches and cross-application, while Qt's cache
classes are only in-memory and not shared between applic
Hi,
I noticed this because of https://git.reviewboard.kde.org/r/101347/ and it
made me wonder.. Why is KDE having it's own image/pixmap caching classes
when the Qt lib also has them (QPixmapCache and QCache).
The only thing you would "miss" is caching QImage.
Anyway, now that the Qt 5 stuff is go
