Using a property with QList<QObject*> is the only thing supported
in Qt 5.12 (Ubuntu 20.04 LTS) and we should not replace the QObject
there with a subclass as things like `myProp.length` stop working.
This fixes the bug that a user creating a new wallet shows one wallet,
but behaves like there are multiple. This was because the initial "not-
user-owned" one was still shows to the GUI.
* split the AccountInfo and Payment classes out into their own files.
* Start a 'color' file to switch between light and dark-theme.
* Start a new main GUI which isn't so hacky and ugly.
* Make this actually a desktop app, with menu and file->quit!
When a user enters a legacy address we parse it and reformat it to the
new style, which is then shown to the user in order to make clear this
is a Bitcoin-Cash payment.
The user-entered text is still visible as a tooltip on desktop.
This provides code for creating the transaction, selecting the UTXOs and
signing the transaction.
Essentially everything except the handling of final tx (like sending it
to a peer).
This is clearly beta-level quality, it won't lose your money, but
kittens can be killed if you use this in production! Don't do that!
This payment client uses the proper P2P client and does not require
any additional indexing services and therefor is very much geared
towards the most private it can be with SPV, while staying scalable and
nible.
The only GUI available right now is for the desktop, it should be pretty
simple to re-do a nice GUI for some mobile or similar form-factors.
That is one area that QML simply rocks in.
tomFlowee
TomZ