|
Attention! Read the forum rules carefully before posting a topic.
Try to find an answer in Wiki before asking a question. Submit programming questions in this forum only. Off topics are strictly forbidden.
Any topics which do not satisfy these rules will be deleted.
Using Eclipse as editor: importing dukascopy.api |
RoadRunner
|
Post subject: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Tue 09 Sep, 2008, 21:31
|
|
User rating: 3
Joined: Wed 18 May, 2011, 16:25 Posts: 331 Location: SwitzerlandSwitzerland
|
I'm using Eclipse as an editor for the strategy and all the external classes I'm calling from within the strategy. I'm wondering if there's a way to making the JForex object model known to the Eclipse project or package, so that Eclipse could do syntax checks on the jforex objects while editing?
Thanks, R.
|
|
|
|
 |
API Support
|
Post subject: Re: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Wed 10 Sep, 2008, 15:08
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17 Posts: 6139
|
Sure, you just need to add jforex jar to the libraries in project properties. The easiest way to get it is - start jForex, compile some strategy (you just need to push compile, doesn't matter what's the strategy). When you compile strategy for the first time, jforex platform saves it's jar file in jfxide\lib\dds2-agent.jar in TEMP directory. On WinXP temp directory usually is c:\Documents and Setting\<user name>\Local Settings\Temp. This file is updated every time you start the platform, so if there is a new version of jForex, you will get new file in jfxide\lib directory
Another way is to download it directly from our site by locating it in jnlp file, but it's more complicated and involves finding it in jnlp, downloading as pack.gz and unpacking
|
|
|
|
 |
RoadRunner
|
Post subject: Re: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Sun 04 Jan, 2009, 11:01
|
|
User rating: 3
Joined: Wed 18 May, 2011, 16:25 Posts: 331 Location: SwitzerlandSwitzerland
|
Would it be possible for you to provide a JavaDoc comments file for the dds2-agent.jar as a download, so it can be included to the Eclipse environment to show the tooltips?
Thanks a lot, R.
|
|
|
|
 |
API Support
|
Post subject: Re: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Mon 05 Jan, 2009, 10:00
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17 Posts: 6139
|
Here it is
Attachments: |
jforex-58.2-javadocs.zip [346.72 KiB]
Downloaded 957 times
|
DISCLAIMER: Dukascopy Bank SA's waiver of responsability - Documents, data or information available on
this webpage may be posted by third parties without Dukascopy Bank SA being obliged to make any control
on their content. Anyone accessing this webpage and downloading or otherwise making use of any document,
data or information found on this webpage shall do it on his/her own risks without any recourse against
Dukascopy Bank SA in relation thereto or for any consequences arising to him/her or any third party from
the use and/or reliance on any document, data or information found on this webpage.
|
|
|
|
|
 |
RoadRunner
|
Post subject: Re: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Mon 05 Jan, 2009, 13:02
|
|
User rating: 3
Joined: Wed 18 May, 2011, 16:25 Posts: 331 Location: SwitzerlandSwitzerland
|
Thanks a lot, Dmitry!
That's doing great! Could you keep posting updates to the JavaDoc shoudl changes occur?
|
|
|
|
 |
API Support
|
Post subject: Re: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Mon 05 Jan, 2009, 16:50
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17 Posts: 6139
|
|
|
|
 |
[vish]
|
Post subject: Re: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Thu 08 Jan, 2009, 12:41
|
|
User rating: 0
Joined: Wed 24 Dec, 2008, 18:49 Posts: 10
|
hmm. i have set up the eclipse external javadocs i tried both the url and the downloaded file, both times , it seemes to be missing the 'package-list' that eclipse complains about . but it does work, so you can ignore the warning
|
|
|
|
 |
RoadRunner
|
Post subject: Re: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Thu 08 Jan, 2009, 21:00
|
|
User rating: 3
Joined: Wed 18 May, 2011, 16:25 Posts: 331 Location: SwitzerlandSwitzerland
|
yes, you can simply ignore the validation warning for the package-list in Eclipse.
|
|
|
|
 |
