Re: [Wireshark-dev] (no subject)

2014-03-06 Thread Dario Lombardo
Do you want to keep the pdml file format, or do you just want to export a subset of infos? In the latter case you can use the -T fields switch plus the -e switch. On Thu, Mar 6, 2014 at 8:04 AM, varsha mintri vmin...@yahoo.com wrote: Hi, I wanted to reduce the details produced while

Re: [Wireshark-dev] (no subject)

2014-03-06 Thread varsha mintri
I want to keep the pdml file. I am seeking for a method that reduces the content. If i put the question other way round  : I want to convert a .cap file to .pdml file to generate only few information not an entire pdml file.Thank you. On Thursday, 6 March 2014 2:01 PM, Dario Lombardo

[Wireshark-dev] FW: [Wireshark-commits] master 579e7e1: Wireshark: Add option to choose format type of capture file

2014-03-06 Thread Anders Broman
Hi, This change broke a custom wiretap plugin I have which used wtap_register_magic_number_open_routine() which now is #if 0:ed out. I gather I should now use wtap_register_open_info() with const struct open_info Unfortunately there isn't a good description of the content of the struct: struct

Re: [Wireshark-dev] FW: [Wireshark-commits] master 579e7e1: Wireshark: Add option to choose format type of capture file

2014-03-06 Thread Pascal Quantin
Hi Anders, name is the string that appears in the file open dialog, allowing you to know which format you are selecting. Cheers, Pascal. 2014-03-06 15:53 GMT+01:00 Anders Broman anders.bro...@ericsson.com: Hi, This change broke a custom wiretap plugin I have which used

Re: [Wireshark-dev] FW: [Wireshark-commits] master 579e7e1: Wireshark: Add option to choose format type of capture file

2014-03-06 Thread Anders Broman
Thanks, so that's the same as struct file_type_subtype_info { /* the file type name */ /* should be NULL for all pseudo types that are only internally used and not read/writeable */ const char *name; shouldn't hurt to put those clarifications in the file :-)) From:

Re: [Wireshark-dev] [Wireshark-commits] master 579e7e1: Wireshark: Add option to choose format type of capture file

2014-03-06 Thread Hadriel Kaplan
Actually it's more like the 'short_name' field in that file_type_subtybe struct, but not exactly - the open_info ones are captialized whereas the file_type_subtybe 'short_name' ones are lower-case. But in my opinion they should be not only the same exact name strings, but inside just one

[Wireshark-dev] make release notes fails

2014-03-06 Thread Toralf Förster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 - --- RELEASE NOTES - TXT --- format=text --lynx \ --xsltproc-opts --stringparam generate.toc \article nop\ \ release-notes.asciidoc /bin/sh: --lynx: command not found make: [release-notes.txt] Error 127 (ignored) mv

Re: [Wireshark-dev] [Wireshark-commits] master 579e7e1: Wireshark: Add option to choose format type of capture file

2014-03-06 Thread Hadriel Kaplan
BTW, is changing the wtap_register_open_info() function prototype/ABI again soon going to cause you problems? I ask because it changes again, with an additional argument, in here: https://code.wireshark.org/review/#/c/431/ The additional argument is for whether the wiretap reader being

Re: [Wireshark-dev] [Wireshark-commits] master 579e7e1: Wireshark: Add option to choose format type of capture file

2014-03-06 Thread Anders Broman
Hi, I try to keep up with the API changes so changing the API is no big problem as long as I understand what to do :-) Regards Anders -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Hadriel Kaplan Sent: den 6 mars

Re: [Wireshark-dev] [Wireshark-commits] master 579e7e1: Wireshark: Add option to choose format type of capture file

2014-03-06 Thread Anders Broman
BTW Putting (doxygen) comments in the code helps :-) -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Anders Broman Sent: den 6 mars 2014 18:31 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev]

Re: [Wireshark-dev] make release notes fails

2014-03-06 Thread Joerg Mayer
On Thu, Mar 06, 2014 at 06:07:33PM +0100, Toralf Förster wrote: - --- RELEASE NOTES - TXT --- format=text --lynx \ --xsltproc-opts --stringparam generate.toc \article nop\ \ release-notes.asciidoc /bin/sh: --lynx: command not found make: [release-notes.txt] Error 127

Re: [Wireshark-dev] make release notes fails

2014-03-06 Thread Alexis La Goutte
Hi, On Thu, Mar 6, 2014 at 6:07 PM, Toralf Förster toralf.foers...@gmx.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 - --- RELEASE NOTES - TXT --- format=text --lynx \ --xsltproc-opts --stringparam generate.toc \article nop\ \ release-notes.asciidoc /bin/sh:

[Wireshark-dev] how to add a menuitem in wireshark?

2014-03-06 Thread ??????????
I want to add a menuitem in Statistics menu,what should i do?I modified the /gtk/menus.c file,but it did not function well.It end up with the same as before.please show me what should i do?___ Sent via:Wireshark-dev

[Wireshark-dev] Good book on Qt?

2014-03-06 Thread Hadriel Kaplan
A bit off-topic, but since I'm asking because Wireshark uses it and I want to grok it for Wireshark... Can anyone recommend a good book on Qt GUI programming? A search on Amazon and stackoverflow and other usual sites came up with lots of hits, but mostly for outdated books. And the docs on