Quoting Ed Beroset
Evan Huus wrote:
The *proper* (for certain values of that word) way to decide this issue is
really to do a usability study, however that is expensive/time-consuming so
unless Riverbed wants to make that investment it isn't likely to happen
with any degree of rigour.
They fo
On 9 April 2013 14:54, Ed Beroset wrote:
> Evan Huus wrote:
> >The *proper* (for certain values of that word) way to decide this issue is
> >really to do a usability study, however that is expensive/time-consuming
> so
> >unless Riverbed wants to make that investment it isn't likely to happen
> >
Evan Huus wrote:
>The *proper* (for certain values of that word) way to decide this issue is
>really to do a usability study, however that is expensive/time-consuming so
>unless Riverbed wants to make that investment it isn't likely to happen
>with any degree of rigour.
There was a study on that v
On Tue, Apr 9, 2013 at 4:53 AM, Jasper Bongertz
wrote:
>>> Either way, we aren't going to have any hard data for the expected
>>> release of 1.10 unless that gets bumped back a *lot*. The best we can do is
>>> probably a quick poll, so I've created >> just that:
>>>
>>>
>>> https://docs.google.com
Title: Re: [Wireshark-dev] Start and stop capture toolbar buttons?
>> Either way, we aren't going to have any hard data for the expected release of 1.10 unless that gets bumped back a *lot*. The best we can do is probably a quick poll, so I've created >> just that:
>>
On 9 April 2013 04:29, Evan Huus wrote:
> The *proper* (for certain values of that word) way to decide this issue is
> really to do a usability study, however that is expensive/time-consuming so
> unless Riverbed wants to make that investment it isn't likely to happen
> with any degree of rigour.
Original Message-
>
> From: Gerald Combs [mailto:ger...@wireshark.org ] **
> **
>
> Sent: Monday, April 08, 2013 10:13 AM
>
> To: Developer support list for Wireshark
>
> Subject: Re: [Wireshark-dev] Start and stop capture toolbar buttons?
>
>
il 08, 2013 10:13 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Start and stop capture toolbar buttons?
On 4/7/13 5:12 PM, Guy Harris wrote:
>
> On Apr 7, 2013, at 10:40 AM, ger...@wireshark.org wrote:
>
>> http://anonsvn.wireshark.org/viewvc/
On 4/7/13 6:35 PM, Evan Huus wrote:
> FWIW:
> - Audacity uses a yellow square for stop.
> - Photoshop's macro recorder uses a blue square for stop.
>
> Though honestly, I'm pretty happy with our new icon set as-is. Perhaps
> changing the fill colour of the stop button (yellow, blue, other?)
> woul
On 4/7/13 5:12 PM, Guy Harris wrote:
>
> On Apr 7, 2013, at 10:40 AM, ger...@wireshark.org wrote:
>
>> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=48776
>>
>> User: gerald
>> Date: 2013/04/07 10:40 AM
>>
>> Log:
>> Change the "stop capture" icon to a Great Big Huge Square to
P.S. Regardless, the new icons are already a big step up over the old ones :)
On Sun, Apr 7, 2013 at 9:35 PM, Evan Huus wrote:
> FWIW:
> - Audacity uses a yellow square for stop.
> - Photoshop's macro recorder uses a blue square for stop.
>
> Though honestly, I'm pretty happy with our new icon se
FWIW:
- Audacity uses a yellow square for stop.
- Photoshop's macro recorder uses a blue square for stop.
Though honestly, I'm pretty happy with our new icon set as-is. Perhaps
changing the fill colour of the stop button (yellow, blue, other?)
would be sufficient.
Or, if we only ever display one
On Apr 7, 2013, at 10:40 AM, ger...@wireshark.org wrote:
> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=48776
>
> User: gerald
> Date: 2013/04/07 10:40 AM
>
> Log:
> Change the "stop capture" icon to a Great Big Huge Square to try to make
> it more obvious (particularly at 1
13 matches
Mail list logo
