Eclipse Community Forums: Standard Widget Toolkit (SWT)

Help

Home

Home » Eclipse Projects » Standard Widget Toolkit (SWT) » JFace vs Swing approach to MVC

Show: Today's Messages :: Show Polls :: Message Navigator

JFace vs Swing approach to MVC [message #438514]

Sun, 27 June 2004 11:51

Eclipse User

Originally posted by: john.rmts.donpac.ru

Hi,

Why JFace and Swing approach to MVC is too different?

I talk about JTable<->TableModel and TableViewer<->Providers for
example. At first side Swing approach is simplest and have more
features. In Swing I can define all table data in one class, but in
JFace I need define some classes and I can't define columns properties
by this classes.

Is this JFace design is generally bad or it will be usefull in some
cases? In which cases JFace design has advantage over Swing?

Report message to a moderator

Re: JFace vs Swing approach to MVC [message #438516 is a reply to message #438514]

Sun, 27 June 2004 12:48

Henning Rogge

Messages: 148
Registered: July 2009

Senior Member

Eugene Prokopiev wrote:
> Why JFace and Swing approach to MVC is too different?
>
> I talk about JTable<->TableModel and TableViewer<->Providers for
> example. At first side Swing approach is simplest and have more
> features. In Swing I can define all table data in one class, but in
> JFace I need define some classes and I can't define columns properties
> by this classes.
>
> Is this JFace design is generally bad or it will be usefull in some
> cases? In which cases JFace design has advantage over Swing?

Most times the Swing approach is just overcomplicated...

Look at a tree provider in both cases, the JFace approach is much easier
to use than the Swing one.

Henning Rogge

Report message to a moderator

Antwort: JFace vs Swing approach to MVC [message #438602 is a reply to message #438514]

Mon, 28 June 2004 14:53

xxx

Messages: 6
Registered: July 2009

Junior Member

As far as I see you shouldn't compare these two.

Swing's table has an unrestricted flexibility. But for the 90% of simple
tables
an application usually needs the use of JTable is not very comfortable.

The application framework layer above Swing is missing.

I don't know JFace in detail but it is addressing this framework layer. It
should be easy for a developer to use a table without having to define
all of its properties. Some useful delegations are foreseen to bring a
standard table immediately to work.

For me this layer is very important. I would like to reduce my development
effort in programming against such a layer only. Below this layer it
should
become easy to switch the toolkit (SWT/Swing). But I expect it will take
some time if such a complex widget like a table has been settled on that
layer.

I'm interested to see comments from others more familiar with this design
question.

regards
Wolfgang R.

Report message to a moderator

Previous Topic:	Drag 'N Drop in SWT
Next Topic:	Removing controls from a composite

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 15:43:42 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter