[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [e4-dev] MDialog / MWizard will be removed in M5
|
Cool. That's a great example. So it's really about DI, not the renderers.
Sent from my BlackBerry 10 smartphone on the Rogers network.
When I implement Dialogs these days, it is not that easy to bring it together with Dependency Injection. When a Dialog is Part of the Application Model I hope it is easy to get dependencies in the same way I can do it with a Part. Nowadays when
I want to get e.g. a Service into a Dialog i have two Options:
1. Drop in the Service manually cia a Setter or the Constructor of the Dialog
2. Use ContextInjectionFactory.make
When a Dialog is Part of the Application Model and if I understand the new APIs correctly I simply need to define the MDialog in my model, connect the Dialog with a Pojo-Class via its Contribution-URI and afterwards I can just
do a
@Inject MyService service
to get the Service the standard way...
I am not sure if the new MDialogs/MWizards is adressing this (I have to less informations about it actually, what Bug is it?) but this is the " problem " I personally have actually with Dialogs in my daily work.
Marc