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; } } }

Component and Primary Variable Scope

Tim__D

I'm trying to put some iw_perl in a component template. The iw_perl contains some logic that constructs a %hash which I wish to create and then share with the host template and other components. I have added the code but am having an issue where the %hash is not accesible from the other templates. How does variable scoping work when using component templates. Interwoven encourages the use of component templates as a method of code reuse but it is not working in this case. Can someone explain?

- Tim

Edited by Tim__D on 09/13/05 02:16 PM (server time).

Find more posts tagged with

Comments

jbonifaci

I believe there is no way to access the variables from your component template in the calling template.

Tim__D

There must be a way to share iw_perl and variables across multiple tpl's? What happens if I need the same subroutine in many host templates?

jbonifaci

You can create a perl module that you can include in each of your tpls, but the functions in those modules will not be able to use the tpl functions. But, you could have them take in values and manipulate them and/or return other values. There have been some threads about people trying to use the tpl functions in modules in the past, but as far as I recall, they were not successful. I could be wrong, you can try searching for them, or perhaps someone else will recall.

~Jeff

Tim__D

I have used custom modules in the past but those functions were indeed generic and had their place in a Perl module. In this case the subroutine I'm creating is not generic and is simply a presentation function that builds a hash of images based on the value of another loaded DCR. I suppose I could just place the routine into all the host .tpls and pass in the hash as an argument. At least that way I have some level of code reuse. I'm disappointed that I have to do it this way it defies common sense.

Adam Stoller

If you define the perl module to accept a fair amount of parameters (I'd think object-oriented would be the way to go) you should be able to reuse it for all your PTs.

Not know the specifics of your requirements - it's kind of hard to get very detailed - (and I don't have time to try and understand your requirements and do the work for you [you didn't ask, I'm just saying]) - but consider passing in the path to the DCR, and a reference to an array of fields you want to extract into the hash - the module could then load the DCR (TeamSite::XMLnode or similar) extract the fields, create the hash, and return a reference to the hash back to the caller.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Tim__D

I know what your saying about the details. I like to keep my posts simple and generic. (How to share a variable or subroutine from a component PT) is my primary generic question. It sounds like I cant from what I have heard so far. I do understand that by moving out the subroutine into a .pm I can have a generic subroutine but I'm not sure that this really helps me. What I need to to share what is basically presentation logic and variables in a series of PTS and I'm not sure that the using a .pm is the cleanest solution.

One other question. Is it possible that pass a %hash as an iw_arg{}?

Tim__D

I have to get moving on this so I think I'm going to place the subroutine in as many primary PT as I need to and then pass separate iw_args into the component templates from the host.