| RAP_RCP [message #72964] |
Tue, 05 February 2008 09:53  |
Eclipse User |
|
|
|
Hi RAP developers;
I have my RCP application which contains many plug-ins, and I want now to
run it on the web using RAP. My questions are:
1: Should I have a separate workspace for my rap application, rather than
my RCP application workspace?
2: How I structure my application, to avoid the redundancy and replication
between RCP and RAP application.
3: Can I build both RCP and RAP application together without getting
conflict and CCE problems among RAP and RCP plug-in rap.ui and
eclipse.ui?
Regards
Salwa
|
|
|
|
|
| Re: RAP_RCP [message #73418 is a reply to message #73387] |
Mon, 11 February 2008 05:56  |
| Eclipse User |
|
|
|
Martin, Salwa,
We found a slightly different solution for this problem and we're
interested in discussion the respective pros and contras of the two
solutions.
Initial position:
a) RCP (platform) and RAP (platform) live in bundles with different
symbolic names but provide API and implementations with the same package
names spaces.
b) There are still slight differences in the provided APIs
Requirement:
Provide RCP and RAP applications (deployments) out of (mostly) the same
code base.
Our solution:
We encapsulate the different prerequisites into two plugin projects with
different project names (so that they can live in parallel within
CVS/SVN/...) but with identical bundle symbolic names. Each of these
bundles reexports the dependencies needed for its respective platform.
This way the application bundles can depend on a single "multi channel
platform" bundle which, at deployment time, has different content and
provides the applications with everything they need in this deployment.
In addition we're using these "MCP" bundles to abstract away some minor
API differences between RCP and RAP (see my posting "Missing API", which
is unanswered so far). Example: The Resource class of real SWT has got a
dispose() method which is missing from the RWT implementation. We plan to
migrate all of our code to use MCPUtil.dispose(resource) instead which is
implemented in the two MCP plugins accordingly (until the RAP project is
able to eliminate such differences).
As I said, we're interested to see some discussion about such design best
practices, not to mention that we're also keen to see how this newsgroup
performs. The latter is an important indicator for us when it comes to
management decisions ;-) So far we're really impressed by what you have
achieved with the RAP project!!! Thx for that.
Cheers
/Eike
|
|
|
Powered by
FUDForum. Page generated in 0.02942 seconds
Home