Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!  (Read 1273 times)

0 Members and 1 Guest are viewing this topic.

Offline toast


DVS 0.6.1 is released and it sure is pretty!

https://github.com/BitShares/DevShares/releases

There are also new cold storage / multisig features which are not accessible via GUI. Please help us test!

https://github.com/BitShares/bitshares/blob/develop/docs/multisig.md
https://github.com/BitShares/bitshares/blob/develop/docs/voter-key.md
« Last Edit: January 22, 2015, 01:54:44 AM by toast »
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline cass

  • Hero Member
  • *****
  • Posts: 4328
  • /(┬.┬)\
    • View Profile
Re: Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!
« Reply #1 on: January 22, 2015, 01:25:49 AM »
IMO voting should get a  top nav position / also Blocks

█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█

Offline Pheonike

Re: Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!
« Reply #2 on: January 22, 2015, 01:43:27 AM »
No more delegate listings?

lzr1900

  • Guest

lzr1900

  • Guest
Re: Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!
« Reply #4 on: January 22, 2015, 01:53:34 AM »
where is the delegate ??and blockexplore?
« Last Edit: January 22, 2015, 01:55:26 AM by lzr1900 »

Offline bytemaster

Re: Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!
« Reply #5 on: January 22, 2015, 01:55:43 AM »
Under vote tab on accounts.  It will be moved back to top
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline davidpbrown

Re: Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!
« Reply #6 on: January 22, 2015, 02:44:04 PM »
I feel it needs another couple of iterations before I'll really like it. It's all in there somewhere at the moment.. and not intuitive enough.

A few thoughts then:

When waiting for a program to do what is necessary, it is nice to watch that progress. The block update wheel, is all very well but it's frustrating, not knowing why it's taking so long. I wonder a progress bar would be less frustrating?

The vote for selection drop-down seems out of place in the transfer dialogue and puts the user on edge; how might a transfer effect the voting and visa versa? You might tempt users to try to action a vote via transfer to themselves in error?

Vote options have always seemed confusing; it's unclear whether the total value of an account is equally spread among those chosen or if the total amount on an account weighs in support of each of those voted to. That is, if you vote for 2 delegates is your vote half the value of voting for 1?

I'd suggest change
"Vote for All" -> "Support all delegates"
"Vote None" -> "Remove support for delegates"
"Vote Random Subset" -> "Vote for a random subset"
"Vote as My Delegates Recommended" -> "Vote for selected delegates"

Lock perhaps should suggest "Unlocked" with a padlock unlocked that when clicked locks. Locked padlock at odds with GUI being open.

The detail could do with being formatted neatly.. too much is floating right. It seems some areas lack a table. So, one element is on the far left, one slight left of middle and another floating far right. That makes the page harder to read. In the [Accounts], for example, if you go maximise the browser, then NAME BALANCE REGISTERED are rather spread apart. Balances/EstYield in accounts and transfer detail perhaps could be on the left, where they are immediately in sight.

Should DVS; BTS be listed as assets?

Unclear what use is intended for this..
"Update Private Infos (stored locally):"
Infos -> Information
Perhaps needs by default a Notes field, if that is what it's for.
฿://1CBxm54Ah5hiYxiUtD7JGYRXykT5Z6ZuMc


Offline Xeldal

Re: Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!
« Reply #8 on: January 22, 2015, 03:19:03 PM »
I like DevShares ... As a test for upcoming things. It's brilliant.

BUT for now.. when i type in my pass it is "loading" infinitely, not sure if frozen or what. windows 7

I had this also.  I fixed it with --resync-blockchain.   That allowed me into the client anyways. I had problems syncing after that.  Had to remove 'chain' and 'peers.leveldb' folders to get it to sync.

Offline CLains

  • Hero Member
  • *****
  • Posts: 2606
    • View Profile
  • BTS: clains
Re: Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!
« Reply #9 on: January 22, 2015, 03:28:47 PM »
I like DevShares ... As a test for upcoming things. It's brilliant.

