| Eclippse Application Admin and e4 [message #558348] |
Sat, 11 September 2010 08:31  |
Eclipse User |
|
|
|
Hi,
I do't know if e4 has anything to offer me here, but I want to
investigate a possiblity of building the next generation of our RCP
product with e4.
The Modeled UI bit I have already tried and find it to be wonderful.
However, since our application is built up of several
subsystems/modules, which all can be thought of as sort of
"applications" of their own (providing services to both internal and
external consumers), I wanted to experiment with treating these as first
class applications in Eclipse/OSGI and try use Eclipse Application Model
(see [1]) to control their startup.
What I wanted to know is if e4 has anything to offer me in this regard.
What I would particularily like to have is to build up a root
IEclipseContext for the main/launcher application and have each
subapplication it's own IEclipseContext with a parent pointing to the
"main application context".
Is this possible? Is this necessary? Does this make sanse?
References:
[1] http://wiki.eclipse.org/Equinox_Application_Model_Demo)
--
Roland Tepp
|
|
|
| Re: Eclippse Application Admin and e4 [message #558357 is a reply to message #558348] |
Sat, 11 September 2010 10:57  |
| Eclipse User |
|
|
|
Do I get that right you'd like to bring up multiple e4 application
instances in one OSGi-Instance?
In theory this could be done but there are some problems you might face:
a) Current Event System is built upon EventAdmin => it is an
OSGi-Singleton => you need to replace this through your own
b) Multiple Display-Instance. IIRC only Win32 SWT supports to have
multiple Display instances. You might ask why this important? The
reason is that I think the keybindings story is based upon display
filters
If you solve problems from above this is a first step in the right
direction and "all" you then need to do is to copy the bootstraping from
E4Application and instead of using create the root-context in there.
You'll have to pass in a IEclipseContext and create child context for
each of your applications.
Tom
Am 11.09.10 14:31, schrieb Roland Tepp:
> Hi,
>
> I do't know if e4 has anything to offer me here, but I want to
> investigate a possiblity of building the next generation of our RCP
> product with e4.
>
> The Modeled UI bit I have already tried and find it to be wonderful.
>
> However, since our application is built up of several
> subsystems/modules, which all can be thought of as sort of
> "applications" of their own (providing services to both internal and
> external consumers), I wanted to experiment with treating these as first
> class applications in Eclipse/OSGI and try use Eclipse Application Model
> (see [1]) to control their startup.
>
> What I wanted to know is if e4 has anything to offer me in this regard.
> What I would particularily like to have is to build up a root
> IEclipseContext for the main/launcher application and have each
> subapplication it's own IEclipseContext with a parent pointing to the
> "main application context".
>
> Is this possible? Is this necessary? Does this make sanse?
>
> References:
> [1] http://wiki.eclipse.org/Equinox_Application_Model_Demo)
>
|
|
|
| Re: Eclippse Application Admin and e4 [message #581716 is a reply to message #558348] |
Sat, 11 September 2010 10:57 |
| Eclipse User |
|
|
|
Do I get that right you'd like to bring up multiple e4 application
instances in one OSGi-Instance?
In theory this could be done but there are some problems you might face:
a) Current Event System is built upon EventAdmin => it is an
OSGi-Singleton => you need to replace this through your own
b) Multiple Display-Instance. IIRC only Win32 SWT supports to have
multiple Display instances. You might ask why this important? The
reason is that I think the keybindings story is based upon display
filters
If you solve problems from above this is a first step in the right
direction and "all" you then need to do is to copy the bootstraping from
E4Application and instead of using create the root-context in there.
You'll have to pass in a IEclipseContext and create child context for
each of your applications.
Tom
Am 11.09.10 14:31, schrieb Roland Tepp:
> Hi,
>
> I do't know if e4 has anything to offer me here, but I want to
> investigate a possiblity of building the next generation of our RCP
> product with e4.
>
> The Modeled UI bit I have already tried and find it to be wonderful.
>
> However, since our application is built up of several
> subsystems/modules, which all can be thought of as sort of
> "applications" of their own (providing services to both internal and
> external consumers), I wanted to experiment with treating these as first
> class applications in Eclipse/OSGI and try use Eclipse Application Model
> (see [1]) to control their startup.
>
> What I wanted to know is if e4 has anything to offer me in this regard.
> What I would particularily like to have is to build up a root
> IEclipseContext for the main/launcher application and have each
> subapplication it's own IEclipseContext with a parent pointing to the
> "main application context".
>
> Is this possible? Is this necessary? Does this make sanse?
>
> References:
> [1] http://wiki.eclipse.org/Equinox_Application_Model_Demo)
>
|
|
|
Powered by
FUDForum. Page generated in 0.07843 seconds
Home