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

Using iwpt_dcr_list and iwpt_dcr_value in custom perl module

ChrisD

Hi All,

I am wanting to abstract out most of the common tpl functions we use across our site into a perl module to include so that the tpl's are very simple and mostly contain their custom code ... As part of this, we have to process the DCR to obtain values to set for metadata on the file.

I have been able to abstract out most of the iwpt_* modules using tech notes 2442 and 49638 but have been unable to abstract out iwpt_dcr_list and iwpt_dcr_value ....

Is it possible to do?

Thanks

Chris

Find more posts tagged with

Comments

ISCBorisB

I... have been unable to abstract out iwpt_dcr_list and iwpt_dcr_value... Is it possible to do?

Yes. Matter of fact, TS already does it for you. It's different though than the usage of closures (if closures are what you used before).

Consider the following example. Let's say in your PT you have:
my @pt_foo = iwpt_dcr_list('pointer.moo'); Formally, 'pointer.moo' is an access string, nothing more.
In the PT namespace however $pointer either already exists or can be created as a blessed object of TeamSite: Smiley Very Happy

CRnode type.

So, in your pm you may have something like the following providing $pointer was passed:
my @pm_foo = $passed_pointer->get_node_list('moo');
iwpt_dcr_value('something.name') corresponds to $something->value('name'), etc...

ChrisD

Yes. Matter of fact, TS already does it for you. It's different though than the usage of closures (if closures are what you used before).

Closures are what I have been using for the main functions ...

Consider the following example. Let's say in your PT you have:
my @pt_foo = iwpt_dcr_list('pointer.moo'); Formally, 'pointer.moo' is an access string, nothing more.
In the PT namespace however $pointer either already exists or can be created as a blessed object of TeamSite:CRnode type.

So, in your pm you may have something like the following providing $pointer was passed:
my @pm_foo = $passed_pointer->get_node_list('moo');
iwpt_dcr_value('something.name') corresponds to $something->value('name'), etc...

If I was previously doing:

my $desc = iwpt_dcr_value('dcr.Metadata.metadata.description');

and then later

my $swordNames=iwpt_dcr_value('dcr.sword-names');

I take it would be best to replace those with passing the $dcr parameter

So I could then do:

$dcr->value('Metadata.metadata.description');

and

$dcr->value('sword-names');

Or can you only get values from one level down?

Thanks

Chris

Ps: Is there anyway to pass in the complete DCR so that I can pick and choose which bits later on I want instead of always having to pass in when I need to ... This way I can abstract calls out of the TPL to the PM so that I am just calling functions most of the time that are the in the PM doing the actual work with the DCR to set values ....

chartdrilldown.rptdesign

ISCBorisB

Your object is in essence XML Node. Do perldoc on the class to see what you can do.
Basically, one level down is the way to go. If you want you can build your own layers on top of DCRNode with the desired API.

Here is the simple way to pass whole DCR as a root node:
$yourOject->yourMethod(iwpt_dcr_list('dcr')); # It will create a scalar and not an array (despite suffix "list" in "iwpt_dcr_list")

Btw, what was the error manifestation when you tried to use closures for iwpt_dcr_****? I never tried that.
Whatever it was, perhaps the fact that access string does not mean much outside of PT contributed to it

ChrisD

Btw, what was the error manifestation when you tried to use closures for iwpt_dcr_****? I never tried that.
Whatever it was, perhaps the fact that access string does not mean much outside of PT contributed to it

In the compilation you get the closures:

sub { iwpt_dcr_value() } , sub { iwpt_dcr_list() }

parsed into:

sub { (eval TeamSite: Smiley Very Happy

CRparser:

erl_name())} ,
sub { (eval TeamSite: Smiley Very Happy

CRparser::dcr_list_perl_name() ) }

When you do your call of:

$dcr_value_pointer->("dcr.Metaname.metatitle");

gives an 'unde' result when printed out as does

$dcr_list_pointer->("dcr");

ISCBorisB

In the compilation you get the closures:

sub { iwpt_dcr_value() } , sub { iwpt_dcr_list() }

parsed into:

sub { (eval TeamSite:CRparser:erl_name())} ,
sub { (eval TeamSite:CRparser::dcr_list_perl_name() ) }

When you do your call of:

$dcr_value_pointer->("dcr.Metaname.metatitle");

gives an 'unde' result when printed out as does

$dcr_list_pointer->("dcr");

I wonder if the inclusion of empty parameter list into closure causes some issues...

If I were you, I would try something like sub {&iwpt_dcr_value} instead of sub { iwpt_dcr_value() }
Not sure if it will help though