Diff for 12013 design
Fri, 2008-06-13 03:53 by imagiczhang | Fri, 2008-06-13 05:02 by imagiczhang | ||
---|---|---|---|
next diff > | |||
Changes to Body | |||
Line 9 | Line 9 | ||
technical design for the change</span></em></strong>
| technical design for the change</span></em></strong>
| ||
</p>
| </p>
| ||
- | <br />
| + | In conrefImpl.xsl, when the target of @conref is processed, the code first copy or proceed all @* attributes of target elements and then use apply-templates on its sub-nodes. After that we need to add the code to check whether @conrefend is valid and proceed the elements in the conref range. Since the template to proceed conref target doesn't know whether there is @conrefend at conref source, the value of @conrefend should be passed as parameter. <br />
|
<br />
| <br />
| ||
<br />
| <br />
|
Revision of Fri, 2008-06-13 05:02:
12013 design
Design for item
What user need will be met by this feature?
Users can use @conref combined with @conrefend to refer to a range of sibling elements and pull them into the specified location.
What is the technical design for the change
In conrefImpl.xsl, when the target of @conref is processed, the code first copy or proceed all @* attributes of target elements and then use apply-templates on its sub-nodes. After that we need to add the code to check whether @conrefend is valid and proceed the elements in the conref range. Since the template to proceed conref target doesn't know whether there is @conrefend at conref source, the value of @conrefend should be passed as parameter.What sections of the toolkit will be impacted by the change?
The change will impact conref resolution xslt script.
See also
none