Hi Luis, > But I was planning adding another feature developing in GSoC 2007, but it > imply a restructure of XML files, and Option Builders of Umit. > Actually Profile Editor need to update because Nmap added great features and > xml files doesn't support them (traceroute, min, max rates, reason of state > of ports etc..) > > I would like quickly import from InterfaceEditor branch: > - ProfileEditor tips (help users with a description about option) > - ProfileEditor - add scrollbar > > But I need to make some fits within Options and Profiles/Wizard Structure. > > options.xml: > -- name > -- hint (used by tips) > -- need root (boolean value) > -- options (from nmap) > -- arguments description > > profile_editor.xml and wizard.xml > -- name > -- label
Could you give us an example of command which can not be expressed in our current xml structure? I'm just afraid that this would represent a problem for those that have an older version of Umit. If we decide to change the xml structure, then we must provide a way to convert old format to the new one. I'll be aiting for your reply so we can think about the best solution. Kind Regards, -- Adriano Monteiro Marques http://adriano-marques.blogspot.com http://www.umitproject.org http://www.pythonbenelux.org "Don't stay in bed, unless you can make money in bed." - George Burns ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Umit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/umit-devel
