Hey,

Can someone please give me some examples to do the following:

Open price of a bar
Close price of a bar
High price of a bar
Low price of a bar

Highest price of an array of bars
Lowest price of an array of bars

Can someone also please explain to me why there is no coding tips while coding? For instance if I want to code a simple moving average, the code looks like this:

double sma50 = this.indicators.sma(instrument, period, OfferSide.BID, IIndicators.AppliedPrice.CLOSE, 50, 0);

There is no incode tips saying what variable I'm working with now or what parameters is required etc...

How am I and other coders supposed to know where the parameters should come and in what sequence? I cannot find any documentation learning new users how to use the built in functions. Did I miss something?

Thanks!

Hi,
You can find code examples in the JForex Wiki page https://www.dukascopy.com/wiki/index.php?title=Main_Page. For the strategy example please consider the Strategy API section. For detailed API methods description please consider the JForex API https://www.dukascopy.com/client/javadoc/

Thanks will try to find my answers there

Use an IDE for JForex coding popup tips. Either Eclipse or Netbeans is good. They're professional IDE that are leaps and bounds better than any EasyLanguage or MQL editor.

Good idea I did not think about that.

Quick question, looks like you know what is going on in JForex. When testing a strategy, why do I get way different values when using tick open/tick close prices versus cubic spline ?

To my knowledge cubic spline is tick interpolation?

The strategy is based on open bars trading only so the two testing methods should give more or less the same results?

I'm a seasoned MT programmer, what makes JForex better?

I opened the file with Eclipse for Java, but I still don't get the coding tips.

For instance the following code:

if(period == Period.ONE_HOUR) {

if (askbar.getVolume() == 0) return;

Don't get any coding tips.

Don't I have to copy the api in some folder or something ?

Sorry I don't know anything about java my programming knowledge is very limited.

Saidar, I'll leave Dukascopy support to answer your question regarding tick choices in backtesting. I think it's been discussed before in the forum, so perhaps you can find your answer.

Better is a personal opinion. One obvious difference is that MQL is easier to code strategies in. But the problem with easy is that it makes the sophisticated impossible. If you want easy, go with MQL. If you want robustness and versatility, go with JForex. The only way to know is to try both and form your own opinion as everybody has different needs.

For Eclipse, you need to assign the javadoc and source files to the JForex library in the build path.

I just wrote my first strategy, must say it was not that hard java is actually quite user friendly... But I'm still confused about the different bactesting methods, I still get way different results when testing the different models.

Will send an email to support about this.

I guess I cannot go wrong with tick tesing (no interpolation) so I'll use that from now on. Only problem is optimization is out it takes way too long to run thousands of iterations.

Please take a look at https://www.dukascopy.com/wiki/index.php?title=Historical_Tester

Thanks. Something that I picked up, lets say the strategy has a constant take profit of 20 pips and a constnat stop loss of 10 pips.

When NOT using the tick testing mode, the actual pips where the profit is taken or where the loss is taken varies greatly. It is seldom precisely the specified take profit or stop loss.

Any idea why this is happening ?

I know the code is run on every opening of a new bar or closing of a new bar, but the tester should recognize that the profit or loss should have been taken at the specified value and not the current one at the beginning of the new bar.

When the Historical tester runs using bars price, then the historical tester assume tick which comes on bar close/open. That's why the take profit has different results.

Yes I have figured that one out. Here is a tip for the developers at Dukascopy:

Modify the tester to close the trade at the SPECIFIED takeprofit and stop loss. I know the tick will never be at that TP or SL but it won't use anymore processing power to anyways close the trade and that price. It is a very small modification I think.

That way the tester will obviously give more accurate results.

This feature is built in in metatrader and works very good.