Could you tell me whether you had a plan or detailed design of your rearchitecting the evolution calendar?
and Could you give me some document about your modification?
I hoped you could hold the API that hydrogen used. you know, The fewer you modify the API, the eaiser we maintain the hydrogen.
I hoped to get some plan about your modification of evolution calendar.
Thanks
jack
JP Rosevear wrote:
On Thu, 2003-07-31 at 23:42, Harry Lu wrote:JP, Currently we cannot think of any requestes:) But we need to make sure that hydrogen will work with the new Evolution's calendar. So please keep us informed about the changes. How long will this take? How many work has been done? Will your changes be posted to evolution-patches list? It will be convenient for us to know what you have done. We will pull the branch regularly to have a look.Changes in the branch likely won't be posted to evolution-patches. The changes will probably take around two months. Hopefully we will post a complete list of the changes shortly (a couple points are still in discussion). Hydrogen will probably need to change somewhat as we are adding cancellability into the API (so you can cancel long operations like opening a calendar) as well as a method of discovering what fields are supported by the backend. Creating and removing of calendars will now be done by the backend. We will also be handling recurrence-ids every where, not just in hydrogen, and so hydrogen can probably stop using the hack where it must create a unique uid from the uid+recurrence-id. Finally we might be moving away from soup for connector to libcurl.-JP
