> > I was thinking about the id'ed FileSet's. Here is what would need > > changing: > > > > * Add an Id property to the FileSet class > > I'm kind of curious about why implement it this way.... it > seems to me, that everything in the buildfile should be able > to be referenced by an ID, so I'd think a more interesting > idea would be to add the Id property to the Element base > class, and instead get the Project class to keep a collection > of Elements... of course, for larger buildfiles this would > imply a fairly heavy runtime memory cost, but perhaps that > could be avoided as well (particularly if we don't mind > parsing an element twice and "executing" it in different instances... > > What do you guys think? I admit I have no clue as to what Ant > does in this context, though....
Great idea! Also you shouldn't get a big runtime cost if you only stored elements that specified an id. If an element included a refid field then the element could initialize itself from the Project's copy and then apply any changes also specified in the buildfile. That sounds pretty simple from a user's point of view while still being pretty easy to implement. Example: <echo id="HelloEcho" message="Hello, World"/> <!-- what happens here? Does the command get executed? This is a bit fuzzy. I would say yes. And if you didn't want it to execute you could use the if attribute. --> <echo refid="HelloEcho"/> <!-- here I would assume the echo task gets initialized with message="Hello, World"/> --> <echo refid="HelloEcho" message="Goodbye!"/> <!-- here the echo task gets init'ed with 'Hello, World!' then gets set to 'Goodbye!'. --> Opinions on this would be useful. ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
