It seems as though views would provide the functionality I was looking for. Am I correct in this assumption?
> Is it possible to create a template for other templates to use as > a type of > widget? What I am looking to for is different ideas on how to provide a > standard set of drop down menus (widgets) that can be associated to a > specific set of data. I do not want to have the logic for retrieving or > referencing the data in the actual template. I was hoping to > somehow 'tie' > a method or subroutine which would be used for accessing the data > that could > be used by the 'widget' template. > > As a very simple Example . . . > > -- In main template -- > <html> > [% INCLUDE dropdownMonth %] > </html> > > -- In dropdownMonth template -- > > <select name="birthdate"> > [% monthL = getMonthArray() %] > [% FOREACH m = monthL %] > <option value="[% m.id %]">[% m.name %]</option> > [% END %] > </select> > > ------ > > With getMonthArray() acting as the interface to the data. Perhaps this > method can also have 'polymorphic' behavior in that it can do different > things based on the 'widget' context it is called from. I am > really open to > ideas so am not stuck on specifying a method to use for the data > retrieval . > . . > > Thanks, > > > > > _______________________________________________ > templates mailing list > [EMAIL PROTECTED] > http://www.template-toolkit.org/mailman/listinfo/templates
