Please help test new features in DVS 0.6.0 + Surprise GUI overhaul!

[abit]

The GUI could do with having an option to switch languages. Even if the translation is not there, then a call to help translate key elements of text could be.
See https://bitsharestalk.org/index.php?topic=13587.0

There is already an option to switch languages in the 'Preferences' menu (left pane).

[bytemaster]

I think the currency should "Default" to something other than blank when ever there is only one currency in the account.   

[bytemaster]

cn-members, thanks for your suggestions, most of them are in our plans and most of the bugs are known and some of them are already fixed.
the only thing I would disagree is #9 - Advanced is not going to be frequently accessed so it would be waste of space to have it as top level menu entry.

Perhaps put the advanced gear next to the network connection status?

[toast]

@arhag   I think you might have not copied the builder to the data directory when you did "builder_file_add_signature"? The file argument is misleading because it only writes there, but it reads from the latest.trx

I will change the builder interface to be much more clear for this

[valzav]

cn-members, thanks for your suggestions, most of them are in our plans and most of the bugs are known and some of them are already fixed.
the only thing I would disagree is #9 - Advanced is not going to be frequently accessed so it would be waste of space to have it as top level menu entry.

[wuyanren]

 

[cn-members]

We have collected the follwing suggestions from chinese community for DVS 0.6.1:

1. the chinese localization is incompleted:


2. the block explorer is for bts, not dvs

3. the issuer of user-issued assets are incorrect:


4. some layout in chinese is bad:


5. While doing transactions, there should be a place to select your favorite accounts:


6. The auto-completion of account names should be disabled by default to avoid transaction to wring accounts:


7. After transaction to a new account, the wallet should ask 'whether to add this account to my favorite?'

8. To avoid transaction of error unit, the default transaction unit should be changable in 'advanced' tab, and should be 'blank', not DVS/BTS by default.


9.The 'advanced' should be on the right side of account names, not hidden in menu, for easier access.

[cgafeng]

can't create uia from ui?
click the create button and nothing happen.

[fundomatic]

"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.



I went to client version 0.5.0. Imported keys with "wallet_import_keys_from_json" command, no problem.

Went back to 0.6.1. The client went unresponsive, eventually gave an error saying to restart with --rebuild-index or --resync-blockchain.

Restarted with no problems.

[arhag]

I tried to follow the voter-key guide and ran into some problems.

I set up the hot client and cold storage addresses according to the guide. My voter address is DVSCp2UnK2SYacZbrhuA1XCSnej9cGsLgqDW. My cold storage address is DVS2AgMjmUsKhUvgv9eRNkfKrqgtdadYrku8. I moved 100 DVS to that address creating a balance with an ID of DVS4sfmSA1jXb7swUkDRm323vhoqXxT69BGj.

Code: [Select]

(wallet closed) >>> blockchain_list_balances DVS4sfmSA1jXb7swUkDRm323vhoqXxT69BGj 1
[[
    "DVS4sfmSA1jXb7swUkDRm323vhoqXxT69BGj",{
      "condition": {
        "asset_id": 0,
        "slate_id": 14656263436760093262,
        "type": "withdraw_signature_type",
        "data": {
          "owner": "DVS2AgMjmUsKhUvgv9eRNkfKrqgtdadYrku8",
          "memo": null
        }
      },
      "balance": 10000000,
      "restricted_owner": null,
      "snapshot_info": null,
      "deposit_date": "2015-01-24T23:59:30",
      "last_update": "2015-01-24T23:59:30",
      "meta_data": null
    }
  ]
]

Then from my cold-storage wallet I do the following:

Code: [Select]

cold-storage (unlocked) >>> wallet_balance_set_vote_info DVS4sfmSA1jXb7swUkDRm323vhoqXxT69BGj DVSCp2UnK2SYacZbrhuA1XCSnej9cGsLgqDW vote_all false
{
  "transaction_record": {
    "index": 0,
    "record_id": "0000000000000000000000000000000000000000",
    "block_num": 0,
    "is_virtual": false,
    "is_confirmed": false,
    "is_market": false,
    "trx": {
      "expiration": "2015-01-25T05:19:39",
      "slate_id": null,
      "operations": [{
          "type": "update_balance_vote_op_type",
          "data": {
            "balance_id": "DVS4sfmSA1jXb7swUkDRm323vhoqXxT69BGj",
            "new_restricted_owner": "DVSCp2UnK2SYacZbrhuA1XCSnej9cGsLgqDW",
            "new_slate": 0
          }
        }
      ],
      "signatures": []
    },
    "ledger_entries": [{
        "from_account": null,
        "to_account": null,
        "amount": {
          "amount": 0,
          "asset_id": 0
        },
        "memo": "Set balance vote info",
        "memo_from_account": null
      }
    ],
    "fee": {
      "amount": 100000,
      "asset_id": 0
    },
    "created_time": "1970-01-01T00:00:00",
    "received_time": "1970-01-01T00:00:00",
    "extra_addresses": []
  },
  "required_signatures": [
    "DVS2AgMjmUsKhUvgv9eRNkfKrqgtdadYrku8"
  ],
  "outstanding_balances": [],
  "notices": []
}
The JSON output is also stored in the file "/home/arhag/.DevShares/wallets/trx/latest.trx". I copy that to builder.trx in the same directory.

