Re: [Actionframework-users] parameters to output-variable methods

[Craig L. <cr...@be...>]

On Fri, 2002-08-09 at 05:07, Mandip S. Sangha wrote:
> Hi Craig
>=20
> Just a quick suggestion, I have found that when I need to load many=20
> objects for a particular template it is useful to build a super object=20
> to encapsulate all the objects needed for the template.  In your case I=20
> would initially build my super object from the given URL store it in a=20
> component that exists session-wide and then redirect to your=20
> show-template url.
> [...snip...]

this sounds good and would work for most cases in my case also.=20
however, what i was really trying to effect was to have the
<template.../> define everything the template needed 'at rest'.  this
way, ANYTHING could finally decide that something it needed was not
available and simply be able to return the default template, which would
then have all of its required data loaded for itself.  handling things
specially in another object (or inside a form/action) would mean that
every time i wanted to default to that template, i would have to set
things up myself, or have them setup for every call and normally just
not use them.

i'm starting to play around with the code to see what it would take to
add a method attribute to the output-variable element, most of the code
is fairly well encapsulated in helper classes, with the exception of the
code that preps and converts the parameter values.  before i get too
involved in it though, i want to see what petr thinks.

cheers,

--=20

     CraigL->Thx();
     Be Developer ID: 5852