[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Storing images in KConfig keys
From:       Kevin Krammer <kevin.krammer () gmx ! at>
Date:       2009-10-12 6:02:05
Message-ID: 200910120802.23340.kevin.krammer () gmx ! at
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Monday, 2009-10-12, Stefan Majewsky wrote:
> Am Montag 12 Oktober 2009 00:42:41 schrieb Michael Pyne:
> > I'm going to assume that's there's no way to simply save out the binary
> >  data to disk and store a reference to the file name in your KConfig? :)
> 
> The problem is that I'm using KConfig not as a storage file format, but as
>  an exchange file format. My two use-cases are:
> 
> 1. In Kolf, course files are read/written with KConfig, because it allows
>  to store the values of arbitrary QMetaProperties with very less code. The
>  properties in question are the heightmap and the texture of the terrain,
>  which were previously stored in separate files, but have been moved to the
>  main KConfig file because it's beneficial for the user interaction to have
>  a one- to-one mapping of courses to files.
> 
> 2. In Palapeli, KConfig is used for metadata caches (with metadata also
> including thumbnails). Here also, the thumbnails were previously stored in
> separate files, but I've moved them into the KConfig file today because I
>  want these files to become "puzzle feeds" which are shared over the
>  network, where it's unconvenient and error-prone to cross-reference
>  between and download multiple remote resources. (See my latest blog entry
>  on the planet for more background on the "puzzle feeds" feature.)

Have you considered using an archive file, e.g. like ODF uses ZIP to combine 
XML and binary data into one user-visible file?

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]