Tom is the person who first asked this question and is the person who can probably answer your question best.
I'm just bumping the question up the list so that it does get done ASAP. Bob. 2008/7/14 Linus Tolke <[EMAIL PROTECTED]>: > Exactly what are you suggesting here Bob? In what timeframe and what classes > are affected? > > /Linus > > > 2008/7/14, Bob Tarling <[EMAIL PROTECTED]>: >> >> Do you have a view on this Linus. >> >> Can we simplify the recently adding events and listeners? >> >> Bob. >> >> >> 2008/7/9 Brian Hudson <[EMAIL PROTECTED]>: >> > What then becomes the new recommended approach? >> > >> > I'd like to change the event mechanism I just added in my branch to the >> > new >> > way before it gets merged into trunk. >> > >> > Brian >> > >> > On Tue, Jul 8, 2008 at 4:51 PM, Bob Tarling <[EMAIL PROTECTED]> >> > wrote: >> >> >> >> > Unless someone comes up with a good reason it should stay, we should >> >> > deprecate this mechanism. The question is whether it's too late to >> >> > split out all the recent additions to the event pump and put them >> >> > some >> >> > more reasonable place in the public API before the release. >> >> >> >> I would say go ahead and do this is we have agreement. This sounds >> >> like simple refactoring and we don't really want to release anything >> >> now that we know we will deprecate later. >> >> >> >> Bob. >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
