First of all, thanks for the votes peoples. Need to confirm something and ask opinions on another before I scuttle the codebase... (need three +1's or 0's, or some -1's with explanations if you please) ...
1) The nested system is going into the main source tree (not contrib)?... 2) The TLD. The nested tags extend the other tags, so this basically means a duplication of their library definition. To date I've just placed all the tags in the one TLD from the others. Any overwhelming opinions to separate the descriptor into the separate parts as the original library (means we would end up with "nest-html", "nest-logic" or whatever). Keep it as one?... 3) The new TLD's docco... To make sure that the new TLD is as current as it can be, I'll create it again rather than just use my current one. In the other TLD's xml files there's a fair amount of docco. My intention here is that any tag which is an extension of an original, I will remove the docco with an exception of a line to say that "this is an extension of [orig tag] tag of [orig tld].tld file". Those tags which are new for the extension will have fresh docco. That way it'll keep the size of the TLD down (if question two is +1), and save duplication of the docco and it's maintenance. Refer docco for original tags? I think that that's about what I need clarified before I commit this thing. Ta. (Ted: http://www.dictionary.com/cgi-bin/dict.pl?term=ta ) Arron. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