I tried to use the command in the guide, but I had to set the broadcast flag to false because it is supposed to be a cold-storage environment meaning that I shouldn't have an internet connection to broadcast the transaction (I only want to sign it). However, as you will see it gave me an error:

Code: [Select]

cold-storage (unlocked) >>> wallet_builder_add_signature null false "/home/arhag/.DevShares/wallets/trx/builder.trx"
7 bad_cast_exception: Bad Cast
Invalid cast from type 'null_type' to Object
    {"type":"null_type"}
    th_a  variant.cpp:568 get_object

    {"command":"wallet_builder_add_signature"}
    th_a  cli.cpp:626 execute_command

So, I gave up on following the guide and tried to figure it out for myself. I used the "wallet_builder_file_add_signature" command instead:

Code: [Select]

cold-storage (unlocked) >>> wallet_builder_file_add_signature false
{
  "transaction_record": {
    "index": 0,
    "record_id": "588316c670f32541363755f28d515f484668bc4a",
    "block_num": 0,
    "is_virtual": false,
    "is_confirmed": false,
    "is_market": false,
    "trx": {
      "expiration": "2015-01-25T05:19:39",
      "slate_id": null,
      "operations": [{
          "type": "update_balance_vote_op_type",
          "data": {
            "balance_id": "DVS4sfmSA1jXb7swUkDRm323vhoqXxT69BGj",
            "new_restricted_owner": "DVSCp2UnK2SYacZbrhuA1XCSnej9cGsLgqDW",
            "new_slate": 0
          }
        }
      ],
      "signatures": [
        "207d264bb6f0a41d6455cd6b9f2d6c1942f87fe461997e46d9b2f0941d6a95e8726d4182dbf05b828e09d93457667622d162abd9448b0cf75b57ad59d94ba34bb0"
      ]
    },
    "ledger_entries": [{
        "from_account": null,
        "to_account": null,
        "amount": {
          "amount": 0,
          "asset_id": 0
        },
        "memo": "Set balance vote info",
        "memo_from_account": null
      }
    ],
    "fee": {
      "amount": 100000,
      "asset_id": 0
    },
    "created_time": "2015-01-25T04:26:01",
    "received_time": "2015-01-25T04:26:01",
    "extra_addresses": []
  },
  "required_signatures": [
    "DVS2AgMjmUsKhUvgv9eRNkfKrqgtdadYrku8"
  ],
  "outstanding_balances": [],
  "notices": []
}

This appears to have taken the transaction in latest.trx, added the signature, and wrote the result back in latest.trx. Here is the diff between builder.trx (the unsigned version of the transaction) and latest.trx (the signed version):

Code: [Select]

$ diff builder.trx latest.trx
4c4
<     "record_id": "0000000000000000000000000000000000000000",
---
>     "record_id": "588316c670f32541363755f28d515f484668bc4a",
21c21,23
<       "signatures": []
---
>       "signatures": [
>         "207d264bb6f0a41d6455cd6b9f2d6c1942f87fe461997e46d9b2f0941d6a95e8726d4182dbf05b828e09d93457667622d162abd9448b0cf75b57ad59d94ba34bb0"
>       ]
38,39c40,41
<     "created_time": "1970-01-01T00:00:00",
<     "received_time": "1970-01-01T00:00:00",
---
>     "created_time": "2015-01-25T04:26:01",
>     "received_time": "2015-01-25T04:26:01",