BUT for now.. when i type in my pass it is "loading" infinitely, not sure if frozen or what. windows 7

I had this also.  I fixed it with --resync-blockchain.   That allowed me into the client anyways. I had problems syncing after that.  Had to remove 'chain' and 'peers.leveldb' folders to get it to sync.

I tried going to "my account" via "file" and it asked me my pass again, then i got in, and now after I quit I can't go back in without it crashing. Then i realized there was a DevShares exe running, so I deleted it and ran DevShares again without reindexing and now it seems it's connecting normally and syncing up. Software magic

Offline CLains

  • Hero Member
  • *****
  • Posts: 2606
    • View Profile
  • BTS: clains
Re: Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!
« Reply #10 on: January 22, 2015, 03:50:52 PM »
I like it. Much better layout than the other one. Still needs some *life* though, it looks and feels like a skeleton interface, only the robot symbols save us from looking skinned to the bone. Currently the blue top-bar in "transfer" makes it the most delightful and easy-on-the-eyes page. It's all about making the interface as cognitively fluent as possible, decreasing the cost of absorbing information: Color coding, symbols and fonts are essential.

Maybe you are already know this, hard to know with no roadmap (?) but here it is anyway:

- Color all buttons
- Associate with all currencies a Symbol, like USD or the national flag color.
- Dashboard feels a bit bottom-heavy, as "accounts" is such a small piece of text compared to "Recent Transactions"
- When you click market pegged assets from the dashboard, you enter a new menu of detailed information about it instead of going straight to trading it - this should be reversed, i.e. the blue "trade x" should be "information about x" on the trading page.

Offline graffenwalder

Re: Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!
« Reply #11 on: January 22, 2015, 06:25:56 PM »
Still not able to claim my vested balances in DVS 6.1, no problem however with BTS 5.1.

I tried reimporting both the .dat and .json wallets. Both resulted in an immidiate crash.
GUI Windows

Offline fundomatic

  • Full Member
  • ***
  • Posts: 149
    • View Profile
Re: Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!
« Reply #12 on: January 22, 2015, 07:47:04 PM »
"client_version": "0.6.1" in Debian GNU/Linux jessie/sid

Cannot import keys (checked with "wallet_account_list_public_keys" command and there was no new keys)

>>> wallet_import_keys_from_json

gives output:

Code: [Select]
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
No errors were encountered, but there is currently no way to check if keys were decrypted using the correct password.




Offline toast

Re: Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!
« Reply #13 on: January 22, 2015, 07:49:01 PM »
"client_version": "0.6.1" in Debian GNU/Linux jessie/sid

Cannot import keys (checked with "wallet_account_list_public_keys" command and there was no new keys)

>>> wallet_import_keys_from_json

gives output:

Code: [Select]
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
No errors were encountered, but there is currently no way to check if keys were decrypted using the correct password.


Are you sure you're using the right password? Right now there's no way for the client to tell if it's a wrong password so it will fail silently.
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline fundomatic

  • Full Member
  • ***
  • Posts: 149
    • View Profile
Re: Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!
« Reply #14 on: January 22, 2015, 08:04:15 PM »
"client_version": "0.6.1" in Debian GNU/Linux jessie/sid

Cannot import keys (checked with "wallet_account_list_public_keys" command and there was no new keys)

>>> wallet_import_keys_from_json

gives output:

Code: [Select]
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
not skipping   
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
error, setting skip_me=true
not skipping   
error, setting skip_me=true
error, setting skip_me=true
not skipping   
not skipping   
No errors were encountered, but there is currently no way to check if keys were decrypted using the correct password.


Are you sure you're using the right password? Right now there's no way for the client to tell if it's a wrong password so it will fail silently.

I think I did have the correct password. I tried a few times. I tried with an old and fresh backups of my BitShares wallet (generated with "wallet_backup_create" command) as well as the ones generated automatically when new accounts are created. I tried backups of different BitShares wallets.

 

Google+