I think your structure is fine. You just have to think more “perlishly” for your iteration. This should get you on the path to what you want–

use strictures;
use Template;

my $stuff = [ { 'filenameLarge' => [ 'fIyvYwJWmstR.jpg',
                                     'koeSHYEaekfv.jpg',
                                     'CtDKXyiRXhWz.jpg' ],
                'title' => 'February event (Feb 2013)',
                'bookid' => 8 } ];

my $tt = Template->new;
$tt->process(\*DATA, { fotos => $stuff })
    || die $tt->error(), "\n";

__DATA__
[%-FOR e IN fotos %]
   [%-e.title %]
   [%-FOR i IN e.filenameLarge %]
     <img src="/photo/[% e.bookid %]/tn/[% i %]" />
   [%-END %]
[%-END %]
[download]

Yields–

February event (Feb 2013)
     <img src="/photo/8/tn/fIyvYwJWmstR.jpg" />
     <img src="/photo/8/tn/koeSHYEaekfv.jpg" />
     <img src="/photo/8/tn/CtDKXyiRXhWz.jpg" />
[download]

pfff... That is great!!

After so much time getting this structure in place (that is maybe a post for some other time) I thought to have tried every possible trick to get this working. You found me the solution and that makes my day (weekend even!).

Thank you,
Gert

It seems to me that your data structure is a little clumsy for what you are trying to do. You are maintaining two separate arrays of file names. If I were to do this, I would probably use a data structure something like:

$VAR1 = [
          {
            'filenames' => [
                { large => 'fIyvYwJWmstR.jpg', small => 'lAwKmMFJVQDI.
+jpg', }
                ...
            ],
            'pos' => 1,
            'title' => 'February event (Feb 2013)',
            'link' => 'february-event-feb-2013',
            'bookid' => 8,
          },
[download]

HTH.

foreach (@{$fotos->{filenameLarge}}){
   print $_;
}
[download]

Thanks, I need to use the TT so I'll change the data structure to get it to work. I definitely like to be able to use different paths and probably create a separate data-structure.

One more small thing to consider, also:   “sometimes the underlying data-structures are closely matched to the needs of the template, and sometimes they aren’t.”   When the structure is complicated, or there are a number of alternatives for displaying it to the user, it might not be desirable to have code within the template be highly dependent on that structure.   (It becomes something that now must be changed in many scattered places.)

So, in cases like that, you can define functions, or “closures,” which can be referenced from within the template, as variables that are provided to it by the caller of the template.   Each time the template refers to it, the underlying function (in the Perl module, and/or in a common package referred-to by the same) does the work.   Now, if the data structure changes or evolves, only the Perl module has to be modified or expanded.

for now I'm overwhelmed by all possibilities of TT The structure will without doubt change so this feature could help. Thanks

Responding myself... guess I painted myself in a corner here. Having an extra variable in the path where the array should be used is a problem. Without this flexible path it worked like...

[% FOREACH e IN artikelen.photo %]
  </photo/[% e %]" alt="" />
[% END %]
[download]