[geeklog-devtalk] Making the Calendar A Plugin

[Tony Bibbs]

Feel free to send ideas on design, etc to the list.  While we all don't 
code as much as we'd like, looking through code giving 
ideas/validation/etc is something easy we can all do.

Thanks,

--Tony

Michael Askew wrote:


> -----BEGIN PGP SIGNED MESSAGE-----

> Hash: SHA1

>

> Tony,

>

> I'm not prone to producing reams of documentation before I dive into 

> coding (although I do *read* reams of documentation), but I will 

> certainly keep Geeklog 2's needs in mind. The code I began writing 

> last year to parse the ical file format did take the form of a PHP 

> class, and I will definitely try to make the rest of the new code 

> reusable where possible in order to save work for Geeklog 2 implementors.

>

> - -Michael

>

> On Feb 6, 2005, at 7:08 PM, Tony Bibbs wrote:

>

>> Michael, given your lofty goals, I think it might be worth noting 

>> that GL2 is going to need a calendar plugin.  In fact, in GL2 

>> everything is a plugin.  Anyway, without wanting to slow your 

>> progress down, I'd like to request that you think outside of 1.3.x 

>> for this.  In other words, I'd like to see you gather some good 

>> requirements for the new plugin and document how you will design the 

>> solution so that someone on the GL2 side can implement it with 

>> little-to-no hassle.

>>

>> I realize this is a lot more than what you were thinking but if you 

>> are agreeable, I'd have no problem taking your ideas and including 

>> them when we go to write the calendar plugin.

>>

>> --Tony

>>

>> Michael Askew wrote:

>>

>>> -----BEGIN PGP SIGNED MESSAGE-----

>>> Hash: SHA1

>>>

>>> Howdy,

>>>

>>> I opened feature request #364 a few weeks ago because I would like 

>>> to turn the Geeklog calendar into a plugin. In addition to causing 

>>> everyone headache's during the transition (joke!!!), I wanted to do 

>>> this so that calendar could be easily disabled by sites that don't 

>>> need it, or replaced with a different calendar plugin (which is what 

>>> I want to work on next).

>>>

>>> I have made significant progress on this and I have set up a public 

>>> test site where the "plugged-in" calendar can be seen in action 

>>> along side the most recent CVS version of geeklog (which still has 

>>> the "built-in" calendar). The test site is:

>>>

>>>     http://demo.fbcrsingles.org

>>>

>>> Please drop by and have a look. I would really like to get this into 

>>> the official Geeklog distribution (along with removing the core 

>>> calendar).

>>>

>>> Because the site has both the built-in and plugged-in calendars, 

>>> there are two "Upcoming Events" blocks, two "My calendar" links in 

>>> the User menu, two "Events" links in the admin menu, etc. In theory 

>>> the only differences should be the URLs of the pages and the fact 

>>> that the plugin calendar can be removed by disabling or uninstalling 

>>> its plugin; any functional differences are probably bugs that need 

>>> to be addressed, so please mention them.

>>>

>>> Thanks,

>>> - -Michael Askew

>>> -----BEGIN PGP SIGNATURE-----

>>> Version: GnuPG v1.2.4 (Darwin)

>>>

>>> iD8DBQFCBxuGnjSMxT8+onIRArL5AKCUD5xUJcbL/MiI2UJAeCpVJRP6TgCfbJTR

>>> LMLJMhhErq+O+8ifxT1o2w4=

>>> =9Y7W

>>> -----END PGP SIGNATURE-----

>>>

>>> _______________________________________________

>>> geeklog-devtalk mailing list

>>> geeklog-devtalk at lists.geeklog.net

>>> http://lists.geeklog.net/listinfo/geeklog-devtalk

>>

>>

>>

>> _______________________________________________

>> geeklog-devtalk mailing list

>> geeklog-devtalk at lists.geeklog.net

>> http://lists.geeklog.net/listinfo/geeklog-devtalk

>

> -----BEGIN PGP SIGNATURE-----

> Version: GnuPG v1.2.4 (Darwin)

>

> iD8DBQFCDc4unjSMxT8+onIRAr/cAJ9ag+2WlEkK7M/McVyvCFoFL9a5pgCguFVK

> G33dTZxU7jkFgajsByfhZ/I=

> =q0Xe

> -----END PGP SIGNATURE-----

>

> _______________________________________________

> geeklog-devtalk mailing list

> geeklog-devtalk at lists.geeklog.net

> http://lists.geeklog.net/listinfo/geeklog-devtalk