ndt-dev - Re: [ndt-dev] JS UI improvement
Subject: NDT-DEV email list created
List archive
- From: Aaron Brown <>
- To: Sebastian Kostuch <>
- Cc: "" <>
- Subject: Re: [ndt-dev] JS UI improvement
- Date: Fri, 7 Mar 2014 22:24:33 +0000
- Accept-language: en-US
Hey Sebastian,
Sorry for the delay, I’ve been on paternity leave. Comments inline.
Cheers,
Aaron
On Mar 7, 2014, at 4:35 AM, Sebastian Kostuch
<>
wrote:
> Hi,
> still looking forward to your comments :). At the beginning of next week I
> will probably attempt to
> create some tickets related to these improvements so it would be nice to
> know which of my thoughts
> are worth implementing and which are not (also I am very receptive for your
> own ideas).
>
> Kind regards,
> Sebastian Kostuch
>
> On 26.02.2014 14:51, Sebastian Kostuch wrote:
>> Hi,
>> after investigating current JS UI I think that part which lacks the most
>> of some improvements is the
>> one showing currently running tests. So most of my proposals will
>> concecrate on this view.
>> Here is the list of all of my suggestions:
>> 1. I think that what could make present UI more attractive to user are
>> live results.
>> I mean that during download and upload tests it would be good to show
>> some kind of gauge
>> presenting speed at current moment.
>> So during speed tests we could add some kind of speedometer gauge at
>> the center (with the
>> current results shown within it). During test its indicator will
>> dynamically point at current speed.
I like this idea. I’d imagine it’d be easy enough to have the flash or java
applet track the current speed of the c2s or s2c speed, and do a callback
periodically (once a second?) with the current status.
>> 2. Move addresses of server and client to the top left and top right part
>> of page accordingly (also
>> with little smaller font size for labels).
Seems reasonable to me.
>> 3. "Preparing your tests" text could dissapear right after this stage is
>> completed. Also this information
>> (and text indicating which test is currently running) would be placed
>> right below gauge. What about
>> making this text blinking also?
>> 4. After first speed test result would be saved and shown on the
>> bottom-left part of page. Accordingly
>> after second one proper text will be shown on botom-right (and after a
>> while whole page will dissapear
>> to show summary one).
>> 5. To make UI nicer we could add some kind of animations on left and right
>> sides of page that will
>> be graphical representation of currently running speed test. I mean
>> that i.e. during download test
>> there will be small arrows moving from top to the bottom part of site
>> (or maybe showing one by
>> one and after some amount of them will be reached then animation will
>> start from beginning).
If we’re going to show live updates, I’d rather have a single ‘testing' page
look pretty much the same as the results page with 2 gauges: one for upload,
one for download. First do the upload test, and update its gauge, and at the
end of the upload test, set the upload gauge to the final result of the test.
Then move onto the download gauge, doing pretty much the same thing.
>> 6. On summary page we could add some small nice looking text field which
>> will show web100/web10g
>> variables (it will be auto-scrolling and when user clicks on this then
>> he/she will be redirected to
>> advanced page). Or maybe instead of text field add some small board on
>> which these values will
>> display and dissapear within set time one by one (or better more at the
>> same time). Maybe good
>> place for this element would be between "Download speed" result and
>> "Test again" button
>> (probably both results rectangles need to be made a bit smaller in
>> height to achieve it).
I don’t think web100/10g variables should ever be shown in a default set of
results. If they click to an “advanced” page, or something, then show the
variables, but at best they’re gobbledygook to the average user.
>> 7. Variable's values on advanced page could be displayed in table to make
>> them more legible.
>>
>> What do you think about such changes? Also I'm receptive to your ideas
>> about what could be
>> done to make current JS UI look nicer.
>>
>> Regards,
>> Sebastian Kostuch
>>
>
- Re: [ndt-dev] JS UI improvement, Sebastian Kostuch, 03/07/2014
- Re: [ndt-dev] JS UI improvement, Aaron Brown, 03/07/2014
- Re: [ndt-dev] JS UI improvement, Richard Carlson, 03/09/2014
- Re: [ndt-dev] JS UI improvement, Matt Mathis, 03/13/2014
- Re: [ndt-dev] JS UI improvement, Tiziana Refice, 03/14/2014
- Re: [ndt-dev] JS UI improvement, Matt Mathis, 03/13/2014
Archive powered by MHonArc 2.6.16.