nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

iw_ostream tag?

curiousmaverick

Hello friends,

What will be a classical scenario that can justify the use of iw_ostream tag?

Regards,
Mav

Find more posts tagged with

Comments

Adam Stoller

Hello friends,

What will be a classical scenario that can justify the use of iw_ostream tag?

Regards,
Mav

Quite simply - you have the need to generate more than one file from a DCR when processing it with a given PT - and you're writing the PT in TPL-XML format as opposed to TPL-Perl or XSLT format.

gzevin

Quite simply - you have the need to generate more than one file from a DCR when processing it with a given PT - and you're writing the PT in TPL-XML format as opposed to TPL-Perl or XSLT format.

and what if one writes in a mixed mode (TPL-Perl plus TPL-XML) ???

Smiley Happy

)))))))))))

gzevin

Hello friends,

What will be a classical scenario that can justify the use of iw_ostream tag?

Regards,
Mav

just to add to what Adam has written - it's a very useful tag, especially if you want to generate a number of auxilliary files - e.g., navigation, other .inc files, etc. Bear in mind though that these files do not get the appropriate extended attributes automatically, unlike the 'ofile'. And also they do not get picked up by the workflow automatically either, one needs to parse the manifest of iwpt_compile in order to attach them.