|Re: Questions re. some basic RCP concepts [message #1059938 is a reply to message #1059765]
||Wed, 22 May 2013 08:48
| Tomas Kramaric
Registered: August 2012
1 ) Rich Client Platform - maybe also because of usage Equinox oSGI, which offers many implemented services; usage of Equinox Extensions... All of these helps you to make really "Rich" application with less coding effort.|
2 ) If its only simple application in JavaSE, I would not convert it to RCP. But it you want to play around with RCP to understand, than why not, you
can even develop simple application using RCP (Equinox OSGi) - me personaly use standard Java + SWT when developing simple app, RCP is more complicated, and sometimes when facing some problems of loading plugins & dependency stuff makes me really angry... etc.
3 ) It depends on point of view I mean, you definately have to know SWT & RCP, if you create some RCP application, and get this system into hands, than you will find it easy to recode your JavaSE+SWT app into RCP
4 ) Big complexity, many things which you don't have in your hand, like OSGi...
5 ) Every RCP application can be exported as normal EXE application, so to run your exported APP you dont need Eclipse to be installed, only JRE (and even not, if you export your APP with JRE inside)
6 ) In RCP you can use Perspectives, Views, JFace Wizards, JFace Dialogs... this is very nice thing on RCP (Equinox) (I think JFace you could use even in J2SE, correct me If I am wrong)
7 ) Yes of course, in Workbench application, there is Menu, Toolbar. Definition of Menu & Toolbar, can be done by very convenient way, by declarative manner, using Equinos Extensions, where you define Menu layout, Commands, Menu contributions, Command Handlers... only your command Handlers has to be coded.
8 ) Eclipse Equinox extension offers this possibility to make Help, google for some tutorials. If you want to have Help in your app, easiest it would be done via RCP
Hope I helped
Powered by FUDForum
. Page generated in 0.03074 seconds