Calendarv2 - Revision history

Vinny: /* Thoughts: */

2010-12-15T06:47:01Z

‎Thoughts:

2010-12-15T06:45:23Z

‎Thoughts:

2010-12-15T06:44:14Z

‎What needs to be done till the alpha release?

2010-12-15T06:43:33Z

‎Thoughts:

2010-12-14T08:02:48Z

2010-12-14T07:32:11Z

‎Future plans/improvements:

2010-11-29T03:24:43Z

‎Future plans/improvements:

2010-11-28T03:07:17Z

‎What needs to be done till the alpha release?

2010-11-28T03:05:54Z

‎Future plans/improvements:

2010-11-23T16:49:03Z

← Older revision		Revision as of 06:47, 15 December 2010
Line 21:		Line 21:
	* addslashes is used extensively to sanitize input. Should Geeklog's filter routines be used instead in places?		* addslashes is used extensively to sanitize input. Should Geeklog's filter routines be used instead in places?
	* upload.php -- mentioned in a previous email, but we should be using the upload.class.php that comes with Geeklog.		* upload.php -- mentioned in a previous email, but we should be using the upload.class.php that comes with Geeklog.
		+	* Geeklog allows the use of InnoDB tables. The calendar should use whatever table type the rest of Geeklog is using.

← Older revision		Revision as of 06:45, 15 December 2010
Line 20:		Line 20:
	** Should the class be aware of whether the event is the moderation or event table? That way the "modify" and "modify_moderation" functions wouldn't be necessary (the class would know the appropriate table automatically).		** Should the class be aware of whether the event is the moderation or event table? That way the "modify" and "modify_moderation" functions wouldn't be necessary (the class would know the appropriate table automatically).
	* addslashes is used extensively to sanitize input. Should Geeklog's filter routines be used instead in places?		* addslashes is used extensively to sanitize input. Should Geeklog's filter routines be used instead in places?
		+	* upload.php -- mentioned in a previous email, but we should be using the upload.class.php that comes with Geeklog.

@@ Line 4: / Line 4: @@
 * Render recurring events immediately after an event was created, not just on page load.
 * Review Security (specifically user access rights to events)
 == Future plans/improvements: ==

← Older revision		Revision as of 06:43, 15 December 2010
Line 15:		Line 15:
	* AEvents Class		* AEvents Class
	** Should the _events array be an associative array with the events' EIDs as keys?		** Should the _events array be an associative array with the events' EIDs as keys?
		+	* Event Class
		+	** Should the class be aware of whether the event already exists in the DB? That way it know which of "update_to_database" and "save_to_database" function is appropriate?
		+	** Should the class be aware of whether the event is the moderation or event table? That way the "modify" and "modify_moderation" functions wouldn't be necessary (the class would know the appropriate table automatically).
		+	* addslashes is used extensively to sanitize input. Should Geeklog's filter routines be used instead in places?

@@ Line 1: / Line 1: @@
 == What needs to be done till the alpha release? ==
 * Fix Ical Support. <br>
 * Render recurring events immediately after an event was created, not just on page load.
 == Future plans/improvements: ==
@@ Line 10: / Line 10: @@
 * Conversion script to convert existing Geeklog calendars to Calendarv2.
 * Use PHP's locale settings for Day of Week, Month Names, etc instead of the language file [http://php.net/manual/en/function.setlocale.php]

← Older revision		Revision as of 07:32, 14 December 2010
Line 9:		Line 9:
	* When Geeklog moves to PHP 5.3 (or earlier, as time permits) switch to using MySQL Datetime types. PHP 5.3's enhanced DateTime class makes the switch easier.		* When Geeklog moves to PHP 5.3 (or earlier, as time permits) switch to using MySQL Datetime types. PHP 5.3's enhanced DateTime class makes the switch easier.
	* Conversion script to convert existing Geeklog calendars to Calendarv2.		* Conversion script to convert existing Geeklog calendars to Calendarv2.
		+	* Use PHP's locale settings for Day of Week, Month Names, etc instead of the language file [http://php.net/manual/en/function.setlocale.php]

← Older revision		Revision as of 03:24, 29 November 2010
Line 8:		Line 8:

	* When Geeklog moves to PHP 5.3 (or earlier, as time permits) switch to using MySQL Datetime types. PHP 5.3's enhanced DateTime class makes the switch easier.		* When Geeklog moves to PHP 5.3 (or earlier, as time permits) switch to using MySQL Datetime types. PHP 5.3's enhanced DateTime class makes the switch easier.
		+	* Conversion script to convert existing Geeklog calendars to Calendarv2.

← Older revision		Revision as of 03:05, 28 November 2010
Line 10:		Line 10:

	== Future plans/improvements: ==		== Future plans/improvements: ==
		+
		+	* When Geeklog moves to PHP 5.3 (or earlier, as time permits) switch to using MySQL Datetime types. PHP 5.3's enhanced DateTime class makes the switch easier.

← Older revision		Revision as of 16:49, 23 November 2010
Line 3:		Line 3:

	- Fix Ical Support. <br>		- Fix Ical Support. <br>
−	- Render recurring events immediately after it was created not just on page load.	+	- Render recurring events immediately after an event was created, not just on page load.