On Wed, 2002-11-13 at 03:03, Rodrigo Moya wrote: > On Tue, 2002-11-12 at 17:51, Ronald Kuetemeier wrote: > > Hi Rodrigo, > > I will certainly do that. One comment, in my code review I found a small > > uuups. I include the header from composer/Composer.h which should be > > Evolution-Composer.h, if I'm not mistaken right now. I haven't looked at > > the code again and working on my first coffee, I write a program which > > writes applications and sometimes finds my mistakes. Anyhow that will be > > fixed, it doesn't effect the app. since they are both created from the > > same idl just a cosmetic fix. > > Another question, there is no evolution-list (addresses) handling in the > > Composer corba interface, so I working on adding it. I try to keep it > > integrated into the existing code base, as little change as possible. I > > will explain why and how when I send the patch. OK, here's the > > question, should I include it into the main patch or keep it separated? > > > if it's for the mailer, that is, another component, might be better to > send it separated from the calendar one. > Yeah, that's what I hoped for, still haven't untangled all the links between mailer and addressbook. There also seems to be a bug in Calendar resolving addresses from a evolution-list, i.e it doesn't. Which I basically will mark but we should actually leave it that way. Maybe make it official, i.e test for a list and than write just the name, as we do now. Don't take my word for it right now, it's just a heads up, I will do more investigation after I got the features I need.
Anyhow my reason being, that we need late binding for list-name to actual list. If we think about a recurring meeting and send a reminder to a list of people attending, this list can change. And we don't want to listen to evolution-list changes and then find in calendar all the places we have to change, also how do we do that if we don't have the list name anymore, i.e.resolved it at creation time. There is also the small problem of bcc lists, and how would we store that info in calendar. And I guess we all remember the cases where somebody in a company send cc instead of bcc and how embarrassed some of those companies were, so we don't want to be part of that. That's why I decided to go for late binding and error handling via email, since we can not guarantee somebody sitting in front of the machine when an alarm triggers. The mail can trigger a rule on how to contact the owner in another way, i.e sms to cell .... But quite frankly evolution is not build for this kind of work, I take it one step at a time. As soon as I have figured out how this all relates I will send separate patches. I will sync with head as soon as I see the light at the end of the tunnel I'm stuck in right now, and I have to do some "real" work :-). BTW, any objections, ideas are as usual well-come. Have fun, Ronald > cheers _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
