public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Good Library Management software
Date: Thu, 17 Jul 2008 19:48:30 +0100	[thread overview]
Message-ID: <AC24E8E1-1A30-4CE9-8680-2880A404DF94@stellar.eclipse.co.uk> (raw)
In-Reply-To: <79e3aefb0807170059y3a8f81ccqe6d6e9e61ac46b27@mail.gmail.com>


On 17 Jul 2008, at 08:59, Dirk Uys wrote:
> On Wed, Jul 16, 2008 at 9:49 PM, Stroller
> <stroller@stellar.eclipse.co.uk> wrote:
>>
>> The screenshots of this look really nice, however to me this seems  
>> like a
>> really odd motivation for writing a program:
>>
>>  I started developing it when I couldn't find a personal database
>>  program for KDE which didn't using a SQL backend.
>>
>> What's wrong with an SQL backend that needs you to re-invent the  
>> wheel?
>> ...
> I don't print that
> often, so why would I have the CUPS daemon running 24/7 when I print a
> page once every two weeks?

There's probably no cost to having the CUPS daemon running 24/7 - it  
starts up, the o/s sticks it in virtual memory when it sees you're  
not using it and then reloads it to RAM when you do.

> Other than that there is also the added complexity to the
> installation. You have to create a user in the database, create the
> database and grant the user all the needed permission to that specific
> database.

Well, ideally the distro should handle all of this. Or have a "setup  
manager" app.

> And what if one app prefers mySQL and another one postgreSQL?

Agreed. This pisses me off no end. I'll bet the two are a pain to  
manage side-by-side on the same machine.

> The app should at least give you the option to use somethings else  
> like SQLlite.

Well, I have to say I was suspicious of Tellico's choice of XML flat- 
files, when this option is available to it, too.

> But, that is just my viewpoint and I felt like I had to defend the
> developers motivation.

You don't need to defend your viewpoint at all. I mean, it looks like  
a great app, so I'm not criticising it. It just seems odd, os all,  
that he cites reluctance to use an SQL backend as his main reason for  
developing the app, then doesn't explain further why he thinks that's  
a problem or why his way is better. True, it makes a big difference  
to setup, but I would have thought there were loads of features that  
would be more obvious during the end-user experience that would  
better distinguish an app.

Stroller.

-- 
gentoo-user@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-07-17 18:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 11:40 [gentoo-user] Good Library Management software Eric Martin
2008-07-14 12:06 ` CJoeB
2008-07-16 16:48   ` Eric Martin
2008-07-16 19:49   ` Stroller
2008-07-17  7:59     ` Dirk Uys
2008-07-17 12:31       ` Eric Martin
2008-07-17 18:48       ` Stroller [this message]
2008-07-20 16:29       ` kashani
2008-07-17 12:27     ` Eric Martin
2008-07-14 15:06 ` Joshua D Doll
2008-07-14 15:16   ` Aaron Clark

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AC24E8E1-1A30-4CE9-8680-2880A404DF94@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox