Hey,
thank you for your kind words. One potential problem I see is the sheer amount of data which might add up after time. I cannot estimate how much that will be in the database. But for the moment, I'm coding locally with an Apache/MySQL webserver/database on my notebook, and I store data from one coin (development phase... no need to add more, yet) and only the open/close/high/low of every full hour to prevent me running out of disk space.
However, Cryptsy has way more than 100 coins in their exchange, so I'm awaiting the data collection testing phase with agony and fear. ^^
Today, I did some frontend work and I partially implemented a user settings view and a view for trading with different options which are not provided by the exchanges. It already displays real data, but next time I get into JavaScript Wizard Mode, I'll have to provide the functionality which does all the magic.
Here is another screenshot; it'll be the last one here. I'll open up a thread soon (this weekend, maybe), but I have to spend some time with my wife first. She's a bit mad because she thinks I'm spending too much time on the computer. Well, actually, she's right. Kind of.
Click here for the image; I can't get this forum software to display the thumbnail of the screenshotI see, I have to open a separate thread, as I don't want to hijack this one or people getting annoyed.
Yes allyouracid, the vast number of Cryptsy markets caused me some headaches too. I've been playing around with something similar in C#, pulling all markets (orderbook, depth and filled order information) at 15 minute intervals. After running for a day, I realised that there was far too much data. I've still got a lot of work to do (it doesn't do much more than pull and store data at present), but I've been planning on revisiting it for a while now. If you do decide to start a thread, I'd certainly love to chat some more about this stuff. I must say though, that interface of yours is really looking lovely; and collapsible menus too. Hopefully Cryptsy will take note! Are you using a UI library or is this all hand-rolled?
Haha, I hear you on the wife thing as I'm guilty of that myself. Still, it keeps us out of trouble
Yeah, that sounds good. In fact, I already "started starting a topic" (I guess, with me, all things just take a bit longer ^^), meaning I started writing the text. Every time something important to be mentioned there comes into my mind, I add it. I think that's the first public posting of an application/service and it has to be good, providing all the information about current state/planned features users might be interested in.
I'd be happy to talk about some coding stuff there, as I have some points (e.g. calculating OHLC data from the single trades... not sure if there's a library yet, and I don't want to reinvent the wheel, but if there isn't, I'll code a library myself, although I'm not sure if I want to put this on the client side, as the 1000 sets of data cause the script to hang) which are worth discussing.
To the user interface: I think in the world we live in, it would be insane to build all those UI elements by hand.
I bought a license for SmartAdmin (uses bootstrap and jquery-ui along with some other libs) which provides the UI elements. But while developing, I already thought that it might have been easier to build those elements myself instead of implementing SmartAdmin
Reason is: SmartAdmin is a template for use in backends. You have a ton of sample pages, each up to multiple thousands of lines of code long, using different features with different libraries to be included. Took some effort to wrap my head around it, but it was worth the time.
Also, SmartAdmin used the JavaScript library "flot" for plotting charts. I was not satisfied with it, mostly because another plugin was needed to display our most needed chart type: candlesticks. So I had a look around and found AmCharts, which I implemented. Currently, it's free, but when my service goes online, I'll have to pay some 1-200 bucks. But as it's really a great, powerful library, I'm more than happy to pay it.