Home » Eclipse Projects » Eclipse 4 » Forms and Wizards
| Forms and Wizards [message #682502] |
Sat, 11 June 2011 09:28  |
 Karl Weber
Messages: 63
Registered: September 2010 |
Member |
|
|
If my understanding is correct, wizards and forms are not yet ported to e4. Dialogs, on the other hand, do not need to be ported, they can already be used in e4 -- at least they are used e.g. in the mailapp demo. (I assume that the compatibility layer is not employed.)
I have not really thought about porting wizards and forms to e4, but would it be complicated? What would be the direction to go? Please be forgiving, since I have only superficially looked at this problem.
e4 has the MPart, which corresponds to ViewPart / EditorPart of the old eclipse. So, in the hierarchy of FormEditor two steps are missing, since:
FormEditor > MultiPageEditorPart > EditorPart ...
Similarly:
FormPage > EditorPart > ...
So, a somehow minimal approach seems to be to the following
- Port FormEditor and FormPage.
- Think about FormToolkit, since it is tied to SWT.
- Try to use all the other pieces (FormPart, SectionPart, MasterDetailsBlock, DetailPage, ManagedForm, ...) unchanged.
Concerning point 1, one might try to model a FormPage as an MPart or an MPartDescriptor, which means that a FormEditor needs to be modeled as an MPartStack or as an MPartStackDescriptor (which would be new), respecively. One may also try to model the FormEditor as an MPart or MPartDescriptor, in which case a FormPage would not be modeled.
Concerning point 2, it may be possible to do without the FormToolkit and employ css-styling instead.
Is there already any work / discussion in progress?
|
|
|
| Re: Forms and Wizards [message #682531 is a reply to message #682502] |
Sat, 11 June 2011 10:59  |
Thomas Schindl
Messages: 6651
Registered: July 2009 |
Senior Member |
|
|
Hi Karl,
The first and most important question here is:
Should the editor UI-Framework be coupled with SWT or not?
a) Coupled with SWT:
--------------------
* Wizards: They are pure JFace components so I don't see a problem
using them as is
* Forms: You can use the FormsToolkit as is but taking a look makeing
it use CSS would be interesting project
* FormEditors (editors in common): There's experimental work in the
SimpleIDE which adds new meta informations to describe editors
in the workbench model you can find the project in CVS
In 4.2 we already discussed splitting ui.workbench stuff and friends so
that they can be used without the compat layer - we currently think that
we can use e4 bridge for 3.x to make that happen. You are free to join
the effort
b) Not coupled with SWT:
------------------------
This where you enter the space of a widget-toolkit neutral JFace-API and
there's already a project I'm leading named UFaceKit which has such an
API it's optimized to build Formbased UIs (currently we have
implementions for SWT, Swing, Qt, GWT) and not a general purpose
ui-toolkit so maybe you want to take a look at it.
The problem with UFaceKit is that I don't have enough cycles to really
push it forward in Eclipse and so I thought about moving it once more
out of Eclipse.org and host it at github
I expect many new features, ui gimmicks, ... are going to happen in the
Juno-Release because in Indigo the most effort went into the compat story.
BTW: An editor is better represented as MInputPart because it holds an
URI but if you checkout the SimpleIDE you'll find that out yourself.
Tom
Am 11.06.11 11:28, schrieb Karl Weber:
> If my understanding is correct, wizards and forms are not yet ported to
> e4. Dialogs, on the other hand, do not need to be ported, they can
> already be used in e4 -- at least they are used e.g. in the mailapp
> demo. (I assume that the compatibility layer is not employed.)
>
> I have not really thought about porting wizards and forms to e4, but
> would it be complicated? What would be the direction to go? Please be
> forgiving, since I have only superficially looked at this problem.
>
> e4 has the MPart, which corresponds to ViewPart / EditorPart of the old
> eclipse. So, in the hierarchy of FormEditor two steps are missing, since:
>
> FormEditor > MultiPageEditorPart > EditorPart ...
>
> Similarly:
>
> FormPage > EditorPart > ...
>
> So, a somehow minimal approach seems to be to the following
>
> Port FormEditor and FormPage.
> Think about FormToolkit, since it is tied to SWT.
> Try to use all the other pieces (FormPart, SectionPart,
> MasterDetailsBlock, DetailPage, ManagedForm, ...) unchanged.
>
>
> Concerning point 1, one might try to model a FormPage as an MPart or an
> MPartDescriptor, which means that a FormEditor needs to be modeled as an
> MPartStack or as an MPartStackDescriptor (which would be new),
> respecively. One may also try to model the FormEditor as an MPart or
> MPartDescriptor, in which case a FormPage would not be modeled.
>
> Concerning point 2, it may be possible to do without the FormToolkit and
> employ css-styling instead.
>
> Is there already any work / discussion in progress?
|
|
| |
Goto Forum:
Current Time: Thu Apr 25 10:50:01 GMT 2024
Powered by FUDForum. Page generated in 0.03259 seconds |
] 
Search
Help
Register
Login
Home
