>> Could you give us an example of command which can not be expressed in >> our current xml structure? > > When I decide create an option I know what kind of argument it receive, if > it need super user access or if it doesn't. > After I created an option I should add it to the Profile or Wizard. It's the > procedure both manually and from Interface Editor.It doesn't make sense add > argument type within profile_editor.xml. Right? It's a options.xml business.
Ok then. It is ok to move on, and make the xml structure changes. > Yeah, we have some options if we decide integrate Interface Editor: > - Change structure and make a script to detect xml versions and convert > - Keep structure and change Interface Editor and > > Otherwise put tips within Profile Editor is mandatory, because it can become > confuse. And I think that isn't need a change of structure. Agreed. It is ok for me then, anyone else? 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
