I will be glad to. It will take me a bit to make it useable outside of
my application.
I might even include a "record layout" for a calendar event. That's a
well kept secret. ;^)
(actually it's not a secret but does take some figuring out. "Records"
are objects that contain fields and collections.)
Jeff
---------------
Jeff Johnson
[email protected]
(623) 582-0323
www.san-dc.com
www.arelationshipmanager.com
On 05/30/2013 09:16 AM, John Harvey wrote:
Okay, now that you've done the bleeding, how about freeing up the code! Lol
John
-----Original Message-----
From: ProFox [mailto:profox-bou [email protected]] On Behalf Of Jeff Johnson
Sent: Thursday, May 30, 2013 10:09 AM
To: [email protected]
Subject: Re: [NF] Google Calendar API - Solved!
Looking through all of the documentation and looking at code I found out
that there is - in fact - an entry id that does not change. The etag is a
version id used for versioning the entry. If I add an entry in my app and
then change it on my phone, the etag will change but the entry id will not.
It only took me about 10 hours to find the answer to this one.
Now that I have changed over to using the entry id everything works great.
Two way synchronization between my app and the Google Calendar.
Jeff
---------------
Jeff Johnson
[email protected]
(623) 582-0323
www.san-dc.com
www.arelationshipmanager.com
On 05/30/2013 06:08 AM, Jeff Johnson wrote:
Sytze: I modified the Python example calendar class and created an
exe. In VFP, I create what might be called a parameter file. When I
run the exe using the run command it reads the parameter file, does
the work, then it writes the results in a response file which I read
in VFP to complete the process. It works flawlessly. The problem I
am having is that there is no way I can tell to reference a calendar
event unless it was created in a controlled environment. Every time a
change is made, the ID changes.
I have been using this technique to read data from on board computers
and communications devices for years. Before Python I used C.
Jeff
---------------
Jeff Johnson
[email protected]
(623) 582-0323
www.san-dc.com
www.arelationshipmanager.com
On 05/29/2013 06:26 PM, Sytze de Boer wrote:
If this relates to a VFP APP, I sure would like to hear more.
I really want to integrate with Google Calendar and I have been stuck
for a long time (Actually, I'm still on base 1)
On Thu, May 30, 2013 at 12:05 PM, Paul McNett <[email protected]> wrote:
On 5/29/13 3:28 PM, Jeff Johnson wrote:
On 05/29/2013 02:41 PM, Paul McNett wrote:
On 5/29/13 2:27 PM, Jeff Johnson wrote:
I have googled it and tried many variations of the request. What
I am
getting is a
302 redirect. I have tried using the id where the entry was
redirected and all sorts
of suggestions, but I am stumped.
Have you read:
https://developers.google.com/google-apps/calendar/v2/developers_gui
de_protocol
and searched for 302 in that page?
Paul
Paul: Yes. I have been using that as well as the Python
documentation.
Also in
Googling the redirects there is some argument as to whether or not
it is
a bug. The
Python coders say that it is intermittent and therefore does not
need
fixing.
Basically what happens is that the original entry is temporarily
moved
and give a
gsessionid. I pick that up and call it again but it still redirects.
It appears
that a whole bunch of developers are experiencing it and I have not
found a solution
as of yet. I have tried several work a rounds which did not work
either. I was just
wondering if anyone in here has any experience with accessing
calendar
events from
two different sources. ie, an application and a smart phone. If I
access everything
from the application it works 100% including updates.
Well if a whole bunch of devs are seeing a problem, that's probably
good news.
Paul
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
