Eclipse Community Forums: Remote Application Platform (RAP)

Help

Home

Home » Eclipse Projects » Remote Application Platform (RAP) » RCP and RAP single-sourcing

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

RCP and RAP single-sourcing [message #633439]

Sun, 17 October 2010 22:59

Stefan Bleibinhaus

Messages: 4
Registered: October 2010

Junior Member

Hi,

i am fairly new with RCP and RAP, but i've successfully ported our RCP-based application to RAP. We want to use techniques of single-sourcing for having a huge common code-base and then platform-dependent projects for RCP and RAP.
I have found some methods on the web, which can help me doing this, but i don't know yet, which is the right one. So i'll present to you, what i have found and hope, you can help me choosing the best practice.
What i am personally thinking about, is to program against an interface and load the implementing class from a fragment, which is platform-dependent...

1)
-abstract type in host-bundle, that encapsulates the problem
-type implementation in the fragment, that platform dependent, solves the problem
-loading the platform specific implementation at runtime by means of reflection
(found at http://www.eclipse.org/rap/documentation/#resources - Webinar: Single-Sourcing Techniques for RAP and RCP, Oct 23, 2008, Frank Appel)

2)
using Patch-Fragments as described here: http://wiki.eclipse.org/RAP/Patch_Fragments

3)
your way to do it...?

Thanks for your help Smile

-Stefan

Report message to a moderator

Re: RCP and RAP single-sourcing [message #633478 is a reply to message #633439]

Mon, 18 October 2010 07:35

Ivan Furnadjiev

Messages: 2426
Registered: July 2009
Location: Sofia, Bulgaria

Senior Member

Hi Stefan,
we provide a Single-Sourcing Guide that will probably help you.
See http://eclipsesource.com/en/info/rcp-rap-single-sourcing-gui deline/
HTH,
Ivan

On 10/18/2010 1:59 AM, Stefan Bleibinhaus wrote:
> Hi,
>
> i am fairly new with RCP and RAP, but i've successfully ported our
> RCP-based application to RAP. We want to use techniques of
> single-sourcing for having a huge common code-base and then
> platform-dependent projects for RCP and RAP.
> I have found some methods on the web, which can help me doing this,
> but i don't know yet, which is the right one. So i'll present to you,
> what i have found and hope, you can help me choosing the best practice.
> What i am personally thinking about, is to program against an
> interface and load the implementing class from a fragment, which is
> platform-dependent...
>
> 1)
> -abstract type in host-bundle, that encapsulates the problem
> -type implementation in the fragment, that platform dependent, solves
> the problem
> -loading the platform specific implementation at runtime by means of
> reflection
> (found at http://www.eclipse.org/rap/documentation/#resources -
> Webinar: Single-Sourcing Techniques for RAP and RCP, Oct 23, 2008,
> Frank Appel)
>
> 2)
> using Patch-Fragments as described here:
> http://wiki.eclipse.org/RAP/Patch_Fragments
>
> 3)
> your way to do it...?
>
> Thanks for your help :)
>
> -Stefan

Report message to a moderator