So, in its current state you would like to discourage casual users from wondering about it. Makes sense to me.
However, on my prebuilt Windows executable, version 0.99.3, there's no top level "Tools" menu. Does this mean my executable was compiled without Lua support? Is this the default? If so, then I'd suggest that "being compiled with Lua support" implies the user is more knowledgeable than the average bear, and in fact has asked (or has been given the option) for Lua support. So, giving them a hook to understanding what that empty "Tools" menu is shouldn't be a problem. So, my suggested solution (some of which may already be implemented): - Default Wireshark build should not include Lua support - "Tools" menu for Lua scripts should be visible iff Lua support compiled in - If the "Tools" menu would otherwise be empty, add a "What is this?" menu item that opens a simple "It's for Lua scripting: see <here>" dialog. Dan -- Daniel T. Griscom [EMAIL PROTECTED] Suitable Systems http://www.suitable.com/ 1 Centre Street, Suite 204 (781) 665-0053 Wakefield, MA 01880-2400 _______________________________________________ Wireshark-dev mailing list [email protected] http://www.wireshark.org/mailman/listinfo/wireshark-dev