I then can copy this latest.trx to the machine where my hot client is running (in reality I'm just doing this on the same machine for convenience). Then after opening the regular hot wallet and unlocking it, I run the following command to broadcast this signed transaction from the internet-enabled machine where the hot client is running:

Code: [Select]

default (unlocked) >>> wallet_builder_file_add_signature true
Transaction was invalid!
default (unlocked) >>> wallet_builder_file_add_signature true{
  "transaction_record": {
    "index": 0,
    "record_id": "588316c670f32541363755f28d515f484668bc4a",
    "block_num": 0,
    "is_virtual": false,
    "is_confirmed": false,
    "is_market": false,
    "trx": {
      "expiration": "2015-01-25T05:19:39",
      "slate_id": null,
      "operations": [{
          "type": "update_balance_vote_op_type",
          "data": {
            "balance_id": "DVS4sfmSA1jXb7swUkDRm323vhoqXxT69BGj",
            "new_restricted_owner": "DVSCp2UnK2SYacZbrhuA1XCSnej9cGsLgqDW",
            "new_slate": 0
          }
        }
      ],
      "signatures": [
        "207d264bb6f0a41d6455cd6b9f2d6c1942f87fe461997e46d9b2f0941d6a95e8726d4182dbf05b828e09d93457667622d162abd9448b0cf75b57ad59d94ba34bb0"
      ]
    },
    "ledger_entries": [{
        "from_account": null,
        "to_account": null,
        "amount": {
          "amount": 0,
          "asset_id": 0
        },
        "memo": "Set balance vote info",
        "memo_from_account": null
      }
    ],
    "fee": {
      "amount": 100000,
      "asset_id": 0
    },
    "created_time": "2015-01-25T04:26:01",
    "received_time": "2015-01-25T04:26:01",
    "extra_addresses": []
  },
  "required_signatures": [
    "DVS2AgMjmUsKhUvgv9eRNkfKrqgtdadYrku8"
  ],
  "outstanding_balances": [],
  "notices": []
}

But as you can see it returns "Transaction was invalid!" as an error message. And sure enough I can see that the restricted_owner field for the balance has not been updated and is still null:

Code: [Select]

default (unlocked) >>> blockchain_list_balances DVS4sfmSA1jXb7swUkDRm323vhoqXxT69BGj 1
[[
    "DVS4sfmSA1jXb7swUkDRm323vhoqXxT69BGj",{
      "condition": {
        "asset_id": 0,
        "slate_id": 14656263436760093262,
        "type": "withdraw_signature_type",
        "data": {
          "owner": "DVS2AgMjmUsKhUvgv9eRNkfKrqgtdadYrku8",
          "memo": null
        }
      },
      "balance": 10000000,
      "restricted_owner": null,
      "snapshot_info": null,
      "deposit_date": "2015-01-24T23:59:30",
      "last_update": "2015-01-24T23:59:30",
      "meta_data": null
    }
  ]
]

I thought about trying the "blockchain_broadcast_transaction" command instead to see if that could work, but that requires me to input the escaped JSON into the CLI and doesn't allow me instead provide a path to a file holding the transaction JSON. Anyway, I don't even know if that would help if the transaction itself is not formed properly.

[arhag]

I haven't had the opportunity to build and try it out yet, but...

https://github.com/BitShares/bitshares/blob/develop/docs/multisig.md

Is there a RPC that allows you to see what a given transaction builder does? You shouldn't just sign any transaction someone gives you without first checking out how much of what asset it is pulling out of which multisigID and sending to which address. Is the only way to figure this stuff out right now to go through the raw transaction builder?

Also, a minor correction: I think you meant to write "angel" instead of "alice" in the "wallet_multisig_deposit" command.

https://github.com/BitShares/bitshares/blob/develop/docs/voter-key.md

Another potential minor correction: Shouldn't you be using "wallet_builder_file_add_signature" rather than "wallet_builder_add_signature" since the last argument is the path to the transaction builder and not the escaped transaction builder itself?


Also, in general I think the documentation would benefit from actual examples copied and pasted from the client with the real names, addresses, keys, etc. rather than your BTS...something... notation. It is especially odd because it appears you are putting the returned results of some of these commands on the same line as the command that was input by the user. Never mind that was just because you forgot to wrap them in code blocks which James Calfee fixed.

[davidpbrown]

The GUI could do with having an option to switch languages. Even if the translation is not there, then a call to help translate key elements of text could be.
See https://bitsharestalk.org/index.php?topic=13587.0

[bytemaster]

for many commands the console just sits there for a very long time.  I can't tell whether its doing something or not.

Just did an import keys from json and
Navigating back to my accounts, the robot picture displays but no other information in the header about the account does.  For all accounts.

then after some time, 2 minutes or more it all shows back up.  background process from the console must have been chugging away.  It would be nice if there were some indication of this.

Import keys for large wallets is very slow with no progress indicator.   That is a known issue.

[Xeldal]

for many commands the console just sits there for a very long time.  I can't tell whether its doing something or not.

Just did an import keys from json and
Navigating back to my accounts, the robot picture displays but no other information in the header about the account does.  For all accounts.

then after some time, 2 minutes or more it all shows back up.  background process from the console must have been chugging away.  It would be nice if there were some indication of this.

[fundomatic]

"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.

[toast]

"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.

[fundomatic]

"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.



[graffenwalder]

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

[CLains]

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.

[CLains]

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

[Xeldal]

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.

[CLains]

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

[davidpbrown]

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.

[bytemaster]

Under vote tab on accounts.  It will be moved back to top

[lzr1900]

where is the delegate ？？and blockexplore？

[lzr1900]

wrong link.
it should be:
https://github.com/BitShares/DevShares/releases

[Pheonike]

No more delegate listings?

[cass]

IMO voting should get a  top nav position / also Blocks

[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