Hi bitcoinspot.nl,
Thanks for your feedback on MultiBit and suggestions. I have had a think as to implementing them:
Bigger QR codeI have put the 'show QR code bigger' functionality into the UI rework I plan to do for the 0.3 release.
The document with all the UI rework is here:
https://docs.google.com/document/d/1eJ-vKf6yc5tLuvzKPJDiSwKzHophVYXH0rPfhpIUzq8/edit?hl=en_GB&pli=1Email supportI have had a think about the emailing of transaction details. It would be possible to add in configuration data for a link to an SMTP server (this is a standard email server type that most non-web email clients connect to). It would then be possible to have a set up with:
1) Whenever you send bitcoins have the option to add in a recipient email address so that they get a message something like:
"You have received X bitcoins to address Y. The label was 'Z'.
There would have to be a template file for the format of the email for it to be useful and localisable.
You would probably want to CC yourself in too.
This would be like the PayPal 'You have received funds' email you get.
2) Even when no recipient email was specified you could CC yourself for your own records.
This would give a "funds sent' email.
Tracking transactionsYou also mentioned earlier keeping track of 'transactions not yet paid for' (Invoices). This is much more work as currently there is no database backing MultiBit. Transactions are only the basic transactions stored in the bitcoinj wallet. To start tracking transactions for which there is no bitcoin transactions means adding a backing db. I can see this coming but it is a big chunk of work - I am hoping I will be able to reuse the work Gary Rowe is doing on MultiBitMerchant when he completes this as it is similiar.
Order of work : What I am currently working onI have put your email support suggestion into the proposed list of work for MultiBit 0.4. The list of what work is in which version is here:
https://github.com/jim618/multibit/wikiCurrently I am doing some maintenance work and then will be making a push on having encrypted private key files and encrypting the wallets themselves. After that I will be working on the UI refresh and basic exchange integration using Tim Molter's XChange library (the two are a bit entwined). The 'show QR code bigger' functionality I will add in then.
That will be, more or less, everything in the 0.3 release so I will then get that out and start bug fixing.
After that I will start on the more detailed 0.4 use cases - including your email support requests - so I will probably ask for more details (or ask for you to review the use cases) at that point.
Also parallel to this is the Open Transactions fork of MultiBit in which they have added OT functionality. I am planning to have a look at what they have done when I do the UI refresh/ basic exchange integration to see if this can be 'folded in' to the UI/ code. This is a bit experimental at this stage so I have not put it explicitly in the deliverables.