Community
Participate
Working Groups
In EGL CE we had one EGL editor, which was smart enough to show the Design and Preview tabs if the part being edited was a RUIHandler. We looked at merging this solution into RBD while developing RBD 8.0, but I believe it was not implemented due to the fact that ; 1) RBD has more editors to consider than just the Rich UI Visual Editor (e.g. TUI Editor), and 2) Eclipse appears to have a better solution to this problem, which does not involve implementing a single editor that displays different options based on the content being edited. At a minimum, new RUI handlers (created with the New RUI Handler wizard) needs to be associated with the VE by default (this is the current RBD behavior) so it gets opened in the VE by default. This does not address the issue where an imported .egl file will always open in the Source editor, even if it is "supposed" to open in the VE.
At a minimum for 0.7, we need to ensure that new RUI handlers (created with the New RUI Handler wizard) open in the VE. Post 0.7, we should plan to make the EGL editor extensible (unless the "Eclipse solution" is viable) such that *anyone* (including the VE plug-in) can contribute tabs to the EGL source editor.
changing from defect to enhancement.
We only plan to open suitable editor in 0.7.0, bug 356704 has opened for that enhancement. So move this to future.
Hi, Will EDT can auto open suitable editor now, for widget and rui handler, it will open VE, for others, it will open EGLEditor. That work is finished in 356704. That is a better solution than CE which only hide the design and preview tabs when the file is not a widget or rui handler, because it is extensible and follow the Eclipse way. So I think this one can be closed.
already finished in bug 356704
Looks good.
