Thus wrote Guy Harris (g...@alum.mit.edu):
> Sounds like a job for capinfos.
You're right, that's where it should go. And for capinfos, the cmdline
options don't have to be aligned with wireshark/tshark/dumpcap ;-)
> (I assume by "capture file comment" you mean the comment in the first
> Section
What dimensions are you shooting for with the icon? Is there a set __ x __
pixels?
My wife is a professional graphic designer, and is called upon regularly to
design or redesign icons. If the goal is to figure out ways to have a "record"
button not look like an indicator light or stop sign, I
Thanks for the graphics.
Funny, on the text-only poll I voted for record/stop, as this is intuitively
correct.
[One can get in trouble for playing packets back into a live network. :-) ]
But it seems that the record button (small red dot on a large button) doesn't
transfer well to the screen, loo
Check out https://www.surveymonkey.com/s/wsiconpoll.
See the pretty pictures?
I can send this to about 25,000 folks on our mailing lists and hit
Twitter/Facebook.
Will provide feedback to the -dev list.
Laura
The "Wireshark UI Metaphor" poll does not offer "start/stop" as an option.
Even this thread uses "start and stop" and that's still the name of the
buttons.
How about a graphical poll that shows the new Start Capture and Stop Capture
icon suggestions - see which they prefer?
I'll open a poll to m
Ok,
Who has time to review this 100kB patch?
Thanks,
Jaap
On 04/09/2013 03:00 PM, Roland Knall wrote:
> Hi
>
> Could I please bump my request one more time on the buglist? I am
> starting to work on some topics for new features on the dissector, and
> only want to really start it, as soon as th
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
Hi
Could I please bump my request one more time on the buglist? I am
starting to work on some topics for new features on the dissector, and
only want to really start it, as soon as the existing patch went
through.
kind regards,
Roland
On Fri, Apr 5, 2013 at 12:25 AM, Evan Huus wrote:
> On Thu,
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:
>>
>> https://docs.google.com/f
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.
12 matches
Mail list logo
