DockingFrames vs RCP

Hello,

cause of a request from the client, I wants to know the pros and cons of using DockingFrames instead of RCP Eclipse

Thanks.

  • Swing and not SWT: you don’t need a version for each platform. You can write Applets and use Webstart.
  • Smaller than RCP Eclipse
  • Chance that a feature request from you gets implemented by me :wink:
  • One developer vs. a company… bet who has more features and less bugs
  • Not as widespread as RCP Eclipse: there are not many people who can help if you have a problem and the library is not tested as good as RCP Eclipse.

Depending on what you want to do:

  • Does not impose a certain style of programming
  • Easy to set up (include two libraries in your classpath, start writing the application)
  • Both libraries are customizeable and extensible.

Personal opinion:
DF is good for smaller projects. I.e. if you want to write a small tool that is used by a limited number of people within your company. I would not yet recommend the library for a 100’000$ project (it would be cool, but realistic speaking: the library as a whole is still on the level of a nearly completed beta-version).

Generally, I prefer small API (with source code), but my responsible put me the pression to use RCP. Explaining me that is the future of rich client application.
I taked a look to RCP application example… I don’t like it.
Since Swing are more fastest, I don’t see the needed of SWT.
I don’t need the plug’in capability, too.
RCP seems to be more difficult to learn.

I think to use dockingFrames with JSR-296 (Swing Application Framework) application style.

I continue to investigate both.

Thanks.