Div layout

Hi

Anybody know about the path of com.interwoven.livesite.layout.impl.DivLayout java file?

Thanks in advance
Shiv

Find more posts tagged with

Comments

It is an internal Java class -- probably not a good idea to be mucking around with it. You can define your own custom layout class if you'd like.

With that said, what are you trying to achieve?

shivgaytri

It is an internal Java class -- probably not a good idea to be mucking around with it. You can define your own custom layout class if you'd like.

With that said, what are you trying to achieve?

I am creating new layout using div layout as a base but it not working as expected i am getting header and footer twice.

PFA.

vpatel

I think there may be some confusion around creating custom layout. What exactly is the requirement?

If all you are trying to do is just create a new custom page type (XSL) then you do NOT need to define the Java class for it and you can re-use the OOTB Java class as it is.

Custom page type XSL defines the overall page structure vs the Java class defines how the <div> tags (in other cases table tags, etc.) are created within the page to wrap the components.

Not to say that you may not have that requirement but I haven't seen a need ever to write your own custom Java class. You can totally create your own Java class but the OOTB one is fairly fine-tuned. OOTB you get Java class for div, table, rss, etc. I think there are 4 of them.

shivgaytri

I think there may be some confusion around creating custom layout. What exactly is the requirement?

If all you are trying to do is just create a new custom page type (XSL) then you do NOT need to define the Java class for it and you can re-use the OOTB Java class as it is.

Custom page type XSL defines the overall page structure vs the Java class defines how the <div> tags (in other cases table tags, etc.) are created within the page to wrap the components.

Not to say that you may not have that requirement but I haven't seen a need ever to write your own custom Java class. You can totally create your own Java class but the OOTB one is fairly fine-tuned. OOTB you get Java class for div, table, rss, etc. I think there are 4 of them.

I am creating new xsl only but I just want xml to tune layout.
For ex. ContainerProperties/@ComponentID element is coming from which xml?

xsl:variable name="ComponentID" select="ContainerProperties/@ComponentID"/

vpatel

What is the end goal of trying to tune out that ID?

shivgaytri

What is the end goal of trying to tune out that ID?

I have already attached the layout file.If i get the information about this element then I would be able to resolve (double header-footer issue)this issue using xsl:if condition.

vpatel

I can guarantee you that the problem is probably somewhere else if you are seeing double headers and footers and not necessarily with page layout.

Just to be clear:
1. Are you seeing the problem of double headers/footers with OOTB layout? Or with custom layout?

2. Did you create the custom layout to specifically address that problem or you created custom layout for some different need?

3. Are you trying to process the DOM after the page loads and remove the component based on that ID?

4. Do you have any page/site level controllers on the page that you are trying this on that maybe injecting / processing HTML?

shivgaytri

1. Are you seeing the problem of double headers/footers with OOTB layout? Or with custom layout?

Issue is with custom layout.

2. Did you create the custom layout to specifically address that problem or you created custom layout for some different need?

I have created the custom layout to add 5 div elements after header and 5 closing div before footer. For that I had to break Div-Container relationship

Default div layout:[html]

[/html]

Custom layout Smiley Sad

Double header footer issue)
[html]

[/html]

3. Are you trying to process the DOM after the page loads and remove the component based on that ID?

I tried to solve this issue using component id but as component id of component is not unique in every page so i think it is not a good coding standard:
[html]

[/html]

That's why I was asking about "ContainerProperties/@ComponentID "element.

4. Do you have any page/site level controllers on the page that you are trying this on that maybe injecting / processing HTML?

We are not using any page/site level controllers on the page.

vpatel

I think I understand a little better now in terms of what you are trying to do. But I still need some clarification on something. Please further clarify this:

...I tried to solve this issue using component id but as component id of component is not unique in every page so i think it is not a good coding standard...

... That's why I was asking about "ContainerProperties/@ComponentID "element. ...

Few thoughts:

1. Why not use the component name itself instead of the component ID? Just make sure that your component name is unique across the board (i.e. header and footer).

2. I am guessing your XSL posted on this forum contains relevant chunks and not entire XSL. I haven't gone through your XSL line-by-line, but if your header and footer are coming up twice then you are probably processing the XML document twice. Try using mode or something to isolate them.

3. I am not totally sure if this is the best approach but you should be able to make it work. Just keep in mind that if the .page file structure changes you'll have to update your custom page types. They tend to make minor tweaks from version to version.

4. I have achieved something very similar with fantastic results by using FALs -- that may help you in your case. It requires a little bit of creativity and thoughtfulness but its gets the job done in a "clean" way. Please look into that.

HTH!