[finimej]
|
Post subject: Re: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Sat 11 Jul, 2009, 23:53
|
|
User rating: 0
Joined: Fri 10 Jul, 2009, 20:17 Posts: 4
|
Very newbie question. 1) How to get the JForex API into Eclipse? Where to download the Jforex API? 2) how to use the strategy tester in JForex? Any documentation? Thanks. The one thread said the compile any simple strategy, does not help. Because no JForex API, then the compile in Eclipe will failed.
|
|
|
|
 |
API Support
|
Post subject: Re: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Mon 13 Jul, 2009, 09:48
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17 Posts: 6139
|
1) You need to compile simple (empty) strategy from the inside of jforex. Right click on strategies node in tree, select New Strategy, rename and save it, right click on newly created strategy and select compile. Then you will have jar file as described in post #2 in this thread. A bit complicated, but compilation from eclipse not officially supported yet, so... 2) Select the period you want to test on, select the strategy and push start  Documentation is still in development
|
|
|
|
 |
[finimej]
|
Post subject: Re: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Mon 13 Jul, 2009, 23:00
|
|
User rating: 0
Joined: Fri 10 Jul, 2009, 20:17 Posts: 4
|
Thanks, get the dukascopy API included as the jar library into Eclipse now. Next question, in Eclipse, I can only export the java as jar file.
Do I must compile inside the JForex? Can I compile the JForex indicator inside the Eclipse? because here has better debug environement. How to get the java file compiled into JFX file then? thanks.
|
|
|
|
 |
RoadRunner
|
Post subject: Re: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Mon 13 Jul, 2009, 23:57
|
|
User rating: 3
Joined: Wed 18 May, 2011, 16:25 Posts: 331 Location: SwitzerlandSwitzerland
|
Hi finimey, yes you have to compile on the JForex platform. (At least until API 2.4 gets released...  ) You can have the strategy's java file open in Eclipse and on the JForex platform at the same time. I'm coding in Eclipse, then switching the application to JForex for compiling. If you activate the editor frame within JForex, a messagebox will pop up saying that the file has been modified outside the JForex editor and if you want to reload the file. Simply opt for reloading and then compile and run on the JForex platform. This works very well for me. Debugging the strategy in Eclipse is not possible with the current JForex API, but will be with API 2.4. Let's hope it will get released soon... Have a good day, RR.
|
|
|
|
 |
dedalus
|
Post subject: Re: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Sun 07 Nov, 2010, 06:16
|
|
User rating: 0
Joined: Tue 24 May, 2011, 00:41 Posts: 38 Location: United KingdomUnited Kingdom
|
Hi all,
I was unable even to locate the files you were referring to.
Have you changed the name of the jar files in newest version of the API?
I am under Mac OS X 10.6; I would like to have snippets and support within Eclipse, also on the JForex API. From this old posts I guess it is achievable; am I right?
I am not experienced with Java (C# background, actually); what is the benefit of using the JavaDocs files? Again, I was not able to accomplish this, under Mac OS X.
Any help, greatly appreciated.
Thanks in advance.
|
|
|
|
 |
[quantisan]
|
Post subject: Re: Using Eclipse as editor: importing dukascopy.api |
Post rating: 0
|
Posted: Mon 08 Nov, 2010, 16:27
|
|
User rating: 1
Joined: Fri 26 Mar, 2010, 19:19 Posts: 116 Location: Canada
|
Download the latest API then...
The API jar filename is currently: JForex-API-2.6.21.jar The javadoc should point to JForex-API-2.6.21-javadocs.zip And the source should point to JForex-API-2.6.21-sources.jar
The benefit of adding javadoc and source in the library of Eclipse is that you get meaningful tooltips. Like when you mouseover a method, Eclipse pops up its javadoc documentation. It's very useful.
|
|
|
|
 |
|
Pages: [
1
]
|
|
|
|
|