[Relations-rcp-devel] Questions concerning SVN repository and target platform

[Luthiger S. B. <ben...@id...>]

Dear Anshul

 

Please subscribe to the project's developer mailing list
(rel...@li..., to subscribe:
https://lists.sourceforge.net/lists/listinfo/relations-rcp-devel). Then,
you can send your mails to the list for that such questions and their
answers can be a resource for further potential contributors too.

 

Concerning setting up a target platform, I send you two links to
relevant information sources:

http://wiki.eclipse.org/index.php/RCP_FAQ includes a paragraph (number
9) about target platform setup. Since I gave you the list of plugins,
you only need to follow the three steps in the lower part of this point.

http://rcpquickstart.com/2008/04/29/rcp-target-platform-tips/ is a good
substantiation for using target platforms.

 

Concerning checking out the SVN repository:

The generic chechout command is: 

svn co https://relations-rcp.svn.sourceforge.net/svnroot/relations-rcp
relations-rcp

(see http://sourceforge.net/svn/?group_id=123234) 

Therefore, if you set up a location in your svn repository browser with
the url:

https://relations-rcp.svn.sourceforge.net/svnroot/relations-rcp

you shouldn't have a problem.

 

Please provide me with more information if you still struggle with this
point.

 

Concerning the config.ini:

I have to clean up the config.ini I use to make it generic and,
therefore, working in you IDE. I'll send you the file beginning next
week.

 

Regards,

Benno

 

From: anshul pandey 
Sent: Donnerstag, 15. Januar 2009 11:32
To: Luthiger Stoll Benno
Subject: Re: Eclipse Developer

 

Hi Benno, 
please provide me with config.ini file details. Also I am unable to
import the SVN repository that you pointed out. Also, How to set up
target-platform ? 
I am eager to learn. Please help. 




On Fri, Jan 9, 2009 at 9:10 PM, Luthiger Stoll Benno
<ben...@id...> wrote:

Dear Anshul

 

Thank you for your feedback.

One year experience in Java programming is not that much, at least in
view of Eclipse RCP programming, which unfortunately has a steep
learning curve.

Therefore, it's definitively a challenge for you, but let's give it a
try J

 

The actual project situation is as follows:

The released versions of Relations runs on Eclipse 3.2.

However, I've ported the code to Eclipse 3.4. (Therefore, you need
Eclipse 3.4 to work with the code in the svn repository).

 

The first step you have to do is to set up the Eclipse IDE so that you
can develop and debug the application.

I strongly suggest that you use a separate Eclipse workspace for this
project using the -data parameter, e.g.

C:\eclipse\eclipse.exe -data C:\my_data\eclipse\workbenches\Relations

 

You then have to set up a Target Platform for the project (see the
RCP-FAQ on http://wiki.eclipse.org/RCP_FAQ  concerning the advantage of
target platforms). I've attached the contents of the target directory I
use as a sample.

 

You then can download the code from the svn repository. You can check
out all projects you see on
http://relations-rcp.svn.sourceforge.net/viewvc/relations-rcp/ . You
have to get rid of all Java compile errors. You need the framework file
viffw_light__src_20090109.jar I've attached to reach that.

 

The last step, then, is to create a debug- and run-configuration. The
configuration is of type "Eclipse Application" and runs the product
"org.elbe.relations.product". Most probably I have to give you more
information concerning the config.ini for this configuration.

 

Here is a good and up-to-date article for RCP development:
http://www.vogella.de/articles/RichClientPlatform/article.html. You'll
find plenty of other good articles on the net.

It's always a good idea to run the RCP examples (from Eclipse.org) to
have a working example from where you can deduce how it should work with
more complex examples.

 

Just for that I know it: Which OS do you have for development?

 

BTW: I'd suggest that you subscribe to
rel...@li... (on
https://lists.sourceforge.net/lists/listinfo/relations-rcp-devel) for
that you can send further mails to the list. Thus, our information
exchange will be documented.

There's another new developer on the project. Using the list as
communication tool, it's easier to share our knowledge.

 

Regards,

Benno