You are right; my vote on the issue: -1.
-- eokyere
On 12/6/05, Geert Bevin <[EMAIL PROTECTED]> wrote:
> > Locally, I currently use it to return the "template" property of my
> > elements
> >
> > public Template getHtmlTemplate() throws TemplateException,
> > EngineException {
> >
> > if (!hasProperty(TEMPLATE))
> > throw new
> > PropertyRequiredException(getDeclarationName(),
> > TEMPLATE);
> >
> > return getHtmlTemplate(getPropertyString(TEMPLATE));
> > }
> >
> > I think that is more practical/useful than the proposed solution and
> > maintains the separation we try to create between the templates and
> > implementations.
>
> Well, afaik, this doesn't do the same. The issue automates the name
> specification of the template, according to the element id.
>
> --
> Geert Bevin Uwyn bvba
> "Use what you need" Avenue de Scailmont 34
> http://www.uwyn.com 7170 Manage, Belgium
> gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
>
> PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
> Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
>
>
> _______________________________________________
> Rife-users mailing list
> [email protected]
> http://www.uwyn.com/mailman/listinfo/rife-users
>
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
