The database queries are only a little bit more efficient – reduced the number of queries some and added an extra index. The next version is going to completely rewrite the data model, however.
Most of the enhancements are in customization and flexibility — but at this point there are more differences from Calendar than similarities.
Thanks for the straightforward reply Joe…
Just a heads-up: I need the capability of having a specific category visible only to users who are logged-in. I will code this (locally) if you don’t. For my purposes it will probably be hardcoded at first; especially since I’m not thoroughly familiar with the code …so this may decrease its potential usefulness for others. (ie: users will have to name a category “private” to make it visible only to logged-in users) The ideal would be a “private” checkbox in the interface so that users could name the category as they wished and it would then be private.
However if you are going to make big changes to the database queries then I might wait for your changes (because my changes may be close to those regions of code) …not sure.
( Long term I want to put in support for retrieval of ics feeds but that’s a lower priority right now.)
I can pretty easily think of ways to do this without changing the code right now; just by using a quick is_user_logged_in() check in a theme template and delivering a different category set depending on the results of that check.
The idea of making private categories is a good one, though. If you wouldn’t mind adding that as a comment on my feature request post, that would be great:
http://www.joedolson.com/articles/my-calendar/requests/
I will be making massive changes to the database queries, however, yes. They won’t touch on categories or locations much, but will touch on every aspect of creating and viewing events.
Thanks for the response …feature request added!
And thanks for the excellent calendar!
