| Re: [e4] How to get ready ? [message #534961] |
Thu, 20 May 2010 19:30 |
 Thomas Schindl
Messages: 6651
Registered: July 2009 |
Senior Member |
|
|
Please use the e4 newsgroup for follow ups.
Tom
Am 20.05.10 21:29, schrieb Tom Schindl:
> Am 20.05.10 20:15, schrieb Christophe Fondacci:
>> Hello guys,
>>
>> I do not know much about e4 but started to read some docs about upcoming
>> features. As a RCP app developer, I am REALLY interested in the service
>> injection feature.
>> So far, I need to handle service consumption in a custom way, most of
>> the time relying on plugin singleton instance that gives me the proper
>> service singleton I need. Not talking about the platform services but
>> about "custom" services which a RCP app needs as well.
>>
>> So now I am wondering :
>> - Will it be possible for us to take advantage of service injection to
>> inject custom services ?
>
> Yes. All services registered in OSGi-Service-Registry are a subject for
> injection
>
>> - Is there anything we can do right now in our developments to "prepare
>> the future" ? I mean, is there some best practices which could reduce
>> the migration efforts when e4 will be released ? This is always less
>> work to prepare this now on fresh code than to refactor it after it has
>> got old...
>> Another question : will e4 migrate to Java 1.5 and will introduce the
>> generics ? I ask this (but I guess the answer is no) because I can see
>> in the e4 docs code like :
>
> Some rules are:
> * Don't inherit from things like ViewPart, EditorPart
> * Don't references pure 3.x workbench services (e.g. ISelectionService)
> => Abstract them away in own services you delegate
>
> If you want a concrete example on how to structure such a component you
> can take a look at my ModelEditor which runs in:
> * 3.x
> * 4.0
> * native e4
>
> http://tomsondev.bestsolution.at/2010/05/17/a-week-at-e4-sha re-me-please/
>
> Sources to it can be found in the
> e4/org.eclipse.e4.tools/bundles/org.eclipse.e4.tools.emf*
>
>
>>
>> MWindow window = (MWindow)
>> mwindow.getContext().get(MWindow.class.getName());
>>
>> And I can't wait being able to do this :
>>
>> MWindow window = mwindow.getContext().get(MWindow.class);
>>
>> thanks to generics: more compact, more readable, less writing.
>
> We are using Java 5 generics so the you are able to write
>
> MWindow window = mwindow.getContext().get(MWindow.class);
>
> with the latest builds.
>
>>
>> I understand that there might be a big compatibility constraint for you
>> Eclipse platform guyz....
>>
>> If anyone could lead me to some documentation on these topics it would
>> be marvellous.
>>
>> Anyway thank you for all the great work you're doing on this release,
>> Christophe
>> http://www.nextep-softwares.com
>>
>
> Tom
|
|
|
Powered by
FUDForum. Page generated in 0.03045 seconds
] 
Search
Help
Register
Login
Home
