On Thu, Nov 8, 2012 at 6:53 AM, Tom Schindl <[email protected]>wrote:
> > > Please note that on the low-level what I'd like to have is: > > a) possibility to mark a method to get invoked and the parameters to be > filled out from the DI engine > b) a more lightweight possibility beside having to invent annotations > [... snip ...] > > I don't see finding the Keys one can use any harder than locating the > annotations. > > I'm not yet for or against this particular approach (invoke(*) instead of events) but I don't see the difference between using annotations for the lifecycle vs annotations with values. ex: @AboutToShow vs @Lifecycle(IWorkbenchConstants.ABOUT_TO_SHOW) except adding extra code to the invoke(*) processing. I'd still go with general annotations. We could define @Lifecycle and have the lifecycle annotations like @AboutToShow extend @Lifecycle (allowing them to be found more easily). Later, PW -- Paul Webster Hi floor. Make me a sammich! - GIR
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
