To add a new row, there could be a "ghost row" at the top. Clicking on it makes the edit boxes empty. Setting them to something creates a new row. Note that this would allow invalid rows (eg empty address), but that's OK, they can just be ignored in the rest of the code.
Ok good idea. The editing could even happen inline in the table, so that separate edit boxes are not needed.
Combined with a ghost row that would allow removing two of the buttons.
Or edit could be beside the highlighted row and new address be beside the ghost row, which in the image provided seems to be the bottom rather than the top. (It should be wherever the newest would be, so top or bottom depending on whether displaying oldest or newest at top).
The list is not sorted by creation date but by label or address. So the ghost row could be anywhere. On top would make the most sense IMO, as the top row is visible when the window opens.
In the main window there are after the addresses the addressbook's aliases in paretheses. How about only writing the aliases and displaying the related addresses on small pop up tip tool, when the mouse hovers over the alias? Or at least exchange the order of the information to "alias (address)"?
I've changed the order to "Label (address...)". Indeed looks better. As you can have multiple addresses with the same label, completely removing the address is not possible.
Also some people have suggested that they want to see the addresses in any case; to see whether they have the right one.
Is there a reason why this project isn't done as a fork of bitcoin on github? It seems to me that it would be easier to integrate changes from the core of the reference client if it was.
It was originally not meant as a fork of the mainline bitcoin. In the beginning I wasn't sure whether to link it directly or go through RPC. I'm not sure whether it is still possible to make it a fork.