salimoha / googlecl

Automatically exported from code.google.com/p/googlecl
0 stars 0 forks source link

Calendar add range not working as I expected #250

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. google calendar add "blah test blah 08/11/2010 10:30:22 AM,08/11/2010 
10:31:25 AM"
2. google calendar add "blah test blah 08/11/2010 10:30:22 AM-08/11/2010 
10:31:25 AM"

What is the expected output? What do you see instead?
I was hoping to see a start and end time get created.

Instead it looks like it strips out the first date leaving seconds and  AM/PM 
fields and then strips out the second date leaving the hours, minutes, seconds 
and AM/PM fields. 

Result in calendar is as follows:
Title of Meeting: blah test blah 22 AM 10:31:25 AM
Time shows a quick add of an hour meeting 10:30 AM - 11:30 AM

What version of the product are you using? On what operating system? What
version of gdata-python-client (aka python-gdata)?

Running on Windows Server 2008
googlecl version 0.9.9

Original issue reported on code.google.com by andrew.b...@gmail.com on 11 Aug 2010 at 2:54

GoogleCodeExporter commented 9 years ago
GoogleCL uses the quick-add text feature, which you can read about here: 
http://www.google.com/support/calendar/bin/answer.py?answer=36604#text

You might want to try something along the lines of

$ google calendar add "blah test blah 8/11/2010 from 10:30 AM to 10:31 AM"

Sub-minute resolution is not supported.

Is there a reason you're including all that extraneous data in there?

Original comment by tom.h.mi...@gmail.com on 11 Aug 2010 at 5:00

GoogleCodeExporter commented 9 years ago
Yeah there is a reason.  I'm using the application to take data out of our NMS 
notification system for creating a much more appealing way to digest 
information.  It spits out the data in that format although I'm sure I can find 
a way to write a script to change it.  

There are good reason to include the extraneous data though.  We log some 
events over multiple days so: 
8/11/2010 from 10:30 AM to 10:31 AM
might need to be
8/11/2010 from 10:30 AM to 8/12/2010 10:31 AM

Its too bad seconds aren't supported... it will mean searching 60 seconds of 
logs to parse events in which we need more detail.  That being said I'm doing 
this for visual representation (high level) not for us people who can read 
logs.  :)

Thanks I'll find a way to truncate it with a script.

Original comment by andrew.b...@gmail.com on 12 Aug 2010 at 3:54

GoogleCodeExporter commented 9 years ago
I thought there was an open issue for creating more detailed calendar events, 
but I can't seem to find it. If you'd like, you can create a new Enhancement 
request along those lines.

Once such an issue is found / created, I'll merge this one into it.

Original comment by tom.h.mi...@gmail.com on 12 Aug 2010 at 1:47

GoogleCodeExporter commented 9 years ago

Original comment by tom.h.mi...@gmail.com on 28 Aug 2010 at 6:42