Re: [PHPiCalendar-DEV] File or DB driven? Or both?

[<ja...@hj...>]

Hi..


On fredag, okt 4, 2002, at 17:41 Europe/Copenhagen, Even Andr=E9 Fiskvik=20=

wrote:

> Ok, I think I'm getting your picture regarding XOOPS now.
> You are seeing XOOPS managing all of the user administration and user=20=

> management?
> This would limit the users of the phpicalendar, because if they really=20=

> wanted to use a db, they would have to have XOOPS to use it,
> wouldn't that be a bad idea?

Actually, I was more thinking about XOOPS as an option. I use it on=20
some of my sites, and IF it would be enabled as a module in XOOPS (a=20
long with being standalone!), using the same userdb as XOOPS would be=20
natural. It could also be a possible solution to use both PHP iCal &=20
XOOPS users... who knows..

> As for theme management, this is an easy thing to do ourselves. Smarty=20=

> (smarty.php.net) is a fine class for doing oop "theming".

Smarty is what XOOPS is moving to, in the next major release, so Smarty=20=

theme support would be natural, and might be the cool way to go.

> I wouldn't want to limit the users to just use MySQL either, with the=20=

> DB class from PEAR (pear.php.net), you can use almost any database you=20=

> like.
> I have myself the possibility of testing at least MySQL, PostgreSQL=20
> and Oracle.

Sure! MySQL was just a suggestion.

> Of course, using XOOPS would help us in that way that we wouldn't have=20=

> to write the code for user management ourselves.
> I don't see any further benefits from using XOOPS, but please correct=20=

> me if I'm wrong..

You are right in Getting benefits. I would just like to use this as a=20
module in XOOPS in the future, if possible. Giving XOOPS the benefits=20
of PHP iCal.

	Jakob Peterh=E4nsel

"Tell me why, don't we try, not to break our hearts
   and make it so hard for our selfs"
P.S.B. 1987

Email: ja...@hj...
AIM: Marook