jump to navigation

Technical Issues - Source Code December 17, 2008

Posted by admin in : Uncategorized , add a comment

The latest source code (for ver.0.7.a) can now be found trough SVN access here:

http://code.google.com/p/openforexplatform/source/checkout

or trough SVN/Team Explorer or direct web browser download here:

http://www.codeplex.com/ofxp/SourceControl/ListDownloadableCommits.aspx

The release of ver.0.7.a is planned for 4.Jan.2009 and will include a revised news control, expert editor, integration to yahoo historical quotes as well as the usual set of overall improvements and extensions.

Technical Issues - SqLite December 7, 2008

Posted by admin in : Uncategorized , comments closed

Open Forex Platform is adopting SQLite as its main data storage. SQLite is lightweight, free and has support for Mono. Having a proper (though lightweight) database as a data storage will now allow the prompt development of additional features including manipulation of large amounts of data items (news, historical quotes etc.).

Linux / MacOS Support in the Making December 5, 2008

Posted by admin in : Uncategorized , add a comment

As it turns out the Mono Project has seen some huge development over the last couple of years and this is great news since many .NET projects are becoming available to Linux based systems.

Open Forex Platform is no different. However since Mono does not cover .NET 3.0 completely the Arbiter Network Transport communication mechanism in Open Forex Platform Support Module needs to be modified slightly to make it compatible with Mono. This is not a big task and it is now in the feature pipeline.

If you are interested in this development aspect of the platform and have some questions use the forum to get more details.

Technical Issues December 1, 2008

Posted by admin in : Uncategorized , add a comment

It seems there is a problem in the .NET framework with the method Control.Invoke - from time to time, in some certain conditions it hangs and does not execute. I managed to find someone with similar experience here: http://www.devnewsgroups.net/group/microsoft.public.dotnet.framework.windowsforms/topic10614.aspx

However they mention this has been addressed in .NET 2.0 and this does not seem to be the case. This is a rather serious issue, since there is no easy general workaround this mechanism. It seems the problem occurs when there is a huge amount of Invokes flying to any control in the application. My guess is the message pump queue gets full and some of the Invoke messages get dumped, but it only happens when there is more than one form involved.