I'm not sure how I feel about it. I'd very much prefer if some features were completed "in the house", so I can physically poke the responsible developer, when they don't do what I want or something is buggy - it is a lot harder to do that remotely :o)
There are some important things that are still missing:
- comment page, similar to hiveblocks - personally I only use it to see what people use to format their posts, so all the vote details etc. are not so important for me
- supplementation of wallet tab with all balances, so when I make some financial operation, the asset does not disappear only to emerge after a while, but just moves from one row to the other (or to some other account's balance in case I transfer funds out); now funds in open orders, pending conversions and incoming escrow transfers are not visible anywhere
- perspective tracking - when I'm looking at account page I'm in perspective of that account, which should influence how operations are visualized, f.e.
"alice voted 100% on bob/hello-there", but"alice/introduction received 50% vote from bob"- the latter would be formatted as"bob voted 50% on alice/introduction"when viewed from neutral perspective like block page; perspective tracking also allows indication of outgoing transactions f.e. with slightly different background color compared to incoming transactions - operation visualizers need a lot of fixing; couple weeks ago I've discussed many cases with jlachor, but I'm not sure if anything was finished; for example it should not be
"alice set recurrent transfer of 0.000 HBD, 5 executions every 26 hours to bob", but"alice canceled recurrent transfer #3 to bob"
hey @andablackwidow,
Thank you for the feedback and sharing your thoughts.
The problem with writing issues is that they are good if the potential solution requires investigation, discussion or documentation on why certain way of handling was chosen. But in cases like point 4 it is actually easier and faster if I make changes myself than to describe it for others to do. I'd have done that long ago if I had an environment ready where I could test such changes before proposing them (and the last time I did anything on front-end was 25 years ago). So next best thing is to stand on top of the dev who can show result of the changes locally before they are committed :o)
By the way, point 4 issue is only here because people that made those visualizers in the first place are not actually using Hive, so they are not familiar with fine details. I'm sure it does not apply to you.