django-gcal - Project Hosting on Google Code

Earlier this year Sep 19, 2009 GettingStarted (Getting started with django-gcal.) Wiki page commented on by dean.malmgren - I'm a little confused about exactly how to use this. Are you supposed to put the code from the [http://code.google.com/p/django-gcal/ djangogcal home page] in a management.py for each model you want to synchronize? I tried to do this but it isn't working for me and I'm not exactly sure where I am going wrong. My ultimate goal here is to embed a google calendar with news items for our website. I have written my own django model for a news item. The trick is synchronizing this model with a google calendar. Assuming that this step works, it is trivial to embed the google calendar in my django site. I am trying to debug so I have a few questions where I think I likely went wrong: # Is the code on the homepage supposed to be adapted and placed in a management.py file? In my case this would go within the news app. # The google calendar I would like to embed is not associated with my gmail account but with another account that uses gmail. Do I need to specify a custom feed? # What data type are the start_time and end_time objects? Are they datetime, strings, timetuples? I'm a little confused about exactly how to use this. Are you supposed to put the code from the [http://code.google.com/p/django-gcal/ djangogcal home page] in a management.py for each model you want to synchronize? I tried to do this but it isn't working for me and I'm not exactly sure where I am going wrong. My ultimate goal here is to embed a google calendar with news items for our website. I have written my own django model for a news item. The trick is synchronizing this model with a google calendar. Assuming that this step works, it is trivial to embed the google calendar in my django site. I am trying to debug so I have a few questions where I think I likely went wrong: # Is the code on the homepage supposed to be adapted and placed in a management.py file? In my case this would go within the news app. # The google calendar I would like to embed is not associated with my gmail account but with another account that uses gmail. Do I need to specify a custom feed? # What data type are the start_time and end_time objects? Are they datetime, strings, timetuples? Older Dec 07, 2008 issue 7 (Keep a cached Calendar service instance) changed by metzen - Fixed in r14 Status: Fixed Owner: metzen Fixed in r14 Status: Fixed Owner: metzen Dec 07, 2008 r14 (Keep a cached copy of the gdata CalendarService. Resolves is...) committed by metzen - Keep a cached copy of the gdata CalendarService. Resolves issue 7 Keep a cached copy of the gdata CalendarService. Resolves issue 7 Nov 27, 2008 issue 6 (Need ability to send notifications on event updates/deletion...) Status changed by metzen - Status: Fixed Status: Fixed Nov 27, 2008 issue 6 (Need ability to send notifications on event updates/deletion...) changed by metzen - Added in r13 Owner: metzen Cc: emperorofcheese Added in r13 Owner: metzen Cc: emperorofcheese Nov 27, 2008 r13 (Add ability for an Adapter to enable Google Calendar event c...) committed by metzen - Add ability for an Adapter to enable Google Calendar event change notifications Add ability for an Adapter to enable Google Calendar event change notifications Nov 27, 2008 issue 5 (value_string argument to Who() constructor does not exist) changed by metzen - Fixed in r12 http://code.google.com/p/django-gcal/source/detail?r=12 Status: Fixed Owner: metzen Fixed in r12 http://code.google.com/p/django-gcal/source/detail?r=12 Status: Fixed Owner: metzen Nov 27, 2008 r12 (Fix incorrect gdata.calendar.Who constructor parameter. ) committed by metzen - Fix incorrect gdata.calendar.Who constructor parameter. Fix incorrect gdata.calendar.Who constructor parameter. Nov 26, 2008 issue 9 (how do i define the instance parameter) changed by emperorofcheese - Hey ThreeVillage, Sorry for the delay, it's entirely my fault, and hopefully things will pick up around here now Metzen's on the project owners. Unless you're implementing a custom observer, you shouldn't need to pass in the instance variable to CalendarAdapter.get_event_data. "Instance" will be an instance of the model being observed/adapted, e.g. CalendarObserver.observe(Movie, MovieCalendarAdapter()) In this case, in calls to the MovieCalendarAdapter instance's get_event_data(...) method, the "instance" parameter will be an object of type Movie. This is a tricky one to explain, especially with Python's duck/dynamic typing, http://en.wikipedia.org/wiki/Adapter_pattern should explain it a little better. If you've got any further questions, please ask away (some code examples might be helpful, too). Status: Invalid Owner: emperorofcheese Labels: Type-Other Priority-Low −Type-Defect −Priority-Medium Hey ThreeVillage, Sorry for the delay, it's entirely my fault, and hopefully things will pick up around here now Metzen's on the project owners. Unless you're implementing a custom observer, you shouldn't need to pass in the instance variable to CalendarAdapter.get_event_data. "Instance" will be an instance of the model being observed/adapted, e.g. CalendarObserver.observe(Movie, MovieCalendarAdapter()) In this case, in calls to the MovieCalendarAdapter instance's get_event_data(...) method, the "instance" parameter will be an object of type Movie. This is a tricky one to explain, especially with Python's duck/dynamic typing, http://en.wikipedia.org/wiki/Adapter_pattern should explain it a little better. If you've got any further questions, please ask away (some code examples might be helpful, too). Status: Invalid Owner: emperorofcheese Labels: Type-Other Priority-Low −Type-Defect −Priority-Medium Oct 26, 2008 issue 9 (how do i define the instance parameter) reported by threevillage - Hi emperorofcheese, I just want to know how to figure out invoke the get_event_data(self,instance). I'm not sure how to pass the instance variable. Hi emperorofcheese, I just want to know how to figure out invoke the get_event_data(self,instance). I'm not sure how to pass the instance variable. Sep 18, 2008 issue 8 (Need a means to allow users to provide their own instance to...) reported by metzen - Currently, users are forced to use the djangogcal model/database table to provide an instance -> calendar event id mapping. Some users may want to roll their own translation for this, and it would be nice to have the abilitiy to customize the behavior of observer.get_event for this purpose. I propose an additional method to override on an adapter where a user could implement their own instance -> event id mapping. See attached patch. Currently, users are forced to use the djangogcal model/database table to provide an instance -> calendar event id mapping. Some users may want to roll their own translation for this, and it would be nice to have the abilitiy to customize the behavior of observer.get_event for this purpose. I propose an additional method to override on an adapter where a user could implement their own instance -> event id mapping. See attached patch. Sep 15, 2008 issue 7 (Keep a cached Calendar service instance) reported by metzen - Currently, the observer will fetch a new Calendar service instance during every action. Wouldn't it be a bit more efficient to only make one ProgrammaticLogin call and reuse that service for any action that follows later on? See attached diff. Currently, the observer will fetch a new Calendar service instance during every action. Wouldn't it be a bit more efficient to only make one ProgrammaticLogin call and reuse that service for any action that follows later on? See attached diff. Sep 12, 2008 issue 6 (Need ability to send notifications on event updates/deletion...) commented on by metzen - Yeah, having it on the Adapter sounds a bit better, so you can choose which models you'd like to get notifications on. Yeah, having it on the Adapter sounds a bit better, so you can choose which models you'd like to get notifications on. Sep 12, 2008 issue 5 (value_string argument to Who() constructor does not exist) changed by emperorofcheese - That's a d'oh on my part, this'll be fixed promptly. Status: Accepted Owner: emperorofcheese Labels: Priority-Critical Milestone-Release1.0 −Priority-Medium That's a d'oh on my part, this'll be fixed promptly. Status: Accepted Owner: emperorofcheese Labels: Priority-Critical Milestone-Release1.0 −Priority-Medium Sep 12, 2008 issue 6 (Need ability to send notifications on event updates/deletion...) Owner changed by emperorofcheese - Doh, forgot to take ownership. Owner: emperorofcheese Doh, forgot to take ownership. Owner: emperorofcheese Sep 12, 2008 issue 6 (Need ability to send notifications on event updates/deletion...) changed by emperorofcheese - I see what you mean, I'm tempted to add a method to CalendarAdapter, along the lines of "CalendarAdapter.can_notify(self, instance) -> True\|False", instead of making it apply to an entire observer. I'll inevitably get a little tired of reading up on computer forensics, so expect to see this implemented sometime today ;) Status: Started Labels: Type-Enhancement −Type-Defect I see what you mean, I'm tempted to add a method to CalendarAdapter, along the lines of "CalendarAdapter.can_notify(self, instance) -> True\|False", instead of making it apply to an entire observer. I'll inevitably get a little tired of reading up on computer forensics, so expect to see this implemented sometime today ;) Status: Started Labels: Type-Enhancement −Type-Defect Sep 11, 2008 issue 6 (Need ability to send notifications on event updates/deletion...) reported by metzen - It would be nice if an observer could be configured to send notifications on event updates and deletes. see attached patch. It would be nice if an observer could be configured to send notifications on event updates and deletes. see attached patch. Sep 11, 2008 issue 5 (value_string argument to Who() constructor does not exist) reported by metzen - Maybe you've developed this against a different gdata version (I'm still fairly new to gdata, so I'm not sure), but I don't see a 'value_string' argument to the gdata.calendar.Who constructor. (see current svn at http://code.google.com/p/gdata-python-client/source/browse/trunk/src/gdata/calendar/__init__.py) Is this a coding error, or differing api version? I've attached a patch to make it work with the version I'm using (1.1.1) and it seems compatible for 1.2.0 as well. Maybe you've developed this against a different gdata version (I'm still fairly new to gdata, so I'm not sure), but I don't see a 'value_string' argument to the gdata.calendar.Who constructor. (see current svn at http://code.google.com/p/gdata-python-client/source/browse/trunk/src/gdata/calendar/__init__.py) Is this a coding error, or differing api version? I've attached a patch to make it work with the version I'm using (1.1.1) and it seems compatible for 1.2.0 as well. Sep 11, 2008 issue 4 (observer does not handle expired EditLinks) reported by metzen - In its current implementation, observer update and delete will fail when the edit link it receives from event.GetEditLink().href has already expired (been used by another source). I've attached a patch to have it retry on failure to make sure the action goes through. In its current implementation, observer update and delete will fail when the edit link it receives from event.GetEditLink().href has already expired (been used by another source). I've attached a patch to have it retry on failure to make sure the action goes through. Sep 11, 2008 issue 3 (observer.observe_related improperly sends class to selector(...) Status changed by emperorofcheese - Patched in r11. Status: Fixed Patched in r11. Status: Fixed Sep 11, 2008 issue 2 (observer.observe_related does properly connect a receiver) Status changed by emperorofcheese - Patched in r11. Status: Fixed Patched in r11. Status: Fixed Sep 11, 2008 r11 (Applied the fixes provided by metzen@gmail.com.) committed by emperorofcheese - Applied the fixes provided by metzen@gmail.com. Applied the fixes provided by metzen@gmail.com. Sep 11, 2008 issue 3 (observer.observe_related improperly sends class to selector(...) changed by emperorofcheese - Thanks for the patch, and d'oh (again) on my behalf - applying it :) Status: Started Labels: Priority-Critical Milestone-Release1.0 −Priority-Medium Thanks for the patch, and d'oh (again) on my behalf - applying it :) Status: Started Labels: Priority-Critical Milestone-Release1.0 −Priority-Medium Sep 11, 2008 issue 2 (observer.observe_related does properly connect a receiver) changed by emperorofcheese - Thanks for the patch, and d'oh on my behalf - applying it :) Status: Started Labels: Priority-Critical Milestone-Release1.0 −Priority-Medium Thanks for the patch, and d'oh on my behalf - applying it :) Status: Started Labels: Priority-Critical Milestone-Release1.0 −Priority-Medium Sep 09, 2008 issue 2 (observer.observe_related does properly connect a receiver) commented on by metzen - D'oh, title of this bug should have been: observer.observe_related does NOT properly connect a receiver D'oh, title of this bug should have been: observer.observe_related does NOT properly connect a receiver Sep 09, 2008 issue 3 (observer.observe_related improperly sends class to selector(...) reported by metzen - The docstring of CalendarObserver.observe_related indicates that the 'selector' argument should be a function which takes in an instance of the 'related' model. However, in the current implementation, the class, or model is passed to this function, and not the actual 'related' instance. I've attached a diff to correct this. The docstring of CalendarObserver.observe_related indicates that the 'selector' argument should be a function which takes in an instance of the 'related' model. However, in the current implementation, the class, or model is passed to this function, and not the actual 'related' instance. I've attached a diff to correct this. Sep 09, 2008 issue 2 (observer.observe_related does properly connect a receiver) reported by metzen - (Version r10 from SVN) The observe_related method of observer.CalendarObserver uses an inner function (on_related_update) to handle the django signal callback. However, since this is an inner function, it looses all strong references once the function goes out of scope. If a python object has only weak references, it falls prey to the garbage collector. In this case, Django can't use the inner function as a callback handler unless a strong reference is used in the dispatch system. see docstring for django.dispatch.dispatcher.connect (http://code.djangoproject.com/browser/django/trunk/django/dispatch/dispatcher.py) I've attached a diff that corrects this issue, and forces the signal dispatcher to keep a strong reference to the inner function. (Version r10 from SVN) The observe_related method of observer.CalendarObserver uses an inner function (on_related_update) to handle the django signal callback. However, since this is an inner function, it looses all strong references once the function goes out of scope. If a python object has only weak references, it falls prey to the garbage collector. In this case, Django can't use the inner function as a callback handler unless a strong reference is used in the dispatch system. see docstring for django.dispatch.dispatcher.connect (http://code.djangoproject.com/browser/django/trunk/django/dispatch/dispatcher.py) I've attached a diff that corrects this issue, and forces the signal dispatcher to keep a strong reference to the inner function. Sep 09, 2008 GettingStarted (Getting started with django-gcal.) Wiki page edited by emperorofcheese Sep 08, 2008 r9 (Updated module comments to reflect the new package name.) committed by emperorofcheese - Updated module comments to reflect the new package name. Updated module comments to reflect the new package name. Sep 08, 2008 issue 1 (Package needs a module name more specific than 'gcalendar') Status changed by emperorofcheese - The package has been renamed to djangogcal. Status: Fixed The package has been renamed to djangogcal. Status: Fixed Sep 08, 2008 r8 (The constructor for djangogcal.adapter.RawEventData now requ...) committed by emperorofcheese - The constructor for djangogcal.adapter.RawEventData now requires the 'when' argument, and accepts arbitrary named parameters. The constructor for djangogcal.adapter.RawEventData now requires the 'when' argument, and accepts arbitrary named parameters. Sep 08, 2008 r7 (Changed package name from gcalendar to djangogcal.) committed by emperorofcheese - Changed package name from gcalendar to djangogcal. Changed package name from gcalendar to djangogcal. Aug 27, 2008 r6 (Adapters are now stateless, and should be instantiated by th...) committed by emperorofcheese - Adapters are now stateless, and should be instantiated by the developer and passed in the call to "CalendarObserver.observe(...)". The CalendarAdapter methods now accept an instance of the target model as their only parameter. Adapters are now stateless, and should be instantiated by the developer and passed in the call to "CalendarObserver.observe(...)". The CalendarAdapter methods now accept an instance of the target model as their only parameter. Aug 21, 2008 issue 1 (Package needs a module name more specific than 'gcalendar') commented on by metzen - I'd be ok with djangogcal. That way, it more closely matches the name you chose for the Google project hosting, and no underscores. I'd be ok with djangogcal. That way, it more closely matches the name you chose for the Google project hosting, and no underscores. Aug 21, 2008 issue 1 (Package needs a module name more specific than 'gcalendar') changed by emperorofcheese - I agree this is a problem, and between now and 1.0 (coinciding roughly with Django 1.0) I'll try and think of a better package name. Unfortunately, I think underscores in package names are a little ugly, and PEP-8 (http://www.python.org/dev/peps/pep-0008/) agrees with my pedantry: Modules should have short, all-lowercase names. Underscores can be used in the module name if it improves readability. Python packages should also have short, all-lowercase names, although the use of underscores is discouraged. Which leaves me a little stumped. Names like `dgcalendar` seems prone to typing errors, and `dgcal` even more so. Does anybody have any other ideas? If nothing better comes along before 1.0, it'll probably be `django_gcal`. Status: Accepted Owner: emperorofcheese Labels: Milestone-Release1.0 I agree this is a problem, and between now and 1.0 (coinciding roughly with Django 1.0) I'll try and think of a better package name. Unfortunately, I think underscores in package names are a little ugly, and PEP-8 (http://www.python.org/dev/peps/pep-0008/) agrees with my pedantry: Modules should have short, all-lowercase names. Underscores can be used in the module name if it improves readability. Python packages should also have short, all-lowercase names, although the use of underscores is discouraged. Which leaves me a little stumped. Names like `dgcalendar` seems prone to typing errors, and `dgcal` even more so. Does anybody have any other ideas? If nothing better comes along before 1.0, it'll probably be `django_gcal`. Status: Accepted Owner: emperorofcheese Labels: Milestone-Release1.0 Aug 21, 2008 r5 (Updated to match the Python Style Guide (PEP-8).) committed by emperorofcheese - Updated to match the Python Style Guide (PEP-8). Updated to match the Python Style Guide (PEP-8). Aug 20, 2008 issue 1 (Package needs a module name more specific than 'gcalendar') commented on by metzen - Or better yet, how about 'django_gcal', to match the Google project name? Or better yet, how about 'django_gcal', to match the Google project name? Aug 20, 2008 issue 1 (Package needs a module name more specific than 'gcalendar') commented on by metzen - Err, that should have read 'django_gcalendar' not 'django-gcalendar'. No dashes in module names. facepalm Err, that should have read 'django_gcalendar' not 'django-gcalendar'. No dashes in module names. facepalm Aug 20, 2008 issue 1 (Package needs a module name more specific than 'gcalendar') reported by metzen - Hi there, I've been looking to integrate the functionality from this project for a little while now (actually first from http://www.djangosnippets.org/snippets/322/, then from http://code.google.com/p/django-googlecalendar, but now I see you've moved the project here. :) If I could make one small request, please rename the base python module for this package from gcalendar to something a bit more descriptive, like django-gcalendar, or something similar. (D'oh looks like there's another project with the name django-gcalendar: http://code.google.com/p/django-gcalendar/, as I'm sure you've probably noticed.) I think the name gcalendar is a bit too generic, and could conflict with other packages installed in a Python environment. Hi there, I've been looking to integrate the functionality from this project for a little while now (actually first from http://www.djangosnippets.org/snippets/322/, then from http://code.google.com/p/django-googlecalendar, but now I see you've moved the project here. :) If I could make one small request, please rename the base python module for this package from gcalendar to something a bit more descriptive, like django-gcalendar, or something similar. (D'oh looks like there's another project with the name django-gcalendar: http://code.google.com/p/django-gcalendar/, as I'm sure you've probably noticed.) I think the name gcalendar is a bit too generic, and could conflict with other packages installed in a Python environment. Aug 20, 2008 RelatedModels (One-sentence summary of this page.) Wiki page added by emperorofcheese Aug 20, 2008 GettingStarted (Getting started with django-gcal.) Wiki page added by emperorofcheese Aug 20, 2008 r2 (Initial project import.) committed by emperorofcheese - Initial project import. Initial project import. Aug 20, 2008 Project django-gcal created by emperorofcheese - Synchronise your models with Google Calendar Synchronise your models with Google Calendar

GettingStarted (Getting started with django-gcal.) Wiki page commented on by dean.malmgren - I'm a little confused about exactly how to use this. Are you supposed to put the code from the [http://code.google.com/p/django-gcal/ djangogcal home page] in a management.py for each model you want to synchronize? I tried to do this but it isn't working for me and I'm not exactly sure where I am going wrong. My ultimate goal here is to embed a google calendar with news items for our website. I have written my own django model for a news item. The trick is synchronizing this model with a google calendar. Assuming that this step works, it is trivial to embed the google calendar in my django site. I am trying to debug so I have a few questions where I think I likely went wrong: # Is the code on the homepage supposed to be adapted and placed in a management.py file? In my case this would go within the news app. # The google calendar I would like to embed is not associated with my gmail account but with another account that uses gmail. Do I need to specify a custom feed? # What data type are the start_time and end_time objects? Are they datetime, strings, timetuples?

I'm a little confused about exactly how to use this. Are you supposed to put the code from the [http://code.google.com/p/django-gcal/ djangogcal home page] in a management.py for each model you want to synchronize? I tried to do this but it isn't working for me and I'm not exactly sure where I am going wrong. My ultimate goal here is to embed a google calendar with news items for our website. I have written my own django model for a news item. The trick is synchronizing this model with a google calendar. Assuming that this step works, it is trivial to embed the google calendar in my django site. I am trying to debug so I have a few questions where I think I likely went wrong: # Is the code on the homepage supposed to be adapted and placed in a management.py file? In my case this would go within the news app. # The google calendar I would like to embed is not associated with my gmail account but with another account that uses gmail. Do I need to specify a custom feed? # What data type are the start_time and end_time objects? Are they datetime, strings, timetuples?

Earlier this year

Older