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_iterate and extra carriage returns

Michael_Mc_OFI

Sample page code below. Basically what is happening is that we iterate through a variety of items, and output some HTML when the condition is met. The problem is in the finally rendered code-excessive amounts of whitespace occurs. Normally, this isn't a huge problem... with from 1-10 lines showing up in normal .tpls with small amounts of iteration. However, when we created a templated page from the code fragment below-we receive over 900 blank lines.

Initially I was looking for a tag attribute that tells iw_iterate to ignore whitespace and to render everything without. Not much luck there, so I thought I'd post here and see what other solutions arise.

Thanks in advance.

[html]

 <%@ taglib uri="/dspTaglib" prefix="dsp" %> <%@ page import="java.util.*"%> <dsp:importbean bean="/atg/userprofiling/Profile"/> <dsp Smiley Tongue

age> 
 <dsp:droplet name="/atg/dynamo/droplet/Switch"> <dsp Smiley Tongue

aram name="value" bean="Profile.firmId"/> 

 my $stripped = iwpt_dcr_value('firmContent.firmText'); $stripped =~ s///g; $stripped =~ s///g; 

 <dsp Smiley Surprised

param name="3808 "> 

 </dsp Smiley Surprised

param> 

 <dsp Smiley Surprised

param name="1580 "> 

 </dsp Smiley Surprised

param> <dsp Smiley Surprised

param name="8439 "> 

 </dsp Smiley Surprised

param> 

 </dsp:droplet> </dsp Smiley Tongue

age> 

[/html]

Find more posts tagged with

Comments

Adam Stoller

Unfortuntely this is what you get when using the XML-style of PT instead of doing the whole thing in an iw_perl block.

The other alternative is to forget making everything nicely formatted and put as much code (XML-directives, etc) on each line that you can.

Migrateduser

Is it not possible to capture the generated output and remove the newlines before outputing?

Adam Stoller

Is it not possible to capture the generated output and remove the newlines before outputing?

If you do it in iw_perl - yes.
If you use iw_ostream - I believe, yes - but you'll probably have to set the EAs on the generated file yourself.

ravio

...we iterate through a variety of items, and output some HTML when the condition is met. The problem is in the finally rendered code-excessive amounts of whitespace occurs. Normally, this isn't a huge problem... with from 1-10 lines showing up in normal .tpls with small amounts of iteration. However, when we created a templated page from the code fragment below-we receive over 900 blank lines.

Initially I was looking for a tag attribute that tells iw_iterate to ignore whitespace and to render everything without. Not much luck there, so I thought I'd post here and see what other solutions arise.

A simple soulution to this issue is to everytime *start* your < iw_ ... >tags on the same line where the last one ended
Also, *end* the < iw_ ... >tags on the line where you have last line of code

Now no matter how many lines of code / content you put inside the tags you will get a clean page without white spaces,

This will *slightly* disturb the redability of your PT though

mstradling

Another option is to clean up the white space with a Perl script.

This can either be one that runs at generation and removes 'bad' white space from the generated HTML or, if you have a seperate branch for developing/mastering your TPL's it could tidy your TPLs when you deploy them to the production branch.

The second option is quite eligant as you keep the readability of your TPL's in your development/mastering branch but have white-space free TPL's (generating white-space free HTML) in your production branches.

Adam Stoller

Another option is to clean up the white space with a Perl script.

This can either be one that runs at generation and removes 'bad' white space from the generated HTML or, if you have a seperate branch for developing/mastering your TPL's it could tidy your TPLs when you deploy them to the production branch.

The second option is quite eligant as you keep the readability of your TPL's in your development/mastering branch but have white-space free TPL's (generating white-space free HTML) in your production branches.

While the approach is kind of "neat" - the problem I would have with it is that this would then mean that you are not using the same files in both Development and Production which breaks a certain amount of the rationale for having the development environment. Perhaps if you used this as a mechanism to move from source-to-usable PTs within the Development environment first and then, assuming they work in Dev, migrate the files to Production...

Personally - I just write my PTs in Perl because I can control what gets output then.

Migrateduser

This solution tends to require more processing than what is necessary. One of the simplest things to do comes down to PT readability versus generated HTML readability, or more simply put: excessive whitespace in the HTML versus not enough whitespace in the PT. You need to choose what your priority is and then go from there. There are several or more ways to get around this.

mstradling

I've always found keeping an eye on where you put your <![CDATA[ ]]> tags makes for a reasonable compromise.

<iw_something>
<![CDATA[
<html_tag>
]]>

Will tend to give you two line feeds before the <html_tag>.

<iw_something><![CDATA[
<html_tag>
]]>

Just gives one

Migrateduser

Very true, and just like that's a small compromise in PT readability, there are other compromises that can be made which may add up to an ugly chunk of code.

Adam Stoller

I've always found keeping an eye on where you put your <![CDATA[ ]]> tags makes for a reasonable compromise.

<iw_something>
<![CDATA[
<html_tag>
]]>

Will tend to give you two line feeds before the <html_tag>.

<iw_something><![CDATA[
<html_tag>
]]>

Just gives one

And you only need the CDATA tags if you're using strict XML-style PTs. If you begin your PT with <iw_pt ... /> -- i.e. an empty element instead of a container element - you no longer need all the CDATA tags - and thus your example would go from:

<iw_something>
<![CDATA[
    <html_tag>
]]>

to:

<iw_something><![CDATA[
    <html_tag>
]]>

to:

<iw_something><html_tag>