Bo Peng wrote:
We call it consistent behaviour. ;-)
Then we can implement a 'compose' dialog, that
1. Option [params ] Compose_Button
2. When the compose button is pressed, dialog 'compose
listings/hyperref/whatever options' is triggered.
3. This dialog has all the validation facilities and hints to help the
user create an option list. Different packages can use this facility
using potentially external definition files.
What do you think?
i agree this is better than what we have now.
still think that an autogenerated properties dialog will be even better
though...
the information you have put now in ParValidator::ParValidator() could
be parsed to build the dialog
if there are a lot of parameters as with listing i am sure they can be
grouped to have a better overview
