| 7b873db28bda10f98f3782b7b161cb66117034d7 |
|
07-Sep-2012 |
Marc Blank <mblank@google.com> |
cherrypick: Try to use names from time zone strings if all else fails...
Fixes b/7232823 Use time zone name when all else fails...
Change-Id: Idc2633041641db43559d32185c6bd0e2a90f4765
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| b931f82fa44c2e26e2645c0d5fde9eef3e666efd |
|
25-Sep-2012 |
Paul Westbrook <pwestbro@google.com> |
Restore MRO's Exchange
Change-Id: I312d44b5fbcd9dae008141ae1e53cc7ac7c167b5
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| bcc7188e6244176cd8b3915af50e5c0034307ba4 |
|
07-Sep-2012 |
Marc Blank <mblank@google.com> |
Try to use names from time zone strings if all else fails...
Change-Id: Ie417a6b27c731f24f0d8ccf5275df9c2fad37efd
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 2c7d44b182654120a98921cbc864be2d135c8fda |
|
17-Nov-2011 |
Marc Blank <mblank@google.com> |
Attempt to better handle screwy MSFT time zone information
* Exchange appears to send time zond data that doesn't really match
any time zone in our database; in these cases, we have been
returning a random one with the same bias (base offset w/o DST)
* In this CL, we try to do better by giving the time zone information
a bit more slack when the regular determination fails (we allow
the hour of change to be up to 4 hours different from expected,
rather than one minute). This is certainly better, though I do
not have an explanation from MSFT about the reason for the
erroneous data.
* Updated unit tests to confirm that we don't break any existing
code and do, in fact, handle the case reported below as a P1/S1
bug.
Bug: 5605219
Change-Id: I8c17a687404204aff4feb1c3009adde279110cab
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 89bee1e3d03b439f4084bc9962bb3cbffd0b878a |
|
25-Aug-2011 |
Marc Blank <mblank@google.com> |
Fix longstanding problem with all-day events VCALENDAR attachment
* Another hard-to-find, but dumb, mistake
* Fix unit test
Bug: 3334965
Change-Id: I5b18add38780bb476e29d9ae2a28247feebe21e5
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| f352bc9f29cacc61b195069e48d5c8b868660694 |
|
27-May-2011 |
Marc Blank <mblank@google.com> |
Review recurrence code and fix issues
* Turns out there were a couple of unusual cases that we weren't
handling correctly, including the referenced bug
* Reworked some of the code, and added test cases for these
unusual cases.
Bug: 4452794
Change-Id: I02734aefd895bccb8fb2bdcecc3539b1cb06adfd
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 60df2ad267f1ad7aed45b583adcd1a5bb2a006b0 |
|
27-Jul-2011 |
Marc Blank <mblank@google.com> |
Handle UNTIL properly in RRULE
* We weren't handling UNTIL properly in cases when the until date
in GMT was on a different day than in the local time zone
* Rewrite this code to take into account the local time zone
Bug: 5057748
Change-Id: I3543671d434fcd672a3151a57877ba15c2195029
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 3f8e329b8d638d02e0b48ad504b18690cefc68e9 |
|
04-Jul-2011 |
Marc Blank <mblank@google.com> |
Remove time zone test for Europe/Moscow
* On Feburary 8, 2011, President Medvedev of Russia decided to
eliminate the switch between standard time and daylight time,
leaving the country permanently in daylight time.
* This change causes the removed code to break; given that Moscow's
new time zone doesn't use daylight time, the test isn't worth
keeping.
Change-Id: I36bbb494d619871cb3fa6ec5a0340a8314295f00
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 693ed7fdd5a7ec7af87d105b76267c78a8acc3db |
|
14-Jun-2011 |
RoboErik <epastern@google.com> |
Rename Calendar.java to CalendarContract.java
Change-Id: I814ba00e8b71003c3ca99126c73069c55fa6df6a
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 7372782488977df778a33d990401ce9e397f646b |
|
14-Jun-2011 |
Marc Blank <mblank@google.com> |
Support move of Account to its own top-level class
Change-Id: Ibf427ddcfb0566354ea169997c56a67de1897c0b
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 04c880a6b5ad041f172d4b1eeecc06d6a06e4141 |
|
09-Jun-2011 |
RoboErik <epastern@google.com> |
Updates for Calendar db v 305
See https://android-git.corp.google.com/g/#change,114332 for more
details.
Change-Id: Id22c802a4d276122f38b3fd7da803ee5054540fe
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 9e86eb14c6e1f7d7730f8ca6953fdfd95fe2b143 |
|
06-May-2011 |
RoboErik <epastern@google.com> |
Update to Calendars table for db v300
See change I515b3e0a for db ugrade details.
Change-Id: I15c22f05dca11f45c3cb27392f1f53a0ffa2f0c1
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 4868e0f09b58104741a5593f6097589ac62c6ce3 |
|
06-May-2011 |
Marc Blank <mblank@google.com> |
Add more time zone parsing tests
* Add test for Hawaii time (no DST)
* Test use of default time zone when parsing
Change-Id: I6a96eca2a491e9651e65618f59c94a57b5b25f53
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 5bb2c4930c27c5385ff1baf033d1f1a97d770d14 |
|
06-May-2011 |
Marc Blank <mblank@google.com> |
Fix serious DST issue with non-DST time zones
* When finding a match for an EAS time zone without DST, we were
checking the offset, but NOT the DST status; therefore, we could
match the wrong time zone (depending on the order of items in the
TZ database)
* All users with events set up in non-DST timezones would have their
events show up at the wrong time after a DST transition
* The fix is to first check against the default time zone, and use
that if it's a match; otherwise, to use the first time zone that
matches both offset and DST availability
Bug: 4337360
Change-Id: I21d59673d2f3b0bb3e513976455071d5ea67d595
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 604a1cf6f2401d78f57edcfb702d560d9c80dd14 |
|
16-Mar-2011 |
Marc Blank <mblank@google.com> |
Add @SmallTest, @MediumTest annotations to Exchange tests
Bug: 4102002
Change-Id: I00ce41e199cc729eec1c740c18f70f57afa2f08d
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| c8e4352ea6cfa67f15140512e84af8ccede222d2 |
|
15-Feb-2011 |
Marc Blank <mblank@google.com> |
Separate Exchange application
* Clean up AndroidManifest, Android.mk, and proguard.flags
* Refactor to use emailcommon
* Remove Email app code/resources (note: this CL starts from the
single Email application)
* Update Exchange unit tests to use EmailProvider "live" and
clean up after itself
* All unit tests pass
Bug: 3442973
Change-Id: Iced00ae546dd4ddb9a66e297d3ac2dc2977e20eb
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 393208ab154d18a876842777781ab153d34a0281 |
|
13-Oct-2010 |
Marc Blank <mblank@google.com> |
Use original all-day flag when upsyncing exceptions
Bug: 3087410
Change-Id: I4bed0039758e98d4b85054876f192605eb00ee82
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| f72b4bc0ea714067ae528e63c916f0237d2202e6 |
|
31-Aug-2010 |
Marc Blank <mblank@google.com> |
Fix issues with handling FREQ=YEARLY in RRULEs
* Turns out that we weren't handling one of the cases for YEARLY
RRULE; that in which the date is specified as a day of week plus
week of month
* Also, we weren't always sending the INTERVAL properly in a few
cases
* Fix these issues and add a unit test that confirms the fixes
* Also removed an unused argument in recurrenceParser in
CalendarSyncAdapter
Bug: 2718948
Change-Id: If9146d484218e7d6bd9f5c2305d0e6a216aeed49
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| ee8c9a284b160f353e3bd918aafbc7ed528bfc4c |
|
02-Aug-2010 |
Marc Blank <mblank@google.com> |
Fix tests that broke due to DST changes in African countries
* In particular, "Africa/Casablanca" has DST in 2010 now, so it can't
be used as a test for non-DST time zones
Bug: 2882900
Change-Id: I3026ae4816fc068bd6c783fa3ca879666e796fc9
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 270a17e49669e0bfc7bd2a6303a684a7acd1266d |
|
22-May-2010 |
Marc Blank <mblank@google.com> |
Fix bugs related to TZ handling for all-day events
* In bug 2703075, all-day events from time zones at GMT or later
appear a day early; this is because the time was calculated from
the GMT date/time of the event rather than the local date/time of
the event; this CL correctly changes this to use local date/time
* In bug 2707966, device-edited all-day events disappear in Outlook
and OWA after upsync; this is due to the fact that we store all-day
events in UTC on device, whereas we need to upload all-day events
using the original (local) time zone. In this CL, we save away
the original time zone and use it on upsync
* In our decoding of Exchange time zone information, we default to
local time when we can't find a time zone that matches the bias
and DST information; we should really default to a time zone with
the same bias, if one exists; we do that in this CL.
* Add/modify unit tests
Bug: 2703075
Change-Id: Id80c481ecc0eae980b2e91dae7f105f924cfca28
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 67010d38cb168666b34431c96f331f36507e1f03 |
|
29-Apr-2010 |
Marc Blank <mblank@google.com> |
Update unit tests for invitation creation
* Tests changed/added for exception/recurrence changes in CL50201
Bug: 2640878
Change-Id: I97e5557c198aa686d1705158f2c9087c1683590e
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| edcfd554728a27a7678306ea7432bd8676ec6990 |
|
22-Apr-2010 |
Marc Blank <mblank@google.com> |
Fix upload/download of attendee status
* It turns out that the UI uses selfAttendeeStatus and the attendee's status
from the Attendees table in confusing and undocumented ways
* selfAttendeeStatus is used in the UI, but only in certain cases. Generally speaking,
the Attendees table status is definitive. However, when the user sets his status
from the UI, this data is reflected in the event's selfAttendeeStatus, since for EAS,
the user is always the owner of his calendar
* On downsync, we'll put the user's busy status into the Attendees table
* On upsync, we'll send busy status based on the user's attendee status in the
Attendees table
* We'll use selfAttendeeStatus only to determine whether the user has manually changed
his status via the UI (as before)
Bug: 2615586
Change-Id: I3a82474cfd07cbf5aa595e5214807cb55005cefa
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| e51fedc3c055588a69da56d0b818ea12ed8f706f |
|
22-Apr-2010 |
Marc Blank <mblank@google.com> |
Send correct busy status information in upsyncs to EAS
* Fix unit test that was failing
Bug: 2615382
Change-Id: I54c7bdd982d57528f55ce4f4c6804c9f532293fb
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| dc27937dda50f991de9e12b98b80ee6aa3fe348e |
|
16-Apr-2010 |
Marc Blank <mblank@google.com> |
Set selfAttendeeStatus and busyStatus properly on downsync/upsync
* Set selfAttendeeStatus on download from busy status
* Set busyStatus on upload from selfAttendeeStatus
Bug: 2587076
Change-Id: I34eaa0d3861bcec0cbfd51761b31965e44f5162b
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| b94d16528fc9c7f5dbb5c75c059f76cee2070c09 |
|
15-Apr-2010 |
Marc Blank <mblank@google.com> |
Properly decode a uid from the globalObjId in invites
* Meeting invitations in EAS include a globalObjId. It turns out
that this id is EITHER the actual uid (if Exchange created it)
or a wrapper for the actual uid (if some other client created it)
* To find out which case we're dealing with, we have to look at
the base64 decoded string for the magic "vCal-Uid" substring
* If it's there, we pull the real uid out of the decoded string
* Otherwise, we build a hex strong from the decoded bytes
* Write unit test for this process
Bug: 2598201
Change-Id: I1cc40af6d1e45be44c19465eb8a4c31851ec8157
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 46e18bd76629be0835a5d5e6c839b6daac6cdfdc |
|
01-Apr-2010 |
Marc Blank <mblank@google.com> |
Don't add "Invitation: " to meeting invitations
* Turns out that most other clients omit this.
* This has the pleasing effect of fixing the referenced bug
* Update unit tests
Bug: 2561821
Change-Id: I39f7db7e05be590373cd5f3d9b23c7ee21bde4f7
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| e3e9ef55a2afd2c121e1f214a8fa34fced3bac38 |
|
01-Apr-2010 |
Marc Blank <mblank@google.com> |
Fix conversion of UNTIL date in RRULEs to EAS calendar dates
* Because we were sending these in the wrong format, upsynced changes
were failing, with the result that both the original event and
the "new" event (from the UNTIL date forward) remained in the calendar
* Fix is to send the proper format; unit test updated to reflect the
change
* Also, we only send the date of an UNTIL, rather than the to-the-minute
time; it turns out that EAS expects to see only a day for UNTIL.
Bug: 2561818
Change-Id: Ic4eacbe96c713d58c637386ceab2cf22ebe3c2d4
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| c1b63a27ed05bed70f74cf33fe08f8bd1f0d745f |
|
01-Apr-2010 |
Marc Blank <mblank@google.com> |
Fix the VCALENDAR we send with all day events
* We need to send date only (without time) in the VCALENDAR file for
all-day events
* Add unit test for this case
Bug: 2561789
Change-Id: I33a43c7a248059c97482ca147a23af083744118a
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| f58e3ba6e6e246a804e6908c831a43b46a61bc07 |
|
01-Apr-2010 |
Marc Blank <mblank@google.com> |
Send CANCEL method with meeting cancellations
* We should be sending CANCEL as the method with cancellations
* Fix this and update unit test
Bug: 2527606
Change-Id: I2b982e4bfd1dbc57660cf578702edf49584d2957
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 00702b7e577ff2b7b1ae3f6dceefc615ba9cba72 |
|
26-Mar-2010 |
Marc Blank <mblank@google.com> |
Add message text for invitation replies
* Updated unit test to make sure there's message text
Bug: 2548714
Change-Id: I70e05b72539ff9ba7d582a51421e5345aa6151e4
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 455f8969854ec1f0ba163ae70cb02e10fb515564 |
|
26-Mar-2010 |
Marc Blank <mblank@google.com> |
Format cleanup for CalendarUtilities
Change-Id: I6633435cbe0ee55f58da76658d2ccb12f421e326
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 79268e63dbda6ebc94d20e72e2bb1c245ee64678 |
|
24-Mar-2010 |
Marc Blank <mblank@google.com> |
Clean up EAS -> TimeZone determination code
* Use one minute before/after for transition checking, instead of the
sloppier early version
* Add tests for additional known time zones
* Change most methods in CalendarUtilities to package private (for use
with unit tests)
* Clean up a little bad formatting
Change-Id: I9e5be5e1c859f2294adf06874459f7db15fb8c22
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| d38b4e9c1893a6c4ac70c08c5211629da3840cb2 |
|
24-Mar-2010 |
Makoto Onuki <omakoto@google.com> |
Moved fromUtf8 from TestUtils to Utility.
And cleaned up SimpleIcsWriter.toString().
Change-Id: I383d91256c48be5263c695c8e8dd151d0e95d0a6
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 10e1bb12c0e78b60c1302186a724e5617a2ba3bc |
|
21-Mar-2010 |
Marc Blank <mblank@google.com> |
Clean up VCALENDAR/TIME_ZONE_INFORMATION code
* Fix the transition times so that they occur at the hour
* Remove an unused variable
* Fix a reference to Calendar.HOUR that should have been
Calendar.HOUR_OF_DAY
* Confirm that unit tests work properly
Change-Id: I3eaf31d160e97b5f3ba59c83878359085aea960d
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 879b4d7bd28de1c8bb8c8aba9c1ab17936d300aa |
|
20-Mar-2010 |
Marc Blank <mblank@google.com> |
Add unit test for VCALENDAR generation from TimeZone
* Sanity check runs through every TimeZone and makes sure that there
are no exceptions thrown
* Also, that we find at least 10x as many TimeZone's with RRULEs as
those without (empirical)
Change-Id: I2f266ac9d2a839f053bb5fda10a5b77dc8dd2c04
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| bf1de871b7ec63c93694ba022282e8789e69f201 |
|
19-Mar-2010 |
Marc Blank <mblank@google.com> |
Send appropriate ics message for cancellations
* We were sending cancellations with a request for reply, which is
incorrect
* Send the correct dats in the ics attachment
* Update unit test to reflect this
Bug: 2527606
Change-Id: I4cea0bb8f1c29a3cad8d09fd6a4750f7ab067229
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| b4d217e5170ae397d741e95308d98e80d0c2f637 |
|
16-Mar-2010 |
Marc Blank <mblank@google.com> |
Send meeting invite mail as multipart/alternative
* Turns out that Exchange 2003 requires the ics attachment to be in a
multipart/alternative, rather than a multipart/mixed MIME message
* Exchange 2007 accepts both types
* Therefore, we change our output for this particular situation, i.e.
a single attachment that is an ics file, to multipart/alternative
* Rename FLAG_SUPPRESS_CONTENT_DISPOSITION to FLAG_ICS_ALTERNATIVE_PART
and make this flag do double duty - 1) suppress the Content-Disposition
header (also required by Exchange) and 2) send the message as
multipart/alternative
* Add unit tests for Rfc822Output to check that mime parts are composed
properly
Bug: 2516394
Change-Id: I60e26f57b8ecaf01d0340e7828533334e0e7d45a
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| bc0c8c1523fc0bc42eb82dba6c2977492e441c03 |
|
16-Mar-2010 |
Makoto Onuki <omakoto@google.com> |
Exchange calendar: fixes for the ICS writer.
- Now SimpleIcsWriter does the UTF-8 conversion, and folds lines according
to the number of bytes in UTF-8.
- It now escapes special chars in TEXT values. You can safely put , ; \ or
line breaks. in summary, location, and description.
- Quotes all CN. (leftover from Ibb8f155a)
- Replace "s in CN with 's (rather than removing them)
Bug 2508283
Bug 2515768
Change-Id: Ibdced53ee32bba950608d63f507b11b24eaad7b0
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 9ca8918b82221dd441293973ffb84d565a52993a |
|
16-Mar-2010 |
Marc Blank <mblank@google.com> |
Improve message text for invites w/ recurrences
* Add the (recurring) text when the invite is for a recurring
meeting
* Add a test for message text creation
Bug: 2515474
Change-Id: Ifefbc2ba1ac444175180cb7a58f4ec554d9674a3
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| b129a5f1b340ae6362397685c407099ceae8d9e9 |
|
15-Mar-2010 |
Marc Blank <mblank@google.com> |
Fix utility that retrieves tokens from RRULEs
* The utility wasn't handling commas properly, causing the referenced
bug
* Fixed the utility and updated the relevant test case
Bug: 2515488
Change-Id: Id229e50fcaaed1a0142db301eedaaba9209bed13
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| e54b75dc4f638e594e9b97e3b4ed8829fbc9b521 |
|
12-Mar-2010 |
Makoto Onuki <omakoto@google.com> |
Explicitly send ICS files in UTF-8.
- In memory attachments are now stored as byte[], not String.
We can store any type of contents now.
- Added blob content_bytes to the Attachment table.
The content field is now deprecated and not used.
- Explicitly convert ICS files to UTF-8.
- Added Utility.to/fromUtf8().
Bug 2509287
Change-Id: I3785a365a9a34039ec12ba82bd857dcdbc4de92d
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| dafc866120dac68fabbddcc9943e3995894c5244 |
|
10-Mar-2010 |
Marc Blank <mblank@google.com> |
Send email related to event exceptions
* We weren't sending out appropriate emails for exceptions and other
event updates
* Write exception specific ics file code in CalendarUtilities (in
the existing ics file creator)
* Send appropriate Update: subject for updated events/exceptions
* Compose simple message text consisting of:
When: <time>
Where: <location>
* Prepend message text for exceptions to indicate that the message
relates to a particular instance of the event:
This event has been canceled for: <date>
The details of this event have been changed for: <date>
* New strings were added in CL#44141
* Updated CalendarUtilities tests
Bug: 2501270
Change-Id: I920de8120bc56d5bd565cbde26ff4807be41579f
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 8e26c42accbaf72eff6694173496aba0e6aa37f6 |
|
02-Mar-2010 |
Mihai Preda <preda@google.com> |
Move parseDateTimeToMillis() to com.android.email.Utility.
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 1c9dfc1ce8d40b4a09fb6baf2fd9ed9c482b8900 |
|
03-Mar-2010 |
Marc Blank <mblank@google.com> |
More unit tests related to meeting-related emails
* Included is a (nearly complete) VCALENDAR parser that is
used to verify the contents of the ics attachments we create
* Added a test for meeting invitation
* More to come (always)
Change-Id: I31eeac66eb635f443c85aacf56e67a943cc3d53b
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 820dbc5ff3497fdd98fdb1cc42c1d298f9c1f199 |
|
27-Feb-2010 |
Marc Blank <mblank@google.com> |
Refine meeting invitation emails; include VTIMEZONE
* VTIMEZONE blocks must be sent in our ics files for meeting
invitations that are recurring, as the originator's time zone
is critical in making attendee's calendars accurate
* Created a utility to convert TimeZone to VTIMEZONE data; the
utility successfully generates data (including recurrence rules)
for the entire tzinfo database (the source of TimeZone).
* Updated our ics files to include VTIMEZONE when appropriate and
send DTSTART/DTEND in local time in that case
* Wrote some unit tests, but more are needed
Change-Id: Iccbdd00cd3b2be2da058b344ebacd17ed6fb0e3d
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 5c6e14ab2f2e4c5dfc97cdeaedcc105159a9f29c |
|
23-Feb-2010 |
Marc Blank <mblank@google.com> |
Send replies to exchange meeting requests
* When the user selects accept/decline/tentative in MessageView, we now send
an email to the organizer, with an iCalendar attachment indicating the reply
* Added a unit test for the reply case, but more tests to be added to handle
other circumstances
Change-Id: Iff799d88a92b6546735bf4965b22febf3a82b56f
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| c10a3beef4f048292e6a4ceb31527c5123801517 |
|
16-Feb-2010 |
Marc Blank <mblank@google.com> |
Add meetingInfo column to Message; use for meeting invites
* Added a meetingInfo column to the Message database
* When a meeting invite is received, the start time is stored here
in ms from start of epoch. Note that this field is defined to be
a String, for extensibility
* Update ProviderTests
Change-Id: If44892d27ccc5ebdc1f8667befafb8b8a27a2cf4
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 21c3c670ff6b932a4ecbeda230bb160178bdd957 |
|
15-Feb-2010 |
Marc Blank <mblank@google.com> |
Add support for UNTIL in recurrences
Change-Id: I983e1bcb209e794b462ec43efaccefe95bf9bd9d
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 377230593dca7cb01483bfaf93959e5821f5f028 |
|
03-Feb-2010 |
Marc Blank <mblank@google.com> |
Build proper TimeZoneInformation strings for upsync; fix bugs
* Create full TZI strings for upload of events (previously, we
omitted DST information)
* Add documentation to some unit tests
* Put in correct logic for determining if upload needed
* Fix problem w/ parsing empty tags
Change-Id: I268ce8a2db30b3cfdf0e44f6a78befd6bd933243
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| f35b67cef20189c12a1a387dedf200eb30089725 |
|
02-Feb-2010 |
Marc Blank <mblank@google.com> |
Handle upsync of multiple BYDAY values; add some unit tests
Change-Id: If3be28df41ed88cb83edca2f6ea6ca1f734f506f
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|
| 5862a85e17e81866ca82a9905577931947fbd44e |
|
29-Oct-2009 |
Marc Blank <mblank@google.com> |
Implement Exchange calendar sync support
What should be working:
* Events sync down from server and appear in calendar
* Recurrences and exceptions appear in calendar
* Changed events on server should be reflected in calendar
* Deletions on server should be reflected in calendar
* Push of new/changed/deleted events should work
* Changes on device are NOT synced back to server
* New, single events on device are synced back to server
(no time zone, attendee, or recurrence support)
* Checkbox for syncing calendar added to setup flow
* System sync glue in manifest, etc.
* Bugs are to be expected
* A few unit tests; needs more
Change-Id: I7ca262eaba562ccb9d1af5b0cd948c6bac30e5dd
/packages/apps/Exchange/tests/src/com/android/exchange/utility/CalendarUtilitiesTests.java
|