On Friday 24 Jun 2011 15:07:06 Nathan Bradshaw wrote:
> I guess going away from an RDF store, there is sqlite if you don't mind
> the dependency.
If the app data maps well to relational tables and you're comfortable with sql
then it's not a very heavy dependency, it's almost always already insta
>On 24 June 2011 10:26, Andreas Pakulat wrote:
> On 24.06.11 15:52:10, Thomas Lübking wrote:
>> Am Friday 24 June 2011 schrieb Parker Coates:
>> > For reading and writing "data storage" XML, I personally think the
>> > QXmlStream(Reader|Writer) classes are nicer (and potentially more
>> > performa
On 24.06.11 15:52:10, Thomas Lübking wrote:
> Am Friday 24 June 2011 schrieb Parker Coates:
> > For reading and writing "data storage" XML, I personally think the
> > QXmlStream(Reader|Writer) classes are nicer (and potentially more
> > performant because the whole document doesn't ever have to be
On Fri, Jun 24, 2011 at 9:41 AM, Vishesh Handa wrote:
>
>
> On Fri, Jun 24, 2011 at 7:07 PM, Nathan Bradshaw <
> nathanlbrads...@gmail.com> wrote:
>
>> On Thu, Jun 23, 2011 at 5:51 PM, Thomas Lübking <
>> thomas.luebk...@gmail.com> wrote:
>>
>>> Am Thursday 23 June 2011 schrieb Steven Sroka:
>>>
Am Friday 24 June 2011 schrieb Parker Coates:
> For reading and writing "data storage" XML, I personally think the
> QXmlStream(Reader|Writer) classes are nicer (and potentially more
> performant because the whole document doesn't ever have to be stored
> in memory). There was also some talk of rem
On Fri, Jun 24, 2011 at 7:07 PM, Nathan Bradshaw
wrote:
> On Thu, Jun 23, 2011 at 5:51 PM, Thomas Lübking > 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 int
On Thu, Jun 23, 2011 at 5:51 PM, Thomas Lübking
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
On Fri, Jun 24, 2011 at 04:45, Thomas Lübking wrote:
> Am Friday 24 June 2011 schrieb Steven Sroka:
>
>> How would I utilize a xml file? Just get my program to hand craft one?
>
> Aside tools like the xmlcompiler, you'd start out with QDomDocument for "just
> basic reading/writing xml".
For readin
Am Friday 24 June 2011 schrieb Steven Sroka:
> How would I utilize a xml file? Just get my program to hand craft one?
Aside tools like the xmlcompiler, you'd start out with QDomDocument for "just
basic reading/writing xml".
Whatever you do, do (rather) NOT "handcraft" xml by entries like
IODevi
On Thursday, 2011-06-23, Steven Sroka wrote:
> 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
Hi,
on Friday 24 June 2011 05:28:25 Steven Sroka wrote:
> >On 23 June 2011 21:28, Michael Pyne wrote:
> > On Thursday, June 23, 2011 23:51:35 Thomas Lübking wrote:
> >> Am Thursday 23 June 2011 schrieb Steven Sroka:
> >> > What is the best way for a KDE program to store data? Not passwords or
>
>On 23 June 2011 21:28, Michael Pyne wrote:
> On Thursday, June 23, 2011 23:51:35 Thomas Lübking 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.
On Thursday, June 23, 2011 23:51:35 Thomas Lübking 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 th
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 configuarti
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.
Any good KDE techniques?
>> Visi
15 matches
Mail list logo