|
1 | 1 | libgcal changelog |
2 | 2 | Adenilson Cavalcanti (adenilson.silva@indt.org.br) |
3 | 3 |
|
| 4 | +== libgcal 0.9 (2009-04-20) == |
| 5 | + |
| 6 | +- porting to google data protocol 2.0; |
| 7 | + |
| 8 | +- support for more contacts fields. Currently supported fields are: |
| 9 | + name, email, telephone, job title, organization, address, notes, photo; |
| 10 | + |
| 11 | +- support for retrieve/add/edit contact's photos; |
| 12 | + |
| 13 | +- cmake based buildsystem (probably will migrate away from autotools |
| 14 | + in next release). For while, both are shipped; |
| 15 | + |
| 16 | +- small changes to make it compile/run happily with a C++ application; |
| 17 | + |
| 18 | +- fix for non-ordered operations (I was testing sequence: |
| 19 | + add/edit/delete). Non-ordered operations trigged a bug where |
| 20 | + operations would fail because default package header was not correct; |
| 21 | + |
| 22 | +- fix for using correct atom feed url for contacts; |
| 23 | + |
| 24 | +- workaround for really weird situation where google calendar server |
| 25 | + answers requests directly *without* a redirect (reported by Tasaki, |
| 26 | + I was not able to reproduce the error but the code has some |
| 27 | + workaround for that); |
| 28 | + |
| 29 | +- fixing a potential SEGFAULT condition (where a failed XPath |
| 30 | + expression could set a DOM node to NULL). Never happened, but |
| 31 | + fortune favors the prepared; |
| 32 | + |
| 33 | +- fix for deleted flag (it was not being setted always, made a valid |
| 34 | + contact appear as deleted); |
| 35 | + |
| 36 | + |
4 | 37 | == libgcal 0.8 (2008-10-03) == |
5 | 38 |
|
6 | 39 | - support to store and access RAW XML of each entry; |
|
0 commit comments