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

List:       kde-devel
Subject:    Re: Storing data
From:       Nathan Bradshaw <nathanlbradshaw () gmail ! com>
Date:       2011-06-24 13:37:09
Message-ID: BANLkTikFtdWmd_+x3k_r0-dHGGEfr_sHoA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Thu, Jun 23, 2011 at 5:51 PM, Thomas L=FCbking
<thomas.luebking@gmail.com>wrote:

> Am Thursday 23 June 2011 schrieb Steven Sroka:
> > What is the best way for a KDE program to store data? Not passwords or
> > anything sensitive, but data a user had typed into text fields.
> >
> > Some sort of database. Something along the lines of KConfig or KConfig
> > XT but for raw data not configuartion data for programs.
> Depends on the type of data and what you want to do with it.
>
> If you want to "dump memory", you need to serialize the data.
> Have a look at QDataStream.
>
> KSharedDataCache helps to to access information from several processes at
> the
> same time (like eg. the icons) and save memory.
>
> Also you can write it to some xml or an kconfig/qsettings ini-a-like file
> with
> the advance of "less" access ;-)
>

Is RDF through Soprano an option here?

[Attachment #5 (text/html)]

<div class="gmail_quote">On Thu, Jun 23, 2011 at 5:51 PM, Thomas Lübking <span \
dir="ltr">&lt;<a href="mailto:thomas.luebking@gmail.com">thomas.luebking@gmail.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"> Am Thursday 23 June 2011 schrieb Steven Sroka:<br>
<div class="im">&gt; What is the best way for a KDE program to store data? Not \
passwords or<br> &gt; anything sensitive, but data a user had typed into text \
fields.<br> &gt;<br>
&gt; Some sort of database. Something along the lines of KConfig or KConfig<br>
&gt; XT but for raw data not configuartion data for programs.<br>
</div>Depends on the type of data and what you want to do with it.<br>
<br>
If you want to &quot;dump memory&quot;, you need to serialize the data.<br>
Have a look at QDataStream.<br>
<br>
KSharedDataCache helps to to access information from several processes at the<br>
same time (like eg. the icons) and save memory.<br>
<br>
Also you can write it to some xml or an kconfig/qsettings ini-a-like file with<br>
the advance of &quot;less&quot; access ;-)<br></blockquote></div><br>Is RDF through \
Soprano an option here?<br><br>



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


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