P2 UI and E4
#83
Replies: 1 comment
-
|
On Sun, Jun 12, 2022, 9:18 PM Christoph Läubrich ***@***.***> wrote:
Currently the P2 UI is heavily bound to the E3 model, mostly because of
excessive usage of PlatformUI.getWorkbench(), this currently makes it
impossible to use the P2 UI in a 'pure' E4 RCP application. Because the P2
UI is non trivial, reimplementing it is most of the time not an option.
Even though it might be much work, I wonder if smaller steps towards this
goal would be desired/accepted by P2
IMHO, migrating more and more parts to e4 is more than welcome and actually
we are quite late with this.
… —
Reply to this email directly, view it on GitHub
<#83>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEMKRB4MGSS2CLRTEUKFETVOYSXHANCNFSM5YSDMOKQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently the P2 UI is heavily bound to the E3 model, mostly because of excessive usage of
PlatformUI.getWorkbench(), this currently makes it impossible to use the P2 UI in a 'pure' E4 RCP application. Because the P2 UI is non trivial, reimplementing it is most of the time not an option.Even though it might be much work, I wonder if smaller steps towards this goal would be desired/accepted by P2.
Beta Was this translation helpful? Give feedback.
All reactions