|Dynamically extending the workbench model [message #575963]
||Thu, 13 May 2010 11:58
| Roland Tepp
Registered: July 2009
I am trying to evaluate Eclipse e4 development and as a test case I
started to implement a proof of concept of a new product.
One of the requests of the new product is that it is an application that
will have to open up on multiple monitors in full screen on all monitors.
The number of available monitors is, of course detected only at runtime
and this means that the model defined in Application.e4xmi needs to be
dynamically extended at startup.
To achieve that I used LifecycleHandler and intercepted
*processAdditions* event to create one new window per monitor.
It mostly worked like a charm (you can read my experiences here:
However I was left with 2 questions:
1) In my initial implementation I used standard EMF model factory
methods to manually create the excess windows in code. However it would
make much more sense to me in many ways if I could instead read the
window configuration from some sort of template instead and
insert/populate window instances loaded/created from the template into
the application model...
2) The other issue I had was that a MWindow model seems to be missing
"fullScreen" attribute. What is your suggestion - is it a deliberate
omission and I should instead create my own window renderer for this
purpose? Or is it simply an oversight and will be added in some near
Powered by FUDForum
. Page generated in 0.02349 seconds