kbooks-devel

[Kbooks-devel] Register Editor

[John H. <jo...@se...>]

Just so everyone knows, I'm seizing control of development for the
register editor.. I'm trying to make it prettier, friendlier, and make
it actually work too. So, be advised, don't expect that all to stay the
same.. (In case you start changing anything in there.)

Re: [Kbooks-devel] Register Editor

[Andrew N. <nel...@po...>]

let me know when you need to connect it to the sql backend.

-Andrew
On Monday 13 May 2002 14:13, you wrote:
> Just so everyone knows, I'm seizing control of development for the
> register editor.. I'm trying to make it prettier, friendlier, and make
> it actually work too. So, be advised, don't expect that all to stay the
> same.. (In case you start changing anything in there.)
>
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> Kbooks-devel mailing list
> Kbo...@li...
> https://lists.sourceforge.net/lists/listinfo/kbooks-devel

[Kbooks-devel] Authors file...

[Daniel D. <du...@ya...>]

I added John and Andrew to the authors file, for the sake of the .4 release 
when that comes.  At this point I figure it will include register editor and 
the sql backend... when they are both complete and working.

-- 
------------
email: du...@to... www: http://paradox.tosos.com/~duhprey icq: 129354442
The European finds intercourse with Americans easy and agreeable.  Einstein
Not a shred of evidence exists in favor of the idea that life is serious.  Gill

[Kbooks-devel] SQL backend

[Daniel D. <du...@ya...>]

Something I was just thinking in reference to the SQL backend.  We probably 
want some way for somebody to have a minimal sql setup required.  Like we have 
a readme somewhere that says "add the kbooks" database and create user 
"kbooks-admin" and then have everything else be done by kbooks or some 
initialization script automatically ... especially the table creation, etc.  
This would make it easier to handle configuration changes later like if we 
need to add columns to tables or new tables.  Is this possible?

-- 
------------
email: du...@to... www: http://paradox.tosos.com/~duhprey icq: 129354442
The European finds intercourse with Americans easy and agreeable.  Einstein
Not a shred of evidence exists in favor of the idea that life is serious.  Gill

Re: [Kbooks-devel] SQL backend

[Andrew N. <nel...@po...>]

Good idea... I'll write a few words to the effect and the statements to add 
etc....

We can also make the program perform an autodetection on startup and create 
the necisary databases.  However that might be .5.  :-)  There might be the 
need for a perl script... however I'd like to avoid it.

I was also thinking of having a table in the database store site wide and 
user settings.  However it should not store security related settings.  This 
way a user "hopefuly" does not have to be tied to a machine, and their 
settings can "follow" them.  Any thoughts??

-Andrew

On Monday 13 May 2002 16:33, you wrote:
> Something I was just thinking in reference to the SQL backend.  We probably
> want some way for somebody to have a minimal sql setup required.  Like we
> have a readme somewhere that says "add the kbooks" database and create user
> "kbooks-admin" and then have everything else be done by kbooks or some
> initialization script automatically ... especially the table creation, etc.
> This would make it easier to handle configuration changes later like if we
> need to add columns to tables or new tables.  Is this possible?

Re: [Kbooks-devel] SQL backend

[John H. <jo...@se...>]

On Mon, 13 May 2002 17:44:32 -0700, Andrew Nelson wrote:

>We can also make the program perform an autodetection on startup and create 
>the necisary databases.  However that might be .5.  :-)  There might be the 
>need for a perl script... however I'd like to avoid it.

I know that table creation should be easy in Qt... there's a QSqlQuery
class that allows you to do raw SQL, so we can do that easy enough.
Autodetection might be a little less easy to do through Qt, but it may
be possible... such as attempting to open a local postgresql, mysql or
ODBC connection... or, can the major SQL servers (including commercial
servers) be detected through a net broadcast? If so, that would make
things even easier... autodetect all available SQL servers and give the
user a choice at install... otherwise we may have to stick to localhost
server autodetection, which would probably be adequate for most small
scale users, and if not, they can enter their own damn IP address :)

>I was also thinking of having a table in the database store site wide and 
>user settings.  However it should not store security related settings.  This 
>way a user "hopefuly" does not have to be tied to a machine, and their 
>settings can "follow" them.  Any thoughts??

I agree, the database is a powerful tool that we'll know we have
available. We should use it. :)

Re: [Kbooks-devel] SQL backend

[Andrew N. <nel...@po...>]

On Tuesday 14 May 2002 07:27, you wrote:
> I know that table creation should be easy in Qt... there's a QSqlQuery
> class that allows you to do raw SQL, so we can do that easy enough.
> Autodetection might be a little less easy to do through Qt, but it may
> be possible... such as attempting to open a local postgresql, mysql or
> ODBC connection... or, can the major SQL servers (including commercial
> servers) be detected through a net broadcast? If so, that would make
> things even easier... autodetect all available SQL servers and give the
> user a choice at install... otherwise we may have to stick to localhost
> server autodetection, which would probably be adequate for most small
> scale users, and if not, they can enter their own damn IP address :)

That will work.  I think for now the server detection should be localhost and 
remote given host.  Postgre has a defined port as you know, which can be 
changed so we need to be ready for that... but I'm sure everyone knows that.

As for database detection within a server, we run a few queries to check to 
see the necisary tables are there and if they aren't then they are created 
with user approval, or the text is placed in a .sql file for the site admin 
to take care of.

> I agree, the database is a powerful tool that we'll know we have
> available. We should use it. :)

heh... it's l33t  :-)

-Andrew