PHPLib Templates - Dealing with blocks (
Page 5 of 8 )
Now we get to dealing with blocks.
Really, it's just more of the same...
We define some variables with some stuff in them, and then we shuffle the variables around to get what we want.
Let's take a file called 'two.ihtml'...
A list of what I want for Christmas:
<OL>
<!-- BEGIN AccessBlock -->
<LI> {item}
<!-- END AccessBlock -->
</OL>
Now, we have two types of buckets we want to manipulate text in: a variable, and a block.
First, we define the variable that contains the entire file...
<?
$T->set_file('input_two', 'two.ihtml');
?>
and then we want to break out the block...
<?
$T->set_block('input_two', 'AccessBlock', 'ABlock');
?>
What did we just do here?
We now have three PHPLIB template variables defined here:
1) 'AccessBlock', which contains the text '<LI> {item}'
2) 'ABlock', which is a place-holder for where AccessBlock USED to be, and is now a variable, dealt with like any other variable!
3) 'input_two', which contained the original text of file two.ihtml MINUS the block we've just removed, which has been replaced with the variable tag 'ABlock'.
When 'AccessBlock' was removed from 'input_two', the text of '<LI> {item}' was taken out of the 'input_two' variable and replaced with the 'ABlock' variable.
Now, let's assume that we have an array of stuff we want for Christmas:
$want_list=array(
0 => 'Baseball bat',
1 => 'Remote Control car',
2 => 'Wagon'
);
We can make that Christmas list very easily here...
<?
for ($i=0; $i<sizeof($want_list); $i++) {
$T->set_var('item', $want_list[$i]);
$T->Parse('ABlock', 'AccessBlock', true);
}
$T->pparse('Output', 'input_two');
?>
Pretty slick, eh?
So long as you keep the template block definitions and variable names the same within the source (.ihtml) file, you can use table rows, ordered/unordered lists, BR tags, whatever suits your fancy.
