> actually i was actually planning to not fiddly with parameter strings, > and therefore avoid the more parameters box
> instead the idea would be to have a "All Options..." button which would > popup a dialog that allows settings the parameters much as one sets > widget options in qt's designer. > > this dialog could then ultimately be reused for all packages > > what do you think? I am not quite sure what you have in mind. :-) My plan is [an edit box with current option string that can be edited directly] [an edit/compose button] 1. If the option is simple, the user can edit this option string directly. It also allows pasting option string from somewhere else. 2. If a definition file is available for this package, the compose button is enabled. For example, in the document class panel, after a user choose a document class, a button after the options textedit can be enabled or disabled accordingly. 3. If this compose button is clicked, the current option string, and the package name is passed. This dialog will load the corresponding package definition file, add each item and set its value to its default or a passed value. 4. The user can change options in this dialog using a property editor interface. Validations are allowed (and the bypass validation button should be moved here). 5. An option string will be returned, and set to the option edit box. Bo
