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

Parsing templating.cfg

milla

In an ipl script I'm using the TeamSite: Smiley Very Happy

TemplateParse package to parse the templating.cfg file in order to find out categories, types and template file name.

I get the categories and types but not the template file names associated to every category-type. ¿How can I get it? ¿It´s possible?

Thanks a lot.

Find more posts tagged with

Comments

Adam Stoller

That does not appear to have been included in the functionality of this particular Perl module (I'm not entirely sure why). I filed a bug report on this, but it may not receive attention in the relatively short-term.

So I'd suggest creating your own code for handling the parsing of this configuration file - at least for the time being.

Essentially you can use XML: Smiley Tongue

arser and create your own handler functions.

--fish
(Interwoven, Curriculum Development)

Renata

Just checking before we jump into development mode,has this functionality been developed any further?

thank you,

james1

Perhaps you can extend the DTemplateParse class to provide the additional functionality that you are looking for? That may or may not be easier that writing your own parser -- I can't say. Either way, everyone else on DevNet would probably love to have a look at your solution code!

-- James

--
James H Koh
Interwoven Engineering

rscibett

How did you even get the categories and data types out of the hash? Something is not working for me with DTemplateParse.

Adam Stoller

Why not post (either inline or as an attachment) the code you are trying to do this with?

My guess (shot in the dark) is that you are assuming a hash and not a reference to a hash and thus are unable to extract the values that you are seeking.

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

Johnny

I hacked that module a while back for the exact same reason.

I posted it here.

Basically just extended it so that it returns the template and extension.

I also needed an extra attribute in templating.cfg to indicate if there was any need to write to the oFile.

I basically use it when im generating everything from ostreams (i use this for navigation or when one dcr writes to specific files automatically.

if ignoreOFile is set to t, then the generate scripts assumes the ofile contains nothing and writes it to nul.

You can safely ignore it if you have no need for it.

You use it in this fashion....

$template = $$cats_ref{$category}{'data_types'}{$type}{'template'};
$extension = $$cats_ref{$category}{'data_types'}{$type}{'ext'};
$ignoreOFile = $$cats_ref{$category}{'data_types'}{$type}{'ignoreOFile'};

I made a copy of the TeamSite module and moved into another package space

IAG: Smiley Very Happy

TemplateParse.

So adjust the package name accordingly.

John Cuiuli

Johnny

oh there is one catch.

It assumes there is only one registered presentation template per data type.

I guess its the reason why it wasnt built in because TeamSite allows you to manually select from multiple PT's

It works for our needs as we try to avoid manual interaction for our users.

If there is more than one, then it selects either the first one, or the last one... cant remember which one it is Smiley Happy

I guess it wouldnt be that tricky to get it to return all the PT's in a hash of some sort if thats what you are after

John Cuiuli

rscibett

Thank you. You are right on the money about how I was handling the hash. Thanks.

rscibett

Thanks for posting your module. I modified it further, adding the ability to have multiple templates associated to a data-type. If anyone is interested in this, I can post it here.

Adam Stoller

You might as well post it in this thread - to keep the variants together for later searchers...

Also - FYI (Johnny, et al):
$template = $$cats_ref{$category}{'data_types'}{$type}{'template'};
Could also be written as:
$template = $cats_ref->{$category}{'data_types'}{$type}{'template'};
Either is fine, the latter is nicer when you get into structures nested within structures nested within ...

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

Johnny

yes yes... this is true.

I find myself doing both... my consistancy can drop off with PERL and its loose rules.

John Cuiuli