Hi,
I have some changes queued up locally that add support for initializing
nested child elements of a given element in the order in which they appear
in the build file.
In order to accomplish this, I've added support for assigning
BuildElementAttributes to methods :
[BuildElement("path")]
Public void AddPath(PathSet path) {
...
}
[BuildElement("path")]
Public void AddPathElement(PathElement path) {
...
}
This allows for the following build fragment :
<...>
<path ... />
<pathelement ... />
<path ... />
</...>
in which the nested elements would be processed in the order in which they
appear. Which is necessary for, for example, parts of a path (and it would
probably also allow us to remove the hack for <filterchain>).
The drawback is that this adds additional processing to element
initialization, which is only necessary for a limited set of elements.
So, I think it would be best to allow an Element to specify whether it
requires support for ordered initialization of nested build elements (backed
by methods) in some way.
Now, I wonder how an element should specify this. Should we :
- add a property to ElementName that would be false by default
- add a virtual property to Element that would return false by default
- add a virtual property to Element that would return the configurator to
use
- ....
What do you think ?
Gert
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
