Good to see community-driven prioritisation of the roadmap. I am more than happy to adapt to it, as I said earlier.
Let me reply in line.
This is work in progress : in particular there is an utility I've built that custodians are already playing with that reports all executed orders. Sample output from my operation on excoin : http://pastebin.com/p2NCKq10
@Ben is working on integrating and making it more human-readable.
In terms of roadmap prioritisation this is currently in
0.4.4 : NuBot toolkit release ( trade history, balance history, price-peg execution bot)
I think it makes sense to leave it where it is in terms of prioritisation, cannot be moved much earlier than that.
There is a GUI designed and coded since last summer we can re-use. I never hooked it up as no-one ever asked for one and I avoided adding complexity. In 7 months many thing changed but most of the code/design is still re-usable.
Please take into account that the totality of custodians to date run nubot from the command line on a VPS or raspberry and they won't be able to use a GUI.
For the above reason I believe that we should leave the "Bots manager UI" prioritised as it is now in 1.0.0 . However, what can be done quickly is another kind of UI :
So this will solve a different problem, probably more useful in the short term : nubot configuration.
Currently to configure the bot the custodian need to configure a json file (or multiple json files)
following this tutorial -> https://bitbucket.org/JordanLeePeershares/nubottrading/src/a59f70b780af8730ba92b99dc2d81e91fc7b7ddf/SETUP.md?at=release/0.1.5
Or they can download the sample.zip configuration file and try edit it and reverse engineer it.
We can build a (stand-alone) UI that does nothing but :
- provide a graphical way to configure the bot, and behind the curtains generates the configuration files for the custodian.
- allow custodians to save configurations and assign a name to each "profile
- provide a "launch bot" button that simply runs nubot with the profile created above.
However, there is no way around it... I believe that custodians must be very aware of what they are doing, and how each parameter they touch will affect the behaviour of the bot.
If you think this makes sense I can add a ticket somewhere between 0.2 and 0.3.
Perhaps the first version should merely contain a start button, a stop button, and the same info that is presently logged presented in the UI. The second version could permit essential options.json settings to be entered in text boxes and dropdowns so that the user doesn't need to edit options.json directly. A third version might show information about open orders and recently executed orders. A fourth might feature reports on trading history, deposits, withdrawals, transaction fees and profits/loss.
Totally agree, the user interface must be built in iteration and the first logical step is making the tool that generates the .json configuration profiles and allow the user to start/stop the bot.
I can envision endless improvements and iterations (API key verification, logging, multiple bot management, move liquidity across markets, reporting, a graphical tool to model the order book etc.
However, everything but the setup UI must be built after v1.0 , where all protocol changes are ready, otherwise it will just enormously slow down the development process requiring change things in several places when we are not even sure of future directions.