on 7/5/01 2:45 PM, "Mike Haberman" <[EMAIL PROTECTED]> wrote:
> that's the case when you need to say setScreenTemplate("news,News.vm")
> those questions, to me, fall under the same category as
> path/classpath problems.
Right, and the problem with that is that we have all been migrating away
from having to define a classpath. Ant hides that for us. I would rather not
migrate back in that direction if at all possible.
Patient: It hurts when I do this.
Doctor: Don't do that.
>> Needless to say, you can create your own VelocityScreen and
>> TurbineTemplateService and whatever files you needed to modify and use those
>> properties instead of using the Turbine supplied ones.
>
> yea. I like to use the out of the box services. Less to remember
> when upgrading.
We really should make it so that the TR.props is generated more easily. That
way, you can have a "local" set of values and then generate your TR.props
based on those local set of values. This would make upgrades a LOT easier.
> How about adding a TR prop that allows you to accept the default behavior
> (prepend "screens") or use the multiple path solution ?
That is fine for me, but I want the default to be as it currently stands.
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
