BitShares Forum

Main => General Discussion => Topic started by: svk on September 24, 2015, 03:36:34 pm

Title: Graphene GUI testing and feedback
Post by: svk on September 24, 2015, 03:36:34 pm
Please use this thread for feedback on the new GUI as well as issues related to graphene.bitshares.org (https://graphene.bitshares.org)

The GUI is available here:

https://github.com/cryptonomex/graphene-ui

If you notice a bug or anything that needs changing, please create an issue for it here if you can:

https://github.com/cryptonomex/graphene-ui/issues
Title: Re: Graphene GUI testing and feedback
Post by: jakub on September 24, 2015, 03:50:39 pm
I can access the https://graphene.bitshares.org (https://graphene.bitshares.org) without any problems using Chrome but in Firefox something is wrong:
- the Dashboard page has only account names but no further info
- explorer/blocks, explorer/witnesses etc shows empty screen
- also the list of markets on the markets page is empty
- but the head block counter in the bottom right corner seems to be working

I've already cleared the browser's cache.

Not sure if it is related  - I get this message in the browser's console:
Quote
17:41:55.900 The connection to wss://graphene.bitshares.org:8090/ was interrupted while the page was loading.1 app.js:39:0

I am on Windows 7.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on September 24, 2015, 04:00:34 pm
Could we have a version number somewhere in the GUI? Maybe somewhere in the app's footer, next to the "Graphene" label on the left.
So that we can be always be sure we are using the latest version after you deploy a bug fix.
Title: Re: Graphene GUI testing and feedback
Post by: mindphlux on September 24, 2015, 04:48:26 pm
Currently, when I log in I cannot see any balances - I just created a new account, but it's not sending me any balance, I'm seeing in the tx history:

"sent  to test003"

It should say "1000 CORE sent to test003" - right?
Title: Re: Graphene GUI testing and feedback
Post by: mindphlux on September 24, 2015, 04:49:12 pm
Also, the block explorer just shows me an empty page in chrome, it worked 2 days ago.
Title: Re: Graphene GUI testing and feedback
Post by: fav on September 24, 2015, 04:54:46 pm
Also, the block explorer just shows me an empty page in chrome, it worked 2 days ago.

strange. I use chrome/win7

(https://s-media-cache-ak0.pinimg.com/originals/6b/98/6c/6b986c5c5218cd89c7b012fa5626eb16.gif) (https://www.pinterest.com/pin/362750944964462486/)
Title: Re: Graphene GUI testing and feedback
Post by: jakub on September 24, 2015, 05:01:51 pm
Also, the block explorer just shows me an empty page in chrome, it worked 2 days ago.

strange. I use chrome/win7


It also works for me on chrome/win7. But this very issue I have on firefox/win7 - an empty page for block explorer.
Title: Re: Graphene GUI testing and feedback
Post by: mindphlux on September 24, 2015, 05:19:10 pm
It does not work for me on chrome. It used to work 2 days ago. I deleted cache, the local storage, created new accounts. No avail.

http://imgur.com/HteYMNM (http://imgur.com/HteYMNM)

Console Log:

Download the React DevTools for a better development experience: https://fb.me/react-devtools
app.js:39 Connecting...
app.js:39 connecting to wss://graphene.bitshares.org:8090
app.js:4 here:  r {path: "/dashboard", abortReason: null}
app.js:41 ChainStore Init
4app.js:41 ChainStore Init

It keeps repeating ChainStore init endlessly, maybe that's the issue

Title: Re: Graphene GUI testing and feedback
Post by: jakub on September 24, 2015, 05:33:00 pm
It keeps repeating ChainStore init endlessly, maybe that's the issue

The same syndrome of endlessly repeating "ChainStore init" happens on my Firefox.
Title: Re: Graphene GUI testing and feedback
Post by: svk on September 24, 2015, 05:37:42 pm
It does not work for me on chrome. It used to work 2 days ago. I deleted cache, the local storage, created new accounts. No avail.

http://imgur.com/HteYMNM (http://imgur.com/HteYMNM)

Console Log:

Download the React DevTools for a better development experience: https://fb.me/react-devtools
app.js:39 Connecting...
app.js:39 connecting to wss://graphene.bitshares.org:8090
app.js:4 here:  r {path: "/dashboard", abortReason: null}
app.js:41 ChainStore Init
4app.js:41 ChainStore Init

It keeps repeating ChainStore init endlessly, maybe that's the issue

This is the same isse as what jakub reported up top, I've got a fix ready just trying to figure out one more thing.

What timezone are you in and what does the footer tell you about the blockchain state? The bug here is related to date handling..
Title: Re: Graphene GUI testing and feedback
Post by: jakub on September 24, 2015, 05:53:36 pm
It does not work for me on chrome. It used to work 2 days ago. I deleted cache, the local storage, created new accounts. No avail.

http://imgur.com/HteYMNM (http://imgur.com/HteYMNM)

Console Log:

Download the React DevTools for a better development experience: https://fb.me/react-devtools
app.js:39 Connecting...
app.js:39 connecting to wss://graphene.bitshares.org:8090
app.js:4 here:  r {path: "/dashboard", abortReason: null}
app.js:41 ChainStore Init
4app.js:41 ChainStore Init

It keeps repeating ChainStore init endlessly, maybe that's the issue

This is the same isse as what jakub reported up top, I've got a fix ready just trying to figure out one more thing.

What timezone are you in and what does the footer tell you about the blockchain state? The bug here is related to date handling..

My Firefox footer shows "2 hours ago" but is continuously updating the head block number.
I'm in the UTC+01:00 time zone. (Current local time is 7.53 PM)
Title: Re: Graphene GUI testing and feedback
Post by: mindphlux on September 24, 2015, 05:59:48 pm
It does not work for me on chrome. It used to work 2 days ago. I deleted cache, the local storage, created new accounts. No avail.

http://imgur.com/HteYMNM (http://imgur.com/HteYMNM)

Console Log:

Download the React DevTools for a better development experience: https://fb.me/react-devtools
app.js:39 Connecting...
app.js:39 connecting to wss://graphene.bitshares.org:8090
app.js:4 here:  r {path: "/dashboard", abortReason: null}
app.js:41 ChainStore Init
4app.js:41 ChainStore Init

It keeps repeating ChainStore init endlessly, maybe that's the issue

This is the same isse as what jakub reported up top, I've got a fix ready just trying to figure out one more thing.

What timezone are you in and what does the footer tell you about the blockchain state? The bug here is related to date handling..

I'm GMT+2, Germany.. local time 19:58 block state said 4 minutes ago - I updated my local time.. you seem to comparing the local user's time to the block time without taking care of the timezone

EDIT: it seems to work now
Title: Re: Graphene GUI testing and feedback
Post by: svk on September 24, 2015, 06:00:10 pm
It does not work for me on chrome. It used to work 2 days ago. I deleted cache, the local storage, created new accounts. No avail.

http://imgur.com/HteYMNM (http://imgur.com/HteYMNM)

Console Log:

Download the React DevTools for a better development experience: https://fb.me/react-devtools
app.js:39 Connecting...
app.js:39 connecting to wss://graphene.bitshares.org:8090
app.js:4 here:  r {path: "/dashboard", abortReason: null}
app.js:41 ChainStore Init
4app.js:41 ChainStore Init

It keeps repeating ChainStore init endlessly, maybe that's the issue

This is the same isse as what jakub reported up top, I've got a fix ready just trying to figure out one more thing.

What timezone are you in and what does the footer tell you about the blockchain state? The bug here is related to date handling..

My Firefox footer shows "2 hours ago" but is continuously updating the head block number.
I'm in the UTC+01:00 time zone. (Current local time is 7.53 PM)

Yea, that's what I see as well in Firefox, it's related to how Firefox returns a Date object without taking into account timezones, unlike the other browsers. I've pushed a fix for the chainstore looping, but the dates displayed everywhere will still be wrong in Firefox, will need to look at that later.

https://github.com/cryptonomex/graphene-ui/issues/242
Title: Re: Graphene GUI testing and feedback
Post by: liondani on September 24, 2015, 07:10:43 pm
for marketing reason's use "average transaction time" instead of "average block time"
because the number will fall from 3sec to about 1.5sec   ;)
Title: Re: Graphene GUI testing and feedback
Post by: mindphlux on September 24, 2015, 07:14:47 pm
Also, maybe change tx/block to tx/seconds .. because we're marketing 100000 tx/second, not 100000 tx/block

Right?
Title: Re: Graphene GUI testing and feedback
Post by: Riverhead on September 24, 2015, 07:42:14 pm

When creating a new account if you hit enter after typing in the first password it goes to the dashbaord. The password works but it did not require verification.
Title: Re: Graphene GUI testing and feedback
Post by: valzav on September 24, 2015, 10:42:45 pm
New version is published, please check it out https://graphene.bitshares.org
Hope it resolves most of the issues discussed in this topic today.
Title: Re: Graphene GUI testing and feedback
Post by: Riverhead on September 24, 2015, 10:59:41 pm
New version is published, please check it out https://graphene.bitshares.org (https://graphene.bitshares.org)
Hope it resolves most of the issues discussed in this topic today.

Cool thing about the Graphene-ui is that you don't need to bring it down to upgrade. Just git pull and it'll refresh itself :).
Title: Re: Graphene GUI testing and feedback
Post by: liondani on September 24, 2015, 11:37:14 pm
a log-out close wallet button ?  near lock wallet button maybe....
Title: Re: Graphene GUI testing and feedback
Post by: jsidhu on September 25, 2015, 03:02:15 am
On my ipad i can create an account and login but nothing works in the dashboard.. No links working
Title: Re: Graphene GUI testing and feedback
Post by: alt on September 25, 2015, 03:16:43 am
On my ipad i can create an account and login but nothing works in the dashboard.. No links working
the browser must support html5, you can try chrome, it works good in my android phone.
Title: Re: Graphene GUI testing and feedback
Post by: Thom on September 25, 2015, 04:17:34 am
I'm writing a VPS install script for graphene nodes and I'm not sure of the best way to handle the boost libs.

I don't plan to build any of the binaries on the VPS. I compile boost on a dev system from source, then afterwards compress the entire boost source hierarchy into a tarball (it's big, yeah I know) and run the "b2 install" after decompressing on it the VPS which installs the shared libs. From what I can tell, that approach still does some compiling and / or linking at install time, but it doesn't take nearly as long as starting from scratch. Still it's minutes not seconds.

The script installs all of the same packages required to compile everything from scratch, even if they're all not needed (tho I think most if not all are).

Once boost is built from source and "b2 install" is run can the boost/boost_1_57_0 folder hierarchy be removed?

Does the witness_node and cli_wallet binaries require anything from the boost tree or only from the shared libraries (/usr/local/lib/libboost*.so.1.57.0)? What about the gui out of curiosity?

Of course all this wouldn't be necessary if a binary package for the version graphene requires were available via apt-get, or I knew how to produce a .deb file from the boost build tree.

The idea of this effort is to start with a brand new VPS, copy a script and a big tarball to it and when it is done executing it will be a configured, secured node for a witness, seed or backbone node. It installs monitoring, packages, users, tools, optimizes inode caching, swaping etc. So far the script is 125 lines long and it's 95% complete.
Title: Re: Graphene GUI testing and feedback
Post by: boombastic on September 25, 2015, 05:01:10 am
I borrowed some USD and the collateral position for USD is displayed correctly in my account overview page.  But how do I cover it?  I can only see a UPDATE button next to the position.
Title: Re: Graphene GUI testing and feedback
Post by: jsidhu on September 25, 2015, 05:50:22 am
On my ipad i can create an account and login but nothing works in the dashboard.. No links working
the browser must support html5, you can try chrome, it works good in my android phone.
Ios 8.1 and safari which scores 405 out of 555 on html5test.com

Maybe it uses the web crypto api, web workers or web rtc all of which are not supported.
Title: Re: Graphene GUI testing and feedback
Post by: alt on September 25, 2015, 06:09:39 am
maybe because of feature 'Beacon'
you can open the javescript console to see what's wrong.
But I prefer to use chrome, the  scores of  html5 test is 521.

On my ipad i can create an account and login but nothing works in the dashboard.. No links working
the browser must support html5, you can try chrome, it works good in my android phone.
Ios 8.1 and safari which scores 405 out of 555 on html5test.com

Maybe it uses the web crypto api, web workers or web rtc all of which are not supported.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on September 25, 2015, 07:32:20 am
@svk, would you post a list of features that are still unimplemented but will be before Oct 13th.
This way we will know if something is a bug or work-in-progress.

E.g. I guess the market history list or switching between different chart periods does not work because it's unimplemented but that's only me guessing.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on September 25, 2015, 07:38:46 am
I'm writing a VPS install script for graphene nodes and I'm not sure of the best way to handle the boost libs.

I don't plan to build any of the binaries on the VPS. I compile boost on a dev system from source, then afterwards compress the entire boost source hierarchy into a tarball (it's big, yeah I know) and run the "b2 install" after decompressing on it the VPS which installs the shared libs. From what I can tell, that approach still does some compiling and / or linking at install time, but it doesn't take nearly as long as starting from scratch. Still it's minutes not seconds.

The script installs all of the same packages required to compile everything from scratch, even if they're all not needed (tho I think most if not all are).

Once boost is built from source and "b2 install" is run can the boost/boost_1_57_0 folder hierarchy be removed?

Does the witness_node and cli_wallet binaries require anything from the boost tree or only from the shared libraries (/usr/local/lib/libboost*.so.1.57.0)? What about the gui out of curiosity?

Of course all this wouldn't be necessary if a binary package for the version graphene requires were available via apt-get, or I knew how to produce a .deb file from the boost build tree.

The idea of this effort is to start with a brand new VPS, copy a script and a big tarball to it and when it is done executing it will be a configured, secured node for a witness, seed or backbone node. It installs monitoring, packages, users, tools, optimizes inode caching, swaping etc. So far the script is 125 lines long and it's 95% complete.

@Thom, I guess you meant to post it in the other thread (https://bitsharestalk.org/index.php/topic,17962.0.html), right?
Title: Re: Graphene GUI testing and feedback
Post by: jakub on September 25, 2015, 09:18:34 am
Also, I wonder what is the idea behind being able to link other people's accounts and then have the option of trying to do some actions (e.g. trading, voting or updating collateral positions) on their behalf?
The system is clearly protected against such actions (you get the "failed to broadcast transaction" error message) but why does the GUI even allow attempting such actions?

Again, I guess these features are still work-in-progress but a clarification from the devs what the final goal is would be much appreciated.
Title: Re: Graphene GUI testing and feedback
Post by: svk on September 25, 2015, 09:44:44 am
@svk, would you post a list of features that are still unimplemented but will be before Oct 13th.
This way we will know if something is a bug or work-in-progress.

E.g. I guess the market history list or switching between different chart periods does not work because it's unimplemented but that's only me guessing.

Yea we're still waiting on a market history api call in the client, it gets populated with transactions that happen while you're in the exchange but for now we have no way to fetch the market history.

The charts also work in the frontend but the api call is broken, been waiting on them to fix it for a while now but I guess it's low priority.
Title: Re: Graphene GUI testing and feedback
Post by: svk on September 25, 2015, 09:48:30 am
Also, I wonder what is the idea behind being able to link other people's accounts and then have the option of trying to do some actions (e.g. trading, voting or updating collateral positions) on their behalf?
The system is clearly protected against such actions (you get the "failed to broadcast transaction" error message) but why does the GUI even allow attempting such actions?

Again, I guess these features are still work-in-progress but a clarification from the devs what the final goal is would be much appreciated.

You'll eventually be able to use the proposed transaction operation in order to propose a transaction for other accounts, but this is currently not implemented in the GUI. Basically you'll pay a higher than standard fee in order propose a transaction done by someone else, eg I can propose that you transfer 1 million BTS to me, and it will be up to you to accept or reject that transfer.

BM wanted to have all transaction operations visible everywhere like it is now but tbh I would've preferred restricting them and having a separate interface for proposed transactions, TBD I guess.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on September 25, 2015, 10:06:11 am
Also, I wonder what is the idea behind being able to link other people's accounts and then have the option of trying to do some actions (e.g. trading, voting or updating collateral positions) on their behalf?
The system is clearly protected against such actions (you get the "failed to broadcast transaction" error message) but why does the GUI even allow attempting such actions?

Again, I guess these features are still work-in-progress but a clarification from the devs what the final goal is would be much appreciated.

You'll eventually be able to use the proposed transaction operation in order to propose a transaction for other accounts, but this is currently not implemented in the GUI. Basically you'll pay a higher than standard fee in order propose a transaction done by someone else, eg I can propose that you transfer 1 million BTS to me, and it will be up to you to accept or reject that transfer.

BM wanted to have all transaction operations visible everywhere like it is now but tbh I would've preferred restricting them and having a separate interface for proposed transactions, TBD I guess.

So this makes sense for transferring money but why did you open it up for trading, voting or updating collateral positions in a similar way?
Surely you will not have a proposed transaction operation for voting, will you?

It looks like there is so much stuff to tackle and clean up in the GUI before Oct 13th. I am afraid there is no chance you can have it done and thoroughly tested in such a short time.

To be clear, the GUI looks awesome, it's real pleasure to play with it but there seems so much to be done and so little time left.
I know from experience as I've done a lot of GUI work in the past, unfortunately not in javascript so all I can do to help you guys is report bugs.

So if you could come up with a list of what is still unimplemented (but planned to be implemented before Oct 13th) then I could be much more helpful with bug reporting.
Otherwise I don't know if it's a bug or an unimplemented feature.
Title: Re: Graphene GUI testing and feedback
Post by: bytemaster on September 25, 2015, 01:06:24 pm
Also, I wonder what is the idea behind being able to link other people's accounts and then have the option of trying to do some actions (e.g. trading, voting or updating collateral positions) on their behalf?
The system is clearly protected against such actions (you get the "failed to broadcast transaction" error message) but why does the GUI even allow attempting such actions?

Again, I guess these features are still work-in-progress but a clarification from the devs what the final goal is would be much appreciated.

You'll eventually be able to use the proposed transaction operation in order to propose a transaction for other accounts, but this is currently not implemented in the GUI. Basically you'll pay a higher than standard fee in order propose a transaction done by someone else, eg I can propose that you transfer 1 million BTS to me, and it will be up to you to accept or reject that transfer.

BM wanted to have all transaction operations visible everywhere like it is now but tbh I would've preferred restricting them and having a separate interface for proposed transactions, TBD I guess.

So this makes sense for transferring money but why did you open it up for trading, voting or updating collateral positions in a similar way?
Surely you will not have a proposed transaction operation for voting, will you?

It looks like there is so much stuff to tackle and clean up in the GUI before Oct 13th. I am afraid there is no chance you can have it done and thoroughly tested in such a short time.

To be clear, the GUI looks awesome, it's real pleasure to play with it but there seems so much to be done and so little time left.
I know from experience as I've done a lot of GUI work in the past, unfortunately not in javascript so all I can do to help you guys is report bugs.

So if you could come up with a list of what is still unimplemented (but planned to be implemented before Oct 13th) then I could be much more helpful with bug reporting.
Otherwise I don't know if it's a bug or an unimplemented feature.

The reason you can propose to VOTE or place a market order, or anything else is because that is how multi-factor authentication is performed.   If I have a company account that requires all market orders be approved by CEO and CFO then the CFO would propose the transaction the the CEO would confirm it.   

Rather than have 2 ways to do everything, we provide one way to do it and then at the last second determine whether it needs to be a proposal or an actual transaction.
Title: Re: Graphene GUI testing and feedback
Post by: bytemaster on September 25, 2015, 01:14:14 pm
As far as testing goes here is the basic guideline for priority bugs:

1. Can you currently do something in 0.9.3 that you cannot do in the Graphene GUI?    If so then that is a bug that needs fixed.
2. Does the graphene GUI have a feature (such as a transfer page, market page) that when you use it generates an error when you don't think it should?

Priority TODO Items between now and Launch

1. Changing Wallet Password
2. Account Upgrade GUI
3. Worker Proposal Voting
4. Account Permissions

Items that will be added after launch:
1. Proposed Transactions
2. Withdraw Permissions
3. Asset Management
4. Whitelist Management

As it exists right now the current GUI feels better to me than 0.9.3 but probably has 2 months worth of work to expose the full feature set in the GUI.
Title: Re: Graphene GUI testing and feedback
Post by: clout on September 25, 2015, 01:45:57 pm
I cannot transfer bitassets. I get this error when I attempt to do so:

Code: [Select]
core_fee_paid <= fee_asset_dyn_data->fee_pool: Fee pool balance of '0 CORE' is less than the 9.99825 CORE required to convert 0.3652 CNY
Title: Re: Graphene GUI testing and feedback
Post by: clout on September 25, 2015, 01:48:42 pm
Also can we make integration of metaexchange and blocktrade a priority.
Title: Re: Graphene GUI testing and feedback
Post by: fav on September 25, 2015, 04:57:36 pm
can someone tell me, if I read https://graphene.bitshares.org/#/account/smartcoin/member-stats correctly?`

(http://i.imgur.com/ILPu8vZ.png)

As I understand it:

Basic Member - 50% < that's the cashback rate (https://bitshares.org/referral-program/ "These cashback referral rates, 50% and 80%, can be adjusted by the consensus of the BitShares Stakeholders at any time. Annual Accounts have their rates locked in for one year, while Lifetime Accounts have their rates locked in for life.)
Registrar - 50% < they paid for my account registration. but does that mean the registar gets actually 25%, since the cashback is set to 50% total?
Lifetime Referrer - 30% < affiliate  who signed me up. same as above, does that number indicate they get 30% of the 50% total cashback?
Referrer - 0% < why?
Title: Re: Graphene GUI testing and feedback
Post by: bytemaster on September 25, 2015, 05:27:12 pm
can someone tell me, if I read https://graphene.bitshares.org/#/account/smartcoin/member-stats correctly?`

(http://i.imgur.com/ILPu8vZ.png)

As I understand it:

Basic Member - 50% < that's the cashback rate (https://bitshares.org/referral-program/ "These cashback referral rates, 50% and 80%, can be adjusted by the consensus of the BitShares Stakeholders at any time. Annual Accounts have their rates locked in for one year, while Lifetime Accounts have their rates locked in for life.)
Registrar - 50% < they paid for my account registration. but does that mean the registar gets actually 25%, since the cashback is set to 50% total?
Lifetime Referrer - 30% < affiliate  who signed me up. same as above, does that number indicate they get 30% of the 50% total cashback?
Referrer - 0% < why?

Those numbers are not displayed properly at the moment.   The numbers should add to 100%, there is a stray 50% copy/paste bug and a MATH error on the page.   

Title: Re: Graphene GUI testing and feedback
Post by: bytemaster on September 25, 2015, 05:49:40 pm
I am attempting to document the calculations as the exist in the code right now.

Assuming you paid a fee of 100 BTS.
The network gets 20% off the top....     20 BTS => Network
The lifetime member gets their 30% off the top too...    30 BTS => LTM
This leaves 50 BTS to be divided among the Affiliate (referrer) and the Registrar (wallet provider)
The Registrar gets to specify the percentage to split with the Affiliate.   In the genesis account the Affiliate gets 0% which leaves all 50% going to the Registrar.

If you upgrade to a Annual Member then the referrer and registrar gets set to yourself until your membership expires.
If you upgrade to a Lifetime member then the Lifetime Referrer, Registrar, and Referrer get set to yourself.

Title: Re: Graphene GUI testing and feedback
Post by: fav on September 25, 2015, 06:07:59 pm
I am attempting to document the calculations as the exist in the code right now.

Assuming you paid a fee of 100 BTS.
The network gets 20% off the top....     20 BTS => Network
The lifetime member gets their 30% off the top to..    30 BTS => LTM
This leaves 50 BTS to be divided among the Affiliate (referrer) and the Registrar (wallet provider)
The Registrar gets to specify the percentage to split with the Affiliate.   In the genesis account the Affiliate gets 0% which leaves all 50% going to the Registrar.

If you upgrade to a Annual Member then the referrer and registrar gets set to yourself until your membership expires.
If you upgrade to a Lifetime member then the Lifetime Referrer, Registrar, and Referrer get set to yourself.

ah... got it, thanks!
Title: Re: Graphene GUI testing and feedback
Post by: jsidhu on September 25, 2015, 09:42:56 pm
web socket doesnt connect on my work computer because anything but port 80/443 is blocked externally...  so i see a blank grey page
Title: Re: Graphene GUI testing and feedback
Post by: bytemaster on September 25, 2015, 09:54:07 pm
web socket doesnt connect on my work computer because anything but port 80 is blocked externally...  so i see a blank grey page

I agree that we need a better failure mode for websocket failing to connect.
Title: Re: Graphene GUI testing and feedback
Post by: jsidhu on September 25, 2015, 09:57:57 pm
web socket doesnt connect on my work computer because anything but port 80 is blocked externally...  so i see a blank grey page

I agree that we need a better failure mode for websocket failing to connect.

Can you use port 80 for the web socket, since the website is using 443.
Title: Re: Graphene GUI testing and feedback
Post by: bytemaster on September 25, 2015, 10:25:43 pm
web socket doesnt connect on my work computer because anything but port 80 is blocked externally...  so i see a blank grey page

I agree that we need a better failure mode for websocket failing to connect.

Can you use port 80 for the web socket, since the website is using 443.

Not a bad idea.
Title: Re: Graphene GUI testing and feedback
Post by: jsidhu on September 25, 2015, 11:26:40 pm
web socket doesnt connect on my work computer because anything but port 80 is blocked externally...  so i see a blank grey page

I agree that we need a better failure mode for websocket failing to connect.

Can you use port 80 for the web socket, since the website is using 443.

Not a bad idea.

I guess you just have to confirm that browsers will run wss on port 80 because i did a quick search and people were asking if browsers would support wss on port 80 or not, although didn't see any bad responses. Give it a try, might be a quick fix!
Title: Re: Graphene GUI testing and feedback
Post by: abit on September 26, 2015, 01:10:28 am
As far as testing goes here is the basic guideline for priority bugs:

1. Can you currently do something in 0.9.3 that you cannot do in the Graphene GUI?    If so then that is a bug that needs fixed.
2. Does the graphene GUI have a feature (such as a transfer page, market page) that when you use it generates an error when you don't think it should?

Priority TODO Items between now and Launch

1. Changing Wallet Password
2. Account Upgrade GUI
3. Worker Proposal Voting
4. Account Permissions

Items that will be added after launch:
1. Proposed Transactions
2. Withdraw Permissions
3. Asset Management
4. Whitelist Management

As it exists right now the current GUI feels better to me than 0.9.3 but probably has 2 months worth of work to expose the full feature set in the GUI.
On the right side of page https://graphene.bitshares.org/#/exchange/trade/USD_CORE, market history is empty.
At the bottom, no chart.
See https://github.com/cryptonomex/graphene/issues/47#issuecomment-141631349
Title: Re: Graphene GUI testing and feedback
Post by: abit on September 26, 2015, 01:13:40 am
https://graphene.bitshares.org/ is down?
Title: Re: Graphene GUI testing and feedback
Post by: mf-tzo on September 26, 2015, 07:15:52 am
it works for me.
I am trying the GUI but to be honest I have no idea what I am doing..This is different from the current system and its confusing.
we will need instructions at some point.
for example:
what happens if i clear the cache and history?
everytime I open the webpage I am automatically on my account. How safe is that? i would expect i would need to put my password everytime.what happens if i forget unlocked my wallet?
what is borrow usd?
what is the collateral i put and why i should put more than needed?
what is update collateral position?
i am trying to understand my balances.I had 10k core and now i see 1k core and a debt of $1.1usd and $1.1usd. how is that even possible? i don't understand what i did to come to that..and how do i repay my debt?

Other than that the GUI is very nice experience to be able to do things without crashing at high speed so  +5%
Title: Re: Graphene GUI testing and feedback
Post by: xeroc on September 26, 2015, 09:53:14 am
what happens if i clear the cache and history?
You cannot easily remove the database that contains your keys ...
If you did so, you would either be required to reimport your accounts with wif
keys, or (if you created your accounts from within the new gui via brain key)
you would need to provide the brain key

Quote
everytime I open the webpage I am automatically on my account. How safe is that?
i would expect i would need to put my password everytime.what happens if i
forget unlocked my wallet?
The wallet will store your keys encrypted and will always ask you to provide the
passphrase if you close the browser window.

Quote
what is borrow usd?
In BitShares 0.9, what you did when "shorting" a bitUSD, you essentially made a
"short+sell". Now you can have this in two separated steps. so "shorting to
yourself" is MUCH easier now.

Quote
what is the collateral i put and why i should put more than needed?
For BitAssets 2.0, you can chose whatever collateral ratio you want > 100%. You
may however be margin called if your position has a low ratio.

Quote
what is update collateral position?
You can put more collateral in any of your short/borrow positions

Quote
i am trying to understand my balances.I had 10k core and now i see 1k core and a
debt of $1.1usd and $1.1usd. how is that even possible? i don't understand what
i did to come to that..and how do i repay my debt?
Seems you had a open short position. Not sure what happend to the other 9kCORE
.. maybe somethin went wrong on import. Rest assured that when you see the funds
in "balance" of BitShares 0.9, you will also be able to import them into BTS2.

Quote
Other than that the GUI is very nice experience to be able to do things without
crashing at high speed so  +5%
Abso..fu**ing..lutely!
Title: Re: Graphene GUI testing and feedback
Post by: mf-tzo on September 26, 2015, 11:23:34 am
xeroc to the rescue again! thank you very much! :)

I did not import any balance i just created a new account and show 10k CORE. I assume that these are not real CORE and are just for testing right? Is BTS2 going to be renamed CORE or Core is just a temporary testing name?

so if I understand correctly "update" collateral is I can add collateral. But how can I repay the bitsud I borrowed? In other words where is the "cover" button?

On the usdcore graph I see 17.9k core and 4.9 usd and borrow usd button. What are these numbers?

Also i tied to create a new account and i got this
fee_paying_account->is_lifetime_member():
Is this normal? I can not register another account?
And yet on the exchange tab under my name there is an arrow showing the new account i tried to create but when i click on it nothing happens

If I click to another account it has a button "LINK".What exactly does this do?

lol..it will take some time to learn the new staff so any heads up are appreciated..

Title: Re: Graphene GUI testing and feedback
Post by: xeroc on September 26, 2015, 11:49:36 am
xeroc to the rescue again! thank you very much! :)

I did not import any balance i just created a new account and show 10k CORE. I
assume that these are not real CORE and are just for testing right? Is BTS2
going to be renamed CORE or Core is just a temporary testing name?
Integrated faucet. And yes, CORE = TESTNET ... BTS=MAINnet..

Quote
so if I understand correctly "update" collateral is I can add collateral. But
how can I repay the bitsud I borrowed? In other words where is the "cover"
button?
Haven't checked. Maybe update also contains that. Can't tell .. yet :D

Quote
Also i tied to create a new account and i got this
fee_paying_account->is_lifetime_member():

Is this normal? I can not register another account?
You need to be a lifetime member (upgrade your account) to create new accounts
since you are then referrer of that new account.

Quote
If I click to another account it has a button "LINK".What exactly does this do?
It is just for convenience if you later want to use 'proposed transactions'
(i.e. multisig). YOu will not gain any rights .. you can see it as a
'watch-only' address/account

Quote
lol..it will take some time to learn the new staff so any heads up are appreciated..
I will focus on documentation next week (hopefully) .. maybe some one can make
some nice screenshots (and send the to fabian@bitshares.eu) so that I don't need
to do them :D

@cass is already preparing a flatdoc page for me. I'll focus on the

* Migration
* Exchange integration
* API

first and add stuff later. Hope things improve over time quickly.

Cheers
Title: Re: Graphene GUI testing and feedback
Post by: mf-tzo on September 26, 2015, 11:57:20 am
Quote
You need to be a lifetime member (upgrade your account) to create new accounts
since you are then referrer of that new account.
And yet on the exchange tab under my name there is an arrow showing the new account i tried to create but when i click on it nothing happens. I guess since I cannot register a name that name shouldn't appear there right?

On the usdcore graph I see 17.9k core and 4.9 usd below borrow usd button. What are these numbers?

Title: Re: Graphene GUI testing and feedback
Post by: boombastic on September 26, 2015, 12:01:54 pm
@mf-tzo when you create account in web wallet, faucet will send you 1000 CORE on testnet, not 10000.  I guess you might mistakenly thought it's 10k.  This is probably where the 'missing' 9k goes.  Anyway, you can check out the recent transactions to verify.
Title: Re: Graphene GUI testing and feedback
Post by: mf-tzo on September 26, 2015, 12:04:24 pm
@mf-tzo when you create account in web wallet, faucet will send you 1000 CORE on testnet, not 10000.  I guess you might mistakenly thought it's 10k.  This is probably where the 'missing' 9k goes.  Anyway, you can check out the recent transactions to verify.

lol..i am an idiot..
Title: Re: Graphene GUI testing and feedback
Post by: Thom on September 26, 2015, 02:52:50 pm
I'm writing a VPS install script for graphene nodes and I'm not sure of the best way to handle the boost libs.

I don't plan to build any of the binaries on the VPS. I compile boost on a dev system from source, then afterwards compress the entire boost source hierarchy into a tarball (it's big, yeah I know) and run the "b2 install" after decompressing on it the VPS which installs the shared libs. From what I can tell, that approach still does some compiling and / or linking at install time, but it doesn't take nearly as long as starting from scratch. Still it's minutes not seconds.

The script installs all of the same packages required to compile everything from scratch, even if they're all not needed (tho I think most if not all are).

Once boost is built from source and "b2 install" is run can the boost/boost_1_57_0 folder hierarchy be removed?

Does the witness_node and cli_wallet binaries require anything from the boost tree or only from the shared libraries (/usr/local/lib/libboost*.so.1.57.0)? What about the gui out of curiosity?

Of course all this wouldn't be necessary if a binary package for the version graphene requires were available via apt-get, or I knew how to produce a .deb file from the boost build tree.

The idea of this effort is to start with a brand new VPS, copy a script and a big tarball to it and when it is done executing it will be a configured, secured node for a witness, seed or backbone node. It installs monitoring, packages, users, tools, optimizes inode caching, swaping etc. So far the script is 125 lines long and it's 95% complete.

@Thom, I guess you meant to post it in the other thread (https://bitsharestalk.org/index.php/topic,17962.0.html), right?

Yeah, I see now this is for the GUI. Thanks for the reply jakub. I did ask if the boost libs are a run time requirement for the gui tho. I'm guessing the answer is no, boost is only for c++ code. Thought I would ask to be sure!
Title: Re: Graphene GUI testing and feedback
Post by: santaclause102 on September 26, 2015, 04:10:29 pm
Stupid question: Will the font and the color scheme still change?

I dont dislike the font in general just the parts where everything is capitalized under Explorer > Blocks
Title: Re: Graphene GUI testing and feedback
Post by: cass on September 26, 2015, 04:16:53 pm
Stupid question: Will the font and the color scheme still change?

I dont dislike the font in general just the parts where everything is capitalized under Explorer > Blocks

i will try to go over these parts next days ...
Title: Re: Graphene GUI testing and feedback
Post by: zhangweis on September 28, 2015, 02:16:03 pm
It works on Chrome in Ubuntu. But it fails on my chromebook.
I got something like below:

Download the React DevTools for a better development experience: https://fb.me/react-devtools
app.js:39 Connecting...
app.js:39 connecting to wss://graphene.bitshares.org:8090
app.js:39 WebSocket connection to 'wss://graphene.bitshares.org:8090/' failed: WebSocket is closed before the connection is established.
app.js:39 !!! WebSocket Error  wss://graphene.bitshares.org:8090
app.js:4 [App.jsx] ----- App.willTransitionTo error -----> CustomEvent {}bubbles: falsecancelBubble: falsecancelable: falsecurrentTarget: nulldefaultPrevented: falsedetail: undefinedeventPhase: 0path: Array[1]0: divlength: 1__proto__: Array[0]returnValue: truesrcElement: nulltarget: nulltimeStamp: 1443449565289type: "error"__proto__: CustomEvent(anonymous function) @ app.js:4r @ app.js:1(anonymous function) @ app.js:1e.exports @ app.js:1g.(anonymous function) @ app.js:2r @ app.js:2n @ app.js:2
app.js:4 [App.jsx] ----- App.willTransitionTo error -----> CustomEvent {}(anonymous function) @ app.js:4r @ app.js:1(anonymous function) @ app.js:1e.exports @ app.js:1g.(anonymous function) @ app.js:2r @ app.js:2n @ app.js:2
app.js:39 WebSocket connection to 'wss://graphene.bitshares.org:8090/' failed: WebSocket is closed before the connection is established.
app.js:39 !!! WebSocket Error  wss://graphene.bitshares.org:8090
app.js:39 WebSocket connection to 'wss://graphene.bitshares.org:8090/' failed: WebSocket is closed before the connection is established.
app.js:39 !!! WebSocket Error  wss://graphene.bitshares.org:8090
Title: Re: Graphene GUI testing and feedback
Post by: xeroc on September 28, 2015, 02:34:39 pm
app.js:39 WebSocket connection to 'wss://graphene.bitshares.org:8090/' failed: WebSocket is closed before the connection is established.
app.js:39 !!! WebSocket Error  wss://graphene.bitshares.org:8090
Seems your client has problems opening a connection the the websocket server ... is port 8090 accessible?
Title: Re: Graphene GUI testing and feedback
Post by: jsidhu on September 28, 2015, 06:40:33 pm
can you guys try to put it on port 80 quickly?
Title: Re: Graphene GUI testing and feedback
Post by: Method-X on September 29, 2015, 05:19:00 am
The GUI is fantastic! I have nothing to criticize whatsoever.
Title: Re: Graphene GUI testing and feedback
Post by: julian1 on September 29, 2015, 08:40:16 am
Had a play with this for the first time the other evening. The 3 second broadcast, confirmation turnaround is a superb step forward for ui responsiveness. Great work, and it's clear that React-js rocks.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on September 29, 2015, 09:51:33 am
I will flood the testnet at 9/29 0:10 UTC with 101 VPSs. Tips for VPS costs are more than welcome.  ;)

And I am happy to report that the GUI was fully responsive during the spamming test.
I did manage to cancel a market order and send a transfer during the flooding and both went smoothly.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on September 29, 2015, 10:24:36 am
But again the GUI is not working in Firefox.
Quote
12:22:05.739 The connection to wss://graphene.bitshares.org:8090/ was interrupted while the page was loading.1 app.js:39:0

Still works in Chrome though.
In both cases it's Windows 7.
Title: Re: Graphene GUI testing and feedback
Post by: zhangweis on September 29, 2015, 11:59:42 am
app.js:39 WebSocket connection to 'wss://graphene.bitshares.org:8090/' failed: WebSocket is closed before the connection is established.
app.js:39 !!! WebSocket Error  wss://graphene.bitshares.org:8090
Seems your client has problems opening a connection the the websocket server ... is port 8090 accessible?
Well, sometimes the websocket connection will fail. But when it makes the connection, it will show blocks and every other page well. But not for exchange page. It can list markets. But when I click USD vs CORE, it shows a blank page and stays blank for ever.
Hope the logs can help.

 ownload the React DevTools for a better development experience: https://fb.me/react-devtools
app.js:39 Connecting...
app.js:39 connecting to wss://graphene.bitshares.org:8090
app.js:4 db init done
app.js:41 ChainStore Init
app.js:41 synced and subscribed, chainstore ready
app.js:65 [Markets.jsx:24] ----- render -----> Object {markets: Object, baseAsset: Object, assets: Object, settings: Object}
app.js:65 defaultMarkets: [Object, Object, Object, Object, Object, Object, Object, Object]
app.js:65 [Markets.jsx:24] ----- render -----> Object {markets: Object, baseAsset: Object, assets: Object, settings: Object}
app.js:65 defaultMarkets: [Object, Object, Object, Object, Object, Object, Object, Object]
app.js:65 [Markets.jsx:24] ----- render -----> Object {markets: Object, baseAsset: Object, assets: Object, settings: Object}
app.js:65 defaultMarkets: [Object, Object, Object, Object, Object, Object, Object, Object]
vendors.js:1 Warning: Failed propType: Invalid prop `amount` of type `string` supplied to `t`, expected `number`. Check the render method of `r`.
app.js:65 [Markets.jsx:24] ----- render -----> Object {markets: Object, baseAsset: Object, assets: Object, settings: Object}
app.js:65 defaultMarkets: [Object, Object, Object, Object, Object, Object, Object, Object]0: Objectbase: "1.3.0"quote: "1.3.1"__proto__: Object1: Object2: Object3: Object4: Object5: Object6: Object7: Objectlength: 8__proto__: Array[0]
app.js:56 !account_name:  Object {id: "1.2.38993", balances: Object, history: Array[104]}
app.js:56 !account_name:  Object {id: "1.2.38993", balances: Object, history: Array[104]}
app.js:56 !account_name:  Object {id: "1.2.38993", balances: Object, history: Array[104]}
app.js:56 !account_name:  Object {id: "1.2.38993", balances: Object, history: Array[104]}
app.js:56 !account_name:  Object {id: "1.2.38993", balances: Object, history: Array[104]}
app.js:65 [Markets.jsx:24] ----- render -----> Object {markets: Object, baseAsset: Object, assets: Object, settings: Object}
app.js:65 defaultMarkets: [Object, Object, Object, Object, Object, Object, Object, Object]
app.js:65 [Markets.jsx:24] ----- render -----> Object {markets: Object, baseAsset: Object, assets: Object, settings: Object}
app.js:65 defaultMarkets: [Object, Object, Object, Object, Object, Object, Object, Object]
Title: Re: Graphene GUI testing and feedback
Post by: fav on September 29, 2015, 08:50:07 pm
exporting and importing the graphene wallet to my mobile was surprisingly easy and without a problem.

(http://ipfs.pics/pic.php?id=QmXJmADzWTRrC3otNbSM5aEMysrrRStHR3e7U5BC2AEZQh) (http://blog.smartcoin.pw)
https://plus.google.com/109380272839829509328/posts/gaCv5V1RwM3
Title: Re: Graphene GUI testing and feedback
Post by: DestBest on September 29, 2015, 10:43:38 pm
Very nice GUI!  +5%

Found a bug
Trying to create a new account name, I got:
  Failed to broadcast the transaction:
     fee_paying_account->is_lifetime_member():
Title: Re: Graphene GUI testing and feedback
Post by: yellowecho on September 29, 2015, 11:47:45 pm
Does anyone have a screenshot of the trading/exchange screen? I don't have time to import my wallet at the moment to check it out.
Title: Re: Graphene GUI testing and feedback
Post by: Method-X on September 30, 2015, 01:44:56 am
Does anyone have a screenshot of the trading/exchange screen? I don't have time to import my wallet at the moment to check it out.

Just create a new account. The base token is CORE not BTS so you can play around with it without any worry.
Title: Re: Graphene GUI testing and feedback
Post by: cass on September 30, 2015, 07:05:38 am
(http://i.imgur.com/Lgn78Rv.png)
(http://i.imgur.com/1sHN0uG.png)
(http://i.imgur.com/q7IWSWx.png)
Title: Re: Graphene GUI testing and feedback
Post by: sittingduck on September 30, 2015, 11:19:58 am

Very nice GUI!  +5%

Found a bug
Trying to create a new account name, I got:
  Failed to broadcast the transaction:
     fee_paying_account->is_lifetime_member():

Not a bug. Only lifetime members can create accounts. 


Sent from my iPhone using Tapatalk
Title: Re: Graphene GUI testing and feedback
Post by: jakub on September 30, 2015, 11:36:31 am

Very nice GUI!  +5%

Found a bug
Trying to create a new account name, I got:
  Failed to broadcast the transaction:
     fee_paying_account->is_lifetime_member():

Not a bug. Only lifetime members can create accounts.

I hope all these "Failed to broadcast the transaction" errors will be replaced with more detailed messages stating the reason for failure.
Otherwise it gives the impression that the system malfunctions.

Alternatively (and this would be even better), these situations could be prevented by disabling actions which the user is not supposed to perform.
Title: Re: Graphene GUI testing and feedback
Post by: DestBest on September 30, 2015, 03:12:14 pm

Very nice GUI!  +5%

Found a bug
Trying to create a new account name, I got:
  Failed to broadcast the transaction:
     fee_paying_account->is_lifetime_member():

Not a bug. Only lifetime members can create accounts. 

Thanks for clarifying this
Title: Re: Graphene GUI testing and feedback
Post by: wuyanren on October 01, 2015, 05:18:52 pm
explorer--Assets,Choose an asset to open. The page appears to be confusing.https://graphene.bitshares.org/#/asset/AUD
Title: Re: Graphene GUI testing and feedback
Post by: bytemaster on October 01, 2015, 06:02:48 pm
explorer--Assets,Choose an asset to open. The page appears to be confusing.https://graphene.bitshares.org/#/asset/AUD

You are correct, that particular page is under heavy development.   
Title: Re: Graphene GUI testing and feedback
Post by: clayop on October 01, 2015, 09:53:44 pm
Cannot load any exchanges (e.g.USD-CORE) in the current wallet.

edit: windows 10 / chrome
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 01, 2015, 10:14:41 pm
Purely cosmetic:  (non-essential)
The left side depth list on the exchange. It would be nice to have the ask/sell side on the top and bid/buy side on the bottom.

This makes more sense to me as the higher the price is, the higher on the page its listed.  Just like a chart. 

100
90
80
-----
50 spread
-----
30
20
10
0

Or have a button that flips it to your preference like Poloniex has for switching buy and sell book , left and right on the page. 
Title: Re: Graphene GUI testing and feedback
Post by: Akado on October 01, 2015, 10:28:08 pm
Can't access it on mozilla. First I wasn't able to do it at college and I thought it could be something about their browser but I can't access it from home either. I think I couldn't with Chromium too. Only thing I have is the dark grey background, nothing else.
Title: Re: Graphene GUI testing and feedback
Post by: tbone on October 02, 2015, 02:42:03 am
Purely cosmetic:  (non-essential)
The left side depth list on the exchange. It would be nice to have the ask/sell side on the top and bid/buy side on the bottom.

This makes more sense to me as the higher the price is, the higher on the page its listed.  Just like a chart. 

100
90
80
-----
50 spread
-----
30
20
10
0

Or have a button that flips it to your preference like Poloniex has for switching buy and sell book , left and right on the page. 

Good point.  And actually, this more than just cosmetic.  Having the order book reversed like this will leave the user feeling somewhat disoriented, which will lead to less frequent use.  So hopefully this can be modified. 

Another thing, I don't see a chart.  Is it there and I'm just missing it?

Title: Re: Graphene GUI testing and feedback
Post by: mike623317 on October 02, 2015, 03:19:50 am
Can't access it on mozilla. First I wasn't able to do it at college and I thought it could be something about their browser but I can't access it from home either. I think I couldn't with Chromium too. Only thing I have is the dark grey background, nothing else.

Same here too.
Title: Re: Graphene GUI testing and feedback
Post by: bitmarket on October 02, 2015, 10:17:56 pm
Feedback.

Great Job and overall much praise for the new wallet.  And now here is the useful(critical) stuff.

1. It is extremely overwhelming for new users with so many tabs and features etc.  I suggest a number of views that can be controlled by settings.

The basic and default view should be account name, history, and transfer and membership only.    It would be really neat if after they have say two transactions a pop up message appears ans says hey... it appears you have mastered transferring money to and from your account. May we take the training wheels of this puppy and introduce you to some advanced features? It is free. Yes/ No

Next view might be called trader.  It opens up the exchange tab.  and maybe permissions tab as well.
Final might be pro view with everything.   Users can choose from the settings menu at all times but we also prompt them after certain milestones.

2. When doing an exchange we show price and the quantity of one currency, but not the quantity of the other currency.  That would be nice.

3. I was confused as to what Pay was versus Transfer.

Anyway, overall very good.



Title: Re: Graphene GUI testing and feedback
Post by: cass on October 02, 2015, 11:46:50 pm
Feedback.

Great Job and overall much praise for the new wallet.  And now here is the useful(critical) stuff.

1. It is extremely overwhelming for new users with so many tabs and features etc.  I suggest a number of views that can be controlled by settings.

The basic and default view should be account name, history, and transfer and membership only.    It would be really neat if after they have say two transactions a pop up message appears ans says hey... it appears you have mastered transferring money to and from your account. May we take the training wheels of this puppy and introduce you to some advanced features? It is free. Yes/ No

Next view might be called trader.  It opens up the exchange tab.  and maybe permissions tab as well.
Final might be pro view with everything.   Users can choose from the settings menu at all times but we also prompt them after certain milestones.

2. When doing an exchange we show price and the quantity of one currency, but not the quantity of the other currency.  That would be nice.

3. I was confused as to what Pay was versus Transfer.

Anyway, overall very good.

i really like the idea of view switches… starter view / trader view … 

also maybe something similar to http://foundation.zurb.com/docs/components/joyride.html would be useful if user sign up first time, to get a guided tour through the GUI ... could this make sense?

Title: Re: Graphene GUI testing and feedback
Post by: wuyanren on October 03, 2015, 02:44:27 am
https://graphene.bitshares.org/ I can't visit this website, it's my problem.
Title: Re: Graphene GUI testing and feedback
Post by: gamey on October 03, 2015, 03:47:39 am

Is graphene.bitshares.org ok to test?  I was able to create an account but could never get past that tab to see anything else.

Actually I just revisited it. It had me logged in. I unlocked it and it is working. The first time I visited and created the account the wallet wasn't working..
Title: Re: Graphene GUI testing and feedback
Post by: jsidhu on October 03, 2015, 04:44:55 am
Feedback.

Great Job and overall much praise for the new wallet.  And now here is the useful(critical) stuff.

1. It is extremely overwhelming for new users with so many tabs and features etc.  I suggest a number of views that can be controlled by settings.

The basic and default view should be account name, history, and transfer and membership only.    It would be really neat if after they have say two transactions a pop up message appears ans says hey... it appears you have mastered transferring money to and from your account. May we take the training wheels of this puppy and introduce you to some advanced features? It is free. Yes/ No

Next view might be called trader.  It opens up the exchange tab.  and maybe permissions tab as well.
Final might be pro view with everything.   Users can choose from the settings menu at all times but we also prompt them after certain milestones.

2. When doing an exchange we show price and the quantity of one currency, but not the quantity of the other currency.  That would be nice.

3. I was confused as to what Pay was versus Transfer.

Anyway, overall very good.

i really like the idea of view switches… starter view / trader view …

also maybe something similar to http://foundation.zurb.com/docs/components/joyride.html would be useful if user sign up first time, to get a guided tour through the GUI ... could this make sense?
Great idea  +5%
Title: Re: Graphene GUI testing and feedback
Post by: betax on October 03, 2015, 08:13:16 am
Datetime issues (I guess) Windows 10 - Chrome
(http://snag.gy/mdPCX.jpg)

Also importing / exporting wallet backup from windows, says invalid format.
Importing / exporting keys from windows console is ok.

Title: Re: Graphene GUI testing and feedback
Post by: betax on October 03, 2015, 08:16:18 am
When importing balances, there is no option to import in a newly created account. Update: After importing the backup (bts2.0) wallet from Chrome to Firefox the option appears.
Importing balances also is not working due to datetime issue.  Importing the backup (bts2.0) wallet to Firefox has not fixed the issue.

Checked on Edge, and same issue, but it seems much slower.
Title: Re: Graphene GUI testing and feedback
Post by: cass on October 03, 2015, 10:19:36 am

Is graphene.bitshares.org ok to test?  I was able to create an account but could never get past that tab to see anything else.

Actually I just revisited it. It had me logged in. I unlocked it and it is working. The first time I visited and created the account the wallet wasn't working..

are u using Firefox or chrome to access the wallet on graphene.bitshares.org ?
Title: Re: Graphene GUI testing and feedback
Post by: clayop on October 03, 2015, 06:07:40 pm
After spamming, the web wallet freezes.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 03, 2015, 06:13:47 pm
After spamming, the web wallet freezes.
In /explorer/blocks? Are you spamming with the witness node thats used by the gui?
Title: Re: Graphene GUI testing and feedback
Post by: spartako on October 03, 2015, 06:17:54 pm
After spamming, the web wallet freezes.
In /explorer/blocks? Are you spamming with the witness node thats used by the gui?

The web wallet at https://graphene.bitshares.org freeze when we spam, it is down now
Title: Re: Graphene GUI testing and feedback
Post by: gamey on October 03, 2015, 06:18:43 pm

Is graphene.bitshares.org ok to test?  I was able to create an account but could never get past that tab to see anything else.

Actually I just revisited it. It had me logged in. I unlocked it and it is working. The first time I visited and created the account the wallet wasn't working..

are u using Firefox or chrome to access the wallet on graphene.bitshares.org ?

I was using chrome under linux.
Title: Re: Graphene GUI testing and feedback
Post by: mariano76 on October 05, 2015, 10:13:48 pm
I always use Chrome under Windows and works fine
Title: Re: Graphene GUI testing and feedback
Post by: liondani on October 06, 2015, 01:39:02 pm
I tried to change my wallet password at
settings > wallets > change password

after I give my initial password and the the new password (+the confirmation)
I see this message:

"Unable to change password: Error: This wallet does not support the change password feature."

when will we have this "future" ready?
Title: Re: Graphene GUI testing and feedback
Post by: CalabiYau on October 06, 2015, 03:37:22 pm
Trying to import accounts from the export .json file (win32):
 
Wallet freezes frequently, but after some waiting, the accounts are showing up.

(http://i.imgur.com/AQ4YZyC.png)
(http://i.imgur.com/yAVp8fh.png)
 
Zero balances (not in the chain ?)

Title: Re: Graphene GUI testing and feedback
Post by: xeroc on October 06, 2015, 04:05:49 pm
what is the size of your wallet.json file?
Title: Re: Graphene GUI testing and feedback
Post by: CalabiYau on October 06, 2015, 04:33:19 pm
what is the size of your wallet.json file?

5'437 KB
Title: Re: Graphene GUI testing and feedback
Post by: xeroc on October 06, 2015, 04:46:37 pm
what is the size of your wallet.json file?

5'437 KB
wow .. that explains a lot ..
just wait for the Wallet to complete .. no other way ..
Javascript is slow and it has to do all the ecc stuff for 5M of data ..
Title: Re: Graphene GUI testing and feedback
Post by: fav on October 06, 2015, 04:52:11 pm
what is the size of your wallet.json file?

5'437 KB

sounds more like the wrong backup json. did you backup via console or through menu?
Title: Re: Graphene GUI testing and feedback
Post by: CalabiYau on October 06, 2015, 05:17:07 pm
what is the size of your wallet.json file?

5'437 KB

sounds more like the wrong backup json. did you backup via console or through menu?

console: wallet_export _keys  in 0.9.3c. With "export wallet" in the GUI  I got a file that was not readable. Are there some balances supposed to show up ?
Title: Re: Graphene GUI testing and feedback
Post by: Akado on October 06, 2015, 07:14:24 pm
Can't access it on mozilla. First I wasn't able to do it at college and I thought it could be something about their browser but I can't access it from home either. I think I couldn't with Chromium too. Only thing I have is the dark grey background, nothing else.

It now seems to work after a little while. Got distracted by tv don't know if it was just 1 or 2 seconds or more.
Title: Re: Graphene GUI testing and feedback
Post by: Troglodactyl on October 07, 2015, 01:54:33 am
Can someone who can successfully build and run graphene-ui report their nodejs version?
Title: Re: Graphene GUI testing and feedback
Post by: xeroc on October 07, 2015, 07:10:56 am
Can someone who can successfully build and run graphene-ui report their nodejs version?
node -v
v4.1.1
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 07, 2015, 10:10:06 am
Before yesterday's upgrade we had open collateral positions listed in the account's overview page with an option to update them - now it's no longer there.
Is it an intended change or a bug?
Title: Re: Graphene GUI testing and feedback
Post by: bitacer on October 07, 2015, 11:24:17 am
On mac safari I am trying to create a backup , download button opens up another tab thats all it does, no file.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 07, 2015, 11:46:29 am
On mac safari I am trying to create a backup , download button opens up another tab thats all it does, no file.

I think this issue is already being sorted out by the devs
https://github.com/cryptonomex/graphene-ui/issues/282 (https://github.com/cryptonomex/graphene-ui/issues/282)
Title: Re: Graphene GUI testing and feedback
Post by: liondani on October 07, 2015, 11:47:52 am
I tried to change my wallet password at
settings > wallets > change password

after I give my initial password and the the new password (+the confirmation)
I see this message:

"Unable to change password: Error: This wallet does not support the change password feature."

when will we have this "future" ready?

any update about the password change future?
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 07, 2015, 11:53:50 am
I tried to change my wallet password at
settings > wallets > change password

after I give my initial password and the the new password (+the confirmation)
I see this message:

"Unable to change password: Error: This wallet does not support the change password feature."

when will we have this "future" ready?

any update about the password change future?

You mean the online wallet? https://graphene.bitshares.org (https://graphene.bitshares.org)
For me the change password feature works without any issues, both in Chrome and Firefox (WIn 7)
Title: Re: Graphene GUI testing and feedback
Post by: liondani on October 07, 2015, 12:18:11 pm
Code: [Select]
Application initialization issues


Websocket Connection Status: Connected

Retry

thats what I get on the web wallet now, and it stuck's there after refreshing
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 07, 2015, 01:30:36 pm
For me https://graphene.bitshares.org (https://graphene.bitshares.org) stopped working in Firefox (Win 7) with this error:
Code: [Select]
The connection to wss://graphene.bitshares.org/ws/ was interrupted while the page was loading.
But still works fine in Chrome.

As I said before, it would really help with the testing efforts if we had a version number hard-coded somewhere in the GUI so that we could know if it's been recently upgraded on the server.
Otherwise it's hard to know if current problems are related to a new version being pushed on the server side.
Title: Re: Graphene GUI testing and feedback
Post by: fav on October 07, 2015, 01:52:35 pm
For me https://graphene.bitshares.org (https://graphene.bitshares.org) stopped working in Firefox (Win 7) with this error:
Code: [Select]
The connection to wss://graphene.bitshares.org/ws/ was interrupted while the page was loading.
But still works fine in Chrome.

As I said before, it would really help with the testing efforts if we had a version number hard-coded somewhere in the GUI so that we could know if it's been recently upgraded on the server.
Otherwise it's hard to know if current problems are related to a new version being pushed on the server side.

clean your cache maybe? that wss error was yesterday and that's when the node was down... I think firefox has a "hard refresh" option too?
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 07, 2015, 02:18:57 pm
For me https://graphene.bitshares.org (https://graphene.bitshares.org) stopped working in Firefox (Win 7) with this error:
Code: [Select]
The connection to wss://graphene.bitshares.org/ws/ was interrupted while the page was loading.
But still works fine in Chrome.

As I said before, it would really help with the testing efforts if we had a version number hard-coded somewhere in the GUI so that we could know if it's been recently upgraded on the server.
Otherwise it's hard to know if current problems are related to a new version being pushed on the server side.

clean your cache maybe? that wss error was yesterday and that's when the node was down... I think firefox has a "hard refresh" option too?

Clearing cache doesn't help. I guess there has been an upgrade on the server side which broke it.
Can anyone confirm this? Firefox on Win 7.

EDIT: I don't know what was the reason, but it works now.
Title: Re: Graphene GUI testing and feedback
Post by: cass on October 07, 2015, 02:44:46 pm
As I said before, it would really help with the testing efforts if we had a version number hard-coded somewhere in the GUI so that we could know if it's been recently upgraded on the server.
Otherwise it's hard to know if current problems are related to a new version being pushed on the server side.

THIS pls  +5%
Title: Re: Graphene GUI testing and feedback
Post by: bitacer on October 07, 2015, 06:01:24 pm
- Can the web wallet be set to logout after a certain period of time ?
- Responsive theme for web wallet could be nice with mobile devices.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 07, 2015, 06:06:18 pm
- Can the web wallet be set to logout after a certain period of time?
It's a planned feature:
https://github.com/cryptonomex/graphene-ui/issues/265 (https://github.com/cryptonomex/graphene-ui/issues/265)
Title: Re: Graphene GUI testing and feedback
Post by: clout on October 07, 2015, 06:08:37 pm
I'm trying to transfer funds from a collateral account however the GUI says that it is not my account and does not allow me to execute the transfer.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 07, 2015, 10:04:55 pm
The Recent Activity list in the Overview section should be paginated.
Or it should show the most recent 10-15 transactions and there should be a LOAD MORE button.

Otherwise accounts with a large number of transactions load very slowly, e.g. clayoptest4
https://graphene.bitshares.org/#/account/clayoptest4/overview
Title: Re: Graphene GUI testing and feedback
Post by: bytemaster on October 07, 2015, 10:32:46 pm
The Recent Activity list in the Overview section should be paginated.
Or it should show the most recent 10-15 transactions and there should be a LOAD MORE button.

Otherwise accounts with a large number of transactions load very slowly, e.g. clayoptest4
https://graphene.bitshares.org/#/account/clayoptest4/overview

Technically it will only load slowly if you had your browser open while he was flooding.   If you hit reload on the page it will be very quick.

You are right though that it does not currently give you the option to "load more".
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 07, 2015, 10:41:49 pm
The Recent Activity list in the Overview section should be paginated.
Or it should show the most recent 10-15 transactions and there should be a LOAD MORE button.

Otherwise accounts with a large number of transactions load very slowly, e.g. clayoptest4
https://graphene.bitshares.org/#/account/clayoptest4/overview

Technically it will only load slowly if you had your browser open while he was flooding.   If you hit reload on the page it will be very quick.

You are right though that it does not currently give you the option to "load more".

I think the option to load more is the easiest solution and at the same time the most appropriate from the UX perspective.
In 99% of cases you are interested in only the most recent transactions and the entire history only produces information overflow for the user.
Title: Re: Graphene GUI testing and feedback
Post by: liondani on October 07, 2015, 10:54:09 pm
I think the option to load more is the easiest solution and at the same time the most appropriate from the UX perspective.
In 99% of cases you are interested in only the most recent transactions and the entire history only produces information overflow for the user.

 +5%
Title: Re: Graphene GUI testing and feedback
Post by: Troglodactyl on October 08, 2015, 12:15:26 am
Can someone who can successfully build and run graphene-ui report their nodejs version?
node -v
v4.1.1

Thanks.  I'm on v4.1.2 and I'm getting this on "npm install":

Code: [Select]
In file included from ../src/contextify.cc:3:0:
../node_modules/nan/nan.h:261:25: error: redefinition of ‘template<class T> v8::Local<T> _NanEnsureLocal(v8::Local<T>)’
 NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Local<T> val) {
                         ^
../node_modules/nan/nan.h:256:25: note: ‘template<class T> v8::Local<T> _NanEnsureLocal(v8::Handle<T>)’ previously declared here
 NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Handle<T> val) {
                         ^
../node_modules/nan/nan.h:661:13: error: ‘node::smalloc’ has not been declared
     , node::smalloc::FreeCallback callback
             ^
../node_modules/nan/nan.h:661:35: error: expected ‘,’ or ‘...’ before ‘callback’
     , node::smalloc::FreeCallback callback
                                   ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(char*, size_t, int)’:
../node_modules/nan/nan.h:665:50: error: ‘callback’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                  ^
../node_modules/nan/nan.h:665:60: error: ‘hint’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                            ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(const char*, uint32_t)’:
../node_modules/nan/nan.h:672:67: error: no matching function for call to ‘New(v8::Isolate*, const char*&, uint32_t&)’
     return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);

I've traced it to this issue with contextify: https://github.com/brianmcd/contextify/issues/180

But I have no idea why it's working for you.  Is this an issue for anyone else?  Does anyone have any ideas?
Title: Re: Graphene GUI testing and feedback
Post by: jamesc on October 08, 2015, 12:42:55 am
I tried to change my wallet password at
settings > wallets > change password

after I give my initial password and the the new password (+the confirmation)
I see this message:

"Unable to change password: Error: This wallet does not support the change password feature."

when will we have this "future" ready?

Create a new wallet..   test net wallets are always backwards compatible

This was added, old wallets did not have this: "encryption_key is the global encryption key (does not change even if the password changes)"
Title: Re: Graphene GUI testing and feedback
Post by: rnglab on October 08, 2015, 07:37:39 am
 is Graphene GUI going to fetch help content from github/somwhere else or will it reside on graphene-u itself?

 I want to implement continual internationalization for help pages on Transifex as with /web/app/assets/locales/ (source language file is automatically updated once a day if there's any change in locale-en.js on github, and translators notified).

Just asking because automating push/pulls for markdown files between Transifex and github when translations are completed or sources modified requires a server to talk with Transifex and Github api, and webhooks on both sides. I'm willing to do that,  just need to know how will this content be managed by graphene-ui to know if I can start right now or better wait if it's a temporary solution.

Thanks!

https://www.transifex.com/bitshares/graphene-ui/dashboard/ (https://www.transifex.com/bitshares/graphene-ui/dashboard/)
Title: Re: Graphene GUI testing and feedback
Post by: jamesc on October 08, 2015, 02:29:03 pm
is Graphene GUI going to fetch help content from github/somwhere else or will it reside on graphene-u itself?

 I want to implement continual internationalization for help pages on Transifex as with /web/app/assets/locales/ (source language file is automatically updated once a day if there's any change in locale-en.js on github, and translators notified).

Just asking because automating push/pulls for markdown files between Transifex and github when translations are completed or sources modified requires a server to talk with Transifex and Github api, and webhooks on both sides. I'm willing to do that,  just need to know how will this content be managed by graphene-ui to know if I can start right now or better wait if it's a temporary solution.

Thanks!

https://www.transifex.com/bitshares/graphene-ui/dashboard/ (https://www.transifex.com/bitshares/graphene-ui/dashboard/)

You could send your pull requests back to the graphene-ui for the next release.  We don't need any live help file loading.  It might be a good idea to have a release schedule so this can be timed so the translations are in on time.  Maybe valzav can tell us about the help files.  Your already found the functional locale files.
Title: Re: Graphene GUI testing and feedback
Post by: valzav on October 08, 2015, 02:55:50 pm
Help files are in help/ folder of graphene-ui repo. They are static files so no need to fetch them on the fly.
We are using markdown (.md files) so it's very easy to edit them - you don't even need to know html. Also github shows .md files prerendered - this makes it very easy to browse and edit them. Here is an example https://github.com/cryptonomex/graphene-ui/blob/master/help/en/index.md
I'm very doubtful that external translation tool like Transifex would be helpful here - it just adds complexity..
Title: Re: Graphene GUI testing and feedback
Post by: rnglab on October 08, 2015, 04:38:27 pm
Help files are in help/ folder of graphene-ui repo. They are static files so no need to fetch them on the fly.
We are using markdown (.md files) so it's very easy to edit them - you don't even need to know html. Also github shows .md files prerendered - this makes it very easy to browse and edit them. Here is an example https://github.com/cryptonomex/graphene-ui/blob/master/help/en/index.md
I'm very doubtful that external translation tool like Transifex would be helpful here - it just adds complexity..

As I see it, once the complex part is ready, the benefits of having all the essential content focused on a single platform that is designed for collaborative continuous internationalization can be huge.  A worker proposal could fund Language Coordinators for the most relevant languages and the value added to the network could be very significant. Ecosystem and it's contents will be constantly growing and changing.

It's already implemented for bitshares.org and docs.bitshares.eu. Also for non github users it's being pretty easy and motivating to translate graphene-ui on transifex. We already have Turkish, Italian and Spanish volunteers working on it pretty fast, with no need to compare or merge locale files to match keys or having to learn github at all. When locale-en.js is committed, changes are pulled from raw github, applied on transifex and translators notified. If a finished translation is not on github or it's incomplete there, I'll manually make a push request.

I like the approach of taking graphene-ui help content directly from github markdown pages.
 In that case, it wouldn't be problematic to automate pushes from pages translated and reviewed, nor pulling pages from github when they change, as there's no code interaction beyond links. We have a set of rules  to define if and how strings can be translated.

It's not so complex either: http://docs.transifex.com/integrations/github/ (http://docs.transifex.com/integrations/github/)

If you agree I can implement that integration on a fork so you can decide if it is worth. My goal is not to interfere in the development process at all. On the contrary i'd like to achieve an integration that let devs released from localization process, and at the same time making this process simpler and unified at one place.





Title: Re: Graphene GUI testing and feedback
Post by: clout on October 08, 2015, 04:50:40 pm
I'm trying to transfer funds from a collateral account however the GUI says that it is not my account and does not allow me to execute the transfer.

Is no one else having this issue?
Title: Re: Graphene GUI testing and feedback
Post by: fav on October 08, 2015, 07:49:44 pm
Available: 0,0126 (USD)

however, you can't send 0,01 bitusd, but 0.01 - semantics are wrong

edit: you can't use comma at all
Title: Re: Graphene GUI testing and feedback
Post by: fav on October 08, 2015, 07:54:32 pm
got the same as https://bitsharestalk.org/index.php/topic,18840.0.html

(http://i.imgur.com/LK9z5Mg.png)
Title: Re: Graphene GUI testing and feedback
Post by: bytemaster on October 08, 2015, 10:29:10 pm
got the same as https://bitsharestalk.org/index.php/topic,18840.0.html

(http://i.imgur.com/LK9z5Mg.png)

The fee pool needs to be funded with some CORE in order for fees to be paid.   
Title: Re: Graphene GUI testing and feedback
Post by: bytemaster on October 08, 2015, 10:32:35 pm
I have just funded the fee pool for USD.
Title: Re: Graphene GUI testing and feedback
Post by: Troglodactyl on October 09, 2015, 12:16:26 am
Can someone who can successfully build and run graphene-ui report their nodejs version?
node -v
v4.1.1

Thanks.  I'm on v4.1.2 and I'm getting this on "npm install":

Code: [Select]
In file included from ../src/contextify.cc:3:0:
../node_modules/nan/nan.h:261:25: error: redefinition of ‘template<class T> v8::Local<T> _NanEnsureLocal(v8::Local<T>)’
 NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Local<T> val) {
                         ^
../node_modules/nan/nan.h:256:25: note: ‘template<class T> v8::Local<T> _NanEnsureLocal(v8::Handle<T>)’ previously declared here
 NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Handle<T> val) {
                         ^
../node_modules/nan/nan.h:661:13: error: ‘node::smalloc’ has not been declared
     , node::smalloc::FreeCallback callback
             ^
../node_modules/nan/nan.h:661:35: error: expected ‘,’ or ‘...’ before ‘callback’
     , node::smalloc::FreeCallback callback
                                   ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(char*, size_t, int)’:
../node_modules/nan/nan.h:665:50: error: ‘callback’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                  ^
../node_modules/nan/nan.h:665:60: error: ‘hint’ was not declared in this scope
         v8::Isolate::GetCurrent(), data, length, callback, hint);
                                                            ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Object> NanNewBufferHandle(const char*, uint32_t)’:
../node_modules/nan/nan.h:672:67: error: no matching function for call to ‘New(v8::Isolate*, const char*&, uint32_t&)’
     return node::Buffer::New(v8::Isolate::GetCurrent(), data, size);

I've traced it to this issue with contextify: https://github.com/brianmcd/contextify/issues/180

But I have no idea why it's working for you.  Is this an issue for anyone else?  Does anyone have any ideas?

Has anyone else done a fresh clone and build on NodeJS > 4 recently?
Title: Re: Graphene GUI testing and feedback
Post by: fav on October 09, 2015, 04:49:57 am
I have just funded the fee pool for USD.

can this happen in the live net too? why can't I pay the fees out of my pocket?
Title: Re: Graphene GUI testing and feedback
Post by: xeroc on October 09, 2015, 07:04:28 am
I have just funded the fee pool for USD.
How would the fee pool be funded in general? Are trading "fees" distributed into the fee fund (for MPA)?
Can a wallet feature be added that pays the fees in CORE/BTS if the fee pool is empty?
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 09, 2015, 05:28:58 pm
We have some issues regarding the GUI in Firefox 41.0.1 on Windows 7.
https://github.com/cryptonomex/graphene-ui/issues/285 (https://github.com/cryptonomex/graphene-ui/issues/285)

Could someone confirm the error I get in the js console when loading the URL https://graphene.bitshares.org in Firefox 41.0.1 on Windows 7?

This is the error I get:
Code: [Select]
The connection to wss://graphene.bitshares.org:8090/ was interrupted while the page was loading.
Title: Re: Graphene GUI testing and feedback
Post by: bytemaster on October 09, 2015, 07:06:27 pm
I have just funded the fee pool for USD.
How would the fee pool be funded in general? Are trading "fees" distributed into the fee fund (for MPA)?
Can a wallet feature be added that pays the fees in CORE/BTS if the fee pool is empty?

Yes, the wallet should eventually support paying the fees directly.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 09, 2015, 08:18:23 pm
We have some issues regarding the GUI in Firefox 41.0.1 on Windows 7.
https://github.com/cryptonomex/graphene-ui/issues/285 (https://github.com/cryptonomex/graphene-ui/issues/285)

Could someone confirm the error I get in the js console when loading the URL https://graphene.bitshares.org in Firefox 41.0.1 on Windows 7?

This is the error I get:
Code: [Select]
The connection to wss://graphene.bitshares.org:8090/ was interrupted while the page was loading.

This is quite urgent as the devs are trying to sort it out right now. Anyone with Win 7 and Firefox please give it a go.
Title: Re: Graphene GUI testing and feedback
Post by: Troglodactyl on October 09, 2015, 10:46:08 pm
We have some issues regarding the GUI in Firefox 41.0.1 on Windows 7.
https://github.com/cryptonomex/graphene-ui/issues/285 (https://github.com/cryptonomex/graphene-ui/issues/285)

Could someone confirm the error I get in the js console when loading the URL https://graphene.bitshares.org in Firefox 41.0.1 on Windows 7?

This is the error I get:
Code: [Select]
The connection to wss://graphene.bitshares.org:8090/ was interrupted while the page was loading.

This is quite urgent as the devs are trying to sort it out right now. Anyone with Win 7 and Firefox please give it a go.

I'm getting that error on Arch Linux with Firefox 41.0.1:

Code: [Select]
The connection to wss://graphene.bitshares.org/ws/ was interrupted while the page was loading. app.js:6:0
"connecting to wss://graphene.bitshares.org:443/ws/" app.js:6:23319
mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create vendors.js:19:30281
Title: Re: Graphene GUI testing and feedback
Post by: Pheonike on October 09, 2015, 11:05:12 pm

When changing collateral amount in the exchange, there should be an option to type in an exact amount and not just using the slider.
Title: Re: Graphene GUI testing and feedback
Post by: CalabiYau on October 10, 2015, 06:53:20 am
We have some issues regarding the GUI in Firefox 41.0.1 on Windows 7.
https://github.com/cryptonomex/graphene-ui/issues/285 (https://github.com/cryptonomex/graphene-ui/issues/285)

Could someone confirm the error I get in the js console when loading the URL https://graphene.bitshares.org in Firefox 41.0.1 on Windows 7?

This is the error I get:
Code: [Select]
The connection to wss://graphene.bitshares.org:8090/ was interrupted while the page was loading.

This is quite urgent as the devs are trying to sort it out right now. Anyone with Win 7 and Firefox please give it a go.

Firefox 41.0.1 on Win7 / 32  -  no such issues here (doing more testing if node in sync again)
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 10, 2015, 12:18:27 pm

When changing collateral amount in the exchange, there should be an option to type in an exact amount and not just using the slider.

There is, you can do it either way, slider or Collateral input field. Or is it not working for you?
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 10, 2015, 01:50:42 pm
We have some issues regarding the GUI in Firefox 41.0.1 on Windows 7.
https://github.com/cryptonomex/graphene-ui/issues/285 (https://github.com/cryptonomex/graphene-ui/issues/285)

Could someone confirm the error I get in the js console when loading the URL https://graphene.bitshares.org in Firefox 41.0.1 on Windows 7?

This is the error I get:
Code: [Select]
The connection to wss://graphene.bitshares.org:8090/ was interrupted while the page was loading.

This is quite urgent as the devs are trying to sort it out right now. Anyone with Win 7 and Firefox please give it a go.

I'm getting that error on Arch Linux with Firefox 41.0.1:

Code: [Select]
The connection to wss://graphene.bitshares.org/ws/ was interrupted while the page was loading. app.js:6:0
"connecting to wss://graphene.bitshares.org:443/ws/" app.js:6:23319
mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create vendors.js:19:30281

Looks to me like you're using an invalid url, try removing the / at the end of it. You can find it in settings.
Title: Re: Graphene GUI testing and feedback
Post by: valzav on October 10, 2015, 02:04:57 pm
The following Firefox error:
Quote
The connection to  .. was interrupted while the page was loading
Is know issue, it doesn't affect any functionality.

Testnet api connection string is wss://graphene.bitshares.org/ws, trailing slash is not necessary.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 10, 2015, 02:54:44 pm
The following Firefox error:
Quote
The connection to  .. was interrupted while the page was loading
Is know issue, it doesn't affect any functionality.

Testnet api connection string is wss://graphene.bitshares.org/ws, trailing slash is not necessary.

More than not necessary it's the cause of the problem; mindphlux was having the issue too and I could reproduce it using his remotely hosted witness node. Once I removed the slash from his url we were both able to connect.
Title: Re: Graphene GUI testing and feedback
Post by: wuyanren on October 10, 2015, 06:19:48 pm
The market history on the right is blank.i Mortgage core,But can't find the list.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on October 10, 2015, 07:33:22 pm
The market history on the right is blank.i Mortgage core,But can't find the list.

Same question here - any place one can see his short positions?
Title: Re: Graphene GUI testing and feedback
Post by: xeroc on October 10, 2015, 07:36:03 pm
It has been addes to the latest development branch .. the page has not yet been updates
Title: Re: Graphene GUI testing and feedback
Post by: Troglodactyl on October 10, 2015, 07:40:18 pm
The market history on the right is blank.i Mortgage core,But can't find the list.

Same question here - any place one can see his short positions?

Looks like you just use the "Borrow [BitAsset]" button in market both to borrow, pay off debt, or to check your current position.  Just update your position and set your desired debt to zero to pay off that debt from your asset balance.

EDIT:
It has been addes to the latest development branch .. the page has not yet been updates

Oh good.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on October 10, 2015, 07:54:34 pm
The market history on the right is blank.i Mortgage core,But can't find the list.

Same question here - any place one can see his short positions?

Looks like you just use the "Borrow [BitAsset]" button in market both to borrow, pay off debt, or to check your current position.  Just update your position and set your desired debt to zero to pay off that debt from your asset balance.

EDIT:
It has been addes to the latest development branch .. the page has not yet been updates

Oh good.

It either needed a restart or it was pushed just now, cause I see the update button for the first time now after restarting. The rest is still the same though...will check again later.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 10, 2015, 08:27:15 pm
The market history on the right is blank.i Mortgage core,But can't find the list.

Same question here - any place one can see his short positions?

Looks like you just use the "Borrow [BitAsset]" button in market both to borrow, pay off debt, or to check your current position.  Just update your position and set your desired debt to zero to pay off that debt from your asset balance.

EDIT:
It has been addes to the latest development branch .. the page has not yet been updates

Oh good.

It either needed a restart or it was pushed just now, cause I see the update button for the first time now after restarting. The rest is still the same though...will check again later.
I think xeroc is talking about the price history used for the charts, we still don't have an api call for order history so the only thing you'll see in the market history column is orders that happened while you had the market open.

You can update your margin positions in two places: account overview and exchange page, that's been available a while. To open a new margin position you need to be in the exchange, then click the Borrow button on the top right.
Title: Re: Graphene GUI testing and feedback
Post by: Troglodactyl on October 10, 2015, 09:09:35 pm
Code: [Select]
ERROR in ./~/css-loader!./~/autoprefixer-loader!./~/sass-loader?outputStyle=expanded!./app/assets/stylesheets/app.scss
Module build failed:
@import "~react-foundation-apps/node_modules/foundation-apps/scss/foundation.scss";
       ^
      File to import not found or unreadable: react-foundation-apps/node_modules/foundation-apps/scss/foundation.scss
      in [...]/graphene-ui/web/app/assets/stylesheets/app.scss (line 3, column 9)
 @ ./app/assets/stylesheets/app.scss 4:14-200 13:2-17:4 14:20-206
webpack: bundle is now VALID.

If I downgrade NodeJS so that the dependencies build/install successfully, I get this error on attempting to start.

Any assistance would be appreciated.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on October 10, 2015, 09:11:20 pm
You can update your margin positions in two places: account overview and exchange page, that's been available a while.

There is something (or several things) that is/are not right.


(http://i.imgur.com/lTSR7O8.png)
There is not one position but several (maybe totaling 8 bitUSD) but anyway I should be able to close/adjust collateral separately.


(http://i.imgur.com/t9IHY76.png)

And how do I adjust the collateral or close the position in this baby above? Do I have to have 8 bitUSD for it to change? and if yes, we go back that it was several separate orders. If I click adjust pos. it is not clear at all what will happen. 0.05 is the lowest amount the "adjust position" button becomes active, but why?
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 10, 2015, 09:21:31 pm
You can update your margin positions in two places: account overview and exchange page, that's been available a while.

There is something (or several things) that is/are not right.


(http://imgur.com/DpLs7q6)

There is not one position but several (maybe totaling 8 bitUSD) but anyway I should be able to close/adjust collateral separately.


(http://imgur.com/t9IHY76)

And how do I adjust the collateral or close the position in this baby above? Do I have to have 8 bitUSD for it to change? and if yes, we go back that it was several separate orders. If I click adjust pos. it is not clear at all what will happen. 0.05 is the lowest amount the "adjust position" button becomes active, but why?

There's only one global margin position per asset now.

To close, try adjusting the debt to 0 I guess? Nm that's not possible since the button gets disabled, I'll fix that tomorrow. We should probably add a "Close position" shortcut too.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 10, 2015, 09:30:54 pm
I've just tested it and it works after this commit https://github.com/cryptonomex/graphene-ui/commit/adb18c1508eefeca38ba37be20ccdc3ceffb5575

Just set debt and collateral to 0, and of course you need to have the required amount of the asset you're covering.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on October 10, 2015, 09:43:42 pm
Can somebody send 'testerjoe' 8 bitUSD backed by CORE or 8*275 CORE. Thanks!

Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 10, 2015, 10:17:36 pm
The following Firefox error:
Quote
The connection to  .. was interrupted while the page was loading
Is know issue, it doesn't affect any functionality.

Testnet api connection string is wss://graphene.bitshares.org/ws, trailing slash is not necessary.

More than not necessary it's the cause of the problem; mindphlux was having the issue too and I could reproduce it using his remotely hosted witness node. Once I removed the slash from his url we were both able to connect.

I still get the same error and a blank screen in Firefox on Windows 7:
Code: [Select]
The connection to wss://graphene.bitshares.org/ws/ was interrupted while the page was loading.
I can see that you already closed the related issue (https://github.com/cryptonomex/graphene-ui/issues/285) on github but for me the blank screen problem still remains.
What has changed since yesterday is that I don't get the "Unknown error" any more.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 11, 2015, 04:05:53 am


The following Firefox error:
Quote
The connection to  .. was interrupted while the page was loading
Is know issue, it doesn't affect any functionality.

Testnet api connection string is wss://graphene.bitshares.org/ws, trailing slash is not necessary.

More than not necessary it's the cause of the problem; mindphlux was having the issue too and I could reproduce it using his remotely hosted witness node. Once I removed the slash from his url we were both able to connect.

I still get the same error and a blank screen in Firefox on Windows 7:
Code: [Select]
The connection to wss://graphene.bitshares.org/ws/ was interrupted while the page was loading.
I can see that you already closed the related issue (https://github.com/cryptonomex/graphene-ui/issues/285) on github but for me the blank screen problem still remains.
What has changed since yesterday is that I don't get the "Unknown error" any more.

You still have a trailing slash in your URL though, did you try removing it?
Title: Re: Graphene GUI testing and feedback
Post by: betax on October 11, 2015, 06:14:31 am
Chrome, W10.

Buying, borrowing, selling (to myself) is all good. A bit confusing to see where your active orders are (until you see them). But I do understand the lack of space, vs extra headers.

The chart at the bottom, seems broken or needs some background colour. I only see the volume black lines.
Title: Re: Graphene GUI testing and feedback
Post by: betax on October 11, 2015, 06:15:47 am
Can somebody send 'testerjoe' 8 bitUSD backed by CORE or 8*275 CORE. Thanks!

Sent
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 11, 2015, 06:26:08 am
Chrome, W10.

Buying, borrowing, selling (to myself) is all good. A bit confusing to see where your active orders are (until you see them). But I do understand the lack of space, vs extra headers.

The chart at the bottom, seems broken or needs some background colour. I only see the volume black lines.
Great :)

The chart at the bottom got fixed this weekend.

Agree about the open orders, we could add a header but I'm hoping we can keep it as clean as possible.

PS a shortcut for entering prices is to simply click on the depth chart, it will fill the buy/sell price with the price you chose. And you can also click on the order book, although I think we might run into some matching issues due to floating point math errors, would be nice to have some testing done of that actually.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on October 11, 2015, 07:39:07 am
Can somebody send 'testerjoe' 8 bitUSD backed by CORE or 8*275 CORE. Thanks!

Sent

received!
Thank you Sir!

------

As per the GUI as of this moment - not working in regards of closing short position....waiting.
Title: Re: Graphene GUI testing and feedback
Post by: betax on October 11, 2015, 07:42:20 am
Chrome, W10.

Buying, borrowing, selling (to myself) is all good. A bit confusing to see where your active orders are (until you see them). But I do understand the lack of space, vs extra headers.

The chart at the bottom, seems broken or needs some background colour. I only see the volume black lines.
Great :)

The chart at the bottom got fixed this weekend.

Agree about the open orders, we could add a header but I'm hoping we can keep it as clean as possible.

PS a shortcut for entering prices is to simply click on the depth chart, it will fill the buy/sell price with the price you chose. And you can also click on the order book, although I think we might run into some matching issues due to floating point math errors, would be nice to have some testing done of that actually.

I actually figured that out myself ;) So it is rather intuitive. Only thing is that if you change market direction usd/core <-> core/usd the same values are kept, which I don't know if is either good or bad.
Title: Re: Graphene GUI testing and feedback
Post by: betax on October 11, 2015, 07:47:12 am
How long is the market history kept / display for? Am i guessing is based on the number of blocks, as opposed a full history? Mine keeps clearing after a while.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 11, 2015, 07:51:14 am
How long is the market history kept / display for? Am i guessing is based on the number of blocks, as opposed a full history? Mine keeps clearing after a while.
Until you switch markets or refresh the page. Inverting is equivalent to switching.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on October 11, 2015, 07:59:04 am
      <---
Back button.

Pls.
Title: Re: Graphene GUI testing and feedback
Post by: fav on October 11, 2015, 08:05:38 am
      <---
Back button.

Pls.

 +5% +5%
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 11, 2015, 08:33:42 am


The following Firefox error:
Quote
The connection to  .. was interrupted while the page was loading
Is know issue, it doesn't affect any functionality.

Testnet api connection string is wss://graphene.bitshares.org/ws, trailing slash is not necessary.

More than not necessary it's the cause of the problem; mindphlux was having the issue too and I could reproduce it using his remotely hosted witness node. Once I removed the slash from his url we were both able to connect.

I still get the same error and a blank screen in Firefox on Windows 7:
Code: [Select]
The connection to wss://graphene.bitshares.org/ws/ was interrupted while the page was loading.
I can see that you already closed the related issue (https://github.com/cryptonomex/graphene-ui/issues/285) on github but for me the blank screen problem still remains.
What has changed since yesterday is that I don't get the "Unknown error" any more.

You still have a trailing slash in your URL though, did you try removing it?
I'm not sure what you mean by "removing a trailing slash in the URL".
But if you mean using https://graphene.bitshares.org instead of https://graphene.bitshares.org/ - it has no effect, I still get the "connection interrupted" error and a blank screen.

I would not insist if I had some non-standard settings. But everything seems to be standard on my side: Window 7, no firewall, the latest version of Firefox, no privacy mode switched on.
The only thing that is non-standard is that I did run lots of previous versions of the GUI on this machine so maybe something got cached. But I did clear the cache in the browser.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 11, 2015, 08:36:13 am




The following Firefox error:
Quote
The connection to  .. was interrupted while the page was loading
Is know issue, it doesn't affect any functionality.

Testnet api connection string is wss://graphene.bitshares.org/ws, trailing slash is not necessary.

More than not necessary it's the cause of the problem; mindphlux was having the issue too and I could reproduce it using his remotely hosted witness node. Once I removed the slash from his url we were both able to connect.

I still get the same error and a blank screen in Firefox on Windows 7:
Code: [Select]
The connection to wss://graphene.bitshares.org/ws/ was interrupted while the page was loading.
I can see that you already closed the related issue (https://github.com/cryptonomex/graphene-ui/issues/285) on github but for me the blank screen problem still remains.
What has changed since yesterday is that I don't get the "Unknown error" any more.

You still have a trailing slash in your URL though, did you try removing it?
I'm not sure what you mean by "removing a trailing slash in the URL".
But if you mean using https://graphene.bitshares.org instead of https://graphene.bitshares.org/ - it has no effect, I still get the "connection interrupted" error and a blank screen.

No I mean in the websocket URL, it shouldn't have the trailing / after .org/ws
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 11, 2015, 08:42:01 am




The following Firefox error:
Quote
The connection to  .. was interrupted while the page was loading
Is know issue, it doesn't affect any functionality.

Testnet api connection string is wss://graphene.bitshares.org/ws, trailing slash is not necessary.

More than not necessary it's the cause of the problem; mindphlux was having the issue too and I could reproduce it using his remotely hosted witness node. Once I removed the slash from his url we were both able to connect.

I still get the same error and a blank screen in Firefox on Windows 7:
Code: [Select]
The connection to wss://graphene.bitshares.org/ws/ was interrupted while the page was loading.
I can see that you already closed the related issue (https://github.com/cryptonomex/graphene-ui/issues/285) on github but for me the blank screen problem still remains.
What has changed since yesterday is that I don't get the "Unknown error" any more.

You still have a trailing slash in your URL though, did you try removing it?
I'm not sure what you mean by "removing a trailing slash in the URL".
But if you mean using https://graphene.bitshares.org instead of https://graphene.bitshares.org/ - it has no effect, I still get the "connection interrupted" error and a blank screen.

No I mean in the websocket URL, it shouldn't have the trailing / after .org/ws
How do I change that?
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 11, 2015, 08:42:39 am
In the settings
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 11, 2015, 08:47:32 am
In the settings
Please be more specific. In FF settings?
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 11, 2015, 08:50:28 am
In the settings
Please be more specific. In FF settings?

Haha I just realized you can't access the settings if the app doesn't initialize correctly, chicken and egg problem...

I mean the wallet settings, where you can enter the WS Api you want to use. I'll push a commit in a bit that removes the / from the default ws connection, guess you'll have to be patient until that reaches the server. If you're running locally then you simply need to edit ApiInstances.js, uncomment line 27 and replace it with the correct ws url.
Title: Re: Graphene GUI testing and feedback
Post by: iHashFury on October 11, 2015, 10:22:45 am
How do you close a 'usd-collateral-holder' position?

When I 'Update Position' and 'Collateral change   -424.46933 CORE' the CORE asset is displayed in the 'usd-collateral-holder' balance

Then when I try to transfer the 'CORE' to my account name, the GUI says 'usd-collateral-holder' is 'Not your account'

Also, all my collateral-holders Memo Keys says 'Not a valid public key'

Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 11, 2015, 11:37:29 am
In the settings
Please be more specific. In FF settings?

Haha I just realized you can't access the settings if the app doesn't initialize correctly, chicken and egg problem...

I mean the wallet settings, where you can enter the WS Api you want to use. I'll push a commit in a bit that removes the / from the default ws connection, guess you'll have to be patient until that reaches the server. If you're running locally then you simply need to edit ApiInstances.js, uncomment line 27 and replace it with the correct ws url.

@svk, what is the logic of exposing this crucial ws URL setting to the user in the online (i.e. not standalone) version?
If the user starts playing with it and mistypes the ws URL then there is no easy way to revert the change as there is no access to the GUI - a clear chicken-and-egg problem.

This is what just happened to me in Chrome: I mistyped the ws URL on purpose, reloaded the GUI and lost access to it.
How do I revert it to the default value???

EDIT: actually there is a way to revert to the default value (by selecting the retry option) but now it seems my wallet is gone as the app asks me to create a new account.
It's not clear to me what you wanted to achieve but surely we cannot leave it the way it is now.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 11, 2015, 11:40:26 am
In the settings
Please be more specific. In FF settings?

Haha I just realized you can't access the settings if the app doesn't initialize correctly, chicken and egg problem...

I mean the wallet settings, where you can enter the WS Api you want to use. I'll push a commit in a bit that removes the / from the default ws connection, guess you'll have to be patient until that reaches the server. If you're running locally then you simply need to edit ApiInstances.js, uncomment line 27 and replace it with the correct ws url.

@svk, what is the logic of exposing this crucial ws URL setting to the user in the online (i.e. not standalone) version?
If the user starts playing with it and mistypes the ws URL then there is no easy way to revert the change as there is no access to the GUI - a clear chicken and egg problem.

This is what just happened to me in Chrome: I mistyped the ws URL on purpose, reloaded the GUI and lost access to it.
How do I revert it to the default value???
The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.

It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 11, 2015, 12:10:29 pm
The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.
It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.

In the online version (i.e. in the GUI accessed by https://graphene.bitshares.org) - what possible reason would I have to want to change it??
I think it should be completely removed (or disabled) in the online version.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 11, 2015, 01:22:56 pm
The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.
It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.

In the online version (i.e. in the GUI accessed by https://graphene.bitshares.org) - what possible reason would I have to want to change it??
I think it should be completely removed (or disabled) in the online version.

No, it can be useful, say you're on OpenLedger but their backend servers go down, you could switch it to another api provider, like BunkerDEX or Banx, or even one you provide yourself.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 11, 2015, 01:53:43 pm
The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.
It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.

In the online version (i.e. in the GUI accessed by https://graphene.bitshares.org) - what possible reason would I have to want to change it??
I think it should be completely removed (or disabled) in the online version.

No, it can be useful, say you're on OpenLedger but their backend servers go down, you could switch it to another api provider, like BunkerDEX or Banx, or even one you provide yourself.

I see. So you can have the html/js served by domain A and at the same time have the blockchain support (i.e. wss) served by domain B.
OK, that makes sense and it's great.

But this definitely requires a fool-proof implementation in the GUI so that people do not become cut off when they mess it up.
Maybe a drop-down offering a choice of available wss domains plus and advanced option to add your own wss URL.
Title: Re: Graphene GUI testing and feedback
Post by: Troglodactyl on October 11, 2015, 02:30:19 pm
The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.
It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.

In the online version (i.e. in the GUI accessed by https://graphene.bitshares.org) - what possible reason would I have to want to change it??
I think it should be completely removed (or disabled) in the online version.

No, it can be useful, say you're on OpenLedger but their backend servers go down, you could switch it to another api provider, like BunkerDEX or Banx, or even one you provide yourself.

I see. So you can have the html/js served by domain A and at the same time have the blockchain support (i.e. wss) served by domain B.
OK, that makes sense and it's great.

But this definitely requires a fool-proof implementation in the GUI so that people do not become cut off when they mess it up.
Maybe a drop-down offering a choice of available wss domains plus and advanced option to add your own wss URL.

The connection failure page should list the web socket connection information and allow the user to alter it before retrying, possibly buried behind an "Advanced" expander.
Title: Re: Graphene GUI testing and feedback
Post by: spartako on October 11, 2015, 02:58:47 pm
How do you close a 'usd-collateral-holder' position?

When I 'Update Position' and 'Collateral change   -424.46933 CORE' the CORE asset is displayed in the 'usd-collateral-holder' balance

Then when I try to transfer the 'CORE' to my account name, the GUI says 'usd-collateral-holder' is 'Not your account'

Also, all my collateral-holders Memo Keys says 'Not a valid public key'

Same problem here
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 11, 2015, 04:26:27 pm
The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.
It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.

In the online version (i.e. in the GUI accessed by https://graphene.bitshares.org) - what possible reason would I have to want to change it??
I think it should be completely removed (or disabled) in the online version.

No, it can be useful, say you're on OpenLedger but their backend servers go down, you could switch it to another api provider, like BunkerDEX or Banx, or even one you provide yourself.

I see. So you can have the html/js served by domain A and at the same time have the blockchain support (i.e. wss) served by domain B.
OK, that makes sense and it's great.

But this definitely requires a fool-proof implementation in the GUI so that people do not become cut off when they mess it up.
Maybe a drop-down offering a choice of available wss domains plus and advanced option to add your own wss URL.

The connection failure page should list the web socket connection information and allow the user to alter it before retrying, possibly buried behind an "Advanced" expander.

Yea I've gone and added this, I also refactored the whole thing so you now choose the websocket using a dropdown menu. In the settings you can add AND remove websockets to the list, while on the init-error page you can choose from the list, or add a new one then pick it.

(http://i.imgur.com/5g665Ar.png)
Title: Re: Graphene GUI testing and feedback
Post by: Troglodactyl on October 11, 2015, 06:22:05 pm
The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.
It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.

In the online version (i.e. in the GUI accessed by https://graphene.bitshares.org) - what possible reason would I have to want to change it??
I think it should be completely removed (or disabled) in the online version.

No, it can be useful, say you're on OpenLedger but their backend servers go down, you could switch it to another api provider, like BunkerDEX or Banx, or even one you provide yourself.

I see. So you can have the html/js served by domain A and at the same time have the blockchain support (i.e. wss) served by domain B.
OK, that makes sense and it's great.

But this definitely requires a fool-proof implementation in the GUI so that people do not become cut off when they mess it up.
Maybe a drop-down offering a choice of available wss domains plus and advanced option to add your own wss URL.

The connection failure page should list the web socket connection information and allow the user to alter it before retrying, possibly buried behind an "Advanced" expander.

Yea I've gone and added this, I also refactored the whole thing so you now choose the websocket using a dropdown menu. In the settings you can add AND remove websockets to the list, while on the init-error page you can choose from the list, or add a new one then pick it.

(http://i.imgur.com/5g665Ar.png)

Awesome!  Looking good.
Title: Re: Graphene GUI testing and feedback
Post by: coiner on October 11, 2015, 11:21:31 pm
(http://i.imgur.com/hAQ088S.png)

Testing on graphene.bitshares.org i am getting a now <= trx.expiration. Also i am missing 108000 bitshares from the total i have on bitshares 0.9.3c (totally syncronized) oh and i sent to myself all the funds previously to export the keys.json

Please advice,
Title: Re: Graphene GUI testing and feedback
Post by: coiner on October 11, 2015, 11:33:11 pm
I was using that new explorer from window10 (edge?). Also on Opera goes really slow and has graphic glitchs. Will give it a try on Firefox.
It seems using chromodo the transaction went fine but for some reason i am missing 108198 Core (bitshares) although the keys.json were exported after a total sync on 0.9.3c and after sending my total amount of bitshares to myself.

Any idea? Should i worry?

Thanks.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 12, 2015, 05:57:19 am
I was using that new explorer from window10 (edge?). Also on Opera goes really slow and has graphic glitchs. Will give it a try on Firefox.
It seems using chromodo the transaction went fine but for some reason i am missing 108198 Core (bitshares) although the keys.json were exported after a total sync on 0.9.3c and after sending my total amount of bitshares to myself.

Any idea? Should i worry?

Thanks.

When did you send it to yourself? The current testnet uses a snapshot state from October 5th, if your transfer was after that you won't see it in the testnet.
Title: Re: Graphene GUI testing and feedback
Post by: fav on October 12, 2015, 07:17:04 am
looks like graphene.bitshares.org / light wallet died.

not sure if it's connected, but I just imported my main keys + tried to claim balances

(http://i.imgur.com/cbAwz8g.png)
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 12, 2015, 07:40:03 am
looks like graphene.bitshares.org / light wallet died.

not sure if it's connected, but I just imported my main keys + tried to claim balances

(http://i.imgur.com/cbAwz8g.png)

Yep, looks like the backend (witness node) crashed, I'll tell Valentine once he's online. It needs to be updated anyway..
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 12, 2015, 02:03:35 pm
We used to have an account's open collateral positions listed in the account's overview page with an option to update them.
This is list is no longer there.
How is the user supposed to manage or close their collateral positions?

EDIT: It turns out the open collateral position list is there but I needed to reload the URL in the browser to get it. Seems like the overview page fails to update itself automatically.
I've already reported the bug here: https://github.com/cryptonomex/graphene-ui/issues/317

But part of the question still remains: how do I close a collateral position?

EDIT: I can see that the latest update has solved this problem as well.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 12, 2015, 02:06:51 pm
In the settings
Please be more specific. In FF settings?

Haha I just realized you can't access the settings if the app doesn't initialize correctly, chicken and egg problem...

I mean the wallet settings, where you can enter the WS Api you want to use. I'll push a commit in a bit that removes the / from the default ws connection, guess you'll have to be patient until that reaches the server. If you're running locally then you simply need to edit ApiInstances.js, uncomment line 27 and replace it with the correct ws url.

@svk, has this been pushed yet? I still get a blank screen in my Firefox...
Title: Re: Graphene GUI testing and feedback
Post by: wuyanren on October 13, 2015, 02:48:07 am
https://graphene.bitshares.org/#/markets  There seems to be a bit of a mess.
Title: Re: Graphene GUI testing and feedback
Post by: JonnyB on October 13, 2015, 05:42:01 am
This Graphene GUI doesn't seem ready yet. seems very buggy. I think the 2.0 launch should be cancelled personally.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 13, 2015, 07:02:43 am
https://graphene.bitshares.org/#/markets  There seems to be a bit of a mess.

Please be more specific, it's working fine last I checked
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 13, 2015, 07:03:21 am
This Graphene GUI doesn't seem ready yet. seems very buggy. I think the 2.0 launch should be cancelled personally.

What parts in particular do you feel are buggy and not ready?
Title: Re: Graphene GUI testing and feedback
Post by: Pheonike on October 13, 2015, 07:13:30 am
One critic is that the witness, committee boxes are too big. I shouldn't have to scroll to see  all 35 witnesses on a 24" monitor.
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 13, 2015, 11:17:11 pm
In the exchange.  For example the USD:BTS market.  (Its listed as USDvsBTS).   On the actual trading page its listed as BTS/USD. 

This is very confusing, as every market on the planet will list trading pairs the other way around, like  USD:BTS not BTS/USD. Where the first asset is the Base( the asset your buying/selling) and the second asset is the quote(the price of each base unit)

I recommend using the colon ' : ' as to not confuse the two

http://www.investopedia.com/terms/c/currencypair.asp
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 14, 2015, 08:01:21 am
In the exchange.  For example the USD:BTS market.  (Its listed as USDvsBTS).   On the actual trading page its listed as BTS/USD. 

This is very confusing, as every market on the planet will list trading pairs the other way around, like  USD:BTS not BTS/USD. Where the first asset is the Base( the asset your buying/selling) and the second asset is the quote(the price of each base unit)

I recommend using the colon ' : ' as to not confuse the two

http://www.investopedia.com/terms/c/currencypair.asp

I just kept this the same way as it is in BTS 1 but I agree with your points, I'll add it when I find the time.
Title: Re: Graphene GUI testing and feedback
Post by: jakub on October 14, 2015, 03:54:12 pm
Wouldn't it be useful if the market history chart in the GUI showed two things at the same time:
(1) the history of trades happening on the BTS blockchain (as it does now)
(2) the history of settlement price (i.e. the average of price feeds supplied by the witnesses)

This way we would achieve two benefits:
(1) You won't have to refer to sites like Poloniex to see the full history and the chart won't look so empty as it does now
(2) It will be clearly visible that the market peg holds as the blockchain trades will (hopefully) be aligned along the settlement price
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 14, 2015, 04:17:43 pm
In the exchange.  For example the USD:BTS market.  (Its listed as USDvsBTS).   On the actual trading page its listed as BTS/USD. 

This is very confusing, as every market on the planet will list trading pairs the other way around, like  USD:BTS not BTS/USD. Where the first asset is the Base( the asset your buying/selling) and the second asset is the quote(the price of each base unit)

I recommend using the colon ' : ' as to not confuse the two

http://www.investopedia.com/terms/c/currencypair.asp

I just kept this the same way as it is in BTS 1 but I agree with your points, I'll add it when I find the time.

The BTS1 markets page have it correctly listed.  It is backwards in BTS2.   I wish i was more familiar with the code as this would be an easy thing to fix myself.  Thanks.  : )

(https://i.imgur.com/YQ38p4e.jpg)
Title: Re: Graphene GUI testing and feedback
Post by: sircodealot on October 14, 2015, 04:23:23 pm
Why does OpenLedger not return the transaction fee when the transaction is cancelled.  This is frankly wrong.  I would expect transaction fees to be returned when there has been NO transaction.  This is almost equivalent to theft.

Is everyone OK with this??????
Title: Re: Graphene GUI testing and feedback
Post by: betax on October 14, 2015, 04:26:03 pm
looks like graphene.bitshares.org / light wallet died.

not sure if it's connected, but I just imported my main keys + tried to claim balances

(http://i.imgur.com/cbAwz8g.png)

Fav you are trying to collect vesting balances again, just untick those and should be ok. (It took me a while to figure it out)
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 14, 2015, 04:27:41 pm
In the exchange.  For example the USD:BTS market.  (Its listed as USDvsBTS).   On the actual trading page its listed as BTS/USD. 

This is very confusing, as every market on the planet will list trading pairs the other way around, like  USD:BTS not BTS/USD. Where the first asset is the Base( the asset your buying/selling) and the second asset is the quote(the price of each base unit)

I recommend using the colon ' : ' as to not confuse the two

http://www.investopedia.com/terms/c/currencypair.asp

I just kept this the same way as it is in BTS 1 but I agree with your points, I'll add it when I find the time.

The BTS1 markets page have it correctly listed.  It is backwards in BTS2.   I wish i was more familiar with the code as this would be an easy thing to fix myself.  Thanks.  : )

(https://i.imgur.com/YQ38p4e.jpg)

Right you are, not sure how I got that one wrong tbh, I distinctly remember looking at the BTS 1 wallet when doing this :o Oh well like you say it's an easy one to fix :)
Title: Re: Graphene GUI testing and feedback
Post by: fav on October 14, 2015, 04:28:59 pm
cross-posting @svk https://bitsharestalk.org/index.php/topic,18951.msg244624.html#msg244624
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 14, 2015, 04:32:03 pm
Why does OpenLedger not return the transaction fee when the transaction is cancelled.  This is frankly wrong.  I would expect transaction fees to be returned when there has been NO transaction.  This is almost equivalent to theft.

Is everyone OK with this??????

What do you mean cancelled transactions? No transaction, no fee.. Only thing you can cancel is market orders and that's free to do, however placing an order always has a fee associated.
Title: Re: Graphene GUI testing and feedback
Post by: sircodealot on October 14, 2015, 05:01:29 pm
Within OpenLedger you can cancel an order that has NOT yet been transacted, but a fee has already occurred.  I assumed that when I cancelled the order from the orderbook, the transaction fee would be returned.  It does not.  I think you agree, that is wrong or is a bug that needs to be fixed. 
Title: Re: Graphene GUI testing and feedback
Post by: Ander on October 14, 2015, 05:08:09 pm
Within OpenLedger you can cancel an order that has NOT yet been transacted, but a fee has already occurred.  I assumed that when I cancelled the order from the orderbook, the transaction fee would be returned.  It does not.  I think you agree, that is wrong or is a bug that needs to be fixed.

While we cannot have the fee be absolutely zero for a cancelled order because it would allow peopel to spam the blockchain, I think the total fee for a cancelled transaction should be like 0.1 BTS.
Title: Re: Graphene GUI testing and feedback
Post by: sircodealot on October 14, 2015, 05:08:27 pm
If the decentralized OpenLedger exchange assumes a "transaction" means placing an order onto the ledger/orderbook  and, subsequently, incurs a fee, this is grossly unfair.  Within any centralized exchange, there is no fee to place an order, execution of an order is when a fee is incurred.  This is how OpenLedger or any decentralized exchange should work at default.
Title: Re: Graphene GUI testing and feedback
Post by: sircodealot on October 14, 2015, 05:18:44 pm
I can appreciate the mitigation against increasing blockchain exposure to spam attacks, but, really, this is a bad trade-off when you consider unreturned fee on cancellation as friction against liquidity.  I'm now much less interested in quickly responding to market changes since it costs me to simply change/cancel an existing order to respond to changing market conditions.  I think a better mitigation is to return the fee after a short period of time, say a minute or two, enough so that the malicious spam attack would not be noticeable by the market.
Title: Re: Graphene GUI testing and feedback
Post by: liondani on October 14, 2015, 05:27:58 pm
I can appreciate the mitigation against increasing blockchain exposure to spam attacks, but, really, this is a bad trade-off when you consider unreturned fee on cancellation as friction against liquidity.  I'm now much less interested in quickly responding to market changes since it costs me to simply change/cancel an existing order to respond to changing market conditions.  I think a better mitigation is to return the fee after a short period of time, say a minute or two, enough so that the malicious spam attack would not be noticeable by the market.

make sense!
Title: Re: Graphene GUI testing and feedback
Post by: maqifrnswa on October 14, 2015, 08:01:58 pm
I can appreciate the mitigation against increasing blockchain exposure to spam attacks, but, really, this is a bad trade-off when you consider unreturned fee on cancellation as friction against liquidity.  I'm now much less interested in quickly responding to market changes since it costs me to simply change/cancel an existing order to respond to changing market conditions.  I think a better mitigation is to return the fee after a short period of time, say a minute or two, enough so that the malicious spam attack would not be noticeable by the market.

I believe each fee can be set independently by a vote on the network. If enough users agree with you, it will be changed.
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 17, 2015, 09:15:05 pm
After some time I managed to import my keys.json into the webwallet.  However, for some reason it didn't import every balance.

I ran the import process again on the same keys.json file and it found several unclaimed balances. However when I try to import, I get the error message that "This wallet has already been imported" and I cannot proceed to claim the balances.
Title: Re: Graphene GUI testing and feedback
Post by: clayop on October 17, 2015, 09:49:15 pm
We have a decimal problem in BTS-TRADE.BTC market

Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 18, 2015, 10:45:53 pm
If you let a market page sit. after about 10 mins some aspects of the market flip on their own
(http://imgur.com/fMxtL9z.jpg)
(http://imgur.com/YvTOg2k.jpg)

and what should be a large yellow box on the depth graph doesn't display on this side of the flip

Orders are often slow to pop up with dialog box and slow to update on screen after completed.

I've only noticed the slowness since I imported all my accounts and keys.

Update: Also the precision need to be greater on BID and ASK book prices. 
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 20, 2015, 04:36:54 pm
Most recent market page update: https://bitsharestalk.org/index.php/topic,19297.msg247768.html#msg247768

Some issues. 
The page is very slow to load. ~45 secs.  I don't know if this is a baseline or based on the number of accounts in the wallet. Every page since importing all my accounts seem very slow.

The Period adjustments take almost 60 seconds to take affect after clicking.  Ideally I'd like to see at least 1Day, 12H, 4H, 1H, 30min, 15min
(http://content.screencast.com/users/Enkianu/folders/Jing/media/23afd6af-a8b0-490f-afcd-50412827ba64/2015-10-20_1226.png)

Maybe just my preference but I think there are too many switch arrows. I'd like to see just one that switches all three of these.
(http://content.screencast.com/users/Enkianu/folders/Jing/media/f024b54e-b661-48e8-befb-d931fcb299f0/2015-10-20_1232.png)

I'd like to see the Last price listed here instead of the spread.
(http://content.screencast.com/users/Enkianu/folders/Jing/media/f79e2e4b-c183-4c2d-a08b-6a33ebe12eeb/2015-10-20_1234.png)
Title: Re: Graphene GUI testing and feedback
Post by: rnglab on October 20, 2015, 06:30:06 pm
Probably this has already been discussed; most new users would be annoyed to find out they have no access to their accounts from other devices, or perhaps even with no way to get back if the cache from the browser they used to create an account has been cleared, for instance.

I'd  suggest changing the BACKUP BRAINKEY RECOMMENDED for something like BACKUP BRAINKEY ^^^NEEDED^^^. or better making it a mandatory step.

Brainkey generation (or Wallet Management) page should then explain that for security reasons, for users not having to trust on a third party, all they're account keys are managed, encrypted and stored locally in they're browsers. That locking they're accounts is the way to prevent other users on that device to access that account, and specially that creating a backup, Brainkey being the most practical, is the only way to hold possession of that account and to be able to access back from any other device they want. Otherwise, once the browser cache is cleared, recovering access to they're accounts might not be possible.

Something like that but in English :P

what do you think?

Edit: forgot to say it's looking great
Title: Re: Graphene GUI testing and feedback
Post by: mindphlux on October 20, 2015, 07:10:12 pm
If the user has BTS1 accounts, I would not show backup brainkey, but Download backup instead.

Brainkey does not include BTS1 accounts
Title: Re: Graphene GUI testing and feedback
Post by: Tuck Fheman on October 20, 2015, 07:38:37 pm
From a non-technical perspective, here are some feelings on the 2.0 client that I've gathered ...

"It doesn't crash!" = Better than 1.0
"It looks good" = Better than 1.0
"It's faster" = Better than 1.0

"Help???" = Worse than 1.0
"The markets are hard to understand for non-'traders' " - "dumb it down if they want people to use it" - "Where do I go to _____?" - "What happened to burn messages and 'For/Against' on the wall?" = Worse than 1.0


A feature I'd personally like to see very soon ...

A setting where I can set an extra warning message or prompt if I'm exceeding a withdrawal limit on individual assets.

Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 20, 2015, 10:11:42 pm
The "Create New Account" button persists on many pages it may not be intended to.

(http://content.screencast.com/users/Enkianu/folders/Jing/media/c58baea2-d9ce-4d2f-884f-093ce1f06b60/2015-10-20_1806.png)

(http://content.screencast.com/users/Enkianu/folders/Jing/media/9e076386-956a-4e9c-a657-2ab72543680c/2015-10-20_1808.png)

(http://content.screencast.com/users/Enkianu/folders/Jing/media/8b8e8073-a93e-4a1a-bd7c-b224efc55faf/2015-10-20_1809.png)

Or is it supposed to be there?
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 20, 2015, 10:22:05 pm
The "Create New Account" button persists on many pages it may not be intended to.

(http://content.screencast.com/users/Enkianu/folders/Jing/media/c58baea2-d9ce-4d2f-884f-093ce1f06b60/2015-10-20_1806.png)

(http://content.screencast.com/users/Enkianu/folders/Jing/media/9e076386-956a-4e9c-a657-2ab72543680c/2015-10-20_1808.png)

(http://content.screencast.com/users/Enkianu/folders/Jing/media/8b8e8073-a93e-4a1a-bd7c-b224efc55faf/2015-10-20_1809.png)

Or is it supposed to be there?
Definitely not, that is a very strange bug :o
Title: Re: Graphene GUI testing and feedback
Post by: ag on October 20, 2015, 10:28:11 pm
Probably this has already been discussed; most new users would be annoyed to find out they have no access to their accounts from other devices, or perhaps even with no way to get back if the cache from the browser they used to create an account has been cleared, for instance.

I'd  suggest changing the BACKUP BRAINKEY RECOMMENDED for something like BACKUP BRAINKEY ^^^NEEDED^^^. or better making it a mandatory step.

Brainkey generation (or Wallet Management) page should then explain that for security reasons, for users not having to trust on a third party, all they're account keys are managed, encrypted and stored locally in they're browsers. That locking they're accounts is the way to prevent other users on that device to access that account, and specially that creating a backup, Brainkey being the most practical, is the only way to hold possession of that account and to be able to access back from any other device they want. Otherwise, once the browser cache is cleared, recovering access to they're accounts might not be possible.

Something like that but in English :P

what do you think?

Edit: forgot to say it's looking great

You're scaring me, all I need to remember is my account name and password... right? What does having a backup do?
Title: Re: Graphene GUI testing and feedback
Post by: mike623317 on October 20, 2015, 11:10:55 pm

My biggest criticism is that the Markets screen is hard to understand for non traders, and thats not just Bitshares but other trading platforms too.

I would really like to see a section with screenshots and examples for non-traders. I'm simply not going to risk loosing money if its too difficult to decipher. Clear examples in an easy to understand fashion is the way to go.

The same can be said for permissions. In my opinion we shouldnt have to go looking for explanations, it should either be self evident or a 'Whats this?' icon to click on and launch a pop up window.

This is really coming together though and the devs deserve a lot of credit. Lets just make it easy to use and easy to understand for people who dont know what a short even is.

my 2 bts
Title: Re: Graphene GUI testing and feedback
Post by: jaran on October 21, 2015, 01:37:30 am
You're scaring me, all I need to remember is my account name and password... right? What does having a backup do?

You need to backup your private keys.  An account name and password are not enough.  See Help -> Backups in the wallet.
Title: Re: Graphene GUI testing and feedback
Post by: maqifrnswa on October 21, 2015, 01:50:26 am
You're scaring me, all I need to remember is my account name and password... right? What does having a backup do?

Even though you go to a website, your information is not stored on a central server, but on your own computer. Unlike centralized exchanges, no one can hack in somewhere and get your password and coins. So you need a backup in case something happens to your computer.

If you don't have any BTS1.0 accounts, you can create an account with a password and brain key, and as long as you remember those two things you are always ok. Any other case requires a backup
Title: Re: Graphene GUI testing and feedback
Post by: ag on October 21, 2015, 04:05:00 am
wow... I made backups... I thought a server was keeping my wallet/keys like blockchain.info does.
Title: Re: Graphene GUI testing and feedback
Post by: Riverhead on October 21, 2015, 05:16:57 pm

Precision slip when viewing "Market Depth". Gets worse as you switch between horizontal and vertical.

(http://i.imgur.com/lr0j10g.png)
(https://bitsharestalk.org/data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAxAAAAFRCAIAAABrANxKAAAgAElEQVR4nO3df3QV1d3v8fPnXXctW8Ur9SCXoJJiEISokSgoCAQTIvJbodHWgkURgYIBRaEEqVgeQH5JlQbREsKPQpQSKCYqkAQNkAMC+R2IOS29eB8r2j7YPpXVu3L/2HWv7cycOSebkH3OzPu7Xoulk5nJOTOz93yyZ86cQLBLEgA9hw4dutK/4lxujrD7xw8CAEwJGD/lAImLwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAXzsGpv948H7HJkpgAoB4QGAC9LVXYBp0ay8ZjCIx3lkAgJ8RmAB97RWYHux3m3taqp/5iPHOAgD8jMAE6Gv3wNQ465EDU0ZblE5+yHhPAQA+R2AC9LV7YGIkCQDiE4EJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPhFImzfbXerTU7smpxg/MwFxiMAEAD4RGH26PKrU6VONn5mAOERgAgCfCGSVFrkYWfne6NPlWaVFQ7ZsSERp82YbP6fCwwhMAOATAffAkblvRyxDUPHM+DkVHkZgAgCfiBKYhmzZkFH02+G7tyQix/w08uP9sQ9QDVj5sryXq2dmpvHTM+INgQkAfCJ6YEpcIw4Vt+9gVc/MB9pd99vvNH7WhzYCEwD4hJcDk6PYB8wy9+2Q93Jd0YuG8ZCZrg92g4b9+/e3y3oy+/ZumPVIw6xHQtPGbZ+U6RM7JmX+7kcjduaMeNd0PwgAUfkuMOnJem/nyMr32t2oEwdGny43frGv1403Fz48/J1HR7z76AgxzgFcUceeGnP0yTGVU0dvHj/s7QkZ2yZlkpkAxDkCk0niQ4hmA9P1wW6FDz/Qs0uXq7539b9dhVhNmTKlXdZzS/D6uQP7zR3Yb9bdfXL69fSDR1NvmX7XrWVPPLR+1OC3J2TszBlhvDcEABcEJgJTt3dysq763tXf/36n7199LdokNze3XdbTp1vXZcPTlw1Pf2nIndPvvs0/jkwds3hY+pvjhv7uRwQmAHGNwERg6vbOo1lXfe/q71997TXXXIc2Wbx4cbus544bk9546N43Hrp3ddY98+67wz+OPjn2pYz018cM2TEp03hvCAAuCEwEpm7ncnNkYOrUqTNi98orr7TLetJu6v722MFvjx38+sh7FwxJ84l5991xLjdn8bD+r48Zsp3ABCC+EZgITN3O5eZcdRWBicBkKjClE5gAxD8CE4GJwERgIjABQBQEJgITgYnARGACgCgITAQmAhOBicAEAFEQmAhMBCYCE4EJAKIgMBGYCEwEJgITAERBYCIwEZgITAQmAIiCwERgcgtMBQWFra2tra2t58+fHzV6bKdOnZ+aNv3ixYut39Y333yzfPlKewIoKChUfySXunjx4lPTpouJy5ev/Oabb9SVq2JfpL3WU1ZWLt5UWVm5/R05LtLS0mJfRGM9Rz86LBY5d7JK5onPw5+KiaF9u10m7lq66J9//7q1tfWff/9619JFllAi529tbT17/Gho3+5WW4X27Vanq7/u4OaN9R+Vi//4+q9fyvV/Hv707PGjC4akWRaUL0bUvy5dOrh5I4EJgAcQmAhMEQPTqNFjjx49Jk7qDQ2NDQ2N9lTkklFkYBo1euz58+cLCgpFmBDreWra9C++uCBmaGhotGSL2Bdpr/XI96L+VH1Hjov813/9l2URvfX852efvfeL2eVrXv7vv30lEsbZ40c/D39qSSr2iZvmTPvbXz4XEUf+1BKYZLJRE9XZ40fFdBG5vv7rl47Jpv6jcjHdMTDZF7RMOXv8qEtmIjABSCAEJgJTTJfkZNpQs0hLS9hxeKmhoXH//hKZDJYvX/nFFxfE6I5MDGrYUmeQwzAxLtJe61HDlv3NRlqkpaXFsojeeo5+dFhckjt3surz8KdqDJLpxHGimmMcc48amNQ4ZQlM//z71+rAkhqYNs2Z5hKYLAvaX8Pn4U/tMY7ABCDhEJgITNEDkxgxEuM0aoRyvORUUFDY0NDoOOiixiw1TDw1bfr58+fVoBP7Iu2ynlWr18iBKPkWIuVFdZGTJ0+qi6gDWm1az+7t20Vgqisp/jz8qX2cxj6cIyaG9u3+218+F5lm05xpX57/sz0wiatjltSiBiZ5ZU2uSqafUwdK5LU5l0tyckF7YLIENQITgARFYCIwRQlMjmnJHk0sIzoEpvgJTCLZnD1+VM1DlsCkpis5YiTubXIPTJYFCUwAvIrARGByC0yON+J0crpbSAYC9W5icRsTl+SirqcDLslZFncMTAu+eyPUqQMlMiG5Bya5oOMlOcdfRGACkFgITAQmt5u+z58/bw9G9lziOC4lkxY3fUddTwfc9H1w88Z//v1rywCVS2DaNGea+HycvDwnb1dyvOfJMTBZ7jQnMAFIXAQmAlPEwGR5goAcLLFfaVq+fOXFixfVcGCJCzF+tr+srNz+/AKNxwrorcf+OAD1s4GX81iBqOvpsMcKqPlG/u/BzRv/demSmEdetpMPFJDU2WQIsyxoeayAS1oiMAFILAQmAlP7PLjy5KlTjp+YaxNxfcr+nAJT61m+fOXJU6dcZvDwgys/3rXN5RFK7YLABCCBEJgITO0QmJYvX9nSEr78gBLpk3em1tPQ0Gi5290/gUk+UIDABAC7CUwEJr4a5XJ4ODB1AAITgARCYCIwEZgITAQmAIiCwERgIjARmAhMABAFgYnARGAiMBGYACAKAhOB6YoEpoKCwtbWVvc7pgsKCtWP+rsTT1SyPOCgk+3ZB/I3NjQ0qo/QdPmSYPUZm47rFMs6vgA1MImnCajvSH0N9k0h5hcrT7upe9MH+1pbW7/+4vNNc6apH9dvbW0VzzdSP65vf9xAIiIwAUggBCYC0xUJTCIrWB7XdDmBSQ0Z6mobGhrFSix5RbwAl8QmA1BZWbl4NpJYVqSlSC/M8gJkYBIBUX0Bck6xcjWQuQem/a+v+ttfPrc8NkkEpn9duiQ+6i++wc0yT8IhMAFIIAQmAlMbAlN2n5Smn088l5tzLjfnV1kDI80mviVt//4S9zzULoFJXVubApMakuT8ZWXlYj2RnkrgGJjkqiypS4YkufJYAlNZ4dtiMEkdQLIEpgVD0s4ePxr1yZBxjsAEIIEQmAhMsQYmNS25ZybxJSQiNMiUoF7nEjlGBiYx2COig/v3rrgEJksoUS+HOaYfx8AkHsmtXvayjAzZA5N48eL7ieUKLStXs1HUwLRpzjQ5gGR5nLcamMRlO3VKwiEwAUggBCYCU6yBacfEB9S0dC435+T08bd1T7LMpn59W0NDo+PXlagjTC++uNDxG+tiDExqDrMHKflT+/rVH8mvK5GBSeQk+21J9sDU0NAov2NYhiTLcFdbA9MC5VtHxDe72QOTfUrCITABSCAEJgJTTIGpe7DLBz99yBKYmn4+MbtPin3kRj71W/2OOcugiwxM58+fd7/VKcYRJktGsUx3vOlb5iTxwkR4UkeqLFfW7C9gz5496u3hclDqo48+vpwRJhkpxDfByZu+GWECAFMITOYDU+rTU3tmPhC7OB9hkl8963hFTL1DSPz3hQtfxn4nk0tgkiNGlvuWIgUplbwBvKCgUP0VUQOT+ik5+53j7vcwqUkuUmCSOamu4pDjPUzyu3ITEYEJQAIhMJkPTG01/N0CI4EplnuYnpo2/YsvLqg3/djv7BajOOqPysrKY8xMlrwi7x+SV8EstxzJJOQ+iKUO9qgfarOPDMUYmDrF8Ck5Ob5VUFCYdlP3r/7U0traeu5klRopxM1M9sBkv8kpERGYACQQApNJmft2jKx8r01EZkqbNzuqrskp7RuYLJnpifR+9hkKCgot0USMtciRGzXTqFlKfqitrTd9x/IcJjm/GqrU5ypZUpF8RoB9aCr2wNQp2nOYLL+otbX1qz+1vD7yXvsjl0L7dtsnJvTFOAITgIRDYEowsQ9E3faTR9s9MMGCJ30TmAD4BIEpwQzfszWrtMidGIjKKi2KZYWDNq45l5tz47hRt0x5rPeMqbc9O/22Z6f3mvKY8SySEAhMBCYAPkFg8qCs0qLYB6IePFJyLjcn5ZknUhfNTVv5UvprvxJuuON243Ek/hGYCEwAfILA5E3Dd2+J0dDtb57Lzbk5Z3yvp5/oO29m6ovP3vXqEgITgYnABAAqApPf2S/J3bViMYGJwERgAgAVgcnvCEwEJgITAERFYPK7SIEp9cU54gbw256dHry1t/FoEp8ITAQmAD5BYPI7e2BK+9Uv5K3fQq8pj91wx+033HF755uTjWeUuEJgIjAB8AkCk985PlYg9YXZqS8+m/ris/bwRGYiMBGYAPgQgcnvHAOTlLpw7l0rFgvpa5ZybxOBicAEwJ8ITH43aOOafbmPRwpMKm4GJzC1e2A6+uRYAhOAhEBg8rtBG9fszX38xvEEpo4ITDd0vn50n54Tb7/V4ul7+vozMB15cuxLGQQmAAmAwOR3gzauLZr30/SHR6VMeaz3jKku7nj5xbSVL3VJTb3mmuv8LkJguqZTZ/cFH+zd842H7nWxOuueeffd4RNLhvWvnDp6yfC7Xx8zZAeBCUB8IzD53eA3X8tcnrfz548VP/v4vrk/OZebg0jeeXTE96++9uqr/5fMTGpgEmnpnZws468z/h17aszRJ8d8/OSY/LH3vzQs/c1xQ3/3oxHGe0MAcEFg8rvBb60fuH75Xctf6vv87H7zZ/d7YXbq887S1y4d8JtVsUhfu/SHj4wVut87sNO1P/CMc7k5amaSgUmkpXO5Odd1vuHaa38w//47tz08zMVvRg967cF7v2PkwGWZ97yUke4TSzLSl2SkLx6Wvm7U4LcnZOzMITABiGsEJt8reGNQ/uqB65cPWPNK+spfuhiwdtmgt19zNLgw//6dm4Rhvy/I2LtN1e3Ou67rfINnqJlp6dKllrTU6dofXNf5hoonRrk4MPnBTeOGvj5mCN4cN/TtCRnbJmW+a7orBAB3BCZsGFLwxuC31g9+87VBG9cO2rjmMg393abhvy8URpTvffBIiSp5eMb1wW6Jq/MPuqqZafHixdd0us6Sljr/oGvDrEeEQ1NGCfsff3D7pEyodkzK/N2PRuzMGUFaAhD/CEy4grLe2znqxIHRp8ulO+f9PNglKXFZMtP8+fPtaen6YLc/PvsjcbOO8RYOAGgXBCZ0kKzSotGny4ds+Y3x0NOOmWnunDn2tBTskiTvbjbewgEA7YLAhA4yfM9WbwSmpK7d70hOvi+l5+BePatyHx/cq2f/m28c3KtnWo8evW68WcxDYAIAjyEwoYMM373FA4Hp9uQfZqf2ye7XJ7PvrUN7p+xav+quHt0H9+o5tHdKZt9bs/v1ub93r5u63URgAgCPITChgyR6YOp6Q/f7eqVkp/b5t359Mvveujd/vZqWxI8e6NubwAQAHkNgQgdJ9MA0QE1L32amg1vfGtanl0hLs4fc/etxwwQCEwB4DIEJHSShA9MtN95sTUupfbJT+3y8q1COLTXOesT+SGvjLRwA0C4ITOggIjCNPl3e/fY7jQegtsroc6tjYDqx7935U6c8mHpbdmofe1pqnj3ReAsHALQLAhM6zkOhD0efLu+ZmWk8ALXJTd1uckxL2al9/nXpm/MfFm9evVINTJ9MnyAcemK08RYOAGgXBCZ0nJGV7yViYLrt5mTHtPTNP/7x5xcmn8vN+T+luzevXikD04dTRgsfTBllvIUDANoFgQkdJ0EDU/otPV3SkvDlgeKv9hRaAtOHU0bv+fFI440cAHD5CEzoOCIw9Ro/1ngGapP7vvv5uB8PH/bn+upzzz9uuWPpq3ff/usfdpyb+6gamPb+xHwjBwBcvsAzx8uAjvHIybLRp8t//Mm//3f1kbLCj/7tUBzXx7/fdaRoq+r/1nzy5d5tlsD0//75339+YXL4+cfPvjRTOrN0TtMruQCARMcIEzqO/KCc3YBXlxofSYok7YcOl+RKtxZ8vrtATUtHZuVUPjVOHV76cMro3z9m/q8iAMDlC1AU5V7X/c//kf6/O9sVv/Wb/3x387ncnEv/+Mf9PbvbZ0gNXmv6tVMURVHtVMb/fNdw6GTY+GtA0Dc7Iqlr90iPFdi+evlX5/40un+a40/Tb+nJvvAbdkT8YF/ECc/sCAIT9PlnRzh+UC6qpK7d2Rd+w46IH+yLOOGZHUFggj7/7Iikrt0f6Nu7TWkp7YcdN7zkq30R59gR8YN9ESc8syMITNDnqx3R+6Yesael+3v36npDxw0v+W1fxDN2RPxgX8QJz+wIAhP0+W1HxJiZOj4t+XBfxC12RPxgX8QJz+wIAhP0+XBHJHXtbnmOpeqBvr1vuzmZfeFn7Ij4wb6IE57ZEQQm6PPtjkjq2v22m5PTb+l5X68U4fbkH95y483sC7Aj4gf7Ik54ZkcQmKCPHRE/2Bdxgh0RP9gXccIzO4LABH3siPjBvogT7Ij4wb6IE57ZEQkZmAAAADpSrIFpxszZFy9+3draeunSpVdXrXGZuHXr9tbW1osXv54xc7Z98dbW1q1bt6tr3rp1u7p4RcXh1m+rouKwmPjqqjWXLl2yrNZxoly8sbFJ/go552effTZhwqQrN7FjOL7HxsYmud3kFhb7wv4iJ0yY9Nlnn6mLy3XKbS7mse8y+YvknI6Lq3M6Lu744h3n1JvYARyP/0jvUc7vflTHfvw77lzHOdVdKWf2WKNw3BpiY1pejNoXyR1kbz5yo6mHtPqL7HNajkDHRhF0an1eahSRtkbQdvzH+MbVFarTY28Uco+rc8Y+0UuNQj341Y7Lfbs5thT3/j9S83FsFHKivfFaJhpvFLEGptLS9+WWlQeT40RxiFy4cEENTBUVh8UGsvxI7BJLYLL3L1VVIbHJGhubxE/F/hBve+vW7WKbzpg5+9ixKvlTMeeMmbMvXLgg1i8XvxITO4bjexQvw949qXPau3LZBtQNKN/X1q3bZcd08eLX9olyPzouXlFxWKxfnfPVVWvC4T9OmDBJfUmOc17mxI7hePw7vke5j2RP4XgARzr+7XNaGoXYApHWKWdQjw0PNwp1m6vbIWhrNequcexDLW9EbQvqr3BsKfZGEXRqfR5uFJaIoB7/bXrj6vYXEyOdFNwbhVx57BM92SjkcevSbzu2lNj7f7nH1TU4zjlj5uzPPvtMrErdbvaJ8dAo2nxJzv04jjSP+lpPn65WN2hp6fvqVrafMKQJEyaFw38Uc6q/Qp1u31Vqu5VLXYmJV+i4d6EejpF6fMvBF/y2n6qqCql/NMj1yD2lLm5pBmKruixuaaJyBrW/a2xsEv9hn/MyJ3b8jrCEQst7VLeYfVMEv3sA24//qIe6Y0cg57TsffliPNko7G/WctqWJ2nLgjEGJpfeKRj57Ki2KXvr82qjsGwry/Ef+xt3302OLSIYoVHIHRT7RE82Cst2U1+knDlSS1H3pn03WU4flj3oOKfaak6frpYpyjIxThpFmwOT/a9V+0THI0P8eaF2XmKjW87HjkN2clRTvmExNKWOzaoNSf1TT92F8mi4EhMv/8huE8sfu46DjWKgVR3Ak+3E8e+q4Hdbgtwj9kFROcVxcfs+lXvT8pIc57zMiR28I4K249++2eVBov4J5XgA249/90Nd/anjnKLjC4f/qB4e3msU9m0up1v6nHD4j+JigTpzpLF6e49fVRWKdIVFtpRIbcre+hxffEI3CnktRn2D9uM/9jeuzmw5y1hOCuqvkw1BPQDk9o99oicbhWXbWkZGxfzuLcW9/5e/Rd3dLnM67krLxDhpFG0LTLGkpWDkS3JiE1iCv+MAhuN4oGWi3KAXLly4cOGC3NaWJOG9c4P9PUpqT+E40T686X7EW9KSJC9CtSkwiZO32GJi8ThpBpfD/teC5T2qm8jyF7bjARyM+VC37277nGrGknvNk43CcYPYA5Ps/e3Htn1xe2BSI5Fl8CnqWcTe+hwPGA80imCE+Gg5/mN548FvW4TjSJJ9R1h2op8DU6Sj2v5Ktir3MMmhNZeW4t7/y9liCUxqmFajs2VinDSKNgQmx1Esx4mWwKTuHvm6K5SbWx1TsOWPMMf9YV+/Pat57+qD+2903CPyoFHv+JN/BUYaU3XcBcFvj37Zf8V+SU4dUW+XMVXjVx/crxqIn8oQI8uyiGNP6rjxHZuS4wuTc6pD63IR7zUKdbtZhiXso9rByO3I5SKCZee6txR7o3BpfR5rFPYj0PH4j/GNR9rC6i5WQ4mlUXBJLmhrFC6HhOwu3FuKe/8f6Rc5zqm+NpeJcdIoYg1MjiMNkYYf7IFJvVJgGRqJOsI0YcKk0tL35USXIa5I4ysx3ot3mRM7huN7dPzpjJmzd+/eIydaXqR6ZMtWrb6vrd+9kV/Iz3/TMnIbaXG5fvVgaPzunZiWv7bVOS9zYsdwPP4d36P6U8e/OixHteOyUVfuMqdlhMl7jSLSoW4JTJZDtK0jTHJt6vZ3bCmOjUI9cuQe91ij2L17j3wN9s2ibs/Y37h9GzqeFFyuS1iuRMc+0XuNwuWQUDegY0uJvf+37+5Ic6rNUB4SkSYabxSxBqZG5WO3shk4TnR8QeofGS6BRl2negrZ6vShR/uclj9l1EPEM5+gdnyP8r6B1ggf17SnTMufAhW2W2fUIUDZNtRfpO5H++LqDpJzqotb/hCxr/MyJ3YAx+M/0nuUi6gnDJdN4T7RMlyhnn3ti8uZ1XFcLzWKYORD3RKY1BfpuMuiBlz7L3JsKcEIjUL+SC7usUbheLA5bs/Y3/irTjcg208KkRrFjJifIOA40WONwn6VJtLx795Sovb/Qdfm43imcDy/O0401Sh4cCUAAEAUBCYAAIAoCEwAAABREJgAAACiIDABAABEQWACAACIgsAEAAAQBYEJAAAgCgITAABAFAQmAACAKAhMAAAAURCYAAAAoiAwAQAAREFgAgAAiILABAAAEAWBCQAAIAoCEwAAQBQEJgAAgCgITAAAAFEQmAAAAKIgMAEAAERBYAIAAIiCwAQAABAFgQkAACAKAhMAAEAUBCYAAIAoCEwAAABREJgAAACiIDABAABEQWACAACIgsAEAAAQRSCPStgyfvQA8LwQRVGhUCgUCpg+6VP6ZbwnBeB5oVComaKo5uaA6ZM+pV/Ge1IAnkdgoihRAdMnfUq/jPekADyPwERRogKmT/qUfhnvSQF4HoGJokQFTJ/0Kf0y3pMC8DwCE0WJCpg+6VP6ZbwnBeB5BCaKEhUwfdKn9Mt4TwrA8whMFCUqYPqkT+mX8Z4UgOcRmChKVMD0SZ/SL+M9KTxp166isFJ1dXWbN2/p2y/Ncc6qqqqRI8cYf824cghMFCUqkJeXd+rUqfLy8qqqqpqaGnkyLioqqqmpKSoqysvLKykpqampaWpqqqmpKSkpETPUfFticROBwe9lvCeFJ+3aVVRbWzd5ytRgl6QeySmvrlrT2NiYn/+m8RcGIwhMFCUqUFxcHA6Hi4uLa2pqwuGwPBnL6SUlJeFwuKamprKyUswjMlM4HG5qapIT6+vr8/PzjWUHX5bxnhSepAamYJekHskpZWXlBw8eEj86fvzE4Y8+amhomDtvvjrC9NPJPysvrxDdyqFDZWPHPSwWX7ZsRXV1dTgcrq6uXrZshfF3h7YiMFGUqMCJEyeampry8vIiBaaqqip1uhhnysvLEylKTBShqrKysiPjAmW8J4UnuQemM2fOvLz0V3JOEZjuGTCooqKioqJizNgJGRlZxcV733//g/7pAxcsXFRfX79hQ/6daXdv3ryluqbmmWdmBbmWl1AITBQlKhAOh8UFtfBXwagAAAteSURBVEiBqby8PBwOHzt2rLCwMC8vr6ioSFynUwNTnhKkqA4r4z0pPMlySW7pK8vkJTlL0JH/u2DBovr6+qWvLJMrGT9+4tBhmSUlpYcPH+6fPjDYJWnylKm1tXXr1q03/gbRJgQmihIVCIfDIglFCkx5eXlikElcd5P3MFkCk7ifqUPzgu/LeE8KT3K56TtSYFq3bn1dXd3Ppk5T1zNy5BjZdcgiMCUcAhNFiQqcOnVKnH1dAlNeXl5hYWF5eXlTU5MckSIwGS/jPSk8yXJJzvKjtgamkpJS4+8Il4PARFGiAnLEyHKvkrgSV1xcfOLEiaqqKjnd8R6m/Pz8cDgssxfVMWW8J4UnaQQm+yW5jIys/ukDS0pKKyuPZGRkGX9T0EZgoihRAXn2PXDggLhXKT8/v7CwsL6+vrm5OS8v79SpU83NzWKoqbi4uLm5WQQjcYWuuLi4uLi4vr4+HA6Le5uoDivjPSk8SSMwqTd9Z2eP2rt3n7jpe/HiX9bX1//2twV9+6U988ysd97ZLT89h0RBYKIoUQH1BKzecNDc3CwGn/Lz88XVOlFNTU3ypm/7zFRHlvGeFJ6kEZiC332swP7972VnjxLzyMcKnD17Vk7nU3IJhMBEUaIClnNwUVGRGDSyPFRJTpdTir8tcc841fFlvCcF4HkEJooSFTB90qf0y3hPCsDzCEwUJSpg+qRP6ZfxnhSA5xGYKEpUwPRJn9Iv4z0pAM8jMFGUqIDpkz6lX8Z7UgCeR2CiKFEB0yd9Sr+M96QAPI/ARFGiAqZP+pR+Ge9JAXgegYmiRAVMn/Qp/TLekwLwPAITRYkKmD7pU/plvCcF4HkhiqJCoVAoFDDeGgEAAOIcgQkAACAKAhMAAEAUBCYAAIAoCEwAAABREJgAAACiIDABAABEQWACAACIgsAEAAAQBYEJAAAgioDpr/eg9Mv40QPA80x/HQVFxUsFTJ/0Kf0y3pMC8LwQX75LUc3NzXz5bkKX8Z4UgOcRmChKVMD0SZ/SL+M9KQDPIzBRlKiA6ZM+pV/Ge1IAnkdgoihRAdMnfUq/jPekADyPwERRogKmT/qUfhnvSQF4HoGJokQFTJ/0Kf0y3pMC8DwCE0WJCpg+6VP6ZbwnBYJdksaPn7h33x8WLswLdklauDBv774/jB8/0firQnshMFGUqIDpkz6lX8Z7UnhSj+SUDRvy6+rqwuFwc3NzeXnFTyf/zGX+yVOm1tbWrVu3Ptglad269bW1dZOnTDX+LtBeCEwUJSpg+qRP6ZfxnhSe9Nprv66vr3911ZoeySkTJz1aVlZ+4sQnEyc9Gml+ApO3EZgoSlTA9Emf0i/jPSk86eDBQ2Vl5T2SU8T/zpg5u7a2bsXKVcFvB58aGhpaWlqOHz8xZ87cIIHJ6whMFCUqYPqkT+mX8Z4UnlS4dVttbd2CBYvsPxKDT7/85dKMjKzi4r3Hj58YO+5hx8A0cuSYqqqqXbuKjL8dXCYCE0WJCpg+6VP6ZbwnhSdlZ486cODgp59+euLEJ9u27ZAX44YOy6ysPFJcvFf87y8WLa6trfvFosWMMHkbgYmiRAVMn/Qp/TLek8LDnpr2zI4dO0+ePHnm7NkthVt7JKeIYBRW6syZMwQmzyMwUZSogOmTPqVfxntSeJ64aampqWnJkpdFMCoo2GKZh8DkbQQmihIVMH3Sp/TLeE8K7xH3HqmpSOYhcUmutPR9eT+4ZYYggcmLCEwUJSpg+qRP6ZfxnhTe0yM5ZefOXTU1tStWrurbLy07e9SePcUNDQ3znpsf7JL069ffEE8c6Nsv7YUXFha9827/9IEEJm8jMFGUqIDpkz6lX8Z7UnhS335pb7zxm+rq6paWlubm5lAoNO+5F8SP5GMFwuFwU1PTjh077xkwiE/JeRuBiaJEBUyf9Cn9Mt6TAvA8AhNFiQqYPulT+mW8JwXgeQQmihIVMH3Sp/TLeE8KwPMITBQlKmD6pE/pl/GeFIDnEZgoSlTA9Emf0i/jPSkAzyMwUZSogOmTPqVfxntSAJ5HYKIoUQHTJ31Kv4z3pAA8j8BEUaICpk/6lH4Z70kBeB6BiaJEBUyf9Cn9Mt6TAvC8EEVRoVAoFAoYb40AAABxjsAEAAAQBYEJAAAgCgITAABAFAQmAACAKAhMAAAAURCYAAAAoiAwAQAAREFgAgAAiILABAAAEEXg7bfeCnZJ4t9E/Bdod/FwYPMv//Iv/8bhv4wwAQAAREFgAgAAiILABAAAEAWBCQAAIAoCEwAAQBSBPCphy/jRA8DzQhRFhUKhUChg+qRP6ZfxnhSA54VCoWaKopqbA6ZP+pR+Ge9J49OePcWTp0w1/jIAbyAwUZSogOmTPqVfxnvSeLNu3fpwOLxrV5HxVwJ4BoGJokQFTJ/0Kf0y3pPGj8lTptbW1oXD4aqqqpEjxxh/PYBnEJgoSlTA9Emf0i/jPWmcOHjwUPjy6uDBQ8bfBRCfCEwUJSpg+qRP6ZfxnjQeiMtwBCbgCiEwUZSogOmTPqVfxnvS+MElOeAKITBRlKiA6ZM+pV/Ge9J4w03fQLsjMFGUqIDpkz6lX8Z70vjEYwUu065dRfJiZUtLS3V19erVa3skp7TX+tetW19bW8c+ShQEJooSFTB90qf0y3hPmohGjhxTXLyXy3Yudu0qkoGmb7+0jRs3NTU1LVnysvEXBiMITBQlKmD6pE/pl/GeNEFx5c6dGpiCXZJGjR4fOn5cbq6fTv5ZRUVFS0vLmTNnduzYec+AQcEuSfcMGLRjx86mpqaWlpbTp08vXPjvgzM7e9T+/e+Jvmb//veys0cFlRGmJUtebmhokFFs48ZN1dXVP3l8SrBL0rJlK6qrq8PhcHV19bJlK4xvEz8jMFGUqIDpkz6lX8Z70gQ1cuSYqqqqcDh85syZXyxabPz1xBvHwLRjx06x6Y4ePfbBhx9mZGQtWLCopqY2P//NYJekjW9uqqmpXbBgUY/klFWr1h4/fuJnU6f1Tx/4/vsfHDt27JGJOVOffPr48RO7d/8+qAQmsSNEFOuRnHLgwMHS0vd7JKcsWLiovr5+w4b8O9Pu3rx5S3VNzTPPzFJnRkciMFGUqIDpkz6lX8Z70nig3nCjV3ywzr5JLZfkamvr5j03P9glacXKVbW1dTNmzhZzHjx46ODBQ1kjHjp27Fhx8V65hqHDMsePnzh33vza2rqlryyTqxWbWr2HSU584okna2pqVq1eG+ySVFJSevjw4f7pA4Pffv5x3br1xjeLbxGYKEpUwPRJn9Iv4z1pPLj8wMTlOfdNevbs2fz8N8VN3/atffDgIZFp1v/6Dct67I/Isgem555/obq6eu68+StWrjp16tRPHp8ix//UIjAZRGCiKFEB0yd9Sr+M96QJikty7tQRph7JKRs25J85c2bZsuXiR6dPn3700cfV+V0CU2Nj49x58+3T5fozMrIqK48UFGwpKSkV1+PE3ikpKTW+HSAQmChKVMD0SZ/SL+M9aYLipm93Ljd9r1i5qqGh4bnnX1Dnt1+S658+MCMja+68+fX19eIqm2X7q+sv3LotFAqdOPHJipWrxJSSktLKyiMZGVnGNwWCBCaK+rYCpk/6lH4Z70kTEY8ViMoSmNS7rceOe/jYsWNlZeVjxk7Izh61bdsOMUQnb/ru2y9t7drXxE3f9wwY9MEHH4ZCoalPPn3PgEEbN25au/a1oC0wPff8C42NjerA1eLFv6yvr//tbwv69kt75plZ77yze+y4h41vFt8iMFGUqIDpkz6lX8Z7UniSJTD1Tx9YVlZeUVEhniAgHyvQ0tISCoXmzJkb/O5jBY4fPyEmBpXHCojHDYgHBFgC09BhmZWVRyzX4ORjBc6ePSueR8Cn5EwhMFGUqP8Puo3/IeLvlYkAAAAASUVORK5CYII=)
Title: Re: Graphene GUI testing and feedback
Post by: Shentist on October 21, 2015, 05:39:20 pm
if you use the search function for assets and for example you put "trade" into account it will find 1 asset, but the used assets or child assets trade.btc and trade.ltc are not found.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 21, 2015, 07:06:17 pm

Precision slip when viewing "Market Depth". Gets worse as you switch between horizontal and vertical.

(http://i.imgur.com/lr0j10g.png)
(https://bitsharestalk.org/data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAxAAAAFRCAIAAABrANxKAAAgAElEQVR4nO3df3QV1d3v8fPnXXctW8Ur9SCXoJJiEISokSgoCAQTIvJbodHWgkURgYIBRaEEqVgeQH5JlQbREsKPQpQSKCYqkAQNkAMC+R2IOS29eB8r2j7YPpXVu3L/2HWv7cycOSebkH3OzPu7Xoulk5nJOTOz93yyZ86cQLBLEgA9hw4dutK/4lxujrD7xw8CAEwJGD/lAImLwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAXzsGpv948H7HJkpgAoB4QGAC9LVXYBp0ay8ZjCIx3lkAgJ8RmAB97RWYHux3m3taqp/5iPHOAgD8jMAE6Gv3wNQ465EDU0ZblE5+yHhPAQA+R2AC9LV7YGIkCQDiE4EJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPkFgAvQRmADAJwhMgD4CEwD4BIEJ0EdgAgCfIDAB+ghMAOATBCZAH4EJAHyCwAToIzABgE8QmAB9BCYA8AkCE6CPwAQAPhFImzfbXerTU7smpxg/MwFxiMAEAD4RGH26PKrU6VONn5mAOERgAgCfCGSVFrkYWfne6NPlWaVFQ7ZsSERp82YbP6fCwwhMAOATAffAkblvRyxDUPHM+DkVHkZgAgCfiBKYhmzZkFH02+G7tyQix/w08uP9sQ9QDVj5sryXq2dmpvHTM+INgQkAfCJ6YEpcIw4Vt+9gVc/MB9pd99vvNH7WhzYCEwD4hJcDk6PYB8wy9+2Q93Jd0YuG8ZCZrg92g4b9+/e3y3oy+/ZumPVIw6xHQtPGbZ+U6RM7JmX+7kcjduaMeNd0PwgAUfkuMOnJem/nyMr32t2oEwdGny43frGv1403Fz48/J1HR7z76AgxzgFcUceeGnP0yTGVU0dvHj/s7QkZ2yZlkpkAxDkCk0niQ4hmA9P1wW6FDz/Qs0uXq7539b9dhVhNmTKlXdZzS/D6uQP7zR3Yb9bdfXL69fSDR1NvmX7XrWVPPLR+1OC3J2TszBlhvDcEABcEJgJTt3dysq763tXf/36n7199LdokNze3XdbTp1vXZcPTlw1Pf2nIndPvvs0/jkwds3hY+pvjhv7uRwQmAHGNwERg6vbOo1lXfe/q71997TXXXIc2Wbx4cbus544bk9546N43Hrp3ddY98+67wz+OPjn2pYz018cM2TEp03hvCAAuCEwEpm7ncnNkYOrUqTNi98orr7TLetJu6v722MFvjx38+sh7FwxJ84l5991xLjdn8bD+r48Zsp3ABCC+EZgITN3O5eZcdRWBicBkKjClE5gAxD8CE4GJwERgIjABQBQEJgITgYnARGACgCgITAQmAhOBicAEAFEQmAhMBCYCE4EJAKIgMBGYCEwEJgITAERBYCIwEZgITAQmAIiCwERgcgtMBQWFra2tra2t58+fHzV6bKdOnZ+aNv3ixYut39Y333yzfPlKewIoKChUfySXunjx4lPTpouJy5ev/Oabb9SVq2JfpL3WU1ZWLt5UWVm5/R05LtLS0mJfRGM9Rz86LBY5d7JK5onPw5+KiaF9u10m7lq66J9//7q1tfWff/9619JFllAi529tbT17/Gho3+5WW4X27Vanq7/u4OaN9R+Vi//4+q9fyvV/Hv707PGjC4akWRaUL0bUvy5dOrh5I4EJgAcQmAhMEQPTqNFjjx49Jk7qDQ2NDQ2N9lTkklFkYBo1euz58+cLCgpFmBDreWra9C++uCBmaGhotGSL2Bdpr/XI96L+VH1Hjov813/9l2URvfX852efvfeL2eVrXv7vv30lEsbZ40c/D39qSSr2iZvmTPvbXz4XEUf+1BKYZLJRE9XZ40fFdBG5vv7rl47Jpv6jcjHdMTDZF7RMOXv8qEtmIjABSCAEJgJTTJfkZNpQs0hLS9hxeKmhoXH//hKZDJYvX/nFFxfE6I5MDGrYUmeQwzAxLtJe61HDlv3NRlqkpaXFsojeeo5+dFhckjt3surz8KdqDJLpxHGimmMcc48amNQ4ZQlM//z71+rAkhqYNs2Z5hKYLAvaX8Pn4U/tMY7ABCDhEJgITNEDkxgxEuM0aoRyvORUUFDY0NDoOOiixiw1TDw1bfr58+fVoBP7Iu2ynlWr18iBKPkWIuVFdZGTJ0+qi6gDWm1az+7t20Vgqisp/jz8qX2cxj6cIyaG9u3+218+F5lm05xpX57/sz0wiatjltSiBiZ5ZU2uSqafUwdK5LU5l0tyckF7YLIENQITgARFYCIwRQlMjmnJHk0sIzoEpvgJTCLZnD1+VM1DlsCkpis5YiTubXIPTJYFCUwAvIrARGByC0yON+J0crpbSAYC9W5icRsTl+SirqcDLslZFncMTAu+eyPUqQMlMiG5Bya5oOMlOcdfRGACkFgITAQmt5u+z58/bw9G9lziOC4lkxY3fUddTwfc9H1w88Z//v1rywCVS2DaNGea+HycvDwnb1dyvOfJMTBZ7jQnMAFIXAQmAlPEwGR5goAcLLFfaVq+fOXFixfVcGCJCzF+tr+srNz+/AKNxwrorcf+OAD1s4GX81iBqOvpsMcKqPlG/u/BzRv/demSmEdetpMPFJDU2WQIsyxoeayAS1oiMAFILAQmAlP7PLjy5KlTjp+YaxNxfcr+nAJT61m+fOXJU6dcZvDwgys/3rXN5RFK7YLABCCBEJgITO0QmJYvX9nSEr78gBLpk3em1tPQ0Gi5290/gUk+UIDABAC7CUwEJr4a5XJ4ODB1AAITgARCYCIwEZgITAQmAIiCwERgIjARmAhMABAFgYnARGAiMBGYACAKAhOB6YoEpoKCwtbWVvc7pgsKCtWP+rsTT1SyPOCgk+3ZB/I3NjQ0qo/QdPmSYPUZm47rFMs6vgA1MImnCajvSH0N9k0h5hcrT7upe9MH+1pbW7/+4vNNc6apH9dvbW0VzzdSP65vf9xAIiIwAUggBCYC0xUJTCIrWB7XdDmBSQ0Z6mobGhrFSix5RbwAl8QmA1BZWbl4NpJYVqSlSC/M8gJkYBIBUX0Bck6xcjWQuQem/a+v+ttfPrc8NkkEpn9duiQ+6i++wc0yT8IhMAFIIAQmAlMbAlN2n5Smn088l5tzLjfnV1kDI80mviVt//4S9zzULoFJXVubApMakuT8ZWXlYj2RnkrgGJjkqiypS4YkufJYAlNZ4dtiMEkdQLIEpgVD0s4ePxr1yZBxjsAEIIEQmAhMsQYmNS25ZybxJSQiNMiUoF7nEjlGBiYx2COig/v3rrgEJksoUS+HOaYfx8AkHsmtXvayjAzZA5N48eL7ieUKLStXs1HUwLRpzjQ5gGR5nLcamMRlO3VKwiEwAUggBCYCU6yBacfEB9S0dC435+T08bd1T7LMpn59W0NDo+PXlagjTC++uNDxG+tiDExqDrMHKflT+/rVH8mvK5GBSeQk+21J9sDU0NAov2NYhiTLcFdbA9MC5VtHxDe72QOTfUrCITABSCAEJgJTTIGpe7DLBz99yBKYmn4+MbtPin3kRj71W/2OOcugiwxM58+fd7/VKcYRJktGsUx3vOlb5iTxwkR4UkeqLFfW7C9gz5496u3hclDqo48+vpwRJhkpxDfByZu+GWECAFMITOYDU+rTU3tmPhC7OB9hkl8963hFTL1DSPz3hQtfxn4nk0tgkiNGlvuWIgUplbwBvKCgUP0VUQOT+ik5+53j7vcwqUkuUmCSOamu4pDjPUzyu3ITEYEJQAIhMJkPTG01/N0CI4EplnuYnpo2/YsvLqg3/djv7BajOOqPysrKY8xMlrwi7x+SV8EstxzJJOQ+iKUO9qgfarOPDMUYmDrF8Ck5Ob5VUFCYdlP3r/7U0traeu5klRopxM1M9sBkv8kpERGYACQQApNJmft2jKx8r01EZkqbNzuqrskp7RuYLJnpifR+9hkKCgot0USMtciRGzXTqFlKfqitrTd9x/IcJjm/GqrU5ypZUpF8RoB9aCr2wNQp2nOYLL+otbX1qz+1vD7yXvsjl0L7dtsnJvTFOAITgIRDYEowsQ9E3faTR9s9MMGCJ30TmAD4BIEpwQzfszWrtMidGIjKKi2KZYWDNq45l5tz47hRt0x5rPeMqbc9O/22Z6f3mvKY8SySEAhMBCYAPkFg8qCs0qLYB6IePFJyLjcn5ZknUhfNTVv5UvprvxJuuON243Ek/hGYCEwAfILA5E3Dd2+J0dDtb57Lzbk5Z3yvp5/oO29m6ovP3vXqEgITgYnABAAqApPf2S/J3bViMYGJwERgAgAVgcnvCEwEJgITAERFYPK7SIEp9cU54gbw256dHry1t/FoEp8ITAQmAD5BYPI7e2BK+9Uv5K3fQq8pj91wx+033HF755uTjWeUuEJgIjAB8AkCk985PlYg9YXZqS8+m/ris/bwRGYiMBGYAPgQgcnvHAOTlLpw7l0rFgvpa5ZybxOBicAEwJ8ITH43aOOafbmPRwpMKm4GJzC1e2A6+uRYAhOAhEBg8rtBG9fszX38xvEEpo4ITDd0vn50n54Tb7/V4ul7+vozMB15cuxLGQQmAAmAwOR3gzauLZr30/SHR6VMeaz3jKku7nj5xbSVL3VJTb3mmuv8LkJguqZTZ/cFH+zd842H7nWxOuueeffd4RNLhvWvnDp6yfC7Xx8zZAeBCUB8IzD53eA3X8tcnrfz548VP/v4vrk/OZebg0jeeXTE96++9uqr/5fMTGpgEmnpnZws468z/h17aszRJ8d8/OSY/LH3vzQs/c1xQ3/3oxHGe0MAcEFg8rvBb60fuH75Xctf6vv87H7zZ/d7YXbq887S1y4d8JtVsUhfu/SHj4wVut87sNO1P/CMc7k5amaSgUmkpXO5Odd1vuHaa38w//47tz08zMVvRg967cF7v2PkwGWZ97yUke4TSzLSl2SkLx6Wvm7U4LcnZOzMITABiGsEJt8reGNQ/uqB65cPWPNK+spfuhiwdtmgt19zNLgw//6dm4Rhvy/I2LtN1e3Ou67rfINnqJlp6dKllrTU6dofXNf5hoonRrk4MPnBTeOGvj5mCN4cN/TtCRnbJmW+a7orBAB3BCZsGFLwxuC31g9+87VBG9cO2rjmMg393abhvy8URpTvffBIiSp5eMb1wW6Jq/MPuqqZafHixdd0us6Sljr/oGvDrEeEQ1NGCfsff3D7pEyodkzK/N2PRuzMGUFaAhD/CEy4grLe2znqxIHRp8ulO+f9PNglKXFZMtP8+fPtaen6YLc/PvsjcbOO8RYOAGgXBCZ0kKzSotGny4ds+Y3x0NOOmWnunDn2tBTskiTvbjbewgEA7YLAhA4yfM9WbwSmpK7d70hOvi+l5+BePatyHx/cq2f/m28c3KtnWo8evW68WcxDYAIAjyEwoYMM373FA4Hp9uQfZqf2ye7XJ7PvrUN7p+xav+quHt0H9+o5tHdKZt9bs/v1ub93r5u63URgAgCPITChgyR6YOp6Q/f7eqVkp/b5t359Mvveujd/vZqWxI8e6NubwAQAHkNgQgdJ9MA0QE1L32amg1vfGtanl0hLs4fc/etxwwQCEwB4DIEJHSShA9MtN95sTUupfbJT+3y8q1COLTXOesT+SGvjLRwA0C4ITOggIjCNPl3e/fY7jQegtsroc6tjYDqx7935U6c8mHpbdmofe1pqnj3ReAsHALQLAhM6zkOhD0efLu+ZmWk8ALXJTd1uckxL2al9/nXpm/MfFm9evVINTJ9MnyAcemK08RYOAGgXBCZ0nJGV7yViYLrt5mTHtPTNP/7x5xcmn8vN+T+luzevXikD04dTRgsfTBllvIUDANoFgQkdJ0EDU/otPV3SkvDlgeKv9hRaAtOHU0bv+fFI440cAHD5CEzoOCIw9Ro/1ngGapP7vvv5uB8PH/bn+upzzz9uuWPpq3ff/usfdpyb+6gamPb+xHwjBwBcvsAzx8uAjvHIybLRp8t//Mm//3f1kbLCj/7tUBzXx7/fdaRoq+r/1nzy5d5tlsD0//75339+YXL4+cfPvjRTOrN0TtMruQCARMcIEzqO/KCc3YBXlxofSYok7YcOl+RKtxZ8vrtATUtHZuVUPjVOHV76cMro3z9m/q8iAMDlC1AU5V7X/c//kf6/O9sVv/Wb/3x387ncnEv/+Mf9PbvbZ0gNXmv6tVMURVHtVMb/fNdw6GTY+GtA0Dc7Iqlr90iPFdi+evlX5/40un+a40/Tb+nJvvAbdkT8YF/ECc/sCAIT9PlnRzh+UC6qpK7d2Rd+w46IH+yLOOGZHUFggj7/7Iikrt0f6Nu7TWkp7YcdN7zkq30R59gR8YN9ESc8syMITNDnqx3R+6Yesael+3v36npDxw0v+W1fxDN2RPxgX8QJz+wIAhP0+W1HxJiZOj4t+XBfxC12RPxgX8QJz+wIAhP0+XBHJHXtbnmOpeqBvr1vuzmZfeFn7Ij4wb6IE57ZEQQm6PPtjkjq2v22m5PTb+l5X68U4fbkH95y483sC7Aj4gf7Ik54ZkcQmKCPHRE/2Bdxgh0RP9gXccIzO4LABH3siPjBvogT7Ij4wb6IE57ZEQkZmAAAADpSrIFpxszZFy9+3draeunSpVdXrXGZuHXr9tbW1osXv54xc7Z98dbW1q1bt6tr3rp1u7p4RcXh1m+rouKwmPjqqjWXLl2yrNZxoly8sbFJ/go552effTZhwqQrN7FjOL7HxsYmud3kFhb7wv4iJ0yY9Nlnn6mLy3XKbS7mse8y+YvknI6Lq3M6Lu744h3n1JvYARyP/0jvUc7vflTHfvw77lzHOdVdKWf2WKNw3BpiY1pejNoXyR1kbz5yo6mHtPqL7HNajkDHRhF0an1eahSRtkbQdvzH+MbVFarTY28Uco+rc8Y+0UuNQj341Y7Lfbs5thT3/j9S83FsFHKivfFaJhpvFLEGptLS9+WWlQeT40RxiFy4cEENTBUVh8UGsvxI7BJLYLL3L1VVIbHJGhubxE/F/hBve+vW7WKbzpg5+9ixKvlTMeeMmbMvXLgg1i8XvxITO4bjexQvw949qXPau3LZBtQNKN/X1q3bZcd08eLX9olyPzouXlFxWKxfnfPVVWvC4T9OmDBJfUmOc17mxI7hePw7vke5j2RP4XgARzr+7XNaGoXYApHWKWdQjw0PNwp1m6vbIWhrNequcexDLW9EbQvqr3BsKfZGEXRqfR5uFJaIoB7/bXrj6vYXEyOdFNwbhVx57BM92SjkcevSbzu2lNj7f7nH1TU4zjlj5uzPPvtMrErdbvaJ8dAo2nxJzv04jjSP+lpPn65WN2hp6fvqVrafMKQJEyaFw38Uc6q/Qp1u31Vqu5VLXYmJV+i4d6EejpF6fMvBF/y2n6qqCql/NMj1yD2lLm5pBmKruixuaaJyBrW/a2xsEv9hn/MyJ3b8jrCEQst7VLeYfVMEv3sA24//qIe6Y0cg57TsffliPNko7G/WctqWJ2nLgjEGJpfeKRj57Ki2KXvr82qjsGwry/Ef+xt3302OLSIYoVHIHRT7RE82Cst2U1+knDlSS1H3pn03WU4flj3oOKfaak6frpYpyjIxThpFmwOT/a9V+0THI0P8eaF2XmKjW87HjkN2clRTvmExNKWOzaoNSf1TT92F8mi4EhMv/8huE8sfu46DjWKgVR3Ak+3E8e+q4Hdbgtwj9kFROcVxcfs+lXvT8pIc57zMiR28I4K249++2eVBov4J5XgA249/90Nd/anjnKLjC4f/qB4e3msU9m0up1v6nHD4j+JigTpzpLF6e49fVRWKdIVFtpRIbcre+hxffEI3CnktRn2D9uM/9jeuzmw5y1hOCuqvkw1BPQDk9o99oicbhWXbWkZGxfzuLcW9/5e/Rd3dLnM67krLxDhpFG0LTLGkpWDkS3JiE1iCv+MAhuN4oGWi3KAXLly4cOGC3NaWJOG9c4P9PUpqT+E40T686X7EW9KSJC9CtSkwiZO32GJi8ThpBpfD/teC5T2qm8jyF7bjARyM+VC37277nGrGknvNk43CcYPYA5Ps/e3Htn1xe2BSI5Fl8CnqWcTe+hwPGA80imCE+Gg5/mN548FvW4TjSJJ9R1h2op8DU6Sj2v5Ktir3MMmhNZeW4t7/y9liCUxqmFajs2VinDSKNgQmx1Esx4mWwKTuHvm6K5SbWx1TsOWPMMf9YV+/Pat57+qD+2903CPyoFHv+JN/BUYaU3XcBcFvj37Zf8V+SU4dUW+XMVXjVx/crxqIn8oQI8uyiGNP6rjxHZuS4wuTc6pD63IR7zUKdbtZhiXso9rByO3I5SKCZee6txR7o3BpfR5rFPYj0PH4j/GNR9rC6i5WQ4mlUXBJLmhrFC6HhOwu3FuKe/8f6Rc5zqm+NpeJcdIoYg1MjiMNkYYf7IFJvVJgGRqJOsI0YcKk0tL35USXIa5I4ysx3ot3mRM7huN7dPzpjJmzd+/eIydaXqR6ZMtWrb6vrd+9kV/Iz3/TMnIbaXG5fvVgaPzunZiWv7bVOS9zYsdwPP4d36P6U8e/OixHteOyUVfuMqdlhMl7jSLSoW4JTJZDtK0jTHJt6vZ3bCmOjUI9cuQe91ij2L17j3wN9s2ibs/Y37h9GzqeFFyuS1iuRMc+0XuNwuWQUDegY0uJvf+37+5Ic6rNUB4SkSYabxSxBqZG5WO3shk4TnR8QeofGS6BRl2negrZ6vShR/uclj9l1EPEM5+gdnyP8r6B1ggf17SnTMufAhW2W2fUIUDZNtRfpO5H++LqDpJzqotb/hCxr/MyJ3YAx+M/0nuUi6gnDJdN4T7RMlyhnn3ti8uZ1XFcLzWKYORD3RKY1BfpuMuiBlz7L3JsKcEIjUL+SC7usUbheLA5bs/Y3/irTjcg208KkRrFjJifIOA40WONwn6VJtLx795Sovb/Qdfm43imcDy/O0401Sh4cCUAAEAUBCYAAIAoCEwAAABREJgAAACiIDABAABEQWACAACIgsAEAAAQBYEJAAAgCgITAABAFAQmAACAKAhMAAAAURCYAAAAoiAwAQAAREFgAgAAiILABAAAEAWBCQAAIAoCEwAAQBQEJgAAgCgITAAAAFEQmAAAAKIgMAEAAERBYAIAAIiCwAQAABAFgQkAACAKAhMAAEAUBCYAAIAoCEwAAABREJgAAACiIDABAABEQWACAACIgsAEAAAQRSCPStgyfvQA8LwQRVGhUCgUCpg+6VP6ZbwnBeB5oVComaKo5uaA6ZM+pV/Ge1IAnkdgoihRAdMnfUq/jPekADyPwERRogKmT/qUfhnvSQF4HoGJokQFTJ/0Kf0y3pMC8DwCE0WJCpg+6VP6ZbwnBeB5BCaKEhUwfdKn9Mt4TwrA8whMFCUqYPqkT+mX8Z4UgOcRmChKVMD0SZ/SL+M9KTxp166isFJ1dXWbN2/p2y/Ncc6qqqqRI8cYf824cghMFCUqkJeXd+rUqfLy8qqqqpqaGnkyLioqqqmpKSoqysvLKykpqampaWpqqqmpKSkpETPUfFticROBwe9lvCeFJ+3aVVRbWzd5ytRgl6QeySmvrlrT2NiYn/+m8RcGIwhMFCUqUFxcHA6Hi4uLa2pqwuGwPBnL6SUlJeFwuKamprKyUswjMlM4HG5qapIT6+vr8/PzjWUHX5bxnhSepAamYJekHskpZWXlBw8eEj86fvzE4Y8+amhomDtvvjrC9NPJPysvrxDdyqFDZWPHPSwWX7ZsRXV1dTgcrq6uXrZshfF3h7YiMFGUqMCJEyeampry8vIiBaaqqip1uhhnysvLEylKTBShqrKysiPjAmW8J4UnuQemM2fOvLz0V3JOEZjuGTCooqKioqJizNgJGRlZxcV733//g/7pAxcsXFRfX79hQ/6daXdv3ryluqbmmWdmBbmWl1AITBQlKhAOh8UFtfBXwagAAAteSURBVEiBqby8PBwOHzt2rLCwMC8vr6ioSFynUwNTnhKkqA4r4z0pPMlySW7pK8vkJTlL0JH/u2DBovr6+qWvLJMrGT9+4tBhmSUlpYcPH+6fPjDYJWnylKm1tXXr1q03/gbRJgQmihIVCIfDIglFCkx5eXlikElcd5P3MFkCk7ifqUPzgu/LeE8KT3K56TtSYFq3bn1dXd3Ppk5T1zNy5BjZdcgiMCUcAhNFiQqcOnVKnH1dAlNeXl5hYWF5eXlTU5MckSIwGS/jPSk8yXJJzvKjtgamkpJS4+8Il4PARFGiAnLEyHKvkrgSV1xcfOLEiaqqKjnd8R6m/Pz8cDgssxfVMWW8J4UnaQQm+yW5jIys/ukDS0pKKyuPZGRkGX9T0EZgoihRAXn2PXDggLhXKT8/v7CwsL6+vrm5OS8v79SpU83NzWKoqbi4uLm5WQQjcYWuuLi4uLi4vr4+HA6Le5uoDivjPSk8SSMwqTd9Z2eP2rt3n7jpe/HiX9bX1//2twV9+6U988ysd97ZLT89h0RBYKIoUQH1BKzecNDc3CwGn/Lz88XVOlFNTU3ypm/7zFRHlvGeFJ6kEZiC332swP7972VnjxLzyMcKnD17Vk7nU3IJhMBEUaIClnNwUVGRGDSyPFRJTpdTir8tcc841fFlvCcF4HkEJooSFTB90qf0y3hPCsDzCEwUJSpg+qRP6ZfxnhSA5xGYKEpUwPRJn9Iv4z0pAM8jMFGUqIDpkz6lX8Z7UgCeR2CiKFEB0yd9Sr+M96QAPI/ARFGiAqZP+pR+Ge9JAXgegYmiRAVMn/Qp/TLekwLwPAITRYkKmD7pU/plvCcF4HkhiqJCoVAoFDDeGgEAAOIcgQkAACAKAhMAAEAUBCYAAIAoCEwAAABREJgAAACiIDABAABEQWACAACIgsAEAAAQBYEJAAAgioDpr/eg9Mv40QPA80x/HQVFxUsFTJ/0Kf0y3pMC8LwQX75LUc3NzXz5bkKX8Z4UgOcRmChKVMD0SZ/SL+M9KQDPIzBRlKiA6ZM+pV/Ge1IAnkdgoihRAdMnfUq/jPekADyPwERRogKmT/qUfhnvSQF4HoGJokQFTJ/0Kf0y3pMC8DwCE0WJCpg+6VP6ZbwnBYJdksaPn7h33x8WLswLdklauDBv774/jB8/0firQnshMFGUqIDpkz6lX8Z7UnhSj+SUDRvy6+rqwuFwc3NzeXnFTyf/zGX+yVOm1tbWrVu3Ptglad269bW1dZOnTDX+LtBeCEwUJSpg+qRP6ZfxnhSe9Nprv66vr3911ZoeySkTJz1aVlZ+4sQnEyc9Gml+ApO3EZgoSlTA9Emf0i/jPSk86eDBQ2Vl5T2SU8T/zpg5u7a2bsXKVcFvB58aGhpaWlqOHz8xZ87cIIHJ6whMFCUqYPqkT+mX8Z4UnlS4dVttbd2CBYvsPxKDT7/85dKMjKzi4r3Hj58YO+5hx8A0cuSYqqqqXbuKjL8dXCYCE0WJCpg+6VP6ZbwnhSdlZ486cODgp59+euLEJ9u27ZAX44YOy6ysPFJcvFf87y8WLa6trfvFosWMMHkbgYmiRAVMn/Qp/TLek8LDnpr2zI4dO0+ePHnm7NkthVt7JKeIYBRW6syZMwQmzyMwUZSogOmTPqVfxntSeJ64aampqWnJkpdFMCoo2GKZh8DkbQQmihIVMH3Sp/TLeE8K7xH3HqmpSOYhcUmutPR9eT+4ZYYggcmLCEwUJSpg+qRP6ZfxnhTe0yM5ZefOXTU1tStWrurbLy07e9SePcUNDQ3znpsf7JL069ffEE8c6Nsv7YUXFha9827/9IEEJm8jMFGUqIDpkz6lX8Z7UnhS335pb7zxm+rq6paWlubm5lAoNO+5F8SP5GMFwuFwU1PTjh077xkwiE/JeRuBiaJEBUyf9Cn9Mt6TAvA8AhNFiQqYPulT+mW8JwXgeQQmihIVMH3Sp/TLeE8KwPMITBQlKmD6pE/pl/GeFIDnEZgoSlTA9Emf0i/jPSkAzyMwUZSogOmTPqVfxntSAJ5HYKIoUQHTJ31Kv4z3pAA8j8BEUaICpk/6lH4Z70kBeB6BiaJEBUyf9Cn9Mt6TAvC8EEVRoVAoFAoYb40AAABxjsAEAAAQBYEJAAAgCgITAABAFAQmAACAKAhMAAAAURCYAAAAoiAwAQAAREFgAgAAiILABAAAEEXg7bfeCnZJ4t9E/Bdod/FwYPMv//Iv/8bhv4wwAQAAREFgAgAAiILABAAAEAWBCQAAIAoCEwAAQBSBPCphy/jRA8DzQhRFhUKhUChg+qRP6ZfxnhSA54VCoWaKopqbA6ZP+pR+Ge9J49OePcWTp0w1/jIAbyAwUZSogOmTPqVfxnvSeLNu3fpwOLxrV5HxVwJ4BoGJokQFTJ/0Kf0y3pPGj8lTptbW1oXD4aqqqpEjxxh/PYBnEJgoSlTA9Emf0i/jPWmcOHjwUPjy6uDBQ8bfBRCfCEwUJSpg+qRP6ZfxnjQeiMtwBCbgCiEwUZSogOmTPqVfxnvS+MElOeAKITBRlKiA6ZM+pV/Ge9J4w03fQLsjMFGUqIDpkz6lX8Z70vjEYwUu065dRfJiZUtLS3V19erVa3skp7TX+tetW19bW8c+ShQEJooSFTB90qf0y3hPmohGjhxTXLyXy3Yudu0qkoGmb7+0jRs3NTU1LVnysvEXBiMITBQlKmD6pE/pl/GeNEFx5c6dGpiCXZJGjR4fOn5cbq6fTv5ZRUVFS0vLmTNnduzYec+AQcEuSfcMGLRjx86mpqaWlpbTp08vXPjvgzM7e9T+/e+Jvmb//veys0cFlRGmJUtebmhokFFs48ZN1dXVP3l8SrBL0rJlK6qrq8PhcHV19bJlK4xvEz8jMFGUqIDpkz6lX8Z70gQ1cuSYqqqqcDh85syZXyxabPz1xBvHwLRjx06x6Y4ePfbBhx9mZGQtWLCopqY2P//NYJekjW9uqqmpXbBgUY/klFWr1h4/fuJnU6f1Tx/4/vsfHDt27JGJOVOffPr48RO7d/8+qAQmsSNEFOuRnHLgwMHS0vd7JKcsWLiovr5+w4b8O9Pu3rx5S3VNzTPPzFJnRkciMFGUqIDpkz6lX8Z70nig3nCjV3ywzr5JLZfkamvr5j03P9glacXKVbW1dTNmzhZzHjx46ODBQ1kjHjp27Fhx8V65hqHDMsePnzh33vza2rqlryyTqxWbWr2HSU584okna2pqVq1eG+ySVFJSevjw4f7pA4Pffv5x3br1xjeLbxGYKEpUwPRJn9Iv4z1pPLj8wMTlOfdNevbs2fz8N8VN3/atffDgIZFp1v/6Dct67I/Isgem555/obq6eu68+StWrjp16tRPHp8ix//UIjAZRGCiKFEB0yd9Sr+M96QJikty7tQRph7JKRs25J85c2bZsuXiR6dPn3700cfV+V0CU2Nj49x58+3T5fozMrIqK48UFGwpKSkV1+PE3ikpKTW+HSAQmChKVMD0SZ/SL+M9aYLipm93Ljd9r1i5qqGh4bnnX1Dnt1+S658+MCMja+68+fX19eIqm2X7q+sv3LotFAqdOPHJipWrxJSSktLKyiMZGVnGNwWCBCaK+rYCpk/6lH4Z70kTEY8ViMoSmNS7rceOe/jYsWNlZeVjxk7Izh61bdsOMUQnb/ru2y9t7drXxE3f9wwY9MEHH4ZCoalPPn3PgEEbN25au/a1oC0wPff8C42NjerA1eLFv6yvr//tbwv69kt75plZ77yze+y4h41vFt8iMFGUqIDpkz6lX8Z7UniSJTD1Tx9YVlZeUVEhniAgHyvQ0tISCoXmzJkb/O5jBY4fPyEmBpXHCojHDYgHBFgC09BhmZWVRyzX4ORjBc6ePSueR8Cn5EwhMFGUqP8Puo3/IeLvlYkAAAAASUVORK5CYII=)
I noticed this one too and fixed it this morning, will have in next update
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 21, 2015, 07:07:30 pm
if you use the search function for assets and for example you put "trade" into account it will find 1 asset, but the used assets or child assets trade.btc and trade.ltc are not found.
Known issue, still waiting on a new api call to upgrade this search.

Until that gets implemented the search has to be exact.
Title: Re: Graphene GUI testing and feedback
Post by: DestBest on October 21, 2015, 07:10:29 pm
Precision slip when viewing "Market Depth". Gets worse as you switch between horizontal and vertical.
Same here. Gets worse as you input price.
 

(http://i.imgur.com/2WHT1KQ.png)
What is this?
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 21, 2015, 07:31:49 pm
Precision slip when viewing "Market Depth". Gets worse as you switch between horizontal and vertical.
Same here. Gets worse as you input price.
 

(http://i.imgur.com/2WHT1KQ.png)
What is this?
Just refresh and it will be back to normal.

Technical explanation is that it's a hack to make highstock display x-axis values with decimals by applying a multiplier to make the values larger than 1, then divide by the same factor when displaying the values. Only problem was the array that I applied it to was mutable so changes persist between mounts of the component.

Trdl: already fixed in dev, a refresh will clear it

Edit: Sorry it was late and I thought you were referring to the same issue as the previous post.
Title: Re: Graphene GUI testing and feedback
Post by: xeroc on October 21, 2015, 07:41:05 pm
(http://i.imgur.com/2wWkVXv.png)
This also a display bug? Refresh doesn't help for me?!
Title: Re: Graphene GUI testing and feedback
Post by: yvv on October 21, 2015, 07:58:53 pm
Same thing for me. Lowest ask and highest bid are crossing for USD:BTS, but no trade occurs.
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 21, 2015, 08:08:29 pm
same thing was mentioned here: https://bitsharestalk.org/index.php/topic,19306.msg247950.html#msg247950

Alt was trying to explain that it is the intended function of the current market rules.

I don't believe this is true.  Or, I really hope its not true.  Its plain dumb if that's how its supposed to work.
please tell me this is a display bug.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 21, 2015, 09:17:57 pm
same thing was mentioned here: https://bitsharestalk.org/index.php/topic,19306.msg247950.html#msg247950

Alt was trying to explain that it is the intended function of the current market rules.

I don't believe this is true.  Or, I really hope its not true.  Its plain dumb if that's how its supposed to work.
please tell me this is a display bug.
alt is right, thats how it works. Since bm always uses flipped markets to explain its just so hard to understand.

I've made a reply in the other thread also.
Title: Re: Graphene GUI testing and feedback
Post by: botfund on October 21, 2015, 11:04:56 pm
same thing was mentioned here: https://bitsharestalk.org/index.php/topic,19306.msg247950.html#msg247950

Alt was trying to explain that it is the intended function of the current market rules.

I don't believe this is true.  Or, I really hope its not true.  Its plain dumb if that's how its supposed to work.
please tell me this is a display bug.

 +5%
Title: Re: Graphene GUI testing and feedback
Post by: maqifrnswa on October 21, 2015, 11:11:11 pm
same thing was mentioned here: https://bitsharestalk.org/index.php/topic,19306.msg247950.html#msg247950

Alt was trying to explain that it is the intended function of the current market rules.

I don't believe this is true.  Or, I really hope its not true.  Its plain dumb if that's how its supposed to work.
please tell me this is a display bug.

Maybe not show the "yellow" orders since they aren't "valid" (as in, they won't be executed) yet? It does seem confusing to people, and this does appear to be an internal market matching feature that might not need to be exposed to users.

EDIT: Those yellow orders should only show up when the highest bid (in BTS:USD) is less than the margin call price. That's the only time it will be be a "valid" ask, and the ask will be at the margin call price.
Title: Re: Graphene GUI testing and feedback
Post by: botfund on October 21, 2015, 11:15:36 pm
same thing was mentioned here: https://bitsharestalk.org/index.php/topic,19306.msg247950.html#msg247950

Alt was trying to explain that it is the intended function of the current market rules.

I don't believe this is true.  Or, I really hope its not true.  Its plain dumb if that's how its supposed to work.
please tell me this is a display bug.

The current rule makes the order book look silly and I think this should be changed to something like:

A margin call will occur any time the highest bid is greater than SQP and CALL PRICE is greater than SQP.
Title: Re: Graphene GUI testing and feedback
Post by: yvv on October 21, 2015, 11:39:55 pm
This is indeed confusing. People make decisions based on order book. If the order is not going to be executed, just don't show it, or show it different way.
Title: Re: Graphene GUI testing and feedback
Post by: ag on October 22, 2015, 04:42:06 am
since about a day ago the site does not work on chrome version 40 for mac.  ( I use an outdated version of chrome ). I get "Loading..." screen, even with new chrome profile ( I originally thought my cache got corrupted). But I did backup my 2.0 wallets, and was able to import them on safari  9.0. SO you were legacy compatible with version 40... but not anymore.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 22, 2015, 05:59:35 am
(http://i.imgur.com/2wWkVXv.png)
This also a display bug? Refresh doesn't help for me?!

I thought he was referring to the same issue as above him.

(http://i.imgur.com/2WHT1KQ.png)

Like I've said elsewhere, this is not a bug but a "feature" of the market engine. Because there are sell orders below the narrow range of [CALL LIMIT, MARGIN CALL PRICE] the call orders will not execute. I'm showing them because I believe this behaviour is crazy and that margin called orders should be allowed to buy at a fair price, that is to say below their call limit.

If everyone who has sell orders below the call limit (in red from ~34 to 43.51637 in that picture) would now cancel their orders, the sells inside the range [CALL LIMIT, MARGIN CALL PRICE] would fill instantly, so the orders are there, it's just weird mechanics of the market engine making them not execute.
Title: Re: Graphene GUI testing and feedback
Post by: maqifrnswa on October 23, 2015, 01:30:45 am
Like I've said elsewhere, this is not a bug but a "feature" of the market engine. Because there are sell orders below the narrow range of [CALL LIMIT, MARGIN CALL PRICE] the call orders will not execute. I'm showing them because I believe this behaviour is crazy and that margin called orders should be allowed to buy at a fair price, that is to say below their call limit.

If everyone who has sell orders below the call limit (in red from ~34 to 43.51637 in that picture) would now cancel their orders, the sells inside the range [CALL LIMIT, MARGIN CALL PRICE] would fill instantly, so the orders are there, it's just weird mechanics of the market engine making them not execute.

I agree it is a feature, but could it only be displayed when the orders are valid for execution? An order which cannot be executed by the market engine isn't a valid order and therefore shouldn't be displayed. At some point it may become valid, at that point it is appropriate to display it.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on October 23, 2015, 05:08:48 am
svk,
The last GUI (BitShares-light_2.15.288) is so bad in the light wallet...I had to downgrade... seriously the ability to actual click on the 'update your position' is kind of important- so it kind have to fit in the window...if you do want to do something with it ,that is.


PS
Anybody has any idea if the idiotic browser the light client is running inside of , has anything that  can do ctrl+/-?
Title: Re: Graphene GUI testing and feedback
Post by: emski on October 23, 2015, 05:39:29 am
svk,
The last GUI (BitShares-light_2.15.288) is so bad in the light wallet...I had to downgrade... seriously the ability to actual click on the 'update your position' is kind of important- so it kind have to fit in the window...if you do want to do something with it ,that is.


PS
Anybody has any idea if the idiotic browser the light client is running inside of , has anything that  can do ctrl+/-?
ctrl+scroll ?
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 23, 2015, 05:57:10 am
svk,
The last GUI (BitShares-light_2.15.288) is so bad in the light wallet...I had to downgrade... seriously the ability to actual click on the 'update your position' is kind of important- so it kind have to fit in the window...if you do want to do something with it ,that is.


PS
Anybody has any idea if the idiotic browser the light client is running inside of , has anything that  can do ctrl+/-?

I've never actually tried the light client myself, Valentine's the one handling that. I'll try to install it this weekend and see if I can make some improvements. I'm guessing I should test it on a low resolution screen?
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on October 23, 2015, 06:01:20 am
svk,
The last GUI (BitShares-light_2.15.288) is so bad in the light wallet...I had to downgrade... seriously the ability to actual click on the 'update your position' is kind of important- so it kind have to fit in the window...if you do want to do something with it ,that is.


PS
Anybody has any idea if the idiotic browser the light client is running inside of , has anything that  can do ctrl+/-?

I've never actually tried the light client myself, Valentine's the one handling that. I'll try to install it this weekend and see if I can make some improvements. I'm guessing I should test it on a low resolution screen?
1366 x 768 would be perfect for me. :(
Title: Re: Graphene GUI testing and feedback
Post by: xeroc on October 23, 2015, 07:07:58 am
svk,
The last GUI (BitShares-light_2.15.288) is so bad in the light wallet...I had to downgrade... seriously the ability to actual click on the 'update your position' is kind of important- so it kind have to fit in the window...if you do want to do something with it ,that is.


PS
Anybody has any idea if the idiotic browser the light client is running inside of , has anything that  can do ctrl+/-?
You can take this release here
https://github.com/bitshares/bitshares-2-ui/releases
unpack it and run it in your local Browser .. it's pretty much the same thing what the lightwallet does.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on October 23, 2015, 07:36:27 am
svk,
The last GUI (BitShares-light_2.15.288) is so bad in the light wallet...I had to downgrade... seriously the ability to actual click on the 'update your position' is kind of important- so it kind have to fit in the window...if you do want to do something with it ,that is.


PS
Anybody has any idea if the idiotic browser the light client is running inside of , has anything that  can do ctrl+/-?
You can take this release here
https://github.com/bitshares/bitshares-2-ui/releases
unpack it and run it in your local Browser .. it's pretty much the same thing what the lightwallet does.

Yee, thought about it.
What I really do not get is, being not the most tech savi of all users - what is the difference using this to just opening  open ledger in my browser?
Title: Re: Graphene GUI testing and feedback
Post by: cass on October 23, 2015, 07:43:41 am
svk,
The last GUI (BitShares-light_2.15.288) is so bad in the light wallet...I had to downgrade... seriously the ability to actual click on the 'update your position' is kind of important- so it kind have to fit in the window...if you do want to do something with it ,that is.


PS
Anybody has any idea if the idiotic browser the light client is running inside of , has anything that  can do ctrl+/-?
You can take this release here
https://github.com/bitshares/bitshares-2-ui/releases
unpack it and run it in your local Browser .. it's pretty much the same thing what the lightwallet does.

Yee, thought about it.
What I really do not get is, being not the most tech savi of all users - what is the difference using this to just opening  open ledger in my browser?

IIRC no difference except other theme skin
Title: Re: Graphene GUI testing and feedback
Post by: xeroc on October 23, 2015, 08:17:15 am
Ol will deliver these sources to you .. less disk space .. but more bandwidth and a little more risk for MITM attacks
Title: Re: Graphene GUI testing and feedback
Post by: valzav on October 24, 2015, 01:40:46 pm
svk,
The last GUI (BitShares-light_2.15.288) is so bad in the light wallet...I had to downgrade... seriously the ability to actual click on the 'update your position' is kind of important- so it kind have to fit in the window...if you do want to do something with it ,that is.


PS
Anybody has any idea if the idiotic browser the light client is running inside of , has anything that  can do ctrl+/-?

I've never actually tried the light client myself, Valentine's the one handling that. I'll try to install it this weekend and see if I can make some improvements. I'm guessing I should test it on a low resolution screen?
1366 x 768 would be perfect for me. :(

tonyk, I'm aware of too large fonts Windows issue - will address this asap.
Title: Re: Graphene GUI testing and feedback
Post by: yvv on October 24, 2015, 02:00:08 pm
Base and counter currencies don't flip in "Price Feed Data" table on asset explorer screen. Flips fine everywhere else.
Title: Re: Graphene GUI testing and feedback
Post by: bitacer on October 24, 2015, 07:30:35 pm
Is CCEDK gateway functional yet ?
Title: Anybody else think the GUI looks better with colours inverted. As an option?
Post by: JonnyB on October 25, 2015, 10:15:26 pm
http://i.imgur.com/vNw5n2b.png (http://i.imgur.com/vNw5n2b.png)

http://i.imgur.com/vNw5n2b.png
Title: Re: Anybody else think the GUI looks better with colours inverted. As an option?
Post by: cass on October 26, 2015, 08:27:27 am
http://i.imgur.com/vNw5n2b.png (http://i.imgur.com/vNw5n2b.png)

http://i.imgur.com/vNw5n2b.png

nice colors
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 27, 2015, 08:51:42 pm
Market history looks like its working, though it appears to be upside down?  The last trade should be on the top not the bottom.

Also regarding Market history.  I think the columns should be reversed. 

|  Price |  Amount  |  Value  | 

to reflect how it is displayed everywhere else on the page
Title: Re: Graphene GUI testing and feedback
Post by: fav on October 27, 2015, 09:11:54 pm
market history is nice, but there's a decimal bug it seems, you can't use the exchanges at all now.

testing?
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 27, 2015, 09:29:58 pm
Market history isn't updating either.  I've completed an order but the market history is unchanged.

Title: Re: Graphene GUI testing and feedback
Post by: gabes on October 27, 2015, 09:37:49 pm
Can't transfer BTS from wallet when pasting memo. Hit send does nothing.
If memo textarea empty, confirm dialog shows up correctly. Any idea?
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 27, 2015, 09:40:02 pm
Market history looks like its working, though it appears to be upside down?  The last trade should be on the top not the bottom.

Also regarding Market history.  I think the columns should be reversed. 

|  Price |  Amount  |  Value  | 

to reflect how it is displayed everywhere else on the page

I had no way of knowing what trade happened at what time happened when in that version because I didn't have a timestamp for each trade. BM has since added it to the api call so the latest version sorts things correctly and also included a short-form timestamp.

Good point about the column order, will fix that.

It should also update correctly now.
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 27, 2015, 10:03:58 pm
market history is nice, but there's a decimal bug it seems, you can't use the exchanges at all now.

testing?

I've just pushed a fix for this, Valentine will update the server asap.
Title: Re: Graphene GUI testing and feedback
Post by: valzav on October 27, 2015, 10:28:27 pm
market history is nice, but there's a decimal bug it seems, you can't use the exchanges at all now.

testing?

Fixed, thanks for testing.
Title: Re: Graphene GUI testing and feedback
Post by: yvv on October 27, 2015, 10:55:02 pm
Market history fixed. Cool! Is there any chance that base/counter asset flip will be fixed on asset explorer page, price feed data table?
Title: Re: Graphene GUI testing and feedback
Post by: clayop on October 28, 2015, 03:39:14 pm
IMO, the market list under the trading history is not useful. Please consider to remove it.
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 28, 2015, 04:43:05 pm
I would like to see on the Trade tab:  ||  Price | Volume | 24h %Change ||  If there are space constraints, I think this information is more valuable than both the current Base Supply and Quote supply columns.
Title: Re: Graphene GUI testing and feedback
Post by: clayop on October 28, 2015, 05:09:16 pm
I would like to see on the Trade tab:  ||  Price | Volume | 24h %Change ||  If there are space constraints, I think this information is more valuable than both the current Base Supply and Quote supply columns.

Svk said he's waiting for pertinent api, e.g. market_summary
Title: Re: Graphene GUI testing and feedback
Post by: tbone on October 28, 2015, 07:14:36 pm
@devs:  Thank you for getting the market history working!  This is a huge step in the right direction in terms of making this a platform traders can really use, which is imperative if we want enough liquidity to make Bitshares useful for everyone. 

Having said that, there are several things that can further improve usability, and I'll be providing feedback as I'm sure others are as well.  Thanks again!
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 28, 2015, 08:33:13 pm
@devs:  Thank you for getting the market history working!  This is a huge step in the right direction in terms of making this a platform traders can really use, which is imperative if we want enough liquidity to make Bitshares useful for everyone. 

Having said that, there are several things that can further improve usability, and I'll be providing feedback as I'm sure others are as well.  Thanks again!
You're welcome :)

There's actually a few bugs left in there that I've fixed this evening, notably the order type is inversed, buys instead of asks and vice versa, and the middle columns are reversed and the prices are a bit off. Will be fixed in next update.

Next up I'll try to get some 24h change and volume from the price history data.
Title: Re: Graphene GUI testing and feedback
Post by: clayop on October 28, 2015, 10:44:48 pm
From my experience, it is better to add an "include (trading) fee" option button into market orders.
Title: Re: Graphene GUI testing and feedback
Post by: lzr1900 on October 28, 2015, 11:10:03 pm
(http://chuantu.biz/t2/17/1446073601x1822610086.png)
why there are nothing showing up?
(http://chuantu.biz/t2/17/1446073928x1822610022.png)
every pairs shows the same result.
Title: Re: Graphene GUI testing and feedback
Post by: tbone on October 29, 2015, 12:13:40 am
IMO, the market list under the trading history is not useful. Please consider to remove it.

@clayop:
The market list on the exchange page is VERY useful if you're interested in watching more than one market and easily switching between them.    Granted, it's not as useful as it should be.  But that's only because it still needs work, as svk mentioned.  Give it a chance.  You'll see what I mean.  Poloniex has a similar feature and it's easily one of the best things about their UI. 

@svk:
I agree, replacing base supply with last price, volume (24h), price change (24h) in the list of markets on the trading UI would be great.  Also, if I could make a couple more suggestions related to the order book, please see "before/after" examples along with notes below: 


Current:
   Value    Amount   Price
   (BTC)   (BTS)   (BTC/BTS) 
------------------------------------------------
   0.0900000    6,750.0000    0.00001330
   0.0060000       449.9998    0.00001330
   0.0010000         80.0000    0.00001250
------------------------------------------------
  Last price: 0.00001    BTC/BTS   
------------------------------------------------
   0.0001000            8.5744    0.00001166
   0.2141000  19,463.6381   0.00001100   
   0.1200000  11,196.0000   0.00001072   


Suggested:

   Cost    Quantity   Bid/Ask
   (BTC)   (BTS)   (BTC/BTS) 
------------------------------------------------
   0.0900000    6,750.0000    0.00001333
   0.0060000       449.9998    0.00001333
   0.0010000         80.0000    0.00001250
------------------------------------------------
0.00001166  
------------------------------------------------
   0.0001000              8.5744    0.00001166
   0.2141000    19,463.6381    0.00001100 
   0.1200000    11,196.0000    0.00001072


1. In the market history table, you've already color coded the sells (red) and buys (green), which is perfect.  But color coding bid/ask on the order book is unconventional and a little confusing since a buy, for example, would be at the ask - and it's coded red on the order book - whereas the actual trade at that same ask price would be coded green in the trade history.  That doesn't make sense.  And reversing the color coding of the bids and asks on the order book would not make sense either.  So I would highly recommend NOT using red/green on the order book itself (except for the last price).  Instead, I would do what most of the other order books do i.e. simply use a larger and/or more bold font for the important part of the bid/ask.

2.  Speaking of highlighting the important part of the bid/ask, currently you are doing that for everything before the decimal point (both on order book and in market history).  That is great when there are non-zero numbers before the decimal.  But when there are leading zeroes, it would be much more helpful to highlight everything AFTER the leading zeroes. 

3. Please strip out the "Last price:" label and the units (e.g. BTC/BTS) indicator.  That text is unnecessary (obvious in the case of the last price label, and redundant in the case of the units indicator since it's in the order book column header) and makes the eyes have to dig for the relevant information.

4. The current order book column headers (Value - Amount - Price) are really too vague and practically all have the same meaning.  That's really not helpful.  Please consider using more precise headers instead (Cost - Quantity - Bid/Ask).  This really does make a difference.   

5. The last price is being truncated to only 5 decimal points instead of 8. 

Thanks again for your effort on this!
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 29, 2015, 12:36:27 am

1. In the market history table, you've already color coded the sells (red) and buys (green), which is perfect.  But color coding bid/ask on the order book is unconventional and a little confusing since a buy, for example, would be at the ask - and it's coded red on the order book - whereas the actual trade at that same ask price would be coded green in the trade history.  That doesn't make sense.  And reversing the color coding of the bids and asks on the order book would not make sense either.  So I would highly recommend NOT using red/green on the order book itself (except for the last price).  Instead, I would do what most of the other order books do i.e. simply use a larger and/or more bold font for the important part of the bid/ask.   
I like the color coding on the orderbook.  I hear what you're saying but it actually describes perfectly what is going on, and makes sense.  Any bid you make will go on the orderbook blue, its not always a market order like you describe, but a limit order to sit on the book.  If that bid happens to be higher than an existing red ask, the trade is executed and there's no reason to put the order on the book. Your bid to buy is the same as every other bid to buy, just a different price.  The colors are also helpful because each part can be flipped left to right in horizontal view so its an important reminder of how you have it oriented.  It would be confusing and laborious without the color.

Looking at various exchanges, I've not been able to find one that doesn't have some kind of color distinction between bid and ask. 

Quote
4. The current order book column headers (Value - Amount - Price) are really too vague and practically all have the same meaning.  That's really not helpful.  Please consider using more precise headers instead (Cost - Quantity - Bid/Ask).  This really does make a difference.   

Nearly every word you use in these cases will be vague with similar meanings.   Cost can be a price or a quantity, is also a value and an amount.   From exchange to exchange I have seen almost every one of those used for different things.   Whatever we chose is probably ok, just stay consistent.
Title: Re: Graphene GUI testing and feedback
Post by: clayop on October 29, 2015, 12:57:39 am
@clayop:
The market list on the exchange page is VERY useful if you're interested in watching more than one market and easily switching between them.    Granted, it's not as useful as it should be.  But that's only because it still needs work, as svk mentioned.  Give it a chance.  You'll see what I mean.  Poloniex has a similar feature and it's easily one of the best things about their UI. 
I understand now. Thanks for your insight!
What do you think about the fee including option?
Title: Re: Graphene GUI testing and feedback
Post by: speedy on October 29, 2015, 01:17:03 am
Minor suggestion:

Make the chart timeframe default to days - there isnt enough volume yet to show anything in 5min timeframes, and seeing low activity does not engender confidence.
Title: Re: Graphene GUI testing and feedback
Post by: Pheonike on October 29, 2015, 02:03:44 am

I suggest putting a thin line border around the chart and other sections on the trade page. The kind on border you have around titles in table views.  I think this would look better than having different color backgrounds.
Title: Re: Graphene GUI testing and feedback
Post by: tbone on October 29, 2015, 05:44:01 am

1. In the market history table, you've already color coded the sells (red) and buys (green), which is perfect.  But color coding bid/ask on the order book is unconventional and a little confusing since a buy, for example, would be at the ask - and it's coded red on the order book - whereas the actual trade at that same ask price would be coded green in the trade history.  That doesn't make sense.  And reversing the color coding of the bids and asks on the order book would not make sense either.  So I would highly recommend NOT using red/green on the order book itself (except for the last price).  Instead, I would do what most of the other order books do i.e. simply use a larger and/or more bold font for the important part of the bid/ask.   
I like the color coding on the orderbook.  I hear what you're saying but it actually describes perfectly what is going on, and makes sense.  Any bid you make will go on the orderbook blue, its not always a market order like you describe, but a limit order to sit on the book.  If that bid happens to be higher than an existing red ask, the trade is executed and there's no reason to put the order on the book. Your bid to buy is the same as every other bid to buy, just a different price. 

Historically, level 2 quotes (order books) have not color coded bid vs. ask.  Although I have to admit that more crypto trading sites than I realized ARE color coding bids in green and asks in red.  But still, many (including the most popular site, BitcoinWisdom) do NOT color code bid vs. ask.  While I do see the reasoning behind color coding on the order book, overall I think it makes more sense not to.  But I could live with it either way.

Market history is more clear cut.  In market history (historically called "time & sales"), a buy is defined as any trade that crosses the tape at or above the ask, and they should be coded green in market history.  A sell is defined as any trade that crosses the tape at or below the bid, and they should be coded red in market history.  Every site does it that way (I can find no exceptions).  Although I think right now we have that coded in reverse, and that should be fixed. 

Quote
The colors are also helpful because each part can be flipped left to right in horizontal view so its an important reminder of how you have it oriented.  It would be confusing and laborious without the color.

I have to disagree with this.  First, it's generally easy to see the difference between a market and it's flipped version just by the price (e.g. there's no mistaking .00001400 for 85,500).  Also, the order book colors currently do not switch when you flip the market.  And they really shouldn't.  Think about it, if you frequently watch, say, BTS:BTC by clicking it in the list of favorite markets, you would be used to blue on the bid and red on the ask.  If you flip it to BTC:BTS, now you have red on the bid and blue on the ask.  That seems fine.  But if you sometimes click on BTC:BTS in the list of favorite markets, now that same market will be coded the opposite of what you would expect.  The flipped version will also be opposite of what you would expect.  Let's please not do that.
Title: Re: Graphene GUI testing and feedback
Post by: donkeypong on October 29, 2015, 06:06:39 am
Sadly, I don't have time to read 19 pages of posts to see if this has been covered. So I'll just mention (and sorry if it's redundant): the "Wallets" button does not look like a button and is not even intuitive as a link. Please make that more prominent, and more obvious as the means for importing keys.
Title: Re: Graphene GUI testing and feedback
Post by: tbone on October 29, 2015, 06:27:31 am
@svk: The chart still has some real issues.  I recall Xeldal pointed some of these issues out, so I apologize if my list overlaps his:

1. The OHLC bars should be the same width as the volume bars. 

2. The vertical line of the crosshairs should be snapped to the bars as you move left and right.  That is working correctly.  On the other hand, the horizontal line should move up and down freely.  Currently that is not working, rendering this important functionality completely useless. 

3. The zoom slider at the bottom of the chart does not work.  The right end of it is not grabbable at all.  The left side is grabbable, but you can only slide it part of the way toward the right side before it automatically snaps back into it's original position.  You're also supposed to be able to slide the whole bar left and right, but that's not working.

4.  Please rename chart periods with single letter, lower-case abbreviations so they are more distinguishable. 

difficult to read:   1D | 4hrs | 1HR | 30MIN | 15MIN | 5MIN | 1MIN | 15S

easier to read:         1d  |  4h  |  1h  |  30m  |  15m  |  5m  |  1m  |  15s

5.  I know you stowed the chart periods in a settings cog to save space...but it's much more desirable to have the periods visible because a) that makes it much easier to see what period you're viewing, b) it's much easier to switch between periods.  I would make all of the periods visible as there is plenty of space if you just move the time, open, high, low, close, volume figures up a little.  Speaking of which, those figures are currently very difficult to read.  Below is an example of how it can be improved. 

difficult to read:     T:10/23/2015, 8:00:00AM   O:0.00001500   H:0.00001500   L:0.00001425   C:0.00001430   V:600,000

easier to read:     T: 10/23/2015, 8:00:00AM   O: 0.00001500   H: 0.00001500   L: 0.00001425   C: 0.00001430   V: 600,000

Thanks!
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 29, 2015, 05:06:48 pm
I don't know if its a GUI issue or something else, I posted this in Tech support?

Order book doesn't seem to match CLI "get_limit_orders"
https://bitsharestalk.org/index.php/topic,19581.0.html
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 29, 2015, 08:09:26 pm
Minor suggestion:

Make the chart timeframe default to days - there isnt enough volume yet to show anything in 5min timeframes, and seeing low activity does not engender confidence.

Done. BTW it will also remember your last setting between sessions and markets, but I agree it should be higher at least now with little data.
Title: Re: Graphene GUI testing and feedback
Post by: CalabiYau on October 30, 2015, 02:59:40 pm
upgraded to the latest "BitShares-light_2.0.151027.exe"  (WIN7/64) 

I see all accounts & balances on the dashboard, but no access to any, no reaction if I type on an account.   Switching Trade/Dashboard/Explore works mostly. New blocks are indicated.

Still getting this error, persistent in all versions:

(http://i.imgur.com/5w4T4lH.png)
Title: Re: Graphene GUI testing and feedback
Post by: Tuck Fheman on October 30, 2015, 03:03:52 pm
(http://i.imgur.com/5w4T4lH.png)

I don't know if this is related, but I had a similar issue and fixed it ... https://bitsharestalk.org/index.php/topic,19304.msg247929.html#msg247929
Title: Re: Graphene GUI testing and feedback
Post by: CalabiYau on October 30, 2015, 03:20:12 pm

I don't know if this is related, but I had a similar issue and fixed it ... https://bitsharestalk.org/index.php/topic,19304.msg247929.html#msg247929

Thx, I'll give it a try.

Edit: no changes
Title: Re: Graphene GUI testing and feedback
Post by: clayop on October 30, 2015, 11:45:11 pm
For me, 151030 version takes forever to load market data. (no price chart shown, no orders shown)
Title: Re: Graphene GUI testing and feedback
Post by: clayop on October 31, 2015, 01:09:14 am
For me, 151030 version takes forever to load market data. (no price chart shown, no orders shown)
After clean reinstall, it works smoothly
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 31, 2015, 03:48:53 pm
I'd like to see a quick way to get back to the trade page you last had open.  Often I find myself switching to the dashboard or explore tab and switching back to Trade tab only to have to search though the list again to find where i was.  Maybe at the top have a selection for last market

Also, the account selection drop down in Trade does not scroll.  If you have many accounts often you have to go back to the dashboard, select the account you want and then return to the Trade page.
Title: Re: Graphene GUI testing and feedback
Post by: clayop on October 31, 2015, 04:04:36 pm
Sometimes market loading is so slow. I am not sure it's my own problem or everyone's.
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on October 31, 2015, 06:53:05 pm
Sometimes market loading is so slow. I am not sure it's my own problem or everyone's.

For the most part they load pretty quick for me.  However, switching from BTS:USD to BTS:BTC  from the market select box in lower right, the new market doesn't load.  the depth graph and orderbook continue to display prices in BTS:USD.  It probably happens with other markets, this is just the one i saw.

(http://content.screencast.com/users/Enkianu/folders/Jing/media/3e5249df-b978-4c10-8008-bedb778b803e/2015-10-31_1444.png)

The market history in this case produces values from who knows where.  or there precision is off. IDK RED BOX
theres also a time format error that I see all the time BLUE ARROW
It looks like its loading the precision from BTS:BTC but using the data from BTS:USD
(http://content.screencast.com/users/Enkianu/folders/Jing/media/bda6b325-842a-4509-8028-882f09c18506/2015-10-31_1438.png)
Title: Re: Graphene GUI testing and feedback
Post by: tbone on November 01, 2015, 10:07:53 am
@svk: The chart still has some real issues.  I recall Xeldal pointed some of these issues out, so I apologize if my list overlaps his:

1. The OHLC bars should be the same width as the volume bars. 

2. The vertical line of the crosshairs should be snapped to the bars as you move left and right.  That is working correctly.  On the other hand, the horizontal line should move up and down freely.  Currently that is not working, rendering this important functionality completely useless. 

3. The zoom slider at the bottom of the chart does not work.  The right end of it is not grabbable at all.  The left side is grabbable, but you can only slide it part of the way toward the right side before it automatically snaps back into it's original position.  You're also supposed to be able to slide the whole bar left and right, but that's not working.

4.  Please rename chart periods with single letter, lower-case abbreviations so they are more distinguishable. 

difficult to read:   1D | 4hrs | 1HR | 30MIN | 15MIN | 5MIN | 1MIN | 15S

easier to read:         1d  |  4h  |  1h  |  30m  |  15m  |  5m  |  1m  |  15s

5.  I know you stowed the chart periods in a settings cog to save space...but it's much more desirable to have the periods visible because a) that makes it much easier to see what period you're viewing, b) it's much easier to switch between periods.  I would make all of the periods visible as there is plenty of space if you just move the time, open, high, low, close, volume figures up a little.  Speaking of which, those figures are currently very difficult to read.  Below is an example of how it can be improved. 

difficult to read:     T:10/23/2015, 8:00:00AM   O:0.00001500   H:0.00001500   L:0.00001425   C:0.00001430   V:600,000

easier to read:     T: 10/23/2015, 8:00:00AM   O: 0.00001500   H: 0.00001500   L: 0.00001425   C: 0.00001430   V: 600,000

Thanks!

I noticed some nice modifications yesterday:  1) time, open, high, low, close, and volume figures are now easier to distinguish, 2) chart period choices are now easier to distinguish, 3) orders in order book are now properly color coded (red for sells, green for buys), 4) prices with leading zeroes in both market history and the order book are much easier to read now that the value after the leading zeroes is highlighted. 5) chart zoom slider now works as it should, 6) horizontal crosshair on chart now moves freely, as it should. 

These modifications really make a difference.  Of course, there are still some outstanding trading UI issues that need to be addressed and I will provide further feedback along with a few others continuing to do so on this thread.  But I also wanted to thank svk et. al. for their continued efforts toward making this a UI befitting the best blockchain on the planet!

Title: Re: Graphene GUI testing and feedback
Post by: CalabiYau on November 01, 2015, 10:13:01 am
upgraded to the latest "BitShares-light_2.0.151027.exe"  (WIN7/64) 

I see all accounts & balances on the dashboard, but no access to any, no reaction if I type on an account.   Switching Trade/Dashboard/Explore works mostly. New blocks are indicated.


if it gets stuck - reload button is a blessing !
Title: Re: Graphene GUI testing and feedback
Post by: tbone on November 01, 2015, 11:18:14 am
I'd like to see a quick way to get back to the trade page you last had open. 

Yes!  We're making progress, but this issue is causing a real lack of grounding in the UI, leaving users feeling lost and/or stuck.  The solution is two-fold.  First, although Open Ledger is technically a wallet, it is marketed as an exchange.  Therefore, when the user clicks the "Trade" main menu item, the trading page should appear with the last viewed market visible (perhaps this page should even be the default page visible upon login).  This alone will go a LONG way, I really cannot emphasize this enough.  By the way, to manage favorite markets now, simply add a link to it on the trade page. 

Speaking of managing favorite markets, this seriously needs work.  Please take a cue from the Poloniex UI on this one.  Instead of the "add/subtract" paradigm (which really isn't working anyway), please put a check box next to each market so users can select (or deselect) markets as favorites.  Then have a check box at the top that says "show favorites only" and make it selected by default.  Deselecting it should make ALL available markets visible.  Don't worry about there being too many markets.  Poloniex lists hundreds of coins.  Plus we can just provide a working way to narrow them down (by base asset) AND sort them (by quoted asset, base asset, volume, etc).  We should also consider having a check box at the top that says something like "hide inverted markets" to limit the list to only one version of each pair.  Perhaps let that default version use the paired asset with greater liquidity as the base. 

Also, some on this forum have asked for this page to show last price, 24h price change, and 24h volume.  I agree.  And I'll point out that you can make more space for those columns by having the table span the entire page left to right, while moving the search criteria fields into a narrow band at the top.  I would also reduce the row height so we can view more markets on the page (please also reduce row height in the list of markets on the trade page). 

The last thing I would request you add to this is a way to move markets up and down in the list of selected favorites.   This way we can have our most favorite markets at the top.  If we can add that along with the other modifications described above, it's going to make a WORLD of difference.
 
Thanks!
Title: Re: Graphene GUI testing and feedback
Post by: tbone on November 01, 2015, 11:32:34 am

I suggest putting a thin line border around the chart and other sections on the trade page. The kind on border you have around titles in table views.  I think this would look better than having different color backgrounds.

I would be hesitant to start trying to fine tune aesthetics before we've handled the usability issues.  However, the gray background is problematic, especially the lighter gray background behind the order book which is making it more difficult to view the values (especially the price).  A black background will provide greater contrast and therefore easier readability. 
Title: Re: Graphene GUI testing and feedback
Post by: fav on November 01, 2015, 02:51:49 pm
trying to buy UIA, nothing's happening when I click on buy... light wallet

(http://i.imgur.com/q99pVEJ.png)
Title: Re: Graphene GUI testing and feedback
Post by: jakub on November 01, 2015, 07:17:41 pm
trying to buy UIA, nothing's happening when I click on buy... light wallet
Do other things work?
If not, you might be the victim of this bug related to the depth chart - it makes the GUI unresponsive.
https://bitsharestalk.org/index.php/topic,19632.msg251932.html#msg251932
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 03, 2015, 05:14:17 am
@svk @valzav

Why is the trade button not working in Chrome now? {From outside 'Trade' redirects to last market, from inside does nothing}

aka one cannot get to any market?????????????????????????????????????????????????????????????????????

Why does the latest release has to render the whole wallet useless???
Title: Re: Graphene GUI testing and feedback
Post by: svk on November 03, 2015, 05:16:39 am
@svk @valzav

Why is the trade button not working in Chrome now?

aka one cannot get to any market?????????????????????????????????????????????????????????????????????
Weird, it should either take you to your latest market or if you don't have one to the Markets overview. Try typing the market you want directly or going to Explore -> Markets
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 03, 2015, 05:18:47 am
@svk @valzav

Why is the trade button not working in Chrome now?

aka one cannot get to any market?????????????????????????????????????????????????????????????????????
Weird, it should either take you to your latest market or if you don't have one to the Markets overview. Try typing the market you want directly or going to Explore -> Markets
when in markets it does not respond!...so I can not type anything.


and refresh or close/reopen does not resolve it, either

will restart the computer itself....
Title: Re: Graphene GUI testing and feedback
Post by: svk on November 03, 2015, 05:29:39 am
@svk @valzav

Why is the trade button not working in Chrome now?

aka one cannot get to any market?????????????????????????????????????????????????????????????????????
Weird, it should either take you to your latest market or if you don't have one to the Markets overview. Try typing the market you want directly or going to Explore -> Markets
when in markets it does not respond!...so I can not type anything.


and refresh or close/reopen does not resolve it, either

will restart the computer itself....

I just tested in Safari and Firefox on my Mac (because I'd never used them to access the site before) and it's working fine here.

Anyone else having issues like tony's?

If they persist, could you tell me what's in the Chrome console pls? (Right click on the page then choose Inspect)
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 03, 2015, 05:33:25 am
Nope restarting the win7 did not help.

It was working fine btw, I made some trades here and there...and it became irresponsive...so you will not easily replicate the issue but it is still there.


I can try cleaning the browser files...if I find the courage to do it, that is.
Title: Re: Graphene GUI testing and feedback
Post by: svk on November 03, 2015, 05:40:51 am
Nope restarting the win7 did not help.

It was working fine btw, I made some trades here and there...and it became irresponsive...so you will not easily replicate the issue but it is still there.


I can try cleaning the browser files...if I find the courage to do it, that is.


You could try clearing your localStorage only, that might help.

At bitshares.openledger.info, do Inspect Element -> Resources tab, > Local Storage

Then find bitshares.openledger.info, you can clear everything there safely.

(http://i.imgur.com/o2DVpUd.png)
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 03, 2015, 05:56:32 am
Nope restarting the win7 did not help.

It was working fine btw, I made some trades here and there...and it became irresponsive...so you will not easily replicate the issue but it is still there.


I can try cleaning the browser files...if I find the courage to do it, that is.


You could try clearing your localStorage only, that might help.

At bitshares.openledger.info, do Inspect Element -> Resources tab, > Local Storage

Then find bitshares.openledger.info, you can clear everything there safely.

(http://i.imgur.com/o2DVpUd.png)


cleared it..no change as to the Trade button unresponsiveness.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 03, 2015, 05:59:51 am
Fuck...
I know it is a strange request but:

Is there a light wallet version (for win) that has both:

-adjust collateral window that is small enough to fit a normal screen

- does not hide called short

?
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 03, 2015, 06:15:36 am
also what is the page of markets?

https://bitshares.openledger.info/#/explorer

is the one for 'explorer'

chrome says:
https://bitshares.openledger.info/#/market
does not exists


PS
OK
https://bitshares.openledger.info/#/explorer/markets

although it is

https://bitshares.openledger.info/#/market/USD_BTS




PS
I found my fix... I guess the regular user will not be too happy if she has to use it though....

Title: Re: Graphene GUI testing and feedback
Post by: mf-tzo on November 03, 2015, 02:11:50 pm
Fuck...
I know it is a strange request but:

Is there a light wallet version (for win) that has both:

-adjust collateral window that is small enough to fit a normal screen

- does not hide called short

?

hahahahaha :)
Title: Re: Graphene GUI testing and feedback
Post by: svk on November 03, 2015, 07:16:29 pm
Fuck...
I know it is a strange request but:

Is there a light wallet version (for win) that has both:

-adjust collateral window that is small enough to fit a normal screen

- does not hide called short

?
I've pushed a small fix to the borrowing modal that hides the help text on small screens, hopefully that'll let you use it. Until it's live I guess youll have to live with zooming.

It's probably best to keep the called shorts as they are since its too confusing to show them.

But if you want to run a local GUI I can tell you how to show them..
Title: Re: Graphene GUI testing and feedback
Post by: fav on November 04, 2015, 04:58:02 pm
there's no way to delete a proxy vote for example on openledger at the moment.
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on November 05, 2015, 05:35:16 pm
I see this all the time.  Orders not matching.  Is this a rounding issue?  Is there a solution?
If you flip the market its obvious that the orders aren't quite the same, and shouldn't match, but I'm sure the trader intended them to be.

(http://content.screencast.com/users/Enkianu/folders/Jing/media/4dfe5cde-5799-4b92-9a81-36a81ce58a97/2015-11-05_1226.png)

Maybe as a setting there could be a "round up"  option that ensure your order will match with the viewable precision. instead of being off by .000000001 and the order not matching.

Im swinging in the dark though, as I may not fully understand what the issue is that causes this.
Title: Re: Graphene GUI testing and feedback
Post by: clayop on November 05, 2015, 05:50:48 pm
I see this all the time.  Orders not matching.  Is this a rounding issue?  Is there a solution?
If you flip the market its obvious that the orders aren't quite the same, and shouldn't match, but I'm sure the trader intended them to be.

(http://content.screencast.com/users/Enkianu/folders/Jing/media/4dfe5cde-5799-4b92-9a81-36a81ce58a97/2015-11-05_1226.png)

Maybe as a setting there could be a "round up"  option that ensure your order will match with the viewable precision. instead of being off by .000000001 and the order not matching.

Im swinging in the dark though, as I may not fully understand what the issue is that causes this.
Prob related.

https://github.com/cryptonomex/graphene-ui/issues/434
Title: Re: Graphene GUI testing and feedback
Post by: Louis on November 06, 2015, 12:32:22 am
(http://i.imgur.com/b7odbz7l.png)

I think we should have headings and also add subtle borders to segregate the different panels on the exchange screen. It makes it easier to follow what your are looking at, otherwise it looks like things are floating around the page.

I think we should add headings to the following:

Title: Re: Graphene GUI testing and feedback
Post by: Akado on November 08, 2015, 12:44:46 am
What does the reset button do after I create a backup?

Also, I create a backup, if I go to create a new one, it says the date of the previous one there's a message "The wallet needs a backup" I think that should be changed since the wallet had a recent backup. Maybe saying it's recommended to have multiple backups or something.

Also a few things more, dunno if they were mentioned already.

1. When I try to copy info that I previous selected I get this error
(http://s1.postimg.org/g0bv20qhr/image.png)


2. When I'm at the markets, the bar seems messed up. At the top is gray but when I pull it down it turns white, it doesn't seem intuitive. Also when I try to push it back up, I can't move it, it's difficult to get it back up. Dunno if this is just me but would like other people to confirm. Instead if I try to push the bar up with the mouse, it ends up selecting everything.

(http://s1.postimg.org/8pgcpwa3j/image.png)

(http://s10.postimg.org/9puhlcal4/image.jpg)
Title: Re: Graphene GUI testing and feedback
Post by: Empirical1.2 on November 08, 2015, 06:14:37 pm
I might be the only one that thinks like this, but on

https://bitshares.openledger.info/#/market/BTS_USD

On the sell side in brackets I'd like to see the deviation from the peg based on the feed price.

So on the buy side I would see trades starting at for example ($0.98) and on the sell side ($1.02)

The main thing I want to know (Without working it out) is how much a premium over the peg I am paying when buying BitUSD and vice versa.
Title: Re: Graphene GUI testing and feedback
Post by: Akado on November 11, 2015, 10:38:28 pm
btw for charts we need to have something at least better than tradingview

http://bitcoinist.net/cex-integrates-tradingview-bitcoin-charts/
Title: Re: Graphene GUI testing and feedback
Post by: svk on November 12, 2015, 09:54:54 am
btw for charts we need to have something at least better than tradingview

http://bitcoinist.net/cex-integrates-tradingview-bitcoin-charts/

"At least better than". You have some pretty high expectations there!

I actually wanted to use Tradingview when I first started building the market page, I think it looks pretty good. It was rejected due to logo and links watermarks IIRC, and I had to stick to Highcharts.
Title: Re: Graphene GUI testing and feedback
Post by: Akado on November 12, 2015, 10:01:01 am
btw for charts we need to have something at least better than tradingview

http://bitcoinist.net/cex-integrates-tradingview-bitcoin-charts/

"At least better than". You have some pretty high expectations there!

I actually wanted to use Tradingview when I first started building the market page, I think it looks pretty good. It was rejected due to logo and links watermarks IIRC, and I had to stick to Highcharts.

Its not about trading view not being good enough, ots just that we should aim to have something better than competition and not copy them. But im not a trader and never used those platforms só i understand if it isnt as easy as i Made it seem.
I usually see People wanting something like this or that, well, People should aim to get somrthing better but its not always possible of course.
I didnt mean tradingview waasnt good enough
Title: Re: Graphene GUI testing and feedback
Post by: Shentist on November 14, 2015, 05:08:31 pm
i am wondering if this is not implemented into the webwallet?

Quote
Settlement
Holders of any bitAsset can request a settlement at a fair price at any time. The settlement closes the borrow/short positions with lowest collateral ratio and sells the collateral for the settlement.
Title: Re: Graphene GUI testing and feedback
Post by: svk on November 14, 2015, 08:00:37 pm
i am wondering if this is not implemented into the webwallet?

Quote
Settlement
Holders of any bitAsset can request a settlement at a fair price at any time. The settlement closes the borrow/short positions with lowest collateral ratio and sells the collateral for the settlement.

No it's not there yet. Soon!
Title: Re: Graphene GUI testing and feedback
Post by: Shentist on November 14, 2015, 08:05:15 pm
i am wondering if this is not implemented into the webwallet?

Quote
Settlement
Holders of any bitAsset can request a settlement at a fair price at any time. The settlement closes the borrow/short positions with lowest collateral ratio and sells the collateral for the settlement.

No it's not there yet. Soon!

wow - i am a little bit disaptointed! the product was really rushed, if this core feature is not included. Nothing personal svk, i know you working hard.
Title: Re: Graphene GUI testing and feedback
Post by: xeroc on November 18, 2015, 12:53:09 pm
its only missing in the gui .. it is available in the cli wallet and on blockchain level ..
Title: Re: Graphene GUI testing and feedback
Post by: Akado on November 19, 2015, 09:36:31 pm
Ok I noticed that after voting for a proposal and publishing changes, the number of "total of votes" doesn't change. It was broadcasted so it's registered on the chain, plus the state is changed for "supported", however the numbers aren't updated. It's nothing critical, but still.

Oh, this happens even after I reload - control+R - the page
Title: Re: Graphene GUI testing and feedback
Post by: svk on November 19, 2015, 09:46:10 pm
Ok I noticed that after voting for a proposal and publishing changes, the number of "total of votes" doesn't change. It was broadcasted so it's registered on the chain, plus the state is changed for "supported", however the numbers aren't updated. It's nothing critical, but still.

Oh, this happens even after I reload - control+R - the page
Most likely votes are only tallied during the maintenance interval so you won't see it until the next one has passed.
Title: Re: Graphene GUI testing and feedback
Post by: Akado on November 19, 2015, 10:04:27 pm
Ok I noticed that after voting for a proposal and publishing changes, the number of "total of votes" doesn't change. It was broadcasted so it's registered on the chain, plus the state is changed for "supported", however the numbers aren't updated. It's nothing critical, but still.

Oh, this happens even after I reload - control+R - the page
Most likely votes are only tallied during the maintenance interval so you won't see it until the next one has passed.

Oh okay I thought they were supposed to be updated in real time on the next block or something
Title: Re: Graphene GUI testing and feedback
Post by: Tuck Fheman on November 19, 2015, 11:48:50 pm
fixed by updating my client.
Title: Re: Graphene GUI testing and feedback
Post by: EstefanTT on November 20, 2015, 02:07:06 am
Hi,

I don't know if it has been reported but when I tried to issue my UIA, the pop up windows didn't let me enter completely the name of the account.
What happened is that I could only enter 4 caracters in the field for the destination account. There is some kind of bug making impossible to enter more than 4 caracter.
I did a copy-past to resolve the problem.
So it seems the field can contain more than 4 catacters but it doesn't allow the user to enter them with the keyboard.

I hope it helps ;)

It was the latest version of the light client on windows 10
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 20, 2015, 01:39:26 pm
uhhhh nope.... I know I should have put in the other thread the version is perfect do not play with it anymore....


What is that? Why my supposedly favorite market are now in smaller font and the only part that used to be visible enough (the blue price) is now gone... the replacement is a shiny yellowish star... but that is just the start.

When I finally find my 'favorite market' the things insist on appearing in their screwy form... 0.44 apples per dollar. Changing it to a human pricing 2.27 dollars per apple is only temporary...the next time I click my favourite market it is again in its , not my favorite form - 0.44 apples per dollar...and if this is not enough it now does not center in the ask/bids (in vertical view) it just shows me some part of the orderbook it thinks I am interested in...deep buy orders. so I have to slide it.

Very bad improvements - revert back to the previous form, it was damn near perfect.

PS
aahhh figured it out...cool.
Title: Re: Graphene GUI testing and feedback
Post by: Akado on November 20, 2015, 02:10:15 pm
I was also under the impression that the font got smaller but since i didnt use the wallet much because i couldnt claim my funds i thought it was just me

Guess its True after all
Title: Re: Graphene GUI testing and feedback
Post by: Akado on November 20, 2015, 08:52:25 pm
The bar is slightly above the info making it appear it should have a bar to scroll down but it doesnt need it

(http://s2.postimg.org/edwewwfsp/image.png)
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on November 21, 2015, 03:29:45 pm
This may not be a gui bug. 

Everyday, I find at least 1 market where someone has attempted to buy/sell the closest bid/ask and the order fails to match.

This issues has been here from the very beginning of bitshares 0.x . 

If I click on an ask and hit buy, it should match *every time. (maybe it does, and the issue is only with manually price entry?)  Currently in order to guarantee my orders go through I am having to manually raise my bid or lower my ask by a fraction over/under what I actually want.  This is of course totally unacceptable.  Curious why this is still the case after over a year. 

Also, If BTS has a precision of 5 why do we allow orders to be entered at a price and quantity with a precision of 8?


Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on November 21, 2015, 08:14:55 pm
Also may not be a gui issue.

Just saw this in BTS:OBITS market history.
(http://content.screencast.com/users/Enkianu/folders/Jing/media/75de2ebc-6e19-4f32-9b39-207a9d2e01a3/2015-11-21_1508.png)

There was an order to sell at 17.80
It was not canceled or replaced.  It was there the whole time.
How does an order to buy register at 17.8002?
that shouldn't happen right?
Title: Re: Graphene GUI testing and feedback
Post by: Riverhead on November 22, 2015, 06:16:45 am
When updating a margin position the base equity has an "Available" amount. It currently shows your current base balance minus your collateral. So if you have 90k BTS in collateral and a 10k BTS balance and want to update your position it'll show -80k BTS as "Available" when I think it should show 10k.
Title: Re: Graphene GUI testing and feedback
Post by: mike623317 on November 22, 2015, 07:14:56 am
In firefox and chrome on windows 7.

(http://i.imgur.com/pO0tH8M.jpg)
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 22, 2015, 07:44:12 am
In firefox and chrome on windows 7.

(http://i.imgur.com/pO0tH8M.jpg)

You somehow do not like it?????

If so complain to your local priest... "no warranty, no responsibility, no care"...deliver to you by "We fix our bugs, sometimes...maybe" Inc.


and this is not even a bug... if you press ctr- repeatedly it will eventual sort itself out. You might need a magnifier at this point but still not a bug....
actually you should start your day praying in front of BM just cause BTS 2.0 has a GUI to begin with.
Title: Re: Graphene GUI testing and feedback
Post by: Tuck Fheman on November 22, 2015, 07:49:08 am
Firefox/Win7 for me looks fine ...
(http://i.imgur.com/Ftr6vf8.jpg)

It looks fine in Chrome too.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 22, 2015, 05:34:39 pm
Chrome... latest GUI aka OL

Cannot open markets with margin called orders[as in already called]...



Thanks, tips for testing  in GreenPoints or BTS  :)
Title: Re: Graphene GUI testing and feedback
Post by: svk on November 22, 2015, 08:47:44 pm
Chrome... latest GUI aka OL

Cannot open markets with margin called orders[as in already called]...



Thanks, tips for testing  in GreenPoints or BTS  :)
Yea i fixed this yesterday but not sure it's been hotfixed yet.
Title: Re: Graphene GUI testing and feedback
Post by: svk on November 22, 2015, 08:50:57 pm
Firefox/Win7 for me looks fine ...
(http://i.imgur.com/Ftr6vf8.jpg)

It looks fine in Chrome too.
That whole page needs to be redone, it completely breaks with the style of the rest of the wallet, and some things are wrong, like the flags/permissions.

We'll get to it eventually..
Title: Re: Graphene GUI testing and feedback
Post by: Akado on November 22, 2015, 09:06:39 pm
Also may not be a gui issue.

Just saw this in BTS:OBITS market history.
(http://content.screencast.com/users/Enkianu/folders/Jing/media/75de2ebc-6e19-4f32-9b39-207a9d2e01a3/2015-11-21_1508.png)

There was an order to sell at 17.80
It was not canceled or replaced.  It was there the whole time.
How does an order to buy register at 17.8002?
that shouldn't happen right?

I placed an order and it happened the same to me, instead of the exact number I've placed with no decimal parts, it was an INT, it appeared on the order book with those decimal values too! For example, I place an order at 200BTS/Xasset and it will appear on the order book as 200.0001/Xasset
Title: Re: Graphene GUI testing and feedback
Post by: speedy on November 22, 2015, 09:19:39 pm
That whole page needs to be redone, it completely breaks with the style of the rest of the wallet, and some things are wrong, like the flags/permissions.

We'll get to it eventually..

It would be nice to show the Asset Id & precision in its asset page too. Probably just me who wants this, for writing scripts.
Title: Re: Graphene GUI testing and feedback
Post by: svk on November 22, 2015, 09:27:34 pm
That whole page needs to be redone, it completely breaks with the style of the rest of the wallet, and some things are wrong, like the flags/permissions.

We'll get to it eventually..

It would be nice to show the Asset Id & precision in its asset page too. Probably just me who wants this, for writing scripts.
No I agree that should be there, as a workaround until we get to it you can look in the dev console, it logs the whole asset object from that page.
Title: Re: Graphene GUI testing and feedback
Post by: speedy on November 22, 2015, 10:17:08 pm
Where is the dev console in the webwallet?
Title: Re: Graphene GUI testing and feedback
Post by: sittingduck on November 22, 2015, 10:34:10 pm
JavaScript console. 
Title: Re: Graphene GUI testing and feedback
Post by: speedy on November 22, 2015, 10:42:18 pm
JavaScript console.

Ah thanks!
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 23, 2015, 12:05:14 am
Chrome... latest GUI aka OL

Cannot open markets with margin called orders[as in already called]...



Thanks, tips for testing  in GreenPoints or BTS  :)
Yea i fixed this yesterday but not sure it's been hotfixed yet.

maan ...did you also fix the update collateral screw up????
This sucks to no end...
Why do you touch thing that work to begin with???
Title: Re: Graphene GUI testing and feedback
Post by: svk on November 23, 2015, 05:49:14 am
Chrome... latest GUI aka OL

Cannot open markets with margin called orders[as in already called]...



Thanks, tips for testing  in GreenPoints or BTS  :)
Yea i fixed this yesterday but not sure it's been hotfixed yet.

maan ...did you also fix the update collateral screw up????
This sucks to no end...
Why do you touch thing that work to begin with???
Yea I did that too...
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 26, 2015, 01:33:26 am
The last version is not working on IE.

Such at "Loading..." same time fine on Chrome
Title: Re: Graphene GUI testing and feedback
Post by: bitacer on November 26, 2015, 08:26:34 am
Where do we submit translation related issues. Is this the right place ?
Title: Re: Graphene GUI testing and feedback
Post by: xeroc on November 26, 2015, 08:43:05 am
Where do we submit translation related issues. Is this the right place ?
If you know how to use github you could put it there aswell:
https://github.com/cryptonomex/graphene-ui/tree/master/web/app/assets/locales
Title: Re: Graphene GUI testing and feedback
Post by: bitacer on November 26, 2015, 08:46:59 am
When I switch it to TR language , the buttons become inactive, they work fine on EN.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 28, 2015, 08:01:20 pm
The last version is not working on IE.

Such at "Loading..." same time fine on Chrome

@svk Is the next Wed version supposed to work in IE or should I look into moving my wallet in some new browser?

and this is of course the second question - what is the reason the wallet no longer allows me to chose a backup to restore from?  -Only the last backup is displayed, which means I cannot restore/change to a different wallet.
Title: Re: Graphene GUI testing and feedback
Post by: svk on November 28, 2015, 10:49:14 pm
The last version is not working on IE.

Such at "Loading..." same time fine on Chrome

@svk Is the next Wed version supposed to work in IE or should I look into moving my wallet in some new browser?

and this is of course the second question - what is the reason the wallet no longer allows me to chose a backup to restore from?  -Only the last backup is displayed, which means I cannot restore/change to a different wallet.

I recommend moving to Chrome, I think we've decided to more or less ignore IE for the moment.

Not sure about the backups, was that something that was possible before? As far as I know nothing's been changed with respect to the backup handling for a while now.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 28, 2015, 10:54:20 pm
The last version is not working on IE.

Such at "Loading..." same time fine on Chrome

@svk Is the next Wed version supposed to work in IE or should I look into moving my wallet in some new browser?

and this is of course the second question - what is the reason the wallet no longer allows me to chose a backup to restore from?  -Only the last backup is displayed, which means I cannot restore/change to a different wallet.

I recommend moving to Chrome, I think we've decided to more or less ignore IE for the moment.

Not sure about the backups, was that something that was possible before? As far as I know nothing's been changed with respect to the backup handling for a while now.
thanks.
at least in [the old] version of the light wallet that I am running you can chose the backup file you import. So one can easily switch wallets.
I do not know if it is an old, or light wallet only function but it is definitely useful in order to switch wallets.
Title: Re: Graphene GUI testing and feedback
Post by: svk on November 28, 2015, 10:59:38 pm
The last version is not working on IE.

Such at "Loading..." same time fine on Chrome

@svk Is the next Wed version supposed to work in IE or should I look into moving my wallet in some new browser?

and this is of course the second question - what is the reason the wallet no longer allows me to chose a backup to restore from?  -Only the last backup is displayed, which means I cannot restore/change to a different wallet.

I recommend moving to Chrome, I think we've decided to more or less ignore IE for the moment.

Not sure about the backups, was that something that was possible before? As far as I know nothing's been changed with respect to the backup handling for a while now.
thanks.
at least in [the old] version of the light wallet that I am running you can chose the backup file you import. So one can easily switch wallets.
I do not know if it is an old, or light wallet only function but it is definitely useful in order to switch wallets.
You can just make several wallets and switch between them in the wallet management console though, no need to restore from backups every time.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 28, 2015, 11:03:12 pm
The last version is not working on IE.

Such at "Loading..." same time fine on Chrome

@svk Is the next Wed version supposed to work in IE or should I look into moving my wallet in some new browser?

and this is of course the second question - what is the reason the wallet no longer allows me to chose a backup to restore from?  -Only the last backup is displayed, which means I cannot restore/change to a different wallet.

I recommend moving to Chrome, I think we've decided to more or less ignore IE for the moment.

Not sure about the backups, was that something that was possible before? As far as I know nothing's been changed with respect to the backup handling for a while now.
thanks.
at least in [the old] version of the light wallet that I am running you can chose the backup file you import. So one can easily switch wallets.
I do not know if it is an old, or light wallet only function but it is definitely useful in order to switch wallets.
You can just make several wallets and switch between them in the wallet management console though, no need to restore from backups every time.
weird...between the initial post and this one this changed. OK it is fine now.
Title: Re: Graphene GUI testing and feedback
Post by: Akado on November 29, 2015, 01:20:20 am
After I updated my orders, on the orders tab it still showed the old ones. I had to control + r to update
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on November 29, 2015, 10:06:24 pm
Request.

Please make the transaction history with arbitrary length... for all kind of cases this is usefull...in last particular case because of too many publish feed entries I cannot see how dele-puppy voted on that committee proposal.
Title: Re: Graphene GUI testing and feedback
Post by: Akado on November 30, 2015, 10:00:51 am
Request.

Please make the transaction history with arbitrary length... for all kind of cases this is usefull...in last particular case because of too many publish feed entries I cannot see how dele-puppy voted on that committee proposal.

Or maybe even a filter? So we could choose what to show to find info faster. Transactions, Votes, feeds, orders, etc
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on December 03, 2015, 01:31:15 am
For some reason, reason I cannot put into words, it looks very cool after this update.

So, 'pending forced settlements' screen did not make it this week or simply there are no such things pending right now, or it is me not finding it?
Title: Re: Graphene GUI testing and feedback
Post by: svk on December 03, 2015, 12:06:20 pm
For some reason, reason I cannot put into words, it looks very cool after this update.

So, 'pending forced settlements' screen did not make it this week or simply there are no such things pending right now, or it is me not finding it?
It's in but due to the high fee that only got changed yesterday I guess there are no orders yet. Look for them at the bottom of the exchange page though.

If you go to the settings there's also an option to add settle orders to the depth chart.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on December 03, 2015, 05:17:32 pm
For some reason, reason I cannot put into words, it looks very cool after this update.

So, 'pending forced settlements' screen did not make it this week or simply there are no such things pending right now, or it is me not finding it?
It's in but due to the high fee that only got changed yesterday I guess there are no orders yet. Look for them at the bottom of the exchange page though.

If you go to the settings there's also an option to add settle orders to the depth chart.
Thanks you.
You know about the jumping issue when entering orders, right.
Title: Re: Graphene GUI testing and feedback
Post by: Shentist on December 03, 2015, 05:27:30 pm
after the last update the amount on the right up corner shows all BTS i have and not anymore only the account i am in.
Title: Re: Graphene GUI testing and feedback
Post by: svk on December 03, 2015, 05:34:31 pm
after the last update the amount on the right up corner shows all BTS i have and not anymore only the account i am in.

Yes, it shows the total for your wallet.
Title: Re: Graphene GUI testing and feedback
Post by: svk on December 03, 2015, 05:36:51 pm
For some reason, reason I cannot put into words, it looks very cool after this update.

So, 'pending forced settlements' screen did not make it this week or simply there are no such things pending right now, or it is me not finding it?
It's in but due to the high fee that only got changed yesterday I guess there are no orders yet. Look for them at the bottom of the exchange page though.

If you go to the settings there's also an option to add settle orders to the depth chart.
Thanks you.
You know about the jumping issue when entering orders, right.

Yes I have noticed that, it's annoying. Will try to get rid of it.
Title: Re: Graphene GUI testing and feedback
Post by: fav on December 05, 2015, 03:44:11 pm
(http://i.imgur.com/46ewPlg.png)

triox added a memo which I did not receive. is this a GUI bug?
Title: Re: Graphene GUI testing and feedback
Post by: sittingduck on December 05, 2015, 03:50:35 pm
Is your wallet unlocked?
Title: Re: Graphene GUI testing and feedback
Post by: fav on December 05, 2015, 04:14:08 pm
Is your wallet unlocked?

it was... I had to scroll through some tabs but now it's visible :)
Title: Re: Graphene GUI testing and feedback
Post by: Akado on December 10, 2015, 11:39:30 pm
is there any way of showing the full 24h volume of the exchange in BTS?
Title: Re: Graphene GUI testing and feedback
Post by: Akado on December 16, 2015, 01:28:24 pm
Could we have the total amount of bids and asks on top as well, like polo? So the user doesn't need to scroll down?

H2-7 Flexibility and efficiency of use  :P

(http://s29.postimg.org/4b0p7znpz/Sem_T_tulo.png)
Title: Re: Graphene GUI testing and feedback
Post by: svk on December 16, 2015, 02:44:02 pm
is there any way of showing the full 24h volume of the exchange in BTS?

Not sure what you mean, across all markets?

Could we have the total amount of bids and asks on top as well, like polo? So the user doesn't need to scroll down?

H2-7 Flexibility and efficiency of use  :P

(http://s29.postimg.org/4b0p7znpz/Sem_T_tulo.png)

Yes, I have this displayed above the depth chart but I'll get it displayed like that too.
Title: Re: Graphene GUI testing and feedback
Post by: Akado on December 16, 2015, 03:02:41 pm
is there any way of showing the full 24h volume of the exchange in BTS?

Not sure what you mean, across all markets?

Could we have the total amount of bids and asks on top as well, like polo? So the user doesn't need to scroll down?

H2-7 Flexibility and efficiency of use  :P

(http://s29.postimg.org/4b0p7znpz/Sem_T_tulo.png)

Yes, I have this displayed above the depth chart but I'll get it displayed like that too.

Yes, the sum of the volume on all markets. To know the volume of the entire exchange in the last 24h. Some exchanges display bar at the top with their volume in BTC, along with the bitcoin price.

Or something like this, market statistics.
https://www.bitfinex.com/pages/stats

Market statistics should be useful, but I would just like to see the entire volume of the BitShares DEX for example, like the bar at the top some exchanges have, like BTC-E for example

https://btc-e.com/
"Volume: 13167 BTC / 5948388 USD"
Title: Re: Graphene GUI testing and feedback
Post by: mint chocolate chip on December 16, 2015, 04:34:01 pm
When trading, when I click on a price in the order book, it fills in the price for the wrong side in the area where I place an order. I would like it to auto fill both buy and sell, like it does on other exchanges. i.e., if I click in the ask column .22 for something, I want that .22 to be added to the order form area on the ask side, right now it only puts the .22 on the buy side, then I can change the amount there to what I want without having to worry about a missing decimal or zeros.
Title: Re: Graphene GUI testing and feedback
Post by: Vizzini on December 18, 2015, 12:03:32 am
You guys working on the GUI have been doing a great job. But with all due respect, I am very unhappy with this new change of having the one's accounts in a list and then showing their value in BTS. The numbers are not even close to reality. I have an account or two with some dust and shitcoin UIAs in them and it shows that I have 419,000,000 BTS. I have given up trying to find out how much I have in actual BTS, which I cannot see anymore. Suggestion: Roll back to how this looked a few days ago. I can see the utility in having the collateral appear also, but a few days ago it was much better looking and easier to understand and use.
Title: Re: Graphene GUI testing and feedback
Post by: fav on December 19, 2015, 12:19:47 pm
good job on the favorite ID thing! helps me keep track of important wallets
Title: Re: Graphene GUI testing and feedback
Post by: phideas on January 01, 2016, 03:42:18 pm
Latest version is crashing after start.
- System: Ubuntu 14.04
- BitShares version: v2.0.151223 installed from deb
- Error: segmentation fault
- PC reboot doesn't help
- Config folder delete doesn't help

Reverted back to version v2.0.151202
- it works, continue using this one
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on January 01, 2016, 05:01:47 pm
Some suggestions:
(I'm using Firefox)

1) On the trade page "My orders" at the bottom of the page are difficult to get to because of the secondary scrolling of the bid and ask orders in horizontal view.  I'd recommend the area between the bids and asks with the button that flips sides, that this area not scroll.  It is currently very difficult to find a place to put the mouse where I can scroll to the bottom of the page without scrolling through the entire bid/ask orderbook.

2) The precision on every market seems to be off by 1.  BTS / OPENBTC for example shows 9 digits after the decimal instead of 8. so the current price of BTS in BTC looks like .000008123 instead of .00000812

3) When you first access the trade page.  Clicking between My History and All History changes the width of the column.  However once you click on My Markets or All Markets, it will no longer adjust the column width.

4) On the trade page the scroll bar extends over top of the top static row that contains the "market depth" / "Price chart" buttons.  The scroll bar should be limited to the range of the window that actually scrolls.  It also appears to extend long past the bottom of the page.

5) On the account overview page I think separating the column "Asset" into two columns Amount and Asset.  This would make it easier to read and locate the asset you're looking for.

6) The Account Orders page columns are repeated for each market and do not line up vertically with each other.

7) The Trade page that just lists the markets fullscreen, lists the columns "Quote supply" and "Base supply" .  I'd like to see the highest "Bid" and Lowest "Ask" listed as well.  the base/quote supply is minimally useful.  If they all fit great, but I think the Bid,Ask,Last is more useful.

8 ) Can we get a deeper history for the price chart.   I'd like to see an entire years worth of data on the chart, or more, if possible.  The default can be a small range so it loads quicker but having the option to see more would be useful.

Title: Re: Graphene GUI testing and feedback
Post by: Akado on January 07, 2016, 12:23:45 am
On the hosted wallet it works but on the light client I can't scroll down to see more bids at the bottom. For example I would like to see the Total up to 1M BTS on the OBITS:BTS market and I can't. Also the scroll bar is messed up.
Title: Re: Graphene GUI testing and feedback
Post by: mint chocolate chip on January 07, 2016, 04:06:32 am
1) On the trade page "My orders" at the bottom of the page are difficult to get to because of the secondary scrolling of the bid and ask orders in horizontal view.  I'd recommend the area between the bids and asks with the button that flips sides, that this area not scroll.  It is currently very difficult to find a place to put the mouse where I can scroll to the bottom of the page without scrolling through the entire bid/ask orderbook.
+5% I am on Chrome

If I click a price in the order book, can the amount clicked on be entered into both of the above entry areas for buy and sell, currently it only does one of them. The reason I would want this is say I am wanting to sell something for slightly less than the lowest current ask,  if I click on the current lowest ask it adds the price to the buy field, if it added it to the ask input field I would then be able to change the price without having to worry as much that I might have missed the decimal place or a 0 or something  which would result in the ask being off by a big amount.

It would be great if there was a spot where I could see a list of all of my current orders. I see this somewhat in the Recent Activity area, but that includes more than just active orders... if this can't be done, it would at least be nice to click in an entry on the Recent Activity feed after it says the order info so that you are taken to that particular market.
Title: Re: Graphene GUI testing and feedback
Post by: speedy on January 14, 2016, 08:32:33 am
@svk @valzav are we going to be able to view markets in the webwallet without having an account? Then we can finally share links to BitShares markets and get altcoin traders interested.

As you know clicking on a market here https://bitshares.openledger.info/#/explorer/markets without an account takes you to the register page, which is dumb. It means that viral growth for BitShares is impossible.
Title: Re: Graphene GUI testing and feedback
Post by: abit on January 14, 2016, 11:03:00 am
@svk @valzav are we going to be able to view markets in the webwallet without having an account? Then we can finally share links to BitShares markets and get altcoin traders interested.

As you know clicking on a market here https://bitshares.openledger.info/#/explorer/markets without an account takes you to the register page, which is dumb. It means that viral growth for BitShares is impossible.
True it's possible. The real question is when will we have it.
Title: Re: Graphene GUI testing and feedback
Post by: Akado on January 14, 2016, 02:40:45 pm
Matching orders. When I try it, it rounds decimals I think and it doesn't let me match other orders, we always need to place the order a little bit above.

I think that's an important issue. No exchange can operate with that bug. It can frustrate other users / affect their user experience negatively
Title: Re: Graphene GUI testing and feedback
Post by: Akado on January 24, 2016, 07:46:43 pm
It's difficult to vote for witnesses. I think there could be a list of witnesses already voted in where the user could set order to show choosing witnesses with the smallest amount of missed blocks. I need to have a previous list compiled by me in order to add them. Plus when I go to the Explore/Witnesses menu to check the ones I want to, when I go back, the list of witnesses disappears making me start all over again. This means each time I add one I need to publish changes. Why can't I add all the ones I want first and then publish them?

Exactly same issue for committee members.

This goes in hand with Nielson's 6th Heuristic

Recognition rather than recall
Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
Title: Re: Graphene GUI testing and feedback
Post by: svk on January 24, 2016, 07:52:13 pm
It's difficult to vote for witnesses. I think there could be a list of witnesses already voted in where the user could set order to show choosing witnesses with the smallest amount of missed blocks. I need to have a previous list compiled by me in order to add them. Plus when I go to the Explore/Witnesses menu to check the ones I want to, when I go back, the list of witnesses disappears making me start all over again. This means each time I add one I need to publish changes. Why can't I add all the ones I want first and then publish them?

Exactly same issue for committee members.

This goes in hand with Nielson's 6th Heuristic

Recognition rather than recall
Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.


Yea totally agree, those pages need to be refactored.
Title: Re: Graphene GUI testing and feedback
Post by: merivercap on January 28, 2016, 02:46:22 am
Few things on the testnet I noticed:  http://testnet.bitshares.eu/#/market/TEST_PEG.FAKEUSD

1) Order doesn't execute.  I see an ask at .00369 PEG.FAKEUSD/TEST and try to buy it and place a matching order, but it doesn't execute. 

2) I used to have 'Cancel' buttons on all my orders, but those no longer show in the order book.  It also may be good to indicate which orders are the users somehow.. (ie. hightlight, stars, different color etc)

3) In  the orders page the link up top doesn't reverse the pricing of the pair ..(ie USD/BTS should switch to BTS/USD) ...instead it links to the price chart.

Thanks.  Trading platform looks and works great overall!
Title: Re: Graphene GUI testing and feedback
Post by: Akado on January 28, 2016, 10:58:23 am
Few things on the testnet I noticed:  http://testnet.bitshares.eu/#/market/TEST_PEG.FAKEUSD

1) Order doesn't execute.  I see an ask at .00369 PEG.FAKEUSD/TEST and try to buy it and place a matching order, but it doesn't execute. 

2) I used to have 'Cancel' buttons on all my orders, but those no longer show in the order book.  It also may be good to indicate which orders are the users somehow.. (ie. hightlight, stars, different color etc)

3) In  the orders page the link up top doesn't reverse the pricing of the pair ..(ie USD/BTS should switch to BTS/USD) ...instead it links to the price chart.

Thanks.  Trading platform looks and works great overall!

1) I think you might need to place an order a bit above it to execute. This has happened to me in the past already, don't know if it's fixed in the most recent release but we need that fixed asap or people just won't use it.
I use the light client btw, dunno if it's working correctly on OpenLedger
Title: Re: Graphene GUI testing and feedback
Post by: merivercap on January 28, 2016, 08:14:24 pm
Few things on the testnet I noticed:  http://testnet.bitshares.eu/#/market/TEST_PEG.FAKEUSD

1) Order doesn't execute.  I see an ask at .00369 PEG.FAKEUSD/TEST and try to buy it and place a matching order, but it doesn't execute. 

2) I used to have 'Cancel' buttons on all my orders, but those no longer show in the order book.  It also may be good to indicate which orders are the users somehow.. (ie. hightlight, stars, different color etc)

3) In  the orders page the link up top doesn't reverse the pricing of the pair ..(ie USD/BTS should switch to BTS/USD) ...instead it links to the price chart.

Thanks.  Trading platform looks and works great overall!

1) I think you might need to place an order a bit above it to execute. This has happened to me in the past already, don't know if it's fixed in the most recent release but we need that fixed asap or people just won't use it.
I use the light client btw, dunno if it's working correctly on OpenLedger

Yeah I'm using the testnet so it should be a pretty recent codebase similar to OL.  I agree this really should be addressed asap if it hasn't already.
Title: Re: Graphene GUI testing and feedback
Post by: merivercap on January 28, 2016, 08:22:40 pm
http://testnet.bitshares.eu/#/account/test1234/orders/

I can see my bids on the price chart and order book, but don't see my asks. 

Could it be that there is a limit of items that can be shown in the order book and once it reaches a limit you can't see the orders on the book nor on the price chart?  Makes the price chart deceptive since it doesn't display asks above a certain amount of TEST when in fact there are. 
Title: Re: Graphene GUI testing and feedback
Post by: Akado on January 28, 2016, 11:56:05 pm
During asset creation we should add the following:

Is backed asset: Yes/No
Backed asset proof of existence: (add an address of the real asset proving it's actually there)

Example:
OPENBTC should be a backed asset with an address with the same amount of bitcoins as the available supply of OPENBTCs and have the owner sign a message so we know it's really him.
Title: Re: Graphene GUI testing and feedback
Post by: Akado on January 29, 2016, 12:22:54 am
On the markets:

When we have the table view, the volume is displayed in BTS, can we have an option to display it in USD, CNY and BTC? And also add the total trading volume on top or something. It's nice to know, people can check it more easily and also for cmc to fetch volumes more easily maybe?

Also when you switch to card view, the cards have no info on the volume, even if they're showing it on the table view (ie BTS:OPENBTC)
Title: Re: Graphene GUI testing and feedback
Post by: Akado on February 02, 2016, 06:37:40 pm
Can we have some tool that calculates the average cost of an asset according to our transaction history? Should this be done via worker proposal?
Title: Re: Graphene GUI testing and feedback
Post by: Akado on February 14, 2016, 12:06:02 am
On OpenLedger each time I click a link to go to one of the markets I get redirected here https://bitshares.openledger.info/#/create-account

It's really, really frustrating. I just want to go straight to the market page I click on. The way it is I have to search it manually.

On the order book, what about creating a table, with lines separating each field to make it more easy to read? Plus each row should have a different colour (darker/lighter/darker/lighter) to make it easier to read.

Also when I'm on a market and I want to move to another market by using the "My Markets" / "All Markets" option on the side, when I type in the market I want and click on it, I can't move to that market. I get the "Loading" Icon and that's it.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on February 18, 2016, 07:13:38 pm
Ubuntu Chrome, trying to restore a wallet backup. Clicking on Restore (default wallet)
Code: [Select]
ConstraintError app.js:53:16847
AbortError app.js:53:16847
---- transaction error ----> DOMError { name: "ConstraintError", message: "A mutation operation in the transac…" } app.js:53:18538

abort { target: IDBTransaction, isTrusted: true, currentTarget: IDBTransaction, eventPhase: 2, bubbles: true, cancelable: false, defaultPrevented: false, timeStamp: 1455822497354740, originalTarget: IDBTransaction, explicitOriginalTarget: IDBTransaction, NONE: 0 } app.js:82:27284

Unhandled promise rejection abort { target: IDBTransaction, isTrusted: true, eventPhase: 0, bubbles: true, cancelable: false, defaultPrevented: false, timeStamp: 1455822497354740, originalTarget: IDBTransaction, explicitOriginalTarget: IDBTransaction, NONE: 0, CAPTURING_PHASE: 1 } app.js:2:1789
Title: Re: Graphene GUI testing and feedback
Post by: CLains on February 29, 2016, 09:52:00 pm
Shouldn't "my orders" and "my history" be below buy and sell window in trading? In fact, shouldn't buy and sell window be right below the chart?
Title: Re: Graphene GUI testing and feedback
Post by: svk on March 01, 2016, 05:52:15 am
Shouldn't "my orders" and "my history" be below buy and sell window in trading? In fact, shouldn't buy and sell window be right below the chart?
They will be in the next update.
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 01, 2016, 09:27:17 am
Shouldn't "my orders" and "my history" be below buy and sell window in trading? In fact, shouldn't buy and sell window be right below the chart?

No, the order book and ticker (history window) should be directly beneath the chart.  The buy/sell windows should be on the next row, directly beneath the order book and ticker.  Currently, the buy/sell windows are on a third row, separated from the order book.  That is the problem that needs to be corrected.  I really hope we get this right. 

@svk, can you confirm this is what's in progress?
Title: Re: Graphene GUI testing and feedback
Post by: svk on March 01, 2016, 10:10:58 am
Shouldn't "my orders" and "my history" be below buy and sell window in trading? In fact, shouldn't buy and sell window be right below the chart?

No, the order book and ticker (history window) should be directly beneath the chart.  The buy/sell windows should be on the next row, directly beneath the order book and ticker.  Currently, the buy/sell windows are on a third row, separated from the order book.  That is the problem that needs to be corrected.  I really hope we get this right. 

@svk, can you confirm this is what's in progress?

In the current dev build they're back up top but with an "accordeon" button that lets you collapse/expand them (open by default, setting persists between session), like this:

(http://i.imgur.com/k39JbAx.png)
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 01, 2016, 11:05:50 am
Shouldn't "my orders" and "my history" be below buy and sell window in trading? In fact, shouldn't buy and sell window be right below the chart?

No, the order book and ticker (history window) should be directly beneath the chart.  The buy/sell windows should be on the next row, directly beneath the order book and ticker.  Currently, the buy/sell windows are on a third row, separated from the order book.  That is the problem that needs to be corrected.  I really hope we get this right. 

@svk, can you confirm this is what's in progress?

In the current dev build they're back up top but with an "accordeon" button that lets you collapse/expand them (open by default, setting persists between session), like this:

(http://i.imgur.com/k39JbAx.png)

I like the idea of that in theory.  However, it is most critical to see the price chart, orderbook, and ticker all at the same time.  As it is, the bottom of the order book is getting cut off.  It's not the end of the world because obviously the bottom of the order book is less important than the top of it.  But still, the more you can see of it the better.  Right now on my screen I can see almost 8 of the 12 rows of the order book.  I suspect now it will drop to 4 or 5 visible rows out of 12, which is getting rough.  So we lose order book visibility in exchange for being able to click the buy/sell windows into view instead of having to scroll them into view.  Actually, come to think of it, after expanding the buy/sell window, you will still have to scroll down since you need to see the order book and buy/sell windows at the same time to place an order.  For these reasons, it really does make the most sense to place the buy/sell windows directly beneath the order book and ticker (price history). 

Ok, I just thought of a possible solution.  Considering that you really can't place an order without seeing the order book, it's inevitable that you'll have to scroll to place an order no matter where you place the buy/sell windows.  Which means you won't be able to see the chart when you place an order.  So why not make the chart collapsible, so now we can have the order book beneath the chart as it should be.  And when someone wants to place an order, they can bring the order book into view with the click of a button by collapsing the chart.  Or they can just scroll down. 
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 01, 2016, 11:37:46 am
By the way, looking at your screenshot, I don't see the ticker (history).  Are you not placing it alongside the order book on the first row beneath the chart?  That was the whole reason for all of this to begin with.  I can't stress enough how critical the ticker is.  It is arguably THE most important live data element when it comes to understanding what is going on in a particular market.

And I'll just stress again that the vast majority of time is spent watching the live data i.e. chart, order book and ticker.  Those elements need to be visible at the same time.  By contrast, you only spend a tiny amount of time actually placing an order.  So the buy/sell windows really only need to be visible when you need to place an order. Beyond that, the only consideration for the buy/sell windows is that they should not be separated from the order book.  They should be placed directly below. 
Title: Re: Graphene GUI testing and feedback
Post by: svk on March 01, 2016, 11:52:13 am
By the way, looking at your screenshot, I don't see the ticker (history).  Are you not placing it alongside the order book on the first row beneath the chart?  That was the whole reason for all of this to begin with.  I can't stress enough how critical the ticker is.  It is arguably THE most important live data element when it comes to understanding what is going on in a particular market.

And I'll just stress again that the vast majority of time is spent watching the live data i.e. chart, order book and ticker.  Those elements need to be visible at the same time.  By contrast, you only spend a tiny amount of time actually placing an order.  So the buy/sell windows really only need to be visible when you need to place an order. Beyond that, the only consideration for the buy/sell windows is that they should not be separated from the order book.  They should be placed directly below.

Yea I hear what you're saying but unless you have a really big screen/high resolution there really isn't enough space to put the orderbook and the history on the same row, and in that case you can probably fit everything anyway, I know I can on my screen here. Especially if you use a vertical orderbook.. I could add the ability to hide the price chart I suppose but it's just as easy to just scroll down, so not sure it would really serve a purpose. It's already better than something like Polo for example though where you have to scroll way down to see the history, isn't it?

(http://i.imgur.com/Wa8bL4P.png)
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 01, 2016, 01:27:30 pm
I have a 17" laptop and as you can see from my screenshot, only 1 row is visible below the chart.  In fact the ticker is even getting a little cut off at the bottom.  If you put the much less often needed buy/sell windows above the ticker, then the ticker will be completely off the screen, or in the best case scenario (with the buy/sell windows collapsed), the ticker will be cut off even more than it is now.  And what is gained to justify diminishing the critical ticker?  I would argue that there is zero need for the buy/sell windows to be at the top.  They just need to border the order book, which currently they do not (at least not in the horizontal layout) and that is a problem that can be solved without creating other problems. 

Also, despite being very constrained vertically as discussed above, you can see that there is a HUGE amount of extra (i.e. wasted) horizontal space within both the order book and the ticker/history in the horizontal layout, enough to place the order book and ticker on the same row (with room to spare).  This layout would be extremely advantageous, offering the best of all worlds.

Vertictal layout:
(http://i.imgur.com/9vZciAs.jpg)




Horizontal layout:
(http://i.imgur.com/5w1CHeW.jpg)
Title: Re: Graphene GUI testing and feedback
Post by: Louis on March 01, 2016, 02:42:10 pm
Is There a mobile version yet?
Title: Re: Graphene GUI testing and feedback
Post by: svk on March 01, 2016, 02:45:14 pm
@tbone what's the resolution of your screen? You have to remember most users have very small screens or small resolutions, 1366x768 is the most common resolution out there. And while I agree with you that the buy/sell forms aren't terribly useful and necessary to have at the top at all times, I'm not so sure everyone else agrees. There seems to be a lot of people wanting them up top and center.

That being said, I could add some screensize detection in javascript to add the market history to the first row for users that do have big enough screens.
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 01, 2016, 03:46:18 pm
The only complaints regarding the buy/sell windows have been that they are now separated from the order book.  That's definitely a big problem and it should be corrected, but it's really not necessary to throw the baby out with the bathwater.  This is where we can be better than Poloniex rather than just copying them. 

Please see my mock-up below in which I reclaimed some of the wasted space, making it possible to put the ticker on the top row alongside the order book.  As you can see there is still plenty of spacing between the columns.  My resolution is 1600 x 900.  Considering all of the extra space that still remains, I am sure it will be fine with 1366 x 768.  For any lower resolutions causing it to not quite fit, it's easy enough to hit ctrl + "-".  So I really don't  think it's necessary for you to go through the trouble of detecting resolution.

(http://i.imgur.com/BudVFQY.jpg)
Title: Re: Graphene GUI testing and feedback
Post by: CLains on March 01, 2016, 08:55:02 pm
@tbone why would you not want buy/sell just below the price chart? btc-e, bittrex, poloniex, yobit, bleutrade etc. does this.. esp for people who have low res, you'd have to scroll down to find the button. makes sense to me both intuitively and to get people to click the buy and sell button.
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 01, 2016, 10:33:04 pm
@tbone why would you not want buy/sell just below the price chart? btc-e, bittrex, poloniex, yobit, bleutrade etc. does this.. esp for people who have low res, you'd have to scroll down to find the button. makes sense to me both intuitively and to get people to click the buy and sell button.

@CLains: Ideally everything would be visible without scrolling.  But that's pretty difficulty, so decisions have to be made.  And a trader doesn't need to see the buy/sell boxes 99% of the time.  Most of the time they need to be monitoring the live action data, which comes from the order book, ticker ("history"), and price chart.  They might also be switching between various markets, scanning the data for each.  Imagine having to scroll up and down each time to get a good snapshot of each market.  And imagine while looking at a single market having to constantly scroll up and down, up and down, up and down, until you're finally ready to make a trade.  I'm sorry, but that just makes no sense whatsoever. 

Not to mention, to make a trade you really need to see the orderbook.  So if the buy/sell boxes are on the top row (just beneath the chart) and nothing below it is visible without scrolling, then you'll have to scroll to make a trade anyway.  So with that configuration we gain nothing and lose a lot, ending up with the worst of all worlds.  Is that really what we want?  If so, I don't know what to say anymore.  I've spent a LOT of time that I simply don't have in an effort to help us get this right.  I really can't do much more.

By the way, overall I like Poloniex, but having to constantly scroll up and down due to their unfortunate placement of the buy/sell boxes is one of the most maddening things I've encountered.  As for btc-e, their interface is extremely weak.  I don't think they've upgraded it since the beginning, although I'm pretty sure any serious trader using btc-e is trading via MetaTrader4.  As for Bittrex, their UI is a total horror show on so many levels and I'm NOT surprised they can't get any traction whatsoever despite having so many different coins trading on their site.  Bleautrade, while their UI is better than Bittrex, they still get way too much wrong. 

I hadn't seen Yobit before now.  But it does seem that their UI is much better than the others.  Notice that the most important elements (orderbook, ticker, and chart) are all visible without scrolling.  Amazingly, they have also managed to make the buy/sell boxes, markets "watchlist", balances, and even a troll box, all visible without scrolling.  That's some feat!  Although I do have to say that their chart is very weak, and that's partly what enables them to pack everything else onto the screen.  In any event, Bitstamp is another one that gets much more right than the others.  Same with cryptowat.ch.  It would be nice if if we could too. 
Title: Re: Graphene GUI testing and feedback
Post by: Akado on March 01, 2016, 11:15:56 pm
On OpenLedger, I clicked on "Explore", then "Trade". "Explore" is still highlighted as if I was still on that menu, when I'm on the "Trade" menu
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 02, 2016, 05:22:37 am
@tbone why would you not want buy/sell just below the price chart? btc-e, bittrex, poloniex, yobit, bleutrade etc. does this.. esp for people who have low res, you'd have to scroll down to find the button. makes sense to me both intuitively and to get people to click the buy and sell button.

By the way, I forgot to mention that both Bitfinex and Coinbase Exchange both have their trading page laid out such that you can see the order book, ticker and chart without scrolling.  Bitfinex actually places their chart (collapsible) between the buy/sell boxes and the order book / ticker.  Clearly they recognize that it's not helpful to let the buy/sell box force the user to scroll back and forth between the important live data screen elements.

Anyway, I also took a look at OKCoin and BTC-China this evening, and both UIs also position the order book, ticker and chart on the screen such that no scrolling is necessary.  For what it's worth, Bitfinex, OKCoin, Coinbase Exchange, and Bitstamp are the top 4 bitcoin exchanges in the world. 
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 03, 2016, 04:50:44 pm
@svk, very nice move narrowing the buy/sell boxes.  That's a nice enhancement on the vertical layout since the most critical live data elements were already visible.  Unfortunately it doesn't help much on the horizontal layout considering you still have to scroll down to place an order (unless you want to do it blindly i.e. without seeing the all-important order book, which is off the page now).  So now you pretty much always have to scroll to do anything on the horizontal layout, instead of having to scroll only when actually placing an order.  None of the serious UIs are set up like that, and this is one of Poloniex's biggest flaws.  I won't push for it anymore, but I do still hope we can correct that.  If/when we do, I have some additional suggestions for enhancing the horizontal layout.   

As always, thanks for your work on this.
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 03, 2016, 05:09:53 pm
I noticed an issue earlier in the week and finally had a chance to finish writing it up.  This is a case where we should be emulating Poloniex because they are getting it right.  Basically, when you click on the order book, you are generally looking to do 1 of 2 things: either 1) you to want place an order on the book, or 2) you want to match one or more orders already on the book.  The buy/sell windows should be populated accordingly, but that's not happening.  And it's far more problematic than most would imagine. 

As an example (see image below), if you click the 4th row of the ask side, you are either looking to place your own ask onto the order book at that price, OR you want to match the orders on the ask side up to that price.  So 2 things should happen: 1) the sell window should be populated with the price you clicked in case you want to place an order on the ask side of the book at the clicked price, and 2) the buy window should be populated with a) the price you clicked, b) the sum of the share amounts on those first 4 rows, and c) the sum of the prices of the shares available on those 4 rows.  This allows you to see how many shares are available up to the price you are willing to pay before either clicking buy or clicking further down the book if you need more shares. 

Not having the order book behave in this manner is a major drawback.  In my estimation this is one of a small handful of things that is preventing Bittrex from getting much if any traction at all. In any event, please check out Poloniex to see how it should work.  Hopefully we can get this into the next update.  Thanks @svk!

(http://i.imgur.com/Qbxrhrn.jpg)
Title: Re: Graphene GUI testing and feedback
Post by: svk on March 03, 2016, 06:43:09 pm
@svk, very nice move narrowing the buy/sell boxes.  That's a nice enhancement on the vertical layout since the most critical live data elements were already visible.  Unfortunately it doesn't help much on the horizontal layout considering you still have to scroll down to place an order (unless you want to do it blindly i.e. without seeing the all-important order book, which is off the page now).  So now you pretty much always have to scroll to do anything on the horizontal layout, instead of having to scroll only when actually placing an order.  None of the serious UIs are set up like that, and this is one of Poloniex's biggest flaws.  I won't push for it anymore, but I do still hope we can correct that.  If/when we do, I have some additional suggestions for enhancing the horizontal layout.   

As always, thanks for your work on this.

Not sure what more I can do here tbh, on my screen which is 1920x1080 I can now see most of the price chart and most of the orderbook at the same time in horizontal mode, and everything easily in vertical mode. So you would still prefer the orderbook to be on the first row with buy/sell below it?

Thanks a lot for your feedback btw, it's much appreciated!
Title: Re: Graphene GUI testing and feedback
Post by: svk on March 03, 2016, 06:45:38 pm
I noticed an issue earlier in the week and finally had a chance to finish writing it up.  This is a case where we should be emulating Poloniex because they are getting it right.  Basically, when you click on the order book, you are generally looking to do 1 of 2 things: either 1) you to want place an order on the book, or 2) you want to match one or more orders already on the book.  The buy/sell windows should be populated accordingly, but that's not happening.  And it's far more problematic than most would imagine. 

As an example (see image below), if you click the 4th row of the ask side, you are either looking to place your own ask onto the order book at that price, OR you want to match the orders on the ask side up to that price.  So 2 things should happen: 1) the sell window should be populated with the price you clicked in case you want to place an order on the ask side of the book at the clicked price, and 2) the buy window should be populated with a) the price you clicked, b) the sum of the share amounts on those first 4 rows, and c) the sum of the prices of the shares available on those 4 rows.  This allows you to see how many shares are available up to the price you are willing to pay before either clicking buy or clicking further down the book if you need more shares. 

Not having the order book behave in this manner is a major drawback.  In my estimation this is one of a small handful of things that is preventing Bittrex from getting much if any traction at all. In any event, please check out Poloniex to see how it should work.  Hopefully we can get this into the next update.  Thanks @svk!

(http://i.imgur.com/Qbxrhrn.jpg)

Yea I had this functionality in before but realized it wasn't adding up sums correctly so I decided to disable it until I could find the time to revisit it and see if I could implement it properly.

Trackable here: https://github.com/cryptonomex/graphene-ui/issues/758
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 04, 2016, 11:45:32 am

Yea I had this functionality in before but realized it wasn't adding up sums correctly so I decided to disable it until I could find the time to revisit it and see if I could implement it properly.

Trackable here: https://github.com/cryptonomex/graphene-ui/issues/758

Looks like you closed this out already.  Great!
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 04, 2016, 01:33:01 pm
@svk, very nice move narrowing the buy/sell boxes.  That's a nice enhancement on the vertical layout since the most critical live data elements were already visible.  Unfortunately it doesn't help much on the horizontal layout considering you still have to scroll down to place an order (unless you want to do it blindly i.e. without seeing the all-important order book, which is off the page now).  So now you pretty much always have to scroll to do anything on the horizontal layout, instead of having to scroll only when actually placing an order.  None of the serious UIs are set up like that, and this is one of Poloniex's biggest flaws.  I won't push for it anymore, but I do still hope we can correct that.  If/when we do, I have some additional suggestions for enhancing the horizontal layout.   

As always, thanks for your work on this.

Not sure what more I can do here tbh, on my screen which is 1920x1080 I can now see most of the price chart and most of the orderbook at the same time in horizontal mode, and everything easily in vertical mode. So you would still prefer the orderbook to be on the first row with buy/sell below it?

Thanks a lot for your feedback btw, it's much appreciated!

I would say yes, the order book should be on the first row (along with the history).  There's nothing to gain (only something to lose) by having the buy/sell boxes on the first row because you can't place an order without simultaneously looking at the order book, so you have to scroll in order to place an order either way.  Unless of course you can see both rows without scrolling, in which case you don't care very much about the order of the first 2 rows to begin with. 

As for placing the order book and history on the same row, your newly sized history box proves that it's perfectly viable since each order book box requires no more space than the history box does.  I highly recommend putting those elements together on the first row since it's important for them to be visible along with the chart at the same time.  See my mock-up below.

As for the 2nd row, you may notice that my mock-up also demonstrates we can combine buy and sell into one box in order to avoid needing a 3rd row.  So for those with high enough resolution, now they can see everything without scrolling.   And for those with lower resolution, the need to scroll is minimized.  That would be a nice improvement.  Keep in mind that not all crypto trading sites employ separate buy and sell order boxes.  And I don't think I had ever seen such a thing prior to crypto trading.  I really don't understand what the purpose is.  Seems like it's just a waste of space.

Lastly, also demonstrated in the mock-up below, I would like to propose orienting the order book so the buy side mirrors the sell side such that the bid and ask columns are immediately adjacent to each other.  This is a superior layout for the horizontal order book as it offers one of the great benefits of the vertical order book, but in the horizontal orientation. 

(http://i.imgur.com/jz1OcGo.jpg)
Title: Re: Graphene GUI testing and feedback
Post by: svk on March 04, 2016, 01:53:21 pm
@svk, very nice move narrowing the buy/sell boxes.  That's a nice enhancement on the vertical layout since the most critical live data elements were already visible.  Unfortunately it doesn't help much on the horizontal layout considering you still have to scroll down to place an order (unless you want to do it blindly i.e. without seeing the all-important order book, which is off the page now).  So now you pretty much always have to scroll to do anything on the horizontal layout, instead of having to scroll only when actually placing an order.  None of the serious UIs are set up like that, and this is one of Poloniex's biggest flaws.  I won't push for it anymore, but I do still hope we can correct that.  If/when we do, I have some additional suggestions for enhancing the horizontal layout.   

As always, thanks for your work on this.

Not sure what more I can do here tbh, on my screen which is 1920x1080 I can now see most of the price chart and most of the orderbook at the same time in horizontal mode, and everything easily in vertical mode. So you would still prefer the orderbook to be on the first row with buy/sell below it?

Thanks a lot for your feedback btw, it's much appreciated!

I would say yes, the order book should be on the first row (along with the history).  There's nothing to gain (only something to lose) by having the buy/sell boxes on the first row because you can't place an order without simultaneously looking at the order book, so you have to scroll in order to place an order either way.  Unless of course you can see both rows without scrolling, in which case you don't care very much about the order of the first 2 rows to begin with. 

As for placing the order book and history on the same row, your newly sized history box proves that it's perfectly viable since each order book box requires no more space than the history box does.  I highly recommend putting those elements together on the first row since it's important for them to be visible along with the chart at the same time.  See my mock-up below.

As for the 2nd row, you may notice that my mock-up also demonstrates we can combine buy and sell into one box in order to avoid needing a 3rd row.  So for those with high enough resolution, now they can see everything without scrolling.   And for those with lower resolution, the need to scroll is minimized.  That would be a nice improvement.  Keep in mind that not all crypto trading sites employ separate buy and sell order boxes.  And I don't think I had ever seen such a thing prior to crypto trading.  I really don't understand what the purpose is.  Seems like it's just a waste of space.

Lastly, also demonstrated in the mock-up below, I would like to propose orienting the order book so the buy side mirrors the sell side such that the bid and ask columns are immediately adjacent to each other.  This is a superior layout for the horizontal order book as it offers one of the great benefits of the vertical order book, but in the horizontal orientation. 

(http://i.imgur.com/jz1OcGo.jpg)

Great stuff once more, sometimes it's incredible how you get fixated on how things are until you suddenly see the light. Not once recently have I considering merging the buy/sell but that's what's we had in BTS 1.. I'd prefer to do it like in BTS 1 though where you have to switch between buy/sell, because of how the prices need to be handled. It might work the way you show it but it'll probably be a bit complicated.

I think I was a bit tired when I last read your feedback though cause I never got the fact you wanted the history with the orderbook but of course that makes sense.

"My positions" would have a maximum of 2 positions but I suppose it would be handy to have there.

Edit: Forgot one thing: I actually used to have the orderbook mirrored like you suggest, but think I removed it because people were complaining about it not being the same as Polo... I do agree that it's far more convenient that way though. Anyone else have an opinion on that?
Title: Re: Graphene GUI testing and feedback
Post by: svk on March 04, 2016, 02:22:27 pm
Might not even be necessary to combine the buy/sell; how does this look to you all:

(http://i.imgur.com/i5jtSeU.png)
Title: Re: Graphene GUI testing and feedback
Post by: Akado on March 04, 2016, 07:05:25 pm
I could swear on my Open Orders my METAFEES order for METAEX.BTC wasn't showing. Then I went to the market pair and it was there, then I went to my Open Orders tab and it now appears.
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 05, 2016, 08:51:38 pm
@svk:  My suggestion to combine buy/sell was really only to save enough space in order to put the My Orders box on the second row.  But if you can do so without combining buy/sell, I agree that it's unnecessary to combine them at this time.

Speaking of My Orders, my suggestion to add My Positions was to show ALL positions, not just the positions for the current market.  This way we can see how our positions are doing without leaving the trading screen.  If we can add (either now or at a later date) P/L for each position, that would be great.  Also, each position should have a link which loads that market into the current view.  This would b a nice enhancement.

As for the mirrored order books, I'm glad we agree that it makes more sense that way.  Although perhaps we could give users the option.  Maybe the order book could have a gear icon that allows the user to choose 1) mirrored or not, and 2)  bid/ask vs. ask/bid (even though I've never understood why anyone would ever want to reverse the bid and ask window positions). 
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 07, 2016, 09:06:05 am
@svk: Another suggestion. It would be helpful if there was greater visual distinction between the order book boxes and the history box.  For that and other reasons, I highly recommend removing the color coding from the bid and ask values since the colors don't vary from one value to the next (so the values themselves don't need to be color coded, just the box itself).  On the other hand, the color coding of the trades in the history does vary and therefore the individual values should remain color coded. 

In addition to the thin line in the headers of the bid and ask order books, you could also color code the entire header.  You can also place a thin box around both the bid and ask columns, which would have the additional benefit of calling attention to specifically which columns are the bid and ask columns.  I also recommend changing the bid/ask column headers to "Bid" and "Ask" instead of both saying "Price".  See image below.

On another note, the chart has become a bit short, too short to reasonably display indicators.  I think that is fine as the default, but it would be really nice if the user could choose to expand its height.  Perhaps you can put a gear icon in the chart header to select chart height: short, medium, tall?  Or even better, can the chart be sized by grabbing the bottom edge of it and dragging it down/up?  That would be great if it's possible.

(http://i.imgur.com/E1TQcNR.jpg)
Title: Re: Graphene GUI testing and feedback
Post by: DestBest on March 07, 2016, 12:18:20 pm
Dropping this here: A cool way to display your portfolio data (www.c*inigy.com)
(https://i.imgur.com/y60HPJg.png)
Title: Re: Graphene GUI testing and feedback
Post by: Akado on March 07, 2016, 01:18:03 pm
@DestBest woah that seems like a nice idea. That way an user could see if his portfolio grew in value throughout time in relation to a certain currency, like BTC for example. That would be a nice addition. Not one that is really needed but a fancy one. That's the type of stuff that will make the user have an attachment to the platform, those small details.
Title: Re: Graphene GUI testing and feedback
Post by: Louis on March 08, 2016, 12:55:05 am
@DestBest woah that seems like a nice idea. That way an user could see if his portfolio grew in value throughout time in relation to a certain currency, like BTC for example. That would be a nice addition. Not one that is really needed but a fancy one. That's the type of stuff that will make the user have an attachment to the platform, those small details.

^^^^^This
Title: Re: Graphene GUI testing and feedback
Post by: Shentist on March 10, 2016, 08:10:35 pm
what's really annoying is the rounding error when i buy or sell. Sometimes you click on the row you want to buy or sell and send the
order, but they are not matching, because of rounding errors on the 0.000001 part. this should be fixed. maybe round up or down, that the order
matches. i think no one cares if i round up .000005 or so satoshi, but anyone cares, if he hast to chancel more then 1 time the order.
costs time and the rounding error would be less expensive then the cancel fee.
Title: Re: Graphene GUI testing and feedback
Post by: jsidhu on March 12, 2016, 03:35:59 am
Gui is pretty nice now that i finally got around to importing my wallet. How does the light client work? just as a relay node? Perhaps on the release page take out the word light if its the only wallst we give. The witnesses im sure know to use cli. Overall pretty good, I prefer to hook into a well known trading api for the dex stuff rather than doing it on our own.. thats the only major inprovement i can see.
Title: Re: Graphene GUI testing and feedback
Post by: Akado on March 13, 2016, 04:08:31 pm
latest version saying it's synchronized when it isnt

(http://i.imgur.com/fx5B8OT.png)
Title: Re: Graphene GUI testing and feedback
Post by: Shentist on March 13, 2016, 08:02:13 pm
latest version saying it's synchronized when it isnt

(http://i.imgur.com/fx5B8OT.png)

in the past it helped to check the clocktime of your computer and close all browser windows and start fresh (or are you using the lightclient?)
Title: Re: Graphene GUI testing and feedback
Post by: Akado on March 13, 2016, 08:06:21 pm
latest version saying it's synchronized when it isnt

(http://i.imgur.com/fx5B8OT.png)

in the past it helped to check the clocktime of your computer and close all browser windows and start fresh (or are you using the lightclient?)

Lightclient. I had no problems syncing, I just had to wait. It's just that someone who isn't used to BitShares might find it confusing.
Title: Re: Graphene GUI testing and feedback
Post by: Shentist on March 13, 2016, 08:12:20 pm
but what are really funny - my client is now also out of sync, so maybe not a local problem on your side!
Title: Re: Graphene GUI testing and feedback
Post by: Akado on March 14, 2016, 01:16:41 am
but what are really funny - my client is now also out of sync, so maybe not a local problem on your side!

I found it strange because I've never seen it out of sync. It ended up syncing after a few minutes though. Don't know what happened.
Title: Re: Graphene GUI testing and feedback
Post by: tbone on March 15, 2016, 05:57:07 pm
@svk:  I've been meaning to comment on the last release and offer additional feedback, just been so busy lately.  But great job with the latest changes to the horizontal order book layout.   Also, the expand and contract buttons on the chart are very helpful.  And the chart timeframes make more sense now (e.g. there was no need for 5s).  Although if it's a relatively easy matter to add them, I would go ahead and add 1m, 2h, 6h, 12h and 1w.  If it's time consuming to add each one, I would add 1m immediately and hold off on the others for now. 

Also with respect to the chart, something has changed where the volume bars now obscure view of the candlesticks.  It was definitely much better before.  And final point about the chart...we once had a crosshair, and now it is just a vertical line.  Can you make it a cross hair again, and have the price of the vertical line's position show on the vertical axis as the crosshair moves?  That would mimic standard behavior. 

By the way, while the horizontal layout is much improved now, the vertical layout has taken a step backwards with the ticker (price history) now pushed further down.  For the very same reasons the price history has been moved immediately below the chart in the horizontal layout, the same should be true on the vertical layout. 

Also, when you click on the order book, it is adding the cumulative available orders and putting a value into the order box, but it's not calculating properly.  Can you take a look at that?

Beyond that, we really need to start working toward having some basic position management.  I mentioned in a previous post that the Open Orders box could be modified to include a Current Positions view.  So the box could have 2 tabs for the user to choose between.  The tab headers could include the number of items in the list like below.  Also, Open Positions could show the P/L (% gain or loss) for each position.  And each position could be hyperlinked so the user can click to load that market into the current view in order to assess the situation and/or close out or add to their position.

|  Open Orders (1)    |   Current Positions (5)  |

Finally, there is still some strange behavior with the Find Markets tab.  For example, if I enter "OPEN.EUR", it returns the OPEN.EUR pairs with BTS, BTC, USD, CNY...but not EUR.  Do you know why that is? 

Title: Re: Graphene GUI testing and feedback
Post by: Pheonike on March 15, 2016, 06:07:38 pm
I think you should move the horizontal/vertical selector into the bar next to the chart options button. This would make it cleaner and keep it in a consistent spot in the UI.
Title: Re: Graphene GUI testing and feedback
Post by: svk on March 16, 2016, 11:39:51 am
@svk:  I've been meaning to comment on the last release and offer additional feedback, just been so busy lately.  But great job with the latest changes to the horizontal order book layout.   Also, the expand and contract buttons on the chart are very helpful.  And the chart timeframes make more sense now (e.g. there was no need for 5s).  Although if it's a relatively easy matter to add them, I would go ahead and add 1m, 2h, 6h, 12h and 1w.  If it's time consuming to add each one, I would add 1m immediately and hold off on the others for now. 

Also with respect to the chart, something has changed where the volume bars now obscure view of the candlesticks.  It was definitely much better before.  And final point about the chart...we once had a crosshair, and now it is just a vertical line.  Can you make it a cross hair again, and have the price of the vertical line's position show on the vertical axis as the crosshair moves?  That would mimic standard behavior. 

By the way, while the horizontal layout is much improved now, the vertical layout has taken a step backwards with the ticker (price history) now pushed further down.  For the very same reasons the price history has been moved immediately below the chart in the horizontal layout, the same should be true on the vertical layout. 

Also, when you click on the order book, it is adding the cumulative available orders and putting a value into the order box, but it's not calculating properly.  Can you take a look at that?

Beyond that, we really need to start working toward having some basic position management.  I mentioned in a previous post that the Open Orders box could be modified to include a Current Positions view.  So the box could have 2 tabs for the user to choose between.  The tab headers could include the number of items in the list like below.  Also, Open Positions could show the P/L (% gain or loss) for each position.  And each position could be hyperlinked so the user can click to load that market into the current view in order to assess the situation and/or close out or add to their position.

|  Open Orders (1)    |   Current Positions (5)  |

Finally, there is still some strange behavior with the Find Markets tab.  For example, if I enter "OPEN.EUR", it returns the OPEN.EUR pairs with BTS, BTC, USD, CNY...but not EUR.  Do you know why that is?

I put the volume bars and the candlesticks on the same y-axis, it gives more space to each one so I prefer it that way at least. In the process the axis indexes changed which is why the crosshair disappeared, I hadn't even noticed but I'll put them back in.

The chart timeframes are defined in the backend, but I decided to filter out anything below 5 minutes because with the low volume we have it just doesn't show anything useful atm. If you really think 1m is useful I can set the cutoff there.

Clicking on the orderbook appears correct to me, I tried to be very careful when I refactored it and checking now I can't find anything wrong. It uses the Total and the Price for that order to calculate the corresponding Amount. That's how it works on Polo as well as far as I can tell. If you think it should work differently, can you give me an example please?

Position management like you say sounds nice, but not sure it's feasible with our current system. A margin position doesn't have any other information attached to it besides the collateral and debt. Whether you've gone short with it or not I don't know, so I don't see how I can define a gain/loss there.

Find markets looks for markets with 4 default quotes, the ones you mentioned. It's simply a case of having to limit the search results in order to not overload the witness node with searches, so I picked the 4 most important assets as I see it..
Title: Re: Graphene GUI testing and feedback
Post by: oldmine on March 16, 2016, 11:50:46 am
Any ETA on when we can try out the trollbox?
Title: Re: Graphene GUI testing and feedback
Post by: Empirical1.2 on March 17, 2016, 04:44:34 pm
https://bitshares.openledger.info/#/explorer/markets

We can't expect new users to know the difference between various type of assets, it looks incredibly confusing. They should be grouped separately with a clear description of what each group of assets represents and then described individually within that grouping too imo.

This page is currently sub-divided into currency groups BTS, BTC, USD, CNY, Others

I would group them as...

Smartcoins         Decentralized price stable currencies collateralized by BTS
MetaExchange   (Description of MetaExchange assets)
OpenLedger       (Desrcription of open ledger assets)
BlockTrades       (Description)
Etc.
 
Next to each individual entry, I would also add a description similar to that found on cryptofresh http://cryptofresh.com/assets & they should be listed by Market Cap/Volume. (ie. most popular first, paretto principle)

You could also have sub-headings for UIA's and PMA's on this page again with a description.

Other

People buying SmartCoins are interested in what % above/below the peg they're buying or selling.

So a line above showing  0.98  0.98 0.99 1.00 1.01 1.02 1.03 would let people easily calculate their orders and track them.

Title: Re: Graphene GUI testing and feedback
Post by: Shentist on March 31, 2016, 12:17:29 pm
who had this "great" idea to label all assets with a STAR ?

my feedback on this. it will not help the users to understand the difference in 4 BTC* . i would like to know, where i can find,
on which place this was discussed? Lately it seems it is not enough to follow the forum to be aware of this changes.

i think it would much better to make first mockups and ask for feedback and not change something you think it is good.

as a daily user of the wallet, this helps me 0 and makes my life not 1 once easier in the wallet. I think it has the opposite effect.
this is not a step forward!

at the moment i have no solution, but it is not better then before and in fact, makes my daily trading not easier.
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on March 31, 2016, 01:23:20 pm
who had this "great" idea to label all assets with a STAR ?

my feedback on this. it will not help the users to understand the difference in 4 BTC* . i would like to know, where i can find,
on which place this was discussed? Lately it seems it is not enough to follow the forum to be aware of this changes.

i think it would much better to make first mockups and ask for feedback and not change something you think it is good.

as a daily user of the wallet, this helps me 0 and makes my life not 1 once easier in the wallet. I think it has the opposite effect.
this is not a step forward!

at the moment i have no solution, but it is not better then before and in fact, makes my daily trading not easier.

I don't like it either.  Its more difficult to find the specific BTC I'm looking for having to hover over every pair.

What about keeping the * to indicate an abbreviated label but make it an option in settings, as well as separating/ sorting the markets by Exchange in the my markets list.  So you might have a METAEX, OPEN, TRADE and ALL tab or select in a drop down.  And this displays only those markets with a Quote currency of METAEX.xxx etc.   

OR instead of stars you could change the color of the prefix or slightly fade the letters, smaller or different font?.

Title: Re: Graphene GUI testing and feedback
Post by: Shentist on March 31, 2016, 05:44:27 pm
i thought about is today and i realized we should maybe structure it this way:

Trading on the top nav bar should be leading to this section who is available in "Explorer" "Assets"

and this section should not be available via alphabetical, but how many trades are happen and how many user are holding the assets.

with this each section is clear structured. if i choose a SMARTCOIN asset i am in the section i want to trade SMARTCOINS etc.

we should think about to give colors to each section so that is clear where i am, like SMARTCOINS : blue, UIA: GREEN, PREDICTIONMARKETS: YELLOW

what should also available ist a button in the trading section who i get to this page for each asset : https://bitshares.org/wallet/#/asset/USD
so informations on the trading section to this pairs.
Title: Re: Graphene GUI testing and feedback
Post by: svk on March 31, 2016, 09:27:46 pm
I'll be making the asset names clickable in the next update so you can keep the full names if you prefer. It was a change requested by the Maker team and it made sense to me to apply it for Openledger as well. I doubt there are many people actually trading the EUR:EUR* pairs etc but I can understand that it's confusing for those few of you who do, but having a whole mess of UIAs makes little sense to newcomers so the more it looks like the actual asset the better imo.

In the end I reckon we should remove all non-OPEN assets from Openledger (default pairs) and even the bridges and gateways. They'll all be available in the light client but Openledger should prioritize their own assets in their hosted wallet.
Title: Re: Graphene GUI testing and feedback
Post by: Shentist on March 31, 2016, 10:28:27 pm
I'll be making the asset names clickable in the next update so you can keep the full names if you prefer. It was a change requested by the Maker team and it made sense to me to apply it for Openledger as well. I doubt there are many people actually trading the EUR:EUR* pairs etc but I can understand that it's confusing for those few of you who do, but having a whole mess of UIAs makes little sense to newcomers so the more it looks like the actual asset the better imo.

In the end I reckon we should remove all non-OPEN assets from Openledger (default pairs) and even the bridges and gateways. They'll all be available in the light client but Openledger should prioritize their own assets in their hosted wallet.

if this is planed, pls remove openledger as the default wallet on the offical website.
Title: Re: Graphene GUI testing and feedback
Post by: tonyk on April 01, 2016, 01:08:36 am
In the end I reckon we should remove all non-OPEN assets from Openledger (default pairs) and even the bridges and gateways. They'll all be available in the light client but Openledger should prioritize their own assets in their hosted wallet.

So let me see if I get it right.

BTS pays a worker  for the GUI development... this development 'improves' the wallet by removing non-OPEN assets from the wallet (aka reducing the available choices to customer-owners-BTS-holders).... and this is all done so OL's products are not confused with the products of the competitors.. [products hidden include the BTS flagship product - the bitAssets -as well, isn't it]
In this whole thing OL pays nothing because?... ok, all right, it is the leading wallet for BTS....

Nothing personal svk, I just think this flashes out how the whole worker system is screwed in far more ways than one.... and @BunkerChain Labs  I see how you see the system being attacked by the so called "anti-dilutionalists"... if you are able to see the trueth regardless of your own agenda/bias... the above is an example  how it is attacked by full-on-No-checks-dilutionalists  as well.
Things/stuff is very rarely black or white...
Title: Re: Graphene GUI testing and feedback
Post by: BunkerChainLabs-DataSecurityNode on April 01, 2016, 01:36:09 am
In the end I reckon we should remove all non-OPEN assets from Openledger (default pairs) and even the bridges and gateways. They'll all be available in the light client but Openledger should prioritize their own assets in their hosted wallet.

So let me see if I get it right.

BTS pays a worker  for the GUI development... this development 'improves' the wallet by removing non-OPEN assets from the wallet (aka reducing the available choices to customer-owners-BTS-holders).... and this is all done so OL's products are not confused with the products of the competitors.. [products hidden include the BTS flagship product - the bitAssets -as well, isn't it]
In this whole thing OL pays nothing because?... ok, all right, it is the leading wallet for BTS....

Nothing personal svk, I just think this flashes out how the whole worker system is screwed in far more ways than one.... and @BunkerChain Labs  I see how you see the system being attacked by the so called "anti-dilutionalists"... if you are able to see the trueth regardless of your own agenda/bias... the above is an example  how it is attacked by full-on-No-checks-dilutionalists  as well.
Things/stuff is very rarely black or white...

I agree with you @tonyk ... a move like that is effectively removes what is supposed to be a 'network effect' that is supposed to encourage others to join the ecosystem. If there is no shared space for newcomers coming in the 'default' channel to Bitshares, then this is private.. and shouldn't be supported by a Worker or Bitshares.

What is the value proposition of the network effect if they are all going to be hidden from sight? Why would a business bother attempting to contribute to OpenLedger development in this kind of situation?

There would be less confusion if there was more information on what people are using... but of all the development of the wallet this somehow has taken a backseat to rearrangements and stars.

I understand with svks work he is designing and coming up with ways to make the wallet better that doesn't require constant input from the community... but this kind of change really requires feedback.

If this change happens then Ronny should be paying svks development wages and not Bitshares.
Title: Re: Graphene GUI testing and feedback
Post by: svk on April 01, 2016, 05:03:29 am
Right, you can always count on members of this community to overreact and proclaim gloom and doom at the slightest thing... :(

My suggestions for openledger were just that, suggestions! Yes I said "we" but that doesn't mean I would do it myself, nor that it absolutely will be done. You may notice that I never made any commits to the OL repo, that's handled by Valentine.. You can't deny that it would make sense for Openledger to prioritize their own offerings though?? In the end it's up to Ronny to decide that though.

There's also a wallet at bitshares.org/wallet which should remain a standard wallet offering the full complexity and all gateway providers, same for the light client. Again, suggestions, not a roadmap...

Sometimes I wonder why I bother tbh..


Title: Re: Graphene GUI testing and feedback
Post by: Shentist on April 01, 2016, 05:59:29 am
I'll be making the asset names clickable in the next update so you can keep the full names if you prefer. It was a change requested by the Maker team and it made sense to me to apply it for Openledger as well. I doubt there are many people actually trading the EUR:EUR* pairs etc but I can understand that it's confusing for those few of you who do, but having a whole mess of UIAs makes little sense to newcomers so the more it looks like the actual asset the better imo.

In the end I reckon we should remove all non-OPEN assets from Openledger (default pairs) and even the bridges and gateways. They'll all be available in the light client but Openledger should prioritize their own assets in their hosted wallet.
Right, you can always count on members of this community to overreact and proclaim gloom and doom at the slightest thing... :(

My suggestions for openledger were just that, suggestions! Yes I said "we" but that doesn't mean I would do it myself, nor that it absolutely will be done. You may notice that I never made any commits to the OL repo, that's handled by Valentine.. You can't deny that it would make sense for Openledger to prioritize their own offerings though?? In the end it's up to Ronny to decide that though.

There's also a wallet at bitshares.org/wallet which should remain a standard wallet offering the full complexity and all gateway providers, same for the light client. Again, suggestions, not a roadmap...

Sometimes I wonder why I bother tbh..

@svk

if you read your original post carefully and assume that you don't know how things are working in the "innercircle" you have to admit, that your post left the
impression, that you directly decide about the features. From this perspective it is a major statement.

I am worried i woke one day up and i can't access anymore my assets, because someone decided to do something, without public discussion.

So my quesion is not answered "where can i find the discussion about removing the Prefixes for UIAs in the wallet?" After your post i assume there is
not such a discussion and this leads me to some major points here.

We have a committe who votes on fees etc. but we just pay for the development of a wallet, but in the end the community has nothing to say what should
be done or not done in the official repo. This is something to discuss. I personal have the feeling that most of the developers are not using the webwallet on
a daily basis for trading.

At the moment Openledger is treated as BitShares, so if the strategy of the Openledger is changing i see no reason why every major button on bitshares.org leads to
the openledger wallet and not to a wallet hosted by the community.

cheers
Title: Re: Graphene GUI testing and feedback
Post by: svk on April 01, 2016, 06:10:33 am
I'll be making the asset names clickable in the next update so you can keep the full names if you prefer. It was a change requested by the Maker team and it made sense to me to apply it for Openledger as well. I doubt there are many people actually trading the EUR:EUR* pairs etc but I can understand that it's confusing for those few of you who do, but having a whole mess of UIAs makes little sense to newcomers so the more it looks like the actual asset the better imo.

In the end I reckon we should remove all non-OPEN assets from Openledger (default pairs) and even the bridges and gateways. They'll all be available in the light client but Openledger should prioritize their own assets in their hosted wallet.
Right, you can always count on members of this community to overreact and proclaim gloom and doom at the slightest thing... :(

My suggestions for openledger were just that, suggestions! Yes I said "we" but that doesn't mean I would do it myself, nor that it absolutely will be done. You may notice that I never made any commits to the OL repo, that's handled by Valentine.. You can't deny that it would make sense for Openledger to prioritize their own offerings though?? In the end it's up to Ronny to decide that though.

There's also a wallet at bitshares.org/wallet which should remain a standard wallet offering the full complexity and all gateway providers, same for the light client. Again, suggestions, not a roadmap...

Sometimes I wonder why I bother tbh..

@svk

if you read your original post carefully and assume that you don't know how things are working in the "innercircle" you have to admit, that your post left the
impression, that you directly decide about the features. From this perspective it is a major statement.

I am worried i woke one day up and i can't access anymore my assets, because someone decided to do something, without public discussion.

So my quesion is not answered "where can i find the discussion about removing the Prefixes for UIAs in the wallet?" After your post i assume there is
not such a discussion and this leads me to some major points here.

We have a committe who votes on fees etc. but we just pay for the development of a wallet, but in the end the community has nothing to say what should
be done or not done in the official repo. This is something to discuss. I personal have the feeling that most of the developers are not using the webwallet on
a daily basis for trading.

At the moment Openledger is treated as BitShares, so if the strategy of the Openledger is changing i see no reason why every major button on bitshares.org leads to
the openledger wallet and not to a wallet hosted by the community.

cheers

Well most of the time I do decide, because I'm the only one actually working on the GUI, and if I had to vet every decision I'd never get anywhere. Your worry about not being able to access your assets is completely unreasonable and unfounded, all we're talking about here is limiting the default market pairs as well as the gateway providers. You'd still be able to search for and add any market pairs you like. Some of those changes were mentioned here for example: https://bitsharestalk.org/index.php/topic,21997.0.html

I'm pretty sure I've seen several people asking for a way to hide the prefixes for gateway assets before, but seeing how the search function on this forum is useless I don't wanna waste my time looking for it.
Title: Re: Graphene GUI testing and feedback
Post by: Shentist on April 01, 2016, 06:15:06 am
Quote
Your worry about not being able to access your assets is completely unreasonable and unfounded, all we're talking about here is limiting the default market pairs as well as the gateway providers.

i compared to the MAKER wallet and in their wallet i cannot recieve or send other tokens as MKR, DAI and OPEN assets, because this functions are not included at all.
Title: Re: Graphene GUI testing and feedback
Post by: svk on April 01, 2016, 06:19:24 am
Quote
Your worry about not being able to access your assets is completely unreasonable and unfounded, all we're talking about here is limiting the default market pairs as well as the gateway providers.

i compared to the MAKER wallet and in their wallet i cannot recieve or send other tokens as MKR, DAI and OPEN assets, because this functions are not included at all.

Not sure what you mean by that.
Title: Re: Graphene GUI testing and feedback
Post by: Shentist on April 01, 2016, 06:28:10 am
Quote
Your worry about not being able to access your assets is completely unreasonable and unfounded, all we're talking about here is limiting the default market pairs as well as the gateway providers.

i compared to the MAKER wallet and in their wallet i cannot recieve or send other tokens as MKR, DAI and OPEN assets, because this functions are not included at all.

Not sure what you mean by that.

in the maker wallet i cannot recieve or send BTS
Title: Re: Graphene GUI testing and feedback
Post by: svk on April 01, 2016, 06:39:18 am
Quote
Your worry about not being able to access your assets is completely unreasonable and unfounded, all we're talking about here is limiting the default market pairs as well as the gateway providers.

i compared to the MAKER wallet and in their wallet i cannot recieve or send other tokens as MKR, DAI and OPEN assets, because this functions are not included at all.

Not sure what you mean by that.

in the maker wallet i cannot recieve or send BTS

Through an integrated gateway no, they decided to limit the gateways. But as far as I can tell the Transfer function is unchanged, and if you have BTS in your account you will be able to use it however you like.
Title: Re: Graphene GUI testing and feedback
Post by: Shentist on April 01, 2016, 06:44:47 am
Quote
Your worry about not being able to access your assets is completely unreasonable and unfounded, all we're talking about here is limiting the default market pairs as well as the gateway providers.

i compared to the MAKER wallet and in their wallet i cannot recieve or send other tokens as MKR, DAI and OPEN assets, because this functions are not included at all.

Not sure what you mean by that.

in the maker wallet i cannot recieve or send BTS

Through an integrated gateway no, they decided to limit the gateways. But as far as I can tell the Transfer function is unchanged, and if you have BTS in your account you will be able to use it however you like.

ah, ok. then i missunderstand the "send" button. It shows no options, because i have no funds in this wallet. ok, my bad. then it is everything fine. speaks nothing with the default pairs to be some chosen pairs. maybe you can look some post above i made suggestions how we could maybe make different pairs clearer.

i personally think the prefixes has to been in the wallet displayed and when you make it METAEX.BTC and different colors like suggested could also help.
Title: Re: Graphene GUI testing and feedback
Post by: liondani on April 01, 2016, 11:56:43 am
i personally think the prefixes has to been in the wallet displayed and when you make it METAEX.BTC and different colors like suggested could also help.

 +5%

METAEX.BTC
Title: Re: Graphene GUI testing and feedback
Post by: EstefanTT on April 02, 2016, 12:47:04 pm
It seems that the "VISIT WEBSITE" link in th e deposit tab of metaexchange and blocktrades is the same. Both lead to blocktrades.

Another thing I notice, I explained it in the telegram chat but it's probably better in here :

When you got to the page to create a asset and click on create an asset, you are stuck on this asset creation page, you can't go back anywhere. If you create or not the asset doesn't change the fact that any button of the client is responding except for the ones to do the asset. So you can't go back to overview or trade or other tabs.


Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on April 02, 2016, 04:06:13 pm
(http://content.screencast.com/users/Enkianu/folders/Jing/media/d3046507-dd23-4cfd-aece-3bfc82be02e8/2016-04-01_2322.png)
Title: Re: Graphene GUI testing and feedback
Post by: Shentist on April 02, 2016, 04:25:38 pm
(http://content.screencast.com/users/Enkianu/folders/Jing/media/d3046507-dd23-4cfd-aece-3bfc82be02e8/2016-04-01_2322.png)

looking great :D could be 1 step to make it clearer which asset is which type.
Title: Re: Graphene GUI testing and feedback
Post by: EstefanTT on April 03, 2016, 11:14:24 am
I have a suggestion.

At the moment, there is a lot of pairs that are display weirdly when you look at the market depth. Mainely because the lack of liquidity.

At Bittrex, they solved this problem having in their charts options a % of price range available to choose when looking at the market depth.

You have 25% by default but can select 50%, 75% and all. That's very useful when you want to see how buy and sell orders are spread on the whole market, where the big supports or resistances, ect ...

As we still have some space in the GUI there, we could have this option.

I strongly beleive that we should gather in the DEX GUI every single advantage (even tiny ones) that other exchanges have ;)

Just my 2 bts ;p


Title: Re: Graphene GUI testing and feedback
Post by: svk on April 03, 2016, 12:25:36 pm
I have a suggestion.

At the moment, there is a lot of pairs that are display weirdly when you look at the market depth. Mainely because the lack of liquidity.

At Bittrex, they solved this problem having in their charts options a % of price range available to choose when looking at the market depth.

You have 25% by default but can select 50%, 75% and all. That's very useful when you want to see how buy and sell orders are spread on the whole market, where the big supports or resistances, ect ...

As we still have some space in the GUI there, we could have this option.

I strongly beleive that we should gather in the DEX GUI every single advantage (even tiny ones) that other exchanges have ;)

Just my 2 bts ;p
Good idea.
Title: Re: Graphene GUI testing and feedback
Post by: tbone on April 03, 2016, 05:13:10 pm
@svk:  I've been meaning to comment on the last release and offer additional feedback, just been so busy lately.  But great job with the latest changes to the horizontal order book layout.   Also, the expand and contract buttons on the chart are very helpful.  And the chart timeframes make more sense now (e.g. there was no need for 5s).  Although if it's a relatively easy matter to add them, I would go ahead and add 1m, 2h, 6h, 12h and 1w.  If it's time consuming to add each one, I would add 1m immediately and hold off on the others for now. 

Also with respect to the chart, something has changed where the volume bars now obscure view of the candlesticks.  It was definitely much better before.  And final point about the chart...we once had a crosshair, and now it is just a vertical line.  Can you make it a cross hair again, and have the price of the vertical line's position show on the vertical axis as the crosshair moves?  That would mimic standard behavior. 

By the way, while the horizontal layout is much improved now, the vertical layout has taken a step backwards with the ticker (price history) now pushed further down.  For the very same reasons the price history has been moved immediately below the chart in the horizontal layout, the same should be true on the vertical layout. 

Also, when you click on the order book, it is adding the cumulative available orders and putting a value into the order box, but it's not calculating properly.  Can you take a look at that?

Beyond that, we really need to start working toward having some basic position management.  I mentioned in a previous post that the Open Orders box could be modified to include a Current Positions view.  So the box could have 2 tabs for the user to choose between.  The tab headers could include the number of items in the list like below.  Also, Open Positions could show the P/L (% gain or loss) for each position.  And each position could be hyperlinked so the user can click to load that market into the current view in order to assess the situation and/or close out or add to their position.

|  Open Orders (1)    |   Current Positions (5)  |

Finally, there is still some strange behavior with the Find Markets tab.  For example, if I enter "OPEN.EUR", it returns the OPEN.EUR pairs with BTS, BTC, USD, CNY...but not EUR.  Do you know why that is?

I put the volume bars and the candlesticks on the same y-axis, it gives more space to each one so I prefer it that way at least. In the process the axis indexes changed which is why the crosshair disappeared, I hadn't even noticed but I'll put them back in.

I've been meaning to respond to this for some time, but I've been so busy.  In any event, I appreciate your reasoning here.  Having both on the same y-axis works well on Poloniex and TradingView, to name a couple.  But I guess with the colors those sites use, the volume bars don't obscure the candlesticks nearly as much.  And in TradingView you can easily hide and unhide the volume with the click of the mouse.  I often wish I could do that on Poloniex as well.  Maybe you can add that capability on the DEX.  It would be helpful.

The chart timeframes are defined in the backend, but I decided to filter out anything below 5 minutes because with the low volume we have it just doesn't show anything useful atm. If you really think 1m is useful I can set the cutoff there.

Once we start getting much more active trading in some of these markets, there will be traders who scalp that will need 1m charts. 


Clicking on the orderbook appears correct to me, I tried to be very careful when I refactored it and checking now I can't find anything wrong. It uses the Total and the Price for that order to calculate the corresponding Amount. That's how it works on Polo as well as far as I can tell. If you think it should work differently, can you give me an example please?

This is definitely not working properly.  What we want is for the total price of the buy/sell order to be populated with the sum of the prices of each row up to the one clicked.  What you're doing is taking the cumulative number of shares and dividing it by the price of the row clicked.  But that doesn't give the actual number of shares available. 

Poloniex, on the other hand, adds the number of shares row by row the way I'm suggesting.  That's what's good about how they auto-populate the order information.  But then unfortunately, when it comes to the price, they do something similar to what you're doing i.e. they calculate the total buy/sell price by multiplying the total number of shares by the price of the row clicked.  That overestimates the cost of the trade when they could easily give the exact total price of the actual shares available on the order book up to the row clicked. 

In summary, to be as useful as possible, both values (amount of shares to buy/sell, and total price of the transaction) should be sums of the corresponding values in each of the rows up to the one clicked.   This is another case where if we get it right, we'll be superior to the others.  That should bode well for us once we get what I hope will soon be an influx of people looking to trade LISK (and hopefully other assets) here on the DEX.

Title: Re: Graphene GUI testing and feedback
Post by: tbone on April 04, 2016, 07:14:57 am
@svk:  I've been meaning to comment on the last release and offer additional feedback, just been so busy lately.  But great job with the latest changes to the horizontal order book layout.   Also, the expand and contract buttons on the chart are very helpful.  And the chart timeframes make more sense now (e.g. there was no need for 5s).  Although if it's a relatively easy matter to add them, I would go ahead and add 1m, 2h, 6h, 12h and 1w.  If it's time consuming to add each one, I would add 1m immediately and hold off on the others for now. 

Also with respect to the chart, something has changed where the volume bars now obscure view of the candlesticks.  It was definitely much better before.  And final point about the chart...we once had a crosshair, and now it is just a vertical line.  Can you make it a cross hair again, and have the price of the vertical line's position show on the vertical axis as the crosshair moves?  That would mimic standard behavior. 

By the way, while the horizontal layout is much improved now, the vertical layout has taken a step backwards with the ticker (price history) now pushed further down.  For the very same reasons the price history has been moved immediately below the chart in the horizontal layout, the same should be true on the vertical layout. 

Also, when you click on the order book, it is adding the cumulative available orders and putting a value into the order box, but it's not calculating properly.  Can you take a look at that?

Beyond that, we really need to start working toward having some basic position management.  I mentioned in a previous post that the Open Orders box could be modified to include a Current Positions view.  So the box could have 2 tabs for the user to choose between.  The tab headers could include the number of items in the list like below.  Also, Open Positions could show the P/L (% gain or loss) for each position.  And each position could be hyperlinked so the user can click to load that market into the current view in order to assess the situation and/or close out or add to their position.

|  Open Orders (1)    |   Current Positions (5)  |

Finally, there is still some strange behavior with the Find Markets tab.  For example, if I enter "OPEN.EUR", it returns the OPEN.EUR pairs with BTS, BTC, USD, CNY...but not EUR.  Do you know why that is?

Position management like you say sounds nice, but not sure it's feasible with our current system. A margin position doesn't have any other information attached to it besides the collateral and debt. Whether you've gone short with it or not I don't know, so I don't see how I can define a gain/loss there.

I understand there are factors that make it difficult or impossible to offer true position management at this time.  But my original suggestion was to start at least for now by simply listing the Open Positions (i.e. balances) in each asset.  That would be very helpful because currently the only way to see your balances is to navigate into the account area.  Then you have to navigate back to the trading screen.  This makes for a very disjointed and inefficient experience.  Instead, the Open Orders box could have 2 tabs so you could also display Open Positions (again, that's simply the balances in each asset).  That would allow the trader to easily switch between those assets in order to assess each market's vitals and potentially close, reduce or add to one of the positions. 

Find markets looks for markets with 4 default quotes, the ones you mentioned. It's simply a case of having to limit the search results in order to not overload the witness node with searches, so I picked the 4 most important assets as I see it..

Perhaps you can display the EUR pair (or anything that doesn't fall under the primary 4) under "OTHER" so the results won't be unexpected and confusing due to missing pairs?

By the way, it used to be that clicking on the "Trade" main menu item when already on the Trade page would take you to Explore-->Markets.  That was very handy.  Now it requires a bunch of navigating to go back and forth.  Can you reinstate that original toggle or create a new one? 

One final suggestion, can you create a way for the user to toggle the My Markets / Find Markets column between normal and full length (i.e. toggle the mini depth chart in and out of view)?  That would be handy.

Thanks @svk as always for all of your effort on the UI.  It just keeps getting better and better!
Title: Re: Graphene GUI testing and feedback
Post by: tbone on April 08, 2016, 09:15:39 pm
Hi @svk, could you please give us some visibility into your immediate roadmap for the GUI?  Which of the ideas in this and other forum threads are making it into upcoming releases?  Also, do you have any questions about my post re: auto-population of the order form?  I think it would be very helpful to have a little more dialog in order to ensure everything important gets buttoned up, and I do have at least one other issue (a pretty critical one, actually) that I'd like to take the time to write up once I know we have some dialog going.  Thanks in advance.
Title: Re: Graphene GUI testing and feedback
Post by: svk on April 18, 2016, 12:56:24 pm
Hi @svk, could you please give us some visibility into your immediate roadmap for the GUI?  Which of the ideas in this and other forum threads are making it into upcoming releases?  Also, do you have any questions about my post re: auto-population of the order form?  I think it would be very helpful to have a little more dialog in order to ensure everything important gets buttoned up, and I do have at least one other issue (a pretty critical one, actually) that I'd like to take the time to write up once I know we have some dialog going.  Thanks in advance.

There are lots of good suggestions here, but I've been trying to focus my time mostly on bug fixing lately. I want to make sure what we have works correctly before adding more stuff, and I also want to simplify some aspects. I intend to add more tooltips throughout to explain things that might be confusing, and rework some components that are confusing.

The auto-population is something I'll have to get to, but it's hard to get right due to js math issues and the "unwieldy" price ratios used in Graphene.
Title: Re: Graphene GUI testing and feedback
Post by: Pheonike on April 18, 2016, 04:14:43 pm

I think we need to add the option to make open.btc a base token for the market panel. There are a lot using it for buying/selling.
Title: Re: Graphene GUI testing and feedback
Post by: Xeldal on April 18, 2016, 04:30:16 pm

I think we need to add the option to make open.btc a base token for the market panel. There are a lot using it for buying/selling.

I would like to see an editable text box that you can enter whatever QUOTE currency you like, and a '+' to add it as a permanent accordian list , as well as a '-' to remove any existing accordian lists.

(http://content.screencast.com/users/Enkianu/folders/Jing/media/d2ffe003-b247-4081-b518-0574ec381c67/2016-04-18_1220.png)

or something, like that..
Title: Re: Graphene GUI testing and feedback
Post by: yvv on April 23, 2016, 07:13:11 pm
I request Fox indicator, like this

(https://pbs.twimg.com/media/CgsFHKtWgAABQJs.jpg:large)
Title: Re: Graphene GUI testing and feedback
Post by: svk on May 01, 2016, 09:00:17 am
Trollbox finally coming next release! I got a great suggestion from hitchcock, the front-end dev of Digix, to use Peerjs to make a p2p chatroom and it turned out to be surprisingly easy :)

Sent fra min MotoG3 via Tapatalk

Title: Re: Graphene GUI testing and feedback
Post by: xeroc on May 01, 2016, 12:10:32 pm
Trollbox finally coming next release! I got a great suggestion from hitchcock, the front-end dev of Digix, to use Peerjs to make a p2p chatroom and it turned out to be surprisingly easy :)

Sent fra min MotoG3 via Tapatalk
BAM! Awesome work! Looking forward to move my trolling from polo to BTS :)
Title: Re: Graphene GUI testing and feedback
Post by: emailtooaj on May 01, 2016, 07:00:12 pm
Trollbox finally coming next release! I got a great suggestion from hitchcock, the front-end dev of Digix, to use Peerjs to make a p2p chatroom and it turned out to be surprisingly easy :)

Sent fra min MotoG3 via Tapatalk
This is awesome news!  Can't wait to see it in action.  This may be a premature question but will this be moderated in any way or is it just wide open?
Great work svk!

Sent from a place unknown to man

Title: Re: Graphene GUI testing and feedback
Post by: svk on May 01, 2016, 07:02:25 pm
Trollbox finally coming next release! I got a great suggestion from hitchcock, the front-end dev of Digix, to use Peerjs to make a p2p chatroom and it turned out to be surprisingly easy :)

Sent fra min MotoG3 via Tapatalk
This is awesome news!  Can't wait to see it in action.  This may be a premature question but will this be moderated in any way or is it just wide open?
Great work svk!

Sent from a place unknown to man
It's unmoderated for now but with mindphlux we brainstormed some ideas for how to add moderation. The easiest one being to allow users to ignore other users, I can probably add that by Wednesday.
Title: Re: Graphene GUI testing and feedback
Post by: speedy on May 01, 2016, 07:06:11 pm
With such a great community, who needs moderators...  :P
Title: Re: Graphene GUI testing and feedback
Post by: emailtooaj on May 01, 2016, 07:08:37 pm
Trollbox finally coming next release! I got a great suggestion from hitchcock, the front-end dev of Digix, to use Peerjs to make a p2p chatroom and it turned out to be surprisingly easy :)

Sent fra min MotoG3 via Tapatalk
This is awesome news!  Can't wait to see it in action.  This may be a premature question but will this be moderated in any way or is it just wide open?
Great work svk!

Sent from a place unknown to man
It's unmoderated for now but with mindphlux we brainstormed some ideas for how to add moderation. The easiest one being to allow users to ignore other users, I can probably add that by Wednesday.
That seems like simple and effective solution.
Another cool idea, if this can be done, would be having an ability to quick tip a user name in the troll box.  This would help to incentivize participation and keep people more engaged.

Sent from a place unknown to man

Title: Re: Graphene GUI testing and feedback
Post by: svk on May 01, 2016, 07:12:47 pm
Trollbox finally coming next release! I got a great suggestion from hitchcock, the front-end dev of Digix, to use Peerjs to make a p2p chatroom and it turned out to be surprisingly easy :)

Sent fra min MotoG3 via Tapatalk
This is awesome news!  Can't wait to see it in action.  This may be a premature question but will this be moderated in any way or is it just wide open?
Great work svk!

Sent from a place unknown to man
It's unmoderated for now but with mindphlux we brainstormed some ideas for how to add moderation. The easiest one being to allow users to ignore other users, I can probably add that by Wednesday.
That seems like simple and effective solution.
Another cool idea, if this can be done, would be having an ability to quick tip a user name in the troll box.  This would help to incentivize participation and keep people more engaged.

Sent from a place unknown to man
One step ahead of you, I just added that 10 minutes ago ;)

/tip user amount asset memo text
Title: Re: Graphene GUI testing and feedback
Post by: emailtooaj on May 01, 2016, 07:16:41 pm
You rock!!!

Sent from a place unknown to man

Title: Re: Graphene GUI testing and feedback
Post by: svk on May 02, 2016, 07:43:53 am
I'm gonna start using Steem to post some more detailed release notes with screenshots, that way we can have feedback on specific releases. You can find the post for last weeks update here:

https://steemit.com/bitshares/@rainman/bitshares-gui-release-2

I control rainman, svk, fbsvk, witness.svk accounts on Steem.
Title: Re: Graphene GUI testing and feedback
Post by: Akado on May 02, 2016, 11:13:31 am
trollbox will most likely bring more people/volume than any other feature so far lol
Title: Re: Graphene GUI testing and feedback
Post by: BunkerChainLabs-DataSecurityNode on May 02, 2016, 12:26:57 pm
trollbox will most likely bring more people/volume than any other feature so far lol

 +5%
Title: Re: Graphene GUI testing and feedback
Post by: speedy on May 02, 2016, 01:48:02 pm
trollbox will most likely bring more people/volume than any other feature so far lol

 +5%

That and the bond market!
Title: Re: Graphene GUI testing and feedback
Post by: Chronos on May 07, 2016, 03:10:46 pm
Is it supposed to say "Create Account" in the upper left, even after you're logged in with an account? It would make more sense to me if that was a Dashboard link to https://bitshares.openledger.info/#/dashboard.

It only does this when all your accounts are set to Ignore. I guess it's pretty unimportant, but it would probably make more sense to show the Home link in that case.
Title: Re: Graphene GUI testing and feedback
Post by: svk on May 07, 2016, 03:30:32 pm
Is it supposed to say "Create Account" in the upper left, even after you're logged in with an account? It would make more sense to me if that was a Dashboard link to https://bitshares.openledger.info/#/dashboard.

It only does this when all your accounts are set to Ignore. I guess it's pretty unimportant, but it would probably make more sense to show the Home link in that case.
Well if you're ignoring all your accounts I guess you need to make a new one? ;)

I could have a look at the logic for that link but that's easily solved on your end by just unignoring an account or following some other account.
Title: Re: Graphene GUI testing and feedback
Post by: Chronos on May 10, 2016, 02:58:14 pm
I think I'd recommend the trollbox default name to be the default account, instead of anonymous. The user can change back to anon using the settings button. It would make the chat feel more like a community.

Also, it says "100 online" but clearly nobody notices any chat. Perhaps the chat tab should lightly pulse a color if there's an unread message.
Title: Re: Graphene GUI testing and feedback
Post by: Chronos on May 10, 2016, 08:38:54 pm
Why is the light wallet cooking my Mac CPU? No other browser tab has this much CPU usage.

(http://i.imgur.com/vCr5LID.png)
Title: Re: Graphene GUI testing and feedback
Post by: Methodise on May 10, 2016, 11:39:55 pm
I've just upgraded from BitShares-light_2.0.160504 (mac)

Upon login, my main bitshares account had become 'ignored'. I managed to search for and 'unignore' it.
Title: Re: Graphene GUI testing and feedback
Post by: svk on May 11, 2016, 06:31:34 am
Why is the light wallet cooking my Mac CPU? No other browser tab has this much CPU usage.

(http://i.imgur.com/vCr5LID.png)

I've had some reports of this kind of behaviour, but never seen it myself. Seems to be related to the trollbox though..
Title: Re: Graphene GUI testing and feedback
Post by: CLains on May 11, 2016, 05:47:53 pm
Idea to increase chat liquidity: Have it open by default, and enable users to see recent history of comments (like slack, polo).

Performance issue: Seems to be some lag-issues when I switch between different tabs in the withdraw/deposit section.
Title: Re: Graphene GUI testing and feedback
Post by: Chronos on May 12, 2016, 09:50:54 pm
Trollbox header warns: "Message frequency is limited to one per 2 seconds." It's better to have a smaller header, and remove it. Instead, show this message if a user tries to send messages above the frequency limit.
Title: Re: Graphene GUI testing and feedback
Post by: svk on May 14, 2016, 01:28:25 pm
New GUI release out now, details here: https://steemit.com/bitshares/@svk/3syrh1-bitshares-gui-release-2
No Windows light wallet as of yet but should come "soon". bitshares.org/wallet and bitshares.openledger.info both updated.

Edit: Looks like the forum @ notification function makes it impossible to post links to steemit..
Title: Re: Graphene GUI testing and feedback
Post by: Chronos on May 21, 2016, 11:28:26 pm
@svk The first thing everyone has to do now is scroll the trollbox to the bottom. Is it possible to make it start out there? It also scrolls itself back to top after changing the chat username or chat color.

Looking good!
Title: Re: Graphene GUI testing and feedback
Post by: bitsharesbrazil on May 22, 2016, 12:21:59 am
Idea to increase chat liquidity: Have it open by default, and enable users to see recent history of comments (like slack, polo).

Performance issue: Seems to be some lag-issues when I switch between different tabs in the withdraw/deposit section.
Agreed
Title: Re: Graphene GUI testing and feedback
Post by: svk on May 22, 2016, 08:38:40 am
@svk The first thing everyone has to do now is scroll the trollbox to the bottom. Is it possible to make it start out there? It also scrolls itself back to top after changing the chat username or chat color.

Looking good!

There was a bug that made the "scroll to bottom" method not work as intended, I already fixed it in dev so it'll be fixed in the next release.

I'll be preparing a release next week to wrap up my worker period which actually expired yesterday (Saturday). Since I've not been able to work much for the last week I'll keep going for another week and wrap up the things I've been working on as of late and make that final release. Then I'll take a little timeout for some R&R and consider my options for the future.
Title: Re: Graphene GUI testing and feedback
Post by: freedom on May 22, 2016, 09:14:07 am
So, you are leaving BTS, aren't you? :'(
Title: Re: Graphene GUI testing and feedback
Post by: svk on May 24, 2016, 08:35:55 pm
New release is out, .deb and.dmg available for now, and bitshares.org/wallet and openledger are both updated.

https://steemit.com/bitshares/@svk/4tlyyw-bitshares-gui-release-2
Title: Re: Graphene GUI testing and feedback
Post by: nmywn on June 26, 2016, 03:04:02 pm
I like what you did with "My Markets", but i don't like that most active BTS markets are placed third.
(https://ipfs.pics/ipfs/QmVm27g45Y8Gt2RBSmV2CnVVmGq5HFWfDoPvDxwsPgV9oN)


(https://ipfs.pics/ipfs/QmY9HMk7wZNXRypUD6DrERmBKoPEe5iA8QdgYD1krPoX4a)
Title: Re: Graphene GUI testing and feedback
Post by: bitsharesbrazil on June 27, 2016, 02:56:37 am
New release is out, .deb and.dmg available for now, and bitshares.org/wallet and openledger are both updated.

https://steemit.com/bitshares/@svk/4tlyyw-bitshares-gui-release-2
shared.
Title: Re: Graphene GUI testing and feedback
Post by: svk on June 28, 2016, 06:00:16 am
I like what you did with "My Markets", but i don't like that most active BTS markets are placed third.
(https://ipfs.pics/ipfs/QmVm27g45Y8Gt2RBSmV2CnVVmGq5HFWfDoPvDxwsPgV9oN)


...

Yea perhaps you're right. The idea was to make it more similar to Polo, but none of those markets are very active so I guess it makes sense to put BTS first.

Openledger will have a different selection though.
Title: Re: Graphene GUI testing and feedback
Post by: svk on June 28, 2016, 06:07:57 am
Just  a heads up that I'm still actively working on the GUI, as those of who you follow the graphene-ui repo can attest to. I've recently started using my graphenejs-lib (https://github.com/svk31/graphenejs-lib) and graphenejs-ws (https://github.com/svk31/graphenejs-ws) libraries in the GUI which, among other improvements, has enabled me to reduce the overall file size of the website by a decent amount.

I've also started working with a designer hired by Ronny who's giving some great suggestions and revamping certain sections. I've implemented a few of his changes already and am currently in the process of wrapping up the Settings page revamp. Once that is done I'll be making a new release.
Title: Re: Graphene GUI testing and feedback
Post by: xeroc on June 28, 2016, 07:56:05 am
I've also started working with a designer hired by Ronny who's giving some great suggestions and revamping certain sections. I've implemented a few of his changes already and am currently in the process of wrapping up the Settings page revamp. Once that is done I'll be making a new release.
Bam! +5%
Title: Re: Graphene GUI testing and feedback
Post by: CLains on June 28, 2016, 03:01:13 pm
Just  a heads up that I'm still actively working on the GUI, as those of who you follow the graphene-ui repo can attest to. I've recently started using my graphenejs-lib (https://github.com/svk31/graphenejs-lib) and graphenejs-ws (https://github.com/svk31/graphenejs-ws) libraries in the GUI which, among other improvements, has enabled me to reduce the overall file size of the website by a decent amount.

I've also started working with a designer hired by Ronny who's giving some great suggestions and revamping certain sections. I've implemented a few of his changes already and am currently in the process of wrapping up the Settings page revamp. Once that is done I'll be making a new release.

Awesome  +5%
Title: Re: Graphene GUI testing and feedback
Post by: svk on June 29, 2016, 09:02:47 pm
I ran into some file loading issues with the light client so I had to postpone the release till tomorrow. Openledger has been updated though. Changelog here : https://github.com/bitshares/bitshares-2-ui/blob/bitshares/CHANGELOG.md


Sent from my iPhone using Tapatalk
Title: Re: Graphene GUI testing and feedback
Post by: Brekyrself on June 29, 2016, 09:14:25 pm
I ran into some file loading issues with the light client so I had to postpone the release till tomorrow. Openledger has been updated though. Changelog here : https://github.com/bitshares/bitshares-2-ui/blob/bitshares/CHANGELOG.md


Sent from my iPhone using Tapatalk

Thanks for the update and continued support.  It's always refreshing to see work still continuing.

Is there a way to modify which tabs are displayed in the exchange window?
Title: Re: Graphene GUI testing and feedback
Post by: tbone on July 14, 2016, 12:31:21 am
Hi @svk.  Thanks for all of the improvements you've made to the wallet pretty recently.  There's one thing I've been meaning to point out, though.  The first image below is what a new person visiting OpenLedger for the first time sees when they land in the wallet.  I don't think that's the best first impression of the wallet.  The second image below is what they see if they click on the home button (OL icon).  I don't think that's the best second impression of the wallet.  Maybe we can create a new default page that includes the featured markets and some other basic introductory/welcome message, including a link to create a new account.  I think that would make a far better impression to new users.


(https://i.imgsafe.org/6da29d6891.png)



(https://i.imgsafe.org/6dab90ffcf.png)
Title: Re: Graphene GUI testing and feedback
Post by: svk on July 14, 2016, 09:47:18 am
Thanks for the feedback @tbone. We actually have some improvements in the pipeline here, just need to code them.


Sent from my iPhone using Tapatalk
Title: Re: Graphene GUI testing and feedback
Post by: yvv on July 14, 2016, 02:51:28 pm
Is it possible to add margin call price and my call price marks to the market depth chart? Or display them in the top bar?

Title: Re: Graphene GUI testing and feedback
Post by: tbone on July 14, 2016, 04:34:02 pm
Thanks for the feedback @tbone. We actually have some improvements in the pipeline here, just need to code them.


Sent from my iPhone using Tapatalk

Sounds good.  Thanks!
Title: Re: Graphene GUI testing and feedback
Post by: hammurabi on July 26, 2016, 11:14:52 am
lightweight wallet feedback:

- flags on asset creation are ambiguous.
Please consider adding label "on/off" to asset creation flags or use color green/red or something obvious.


- active markets list
On the wallet's main page, above featured markets, there should be a row with the most active markets on the platform to attract traders!
Figuring out where trading takes place requires additional brainpower and brainpower is costly to use :)
Currently there is for example open.dao featured as first item. I personally would remove such items from the very first page. It makes false first impression that the platform is not being actively used at all.
The current feature list would be just fine if it listed the most active markets instead of dead ones!

Title: Re: Graphene GUI testing and feedback
Post by: yvv on July 26, 2016, 04:32:05 pm
Agreed with the previous post on active markets. Take a look at ripplecharts.com. It has 24h network stats with a pie chart which show where the volume comes from on the front page. This is very useful. And overall this site is worth to explore since it has some elegant solution which openledger could borrow.

Title: Re: Graphene GUI testing and feedback
Post by: hammurabi on July 27, 2016, 04:26:32 pm
Another feature missing:

The mouse pointer/cross doesn't show the price level I am pointing at.
I need to guess or use school ruler and calculate :)

Expected behavior:
pointing somewhere at the chart should show me the price level I pointed at.
similar to the current price shown on the right side of the chart.


This is important feature!

Title: Re: Graphene GUI testing and feedback
Post by: Brekyrself on August 21, 2016, 01:18:45 am
Trollbox issues on firefox 48.0.1 win10 x64

The pin button used to put it nicely on the side of the screen now it basically minimizes it to the bottom.
Title: Re: Graphene GUI testing and feedback
Post by: GChicken on September 09, 2016, 11:46:28 am
Sorry if this has been mentioned before; i did not trawl through the 34 pages prior to making this post. (i just noticed it was also mentioned by @hammurabi a few posts back)

I am always confused by the toggle buttons within the asset creation menus...  i always finding myself going back to the market fee toggle button or the smart coin toggle button to confirm which is on and off; i do this because these are the only button with visual feedback that i can tell when it is enabled/on and disabled/off.

Given they are simple binary option i think it would be better served with a checkbox or some other button type that is more recognisable which toggle is on and which toggle is off.

i think this simple change would help the intuitiveness of that interface.
Title: Re: Graphene GUI testing and feedback
Post by: tbone on September 09, 2016, 03:49:09 pm
Sorry if this has been mentioned before; i did not trawl through the 34 pages prior to making this post. (i just noticed it was also mentioned by @hammurabi a few posts back)

I am always confused by the toggle buttons within the asset creation menus...  i always finding myself going back to the market fee toggle button or the smart coin toggle button to confirm which is on and off; i do this because these are the only button with visual feedback that i can tell when it is enabled/on and disabled/off.

Given they are simple binary option i think it would be better served with a checkbox or some other button type that is more recognisable which toggle is on and which toggle is off.

i think this simple change would help the intuitiveness of that interface.

I agree 100%.
Title: Re: Graphene GUI testing and feedback
Post by: nmywn on September 09, 2016, 05:23:53 pm
[imgage removed]

Title: Re: Graphene GUI testing and feedback
Post by: Brekyrself on October 05, 2016, 08:24:05 pm
One of the releases changed the naming scheme and dropped the "open" part of assets.  This is confusing for new users as when your on the bts trading tab for example there is now BTC and bitBTC.  They do not know the difference.

If we keep this style of dropping the prefix, I believe there should be an additional tab with ONLY bitassets so users can be assured they are trading blockchain backed assets.
Title: Re: Graphene GUI testing and feedback
Post by: nmywn on October 05, 2016, 09:13:19 pm
One of the releases changed the naming scheme and dropped the "open" part of assets.  This is confusing for new users as when your on the bts trading tab for example there is now BTC and bitBTC.  They do not know the difference.

If we keep this style of dropping the prefix, I believe there should be an additional tab with ONLY bitassets so users can be assured they are trading blockchain backed assets.
This is done by Openledger and it's only their choice. Bitshares client display prefixes as earlier.
Title: Re: Graphene GUI testing and feedback
Post by: Brekyrself on October 05, 2016, 09:29:33 pm
One of the releases changed the naming scheme and dropped the "open" part of assets.  This is confusing for new users as when your on the bts trading tab for example there is now BTC and bitBTC.  They do not know the difference.

If we keep this style of dropping the prefix, I believe there should be an additional tab with ONLY bitassets so users can be assured they are trading blockchain backed assets.
This is done by Openledger and it's only their choice. Bitshares client display prefixes as earlier.

I sent them a message, thanks for the tip.  I thought @svk was doing the GUI work for Openledger also?
Title: Re: Graphene GUI testing and feedback
Post by: svk on October 05, 2016, 10:20:59 pm
One of the releases changed the naming scheme and dropped the "open" part of assets.  This is confusing for new users as when your on the bts trading tab for example there is now BTC and bitBTC.  They do not know the difference.

If we keep this style of dropping the prefix, I believe there should be an additional tab with ONLY bitassets so users can be assured they are trading blockchain backed assets.
This is done by Openledger and it's only their choice. Bitshares client display prefixes as earlier.

I sent them a message, thanks for the tip.  I thought @svk was doing the GUI work for Openledger also?
Nope this was the Openledger team, not me.
Title: Re: Graphene GUI testing and feedback
Post by: nmywn on March 31, 2017, 03:33:27 pm
Any plans to make MPA's average user friendly? I'm not sure what would we be possible through GUI without much effort.
What I want  is ability to provide feed by hand, same issue with prediction market. I did some tests and could not find any options responsible for that.
Next, I can't find MCR and SQP options - I"m almost sure this was available before.

Do I need full node to run MPA with my own feed? For my needs simple in GUI feed providing would be enough.
I think minimum what must be done now is simple warning for users: " Don't touch this,  you will be unable to provide feed and change market options through GUI" - something like that.
Same goes for others features not ready yet.