| JFACE or SWT [message #464226] |
Tue, 27 February 2007 20:13  |
Eclipse User |
|
|
|
Originally posted by: ccouper.us.ibm.com
I am debating trashing JFACE from a potential heavy weight RCP app and doing
nothing but SWT. The application is a very intensive graphical, GIS and
database application. The only menu items that I can use from JFace are
File-Exit, Edit (cut/copy/paste) and a few of the help menu's. I have
about 80 unique menu items for the app.
On the toolbar front I have a need for large button toolbars with both
images and text (it seems JFace removes the text if you add an image). I
also have a need for toolbars in top, left and bottom areas.
My status bar not only has a status message area, but has message areas and
icons for about 8 other application unique status items.
I have one major view in the middle (there are actually 3 view types of up
to 20 views there but they are swapped based on a one item selectable tab).
There are some unique views as 'sort of property pages' that get stuck in
the quadrant layouts.
I have scoped most of this in SWT already. Yes it lacks the actions
capabilities of JFace, but since I have to write all those anyway, what
would I be using?
So a two part question:
1. Should I just skip JFace?
2. What is the minimum Advisors I need to keep around to make a RCP/SWT app
work?
Chris
|
|
|
| Re: JFACE or SWT [message #464232 is a reply to message #464226] |
Wed, 28 February 2007 03:44  |
| Eclipse User |
|
|
|
I think You are getting RCP and JFace mixed up.
JFace is quite lightweight API for using SWT widgets and binding them to
appropriate data models (e.g. TableViewer and friends) or user
interaction (Action, ContributionItem, etc.)
Examples of the JFace API are table- and tree viewers, their content-,
label-, color- and font providers, that make presenting your data in a
table or tree widget much easier; Actions, contribution items and all
the contribution manager classes that make encapsulating and reusing
common actions a breeze; Common window, dialog and wizard classes that
help managing the lifecycle of these very important UI pieces.
RCP is on the other hand the often heavy-weight framework for full-blown
fat desktop application client that defines many of API's and
extension points for some of the most common UI elements an application
would usually need to implement in your application yourself any way.
Personally - the o.e.workbench.ui plugin (which is the core of the RCP
UI framewok services) often seems to be rather overkill with all the API
it brings together. It would be nice if it would be possible to break up
all the extension points in eclipse RCP so that I could pick and choose
between these instead of being forced to take "all or nothing".
All in all I would suggest that if you want a simpler base to build your
application from, ditch o.e.workbench.ui plug-in, but keep JFace. JFace
is itself rather useful API, that makes writing your UI much easier...
Chris Couper kirjutas mulle midagi seesugust:
> I am debating trashing JFACE from a potential heavy weight RCP app and doing
> nothing but SWT. The application is a very intensive graphical, GIS and
> database application. The only menu items that I can use from JFace are
> File-Exit, Edit (cut/copy/paste) and a few of the help menu's. I have
> about 80 unique menu items for the app.
>
> On the toolbar front I have a need for large button toolbars with both
> images and text (it seems JFace removes the text if you add an image). I
> also have a need for toolbars in top, left and bottom areas.
>
> My status bar not only has a status message area, but has message areas and
> icons for about 8 other application unique status items.
>
> I have one major view in the middle (there are actually 3 view types of up
> to 20 views there but they are swapped based on a one item selectable tab).
> There are some unique views as 'sort of property pages' that get stuck in
> the quadrant layouts.
>
> I have scoped most of this in SWT already. Yes it lacks the actions
> capabilities of JFace, but since I have to write all those anyway, what
> would I be using?
>
> So a two part question:
>
> 1. Should I just skip JFace?
> 2. What is the minimum Advisors I need to keep around to make a RCP/SWT app
> work?
>
> Chris
>
>
--
Roland Tepp
|
|
|
| Re: JFACE or SWT [message #466746 is a reply to message #464226] |
Tue, 24 April 2007 09:30 |
| Eclipse User |
|
|
|
Originally posted by: javaloco.argentina.com
It isn't an issue of using one or the
other. You can use both together if you like.
|
|
|
Powered by
FUDForum. Page generated in 0.02691 seconds
Home