I knew this felt familiar; the issue came up a couple months ago, but
with no solution at the time. This isn't a really a problem, it's a
matter of convenience for programmers.
The thread was:
"T5: static page variables in templates"
On 10/9/07, Daniel Jue <[EMAIL PROTECTED]> wrote:
> Hi, I wanted to try eliminating a bunch of getters in my Java class.
>
> Right now I have something like this in my template:
>
> <t:if test="showYear">
> <t:selectyear />
> </t:if>
>
> And I have a getter that is
>
> public boolean getShowYear() {
> return this.getUsesSetting(ReportVariableEnum.FISCALYEARSINGLE);
> }
>
>
> I want to do something like this:
>
> <t:if test="getUsesSetting(ReportVariableEnum.PARTICULARVARIABLE)">
> This uses Particular Variable
> </t:if>
>
> So I will only have to have getUsesSetting() in my page class.
>
> I have about 30 or so components, with 30 or so getters, and with 30
> or so getShowComponentName() methods.
>
> This class is getting to be a pain to read through.
>
> Any Ideas?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
