The following projects have changed:
The build contains commits that mentioned these bugs:
___
e4-dev mailing list
e4-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/e4-dev
MUILabel extends MLocalizable
MCommand extends MLocalizable
...
Tom
On 03.12.13 23:17, Dirk Fauth wrote:
> Ok I see. So for the feature I think I got it.
>
> "Yes the whole point about this is that not only stuff on MUILabled needs
> to allow localization!"
>
> So should MUILabel extend MLocali
Ok I see. So for the feature I think I got it.
"Yes the whole point about this is that not only stuff on MUILabled needs
to allow localization!"
So should MUILabel extend MLocalizeable or should they be separated. Both
are interfaces, so MUILabel extends MLocalizeable would be possible. But
shoul
On 03.12.13 21:41, Dirk Fauth wrote:
> While implementing stuff as suggested some questions came to my mind.
>
> Most of them are already answered by Tom. Many thanks for being so
> patient and helpful!!!
>
> But why should we change the localize methods to features and extend the
> renderers to
While implementing stuff as suggested some questions came to my mind.
Most of them are already answered by Tom. Many thanks for being so patient
and helpful!!!
But why should we change the localize methods to features and extend the
renderers to listen to those features? Technically a localized l
Hi,
I'm +1 on moving the service to the application context this where it
should have been put since day 1.
Just one note on multi-instance envs:
-
While thinking about this I remembered that this impacts the
TranslationObjectSupplier which currently is buildin
Pawel,
Please work with Marco Descher. Marco is currently working on a set of
patches to add a tab to any of the model elements in the editor. I think if
we look at extending the model editor we should combine these two use
cases.
Here is the bug that Marco is working on:
https://bugs.eclipse.or
Hi,
on implementing the Locale change for the application model I came across
something.
The current set Locale and the TranslationService are put in the OSGi
context. By discussing this fact with Tom Schindl, this is
1. a implementation detail
2. not intended
Usually only ExtendedObjectSupplie
