php-calendar-discussion — development, announcements, etc

RE: [Php-calendar-discussion] welcome to the list

[Sons, F. <Fra...@da...>]

Sorry for the delay - either the list is still dead or i don't get other =
mails - if the list is used, can someone please reply to me directly? ;)

Anyway, i don't have that much time to test new versions atm, i lost my =
old webhoster (and lost my own version of the calender where i created =
login etc.) and i'm too lazy/don't have that much time to set up a new =
version and create login etc. again.

Maybe during xmas vacation or at the beginning of 2003 *g*

about the new ideas:

- a standard for calendar data sounds nice, but i think you need to talk =
to other developers of calendars before and ask them if they would like =
something like that too. makes no sense to create a standard if no one =
uses it, right?

- i never had problems with the install script, can't say anything to =
that

- anonymous/registrated user post, well - my edited version had support =
for login and only show entries to the owner, but he could also make an =
entry "public" so everyone could see it, he even could also make it =
editable, so everyone could change it also...
i guess it wouldn't have been that hard to allow anonymous postings as =
well, but it was based on 0.5, so the code is as bit older *g*

if you want to take a look at it anyway, i can try to find it and send =
it to you Sean.

- language support, i changed the calendar to display english/german =
before it has that support, need to test your version before i can say =
more to that *g*

Frank

> -----Original Message-----
> From: Sean Proctor [mailto:spr...@cc...]
> Sent: Monday, December 02, 2002 11:05 PM
> To: php...@li...
> Subject: [Php-calendar-discussion] welcome to the list
>=20
>=20
> Hi,
> I justed added a lot of you to this list.  Please feel free=20
> to unsubscribe if
> you are uninterested.  I've only added people who have=20
> contacted me and
> showed what I thought was a significant amount of interest in=20
> the calendar.
> If I was mistaken, or out of line to do this, I'm sorry.
>=20
> I hope this list will become a place where people can talk=20
> about ideas or
> work they're done for the calendar, and problems they've had,=20
> etc.  It would
> be nice if when people contact me with problems, I could get=20
> other people
> help diagnose and solve those problems.  Also this will be=20
> where I let people
> know what's up with the calendar, or whoever else is working=20
> on it lets
> us know. :)
>=20
> I know the calendar is a relatively simple piece of software,=20
> but I would
> like to have a small discussion of ideas.  Here are mine:
> -write a gtk front end
> -follow some sort of standard for storing or sending data. =20
> (to enable other
> calendars to use it, and possibly to allow us to retrieve=20
> data from remote
> calendars.  this would enable the gtk part to work)
> -fix the install script.  a few people have complained of it=20
> causing chaos
> with their databases (a few of you might be on this list), that's bad.
> -user support.  I always want an option for anonymous users=20
> to post, but it
> would be nice to allow real users to have protected data=20
> (anonymous users
> couldn't delete it)
> -better language support.  I wrote the gettext stuff, but I haven't
> maintained it and it doesn't work for me now. (it could be=20
> php isn't set up
> properly)
>=20
> Also, I would really like someone to help me maintain the=20
> calendar.  If
> someone could test the CVS version right now and make sure=20
> it's all working,
> I'll release an 0.8.
>=20
> future:
> for 1.0 I want to get user support, I'm not going to make a=20
> 1.0 before then.
>=20
> -Sean
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Get the new Palm Tungsten T=20
> handheld. Power & Color in a compact size!=20
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
> _______________________________________________
> Php-calendar-discussion mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/php-calendar-discussion
>=20

[Php-calendar-discussion] welcome to the list

[Sean P. <spr...@cc...>]

Hi,
I justed added a lot of you to this list.  Please feel free to unsubscribe if
you are uninterested.  I've only added people who have contacted me and
showed what I thought was a significant amount of interest in the calendar.
If I was mistaken, or out of line to do this, I'm sorry.

I hope this list will become a place where people can talk about ideas or
work they're done for the calendar, and problems they've had, etc.  It would
be nice if when people contact me with problems, I could get other people
help diagnose and solve those problems.  Also this will be where I let people
know what's up with the calendar, or whoever else is working on it lets
us know. :)

I know the calendar is a relatively simple piece of software, but I would
like to have a small discussion of ideas.  Here are mine:
-write a gtk front end
-follow some sort of standard for storing or sending data.  (to enable other
calendars to use it, and possibly to allow us to retrieve data from remote
calendars.  this would enable the gtk part to work)
-fix the install script.  a few people have complained of it causing chaos
with their databases (a few of you might be on this list), that's bad.
-user support.  I always want an option for anonymous users to post, but it
would be nice to allow real users to have protected data (anonymous users
couldn't delete it)
-better language support.  I wrote the gettext stuff, but I haven't
maintained it and it doesn't work for me now. (it could be php isn't set up
properly)

Also, I would really like someone to help me maintain the calendar.  If
someone could test the CVS version right now and make sure it's all working,
I'll release an 0.8.

future:
for 1.0 I want to get user support, I'm not going to make a 1.0 before then.

-Sean

[Php-calendar-discussion] first message, I think

[Sean P. <spr...@cc...>]

this is just a test.  if anyone is subscribed already, sorry

Sean