>The one caveat I'd add here is that it might be valuable to consider a >config mechanism for parameters. If for example, a parameter >effectively takes an option from an enumerated list (let's say "yes" >and "no"), then:
>1. there's no way for the user to have a pop-up list of options without >configuring it outside the XSLT >2. you couldn't localize without the config option Well in a product I worked on where we needed to do User defined parameters we had the following: 1. A dialogue for choosing parameters and setting parameters, when you set parameters it is done as a name value pair, you just keep adding parameters. 2. Parameters for a particular process can be saved and given a name, my_cool_teiTransform, this was done in a flat list xml file. <params> <param name="foo">bar</param> ... </params> 3. so if you hade a saved my_cool_teitransform and you read it in and then set the parameter foo to be baz that parameter in your list would be changed. you could also add the parameter foo2 and run it, save it if you wanted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
