Thanks for your reply about BTC-Trader. Well using different MtGox keys would be possible. Lets say you have 4 different API keys. I can change BTC-Trader to use 4 different password protected 7z-files in order to handle several API-Keys. Each key will be saved in another 7z file. For example: user01pw.7z, user02pw.7z, user03pw.7z and user04pw.7z
Then one user can handle several different API-Keys or you can even have different API-Keys for different users.
About the window mode:
Personally I like this fullscreen mode, because this way you will have maximum space for your objects on the screen. This mode is best, if your screen resolution is equal to the one of BTC-Trader. However it is sometimes annoying, if you have to tab out of the application several times! And if your screen resolution is higher than the one of BTC-Trader a windowed version of BTC-Trader would be desireable, because this small screen inside a large one looks kind of poor.
It's not a great effort to compile a windowed version. Lets start with one test-version. What screen resolution would you prefer for your windowed version of BTC-Trader?
About the charts:
Well, I don't exactly know yet how to implement charts into BTC-Trader. It may be some effort. What charts are you thinking about? Something like mtgoxlive.com/orders ?
But I also have another idea regarding the Bitinstant arbitrage: I use an Excel file to calculate if a Bitinstant transfer from MtGox to BTC-e would be profitable. I would like it to have this kind of calculator function integrated into BTC-Trader. This is my idea about a new function in BTC-Trader.
Regards
Andreas
I do use most of my programs in full screen, but windowed full screen.
I would suggest to build a 1920x1080 version, as that's the version i use mainly.
As for the "self made keys" i meant, the mtgox key, as in "redeem key" or "withdraw key", not the api key, but multi user support would be nice also now that you've mentioned it;
Like for example to store the last 5 or 10 mtgox keys until they become invalid after the have been used.
Now when you generate a mtgox key (withdraw) it stays in the upper text field.
The idea is when opening that page the next time, or when generating another key, the key would move on tho the next text field, so it wont get lost and saved in the ini file under "MtGoxCode02=" instead of overwriting "MtGoxCode01=" with the last key generated.
For charts, i would suggest to choose for the most common chart type used in forex trading, "Chineese Candle Stick Charts" or eventually "bar charts" for example:
image source: http://stephansmithfx.com/explanations/technical-analysis/
But i suppose therefore we need to store tick data somehow, could be on a server or local.
I was thinking about local data in the first place.
Wish would mean that chart data will not be available when starting up the application for the first time.
This i think, could only be accomplished if we let the application run 24/7, we would have gaps and false results if we close the application often, the data would be unreliable.
So i suppose the only option left is to have a tick data server wish serves as caching proxy for the data pulled from mtgox.
As for the idea about the excel calculator file, i saw you using it on one of the video's, that indeed would be nice to have it integrated.
Regards,
MasterX
I already did the 1600 x 900 pixel window version of BTC-Trader. The others will follow.
Please note, that your screen resolution should exceed the one of BTC-Trader, if you want to use the window version.
Best regards
Andreas
Thank you, i'll test it right away.
Good night!