Tomas,
I have just checked the change in to provide the "Field Information" context
menu item (18125).
I've added the function to oid_resolv.[ch] rather than packet-ber.[ch] as
you suggested.
However this means the URL template is not (currently) configurable as I
didn't know where "OID" preferences should appear. Any suggestions?
For now the URL template is fixed to the www.alvestrand.no site (which
contain links to the elibel site).
I have another change (which I haven't checked in) that introduces a new
field type for URIs (FT_URI) . This allows the new "Field Information" menu
item to then bring up the indicated location. My particular interest is the
URI form of a GeneralName which is used in a number of X.509 certificate
extensions.
But is a URI field type a sensible addition?
Graeme
_____
From: Kukosa, Tomas [mailto:tomas.kukosa@xxxxxxxxxxx]
Sent: 01 May 2006 13:05
To: graeme@xxxxxxxxxxx; Ethereal development
Subject: RE: [Ethereal-dev] OID Field Information
Hi,
I would prefer to put OID related functions into e.g. oid_resolv.[ch]
instead of packet-ber.[ch].
I guess ber_get_oid_url() could be ranamed to get_oid_url() and located in
oid_resolv.[ch] as it is not BER related.
Regards,
Tomas
_____
Od: ethereal-dev-bounces@xxxxxxxxxxxx za uživatele Graeme Lunt
Odesláno: po 1.5.2006 12:34
Komu: 'Ethereal development'
Předmět: [Ethereal-dev] OID Field Information
Hi,
I have developed a patch so that if the user chooses "Field Information" (a
new context menu item) on a field type of FT_OID, a web page will be brought
up with their preferred reference page. (e.g.
http://www.alvestrand.no/objectid/2.5.18.5.html)
I just wanted to check that this is an appropriate way to go about it before
I check it in.
Specifically:
a) Is it architecturally correct to reference a dissector (packet-ber) from
the gtk\ portion of the tree?
b) Would a "link" style (like FT_FRAMENUM) be better than extending the
context menu?
There is a diff attached for the gtk/ files (packet-ber.[ch] patch not
included).
Comments?
Graeme
<<attachment: winmail.dat>>