|
|
Re: Dynamically extending the workbench model [message #533472 is a reply to message #533383] |
Fri, 14 May 2010 07:38 |
Roland Tepp Messages: 336 Registered: July 2009 |
Senior Member |
|
|
Hey Tom,
> (Take a look at
> org.eclipse.e4.workbench.ui.internal.ModelExtensionProcessor )
Thanks for the tips - I'll take a look at it :)
13.05.2010 18:21, Tom Schindl kirjutas:
> Well, first of you are the first requesting this but I'm not sure the
> Application Model is the right place for this information. IMHO it would
> make probably sense to control this use CSS and as you already said
> yourself you could easily write your own renderer.
I was actually considering this approach - and in my particular case it
would most likely make a whole lot of sense, since the appliocation's
natural state is in full-screen, but then I remembered great many
applications where an ability to switch at between full-screen and
windowed mode at runtime is quite expected behavior (like media players
graphics editing tools, presentation software, etc.)
I'd say, e4 is still young enough platform to be largely unknown or
mistrusted by many developers, so the fact that I was the first one to
request such a thing is not really surprising...
> Beside that you can naturally extend our EMF-Model and add such an
> attribute so that your renderers can use this information.
True, but if "fullScreen" attribute is to be included in the model, I'd
rather see it as part of a "standard model". YMMV :)
--
Roland Tepp
|
|
|
Re: Dynamically extending the workbench model [message #533671 is a reply to message #533472] |
Sat, 15 May 2010 08:56 |
Thomas Schindl Messages: 6651 Registered: July 2009 |
Senior Member |
|
|
Am 14.05.10 09:38, schrieb Roland Tepp:
> Hey Tom,
>
>> (Take a look at
>> org.eclipse.e4.workbench.ui.internal.ModelExtensionProcessor )
>
> Thanks for the tips - I'll take a look at it :)
>
>
> 13.05.2010 18:21, Tom Schindl kirjutas:
>> Well, first of you are the first requesting this but I'm not sure the
>> Application Model is the right place for this information. IMHO it would
>> make probably sense to control this use CSS and as you already said
>> yourself you could easily write your own renderer.
>
> I was actually considering this approach - and in my particular case it
> would most likely make a whole lot of sense, since the appliocation's
> natural state is in full-screen, but then I remembered great many
> applications where an ability to switch at between full-screen and
> windowed mode at runtime is quite expected behavior (like media players
> graphics editing tools, presentation software, etc.)
>
> I'd say, e4 is still young enough platform to be largely unknown or
> mistrusted by many developers, so the fact that I was the first one to
> request such a thing is not really surprising...
>
True
>
>> Beside that you can naturally extend our EMF-Model and add such an
>> attribute so that your renderers can use this information.
>
> True, but if "fullScreen" attribute is to be included in the model, I'd
> rather see it as part of a "standard model". YMMV :)
>
>
You can file a bug and then we can discuss there.
Tom
|
|
|
|
Re: Dynamically extending the workbench model [message #576063 is a reply to message #533383] |
Fri, 14 May 2010 07:38 |
Roland Tepp Messages: 336 Registered: July 2009 |
Senior Member |
|
|
Hey Tom,
> (Take a look at
> org.eclipse.e4.workbench.ui.internal.ModelExtensionProcessor )
Thanks for the tips - I'll take a look at it :)
13.05.2010 18:21, Tom Schindl kirjutas:
> Well, first of you are the first requesting this but I'm not sure the
> Application Model is the right place for this information. IMHO it would
> make probably sense to control this use CSS and as you already said
> yourself you could easily write your own renderer.
I was actually considering this approach - and in my particular case it
would most likely make a whole lot of sense, since the appliocation's
natural state is in full-screen, but then I remembered great many
applications where an ability to switch at between full-screen and
windowed mode at runtime is quite expected behavior (like media players
graphics editing tools, presentation software, etc.)
I'd say, e4 is still young enough platform to be largely unknown or
mistrusted by many developers, so the fact that I was the first one to
request such a thing is not really surprising...
> Beside that you can naturally extend our EMF-Model and add such an
> attribute so that your renderers can use this information.
True, but if "fullScreen" attribute is to be included in the model, I'd
rather see it as part of a "standard model". YMMV :)
--
Roland Tepp
|
|
|
Re: Dynamically extending the workbench model [message #576099 is a reply to message #533472] |
Sat, 15 May 2010 08:56 |
Thomas Schindl Messages: 6651 Registered: July 2009 |
Senior Member |
|
|
Am 14.05.10 09:38, schrieb Roland Tepp:
> Hey Tom,
>
>> (Take a look at
>> org.eclipse.e4.workbench.ui.internal.ModelExtensionProcessor )
>
> Thanks for the tips - I'll take a look at it :)
>
>
> 13.05.2010 18:21, Tom Schindl kirjutas:
>> Well, first of you are the first requesting this but I'm not sure the
>> Application Model is the right place for this information. IMHO it would
>> make probably sense to control this use CSS and as you already said
>> yourself you could easily write your own renderer.
>
> I was actually considering this approach - and in my particular case it
> would most likely make a whole lot of sense, since the appliocation's
> natural state is in full-screen, but then I remembered great many
> applications where an ability to switch at between full-screen and
> windowed mode at runtime is quite expected behavior (like media players
> graphics editing tools, presentation software, etc.)
>
> I'd say, e4 is still young enough platform to be largely unknown or
> mistrusted by many developers, so the fact that I was the first one to
> request such a thing is not really surprising...
>
True
>
>> Beside that you can naturally extend our EMF-Model and add such an
>> attribute so that your renderers can use this information.
>
> True, but if "fullScreen" attribute is to be included in the model, I'd
> rather see it as part of a "standard model". YMMV :)
>
>
You can file a bug and then we can discuss there.
Tom
|
|
|
Powered by
FUDForum. Page generated in 0.04157 seconds