Quote from: pinarello on February 04, 2014, 05:58:44 PM

Quote from: landomata on February 04, 2014, 05:57:38 PM

Quote from: pinarello on February 04, 2014, 05:46:18 PM

Quote from: landomata on February 04, 2014, 05:36:09 PM

Quote from: Come-from-Beyond on February 04, 2014, 02:07:50 PM

Quote from: landomata on February 04, 2014, 02:04:45 PM

what date do you have in mind?

What about 7th of Feb?

February 7th is a GO!

Go for what?

testnet....the AE client is ready....its not the most pretty.....I'll let the dev post about it....he has been working like a dog since last 3-4 weeks....HE IS GOOD he built HF prototype for Nasdaq.

I think he has a bot module inside the client...if im not mistaken.

Cool do you have more info somewhere?

I have a scalable high performance implementation of the api. Facilities for Use Case logic are there, and it should not be too difficult to put some basic functions in.

Right now I have a button for every API call, and I can shoot requests to the NRS from an apiBroker class that puts the requests into threads from the QThreadpool object.

ATM, the replies are dumped onto a QTextwidget. But there is a total of seven windows already in the app, and when someone wants more, it is a piece of cake to add them.

Also, the signals from the apiBroker can be connected to as many widgets on as many windows as desired. i.e. when you call or poll 'getBalance' and you have the balance displayed on multiple windows,
the displays on ALL the windows get updated automatically by the same signal.

Regarding the AE testnet. I have actually already been using it while testing my client, i.e. I have all the functions actually tested. This also means that I have created some assets, place and cancelled bid and ask orders, transferred assets, and sent messages.
The only function that I have not tested is the 'decodeToken', I had no time for that yet.

I'll need to put some basic use cases in - I can not promise to release the client on Feb7. but I'll see what I can do.

I'll post some code samples and more explanations on the client dev thread.