Originally Posted by Szymon Hi Blowfish,
I will take your comments into consideration. The first stage is to build a test application to see if the concept works then I will consider expanding it.
Regards
Simon |
I am a great believer in prototyping

Picked that up from my first boss when I needed to write firmware and software to utilise hardware my fellow researchers had designed. He would insist on writing a test suite first and then a prototype. The code would morph into the app anyway. This is one of the reasons I wasn't particularly bowled over by OOP, I was kind of used to writing re usable code.
I do wonder why you picked 1 hour granularity to collect and store? Forgetting tick data for now nearly all applications (and data providers for that matter) provide and store data in chunks of 1 minute. Even if you only want hourly bars it makes sense to collect and store minute data (later perhaps ad tick data) and to aggregate them into hours. The only expense is a little more storage.
I am not familiar with OEC's data feed api but it is likely not to be a question of expanding later but of adding code now to filter and aggregate minute data into hour bars and then removing it later. Hope you don't mind me bleating on about this but I think this is a fundememental design concideration that will actually add complexity to diminish utility.
The visualisation stuff looks nice! A shame that open source stuff is relatively rudimentary though JFreecharts isn't too bad. I know a couple of people who have done great things with it. IB wasn't one of them!
Have fun this weekend with the new software!