[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Outputing tables on the fly (Was incrementing mid-
> -----Original Message----- > From: Durston, Andrew (AGRE) Hi, > One quick hitch I came across, at the same point in > the document (1.2.2.xxx) there can be multiple tables imbedded > (of various sizes). I have one imbedded at > objectnumber=1.2.2.2.0-2.0-1.0-1.0-1 and another one at > objectnumber=1.2.2.2.0-4.0-1.0-1.0-1 for example. > I do know that when the requirement tool (DOORS) creates a table, > the first element is always objectnumber=X.Y.Z.0-1.0-1.0-1 (a > table following objectnumber=1.5.4 would be 1.5.4.0-1.0-1.0-1 for > example) and flagged as tabletype=TableCell. > So I guess I need to modify the table-row template to process > only the 1st row of the first table encountered (now it seems to > be concatenating the 1st row of all tables encountered at that > level). Do the tablenumcols and tablenumrows variables become > relevant now? > Hmm. I'm not too sure, and I've been pondering over it yesterday, but it seems that that objectnumber node lends itself to perform some grouping on the doorsobject nodes. IOW, it seems that that node in itself contains all relevant information. Strictly speaking, you could extract the row and column-indices from that node. In my solution, the part that actually initiates the table creation, selects only nodes with an objectnumber node whose first 6 characters match the first 6 of the current node's objectnumber. If you extend this to match more characters... ... And while I was typing this, received your message in which you inform us of having found the solution, so I'll leave you to it then. Best of luck! Cheers, Andreas
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|