Guy Harris skrev 2013-04-09 00:32:
On Apr 8, 2013, at 3:02 PM, Anders Broman wrote:
I think we have getopt_long already
http://anonsvn.wireshark.org/viewvc?view=revision&revision=41926
We do, so we have it available on both platforms that have it (most UN*Xes,
these days) and platforms that
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.
(though if there is sufficient interest it may b
Ashish Raste writes:
> 1. Could you suggest me some pointers/references
> specifically related to knowing the process info of the packets so that I
can start working/thinking along
> those lines.
For starters, you might want to have a look at this bug report:
https://bugs.wireshark.org/bugzill
Hi all,
I'm a CS student from National University of Singapore. I came through the
GSoC project ideas of Wireshark and I'm interested to know/learn about
having Wireshark tell the Process information of the packets captured.
I mainly wanted to ask you the following:
1. Could you suggest me some p
On Apr 8, 2013, at 3:02 PM, Anders Broman wrote:
> I think we have getopt_long already
> http://anonsvn.wireshark.org/viewvc?view=revision&revision=41926
We do, so we have it available on both platforms that have it (most UN*Xes,
these days) and platforms that don't (Windows, which has neithe
Ok... I just gotta jump in here. I'm probably causing Gerald major headaches
on the icon issue.
IMHO, I think the "media control" icon look is going to cause confusion.
Specifically the red "record" button to start capture.
That red button doesn't say "start" to me. it says "stop."
cid:image
Dirk Jagdmann skrev 2013-04-08 23:29:
Sadly, -j is already taken for Wireshark, so you couldn't run
Wireshark from the command line with "-j", unless we go with either
getopt_long() (pulling in a version from GNU libc for platforms that
don't have it in the system library) or with g_option:
I
Sadly, -j is already taken for Wireshark, so you couldn't run Wireshark from the command
line with "-j", unless we go with either getopt_long() (pulling in a version
from GNU libc for platforms that don't have it in the system library) or with g_option:
I suggest using the glib functions. Othe
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
10 matches
Mail list logo
