Jirka Kosek wrote: > >> Also note that in order to be parametrizable, a <transform> element must >> contain an empty <parameterGroup> element as its last child. > > I have to use two parameterGroups inside transform -- one is special to > each transformation and one is shared (it contains settings of > profiling/conditional processing). With this setup XXE offers two > parameter groups with the same name. I solved this by creating dummy > transformation which holds only profiling parameter group and this made > XXE happy. > > But this could be improved. For example standalone parameterGroup > (outside transform) could also have @label/@documentation and then it > could be made editable by user. Also it might be useful to allow editing > of preset parameters in such group. >
It is not designed to work like this. The end user sees *all* the parameters of a transform element having a label attribute, whether these parameters are specified in the body of the transform element or are specified in a ``standalone'' parameterGroup contained in a customization file created by hand (i.e. created by a guru like you). The end user cannot *edit* any of the above parameters per se, however she/he can *override* them with her/his own values. All in all, the role of everyone, XMLmind, local guru, end user, is respected here, the end user always having the last word. And I don't see cases where the end user cannot do what she/he wants.
