Archive for January, 2007
We are attempting to capture various tasks using our project’s Google Code Issue Tracker.
Where’s The Code?
We are not releasing the code until we have a solid foundation good enough to call “beta”. There are several reasons. Arguably the most important reason is due to the constant code changes. The APIs have dramatically changed in just a few days. Thus you would become quite angry with us as we pull the API carpet out from under your feet.
Is There a Roadmap?
Unfortunately we do not have a roadmap (yet). We’ll post the roadmap as soon as possible. In the meantime, feel free to keep tabs on the Google Code Issue Tracker. Feel free to add feature requests to the list.
January 30th, 2007
Currently this site discusses a single application called Log4FIX, which is a great tool for viewing raw FIX messages in real-time as part of your QuickFIX/J application, or later using any file containing raw FIX messages. Very soon more details will emerge about another product named OpenOMS. OpenOMS is an order management system based on a FIX engine. Of course, OpenOMS will “ship” configured for QuickFIX/J. A major goal of OpenOMS is to fill the gap between your trading algorithms and order management. QuickFIX/J provides FIX connectivity. OpenOMS manages your orders. You concentrate on your trading algorithms.
Are there other open source trading applications or tools that you would like to bring to this site? If so, let me know. We can talk.
January 23rd, 2007
I moved Log4FIX from SourceForge.net to Googe Code. SourceForge, in my opinion, is slow, clunky, and hard to use. So far I have enjoyed my experiences with Google Code.
http://code.google.com/p/log4fix/
January 6th, 2007
I am pleased to announce the release of Log4FIX 1.0. This release includes numerous bug fixes, enhanced memory management, and updated message logging.
Please visit http://code.google.com/p/log4fix/ for more information.
January 6th, 2007