on 8/9/01 3:38 PM, "Eric Dobbs" <[EMAIL PROTECTED]> wrote:
>
> On Thursday, August 9, 2001, at 11:12 AM, Jason van Zyl wrote:
>
>> On 8/9/01 11:59 AM, "Jon Stevens" <[EMAIL PROTECTED]> wrote:
>>
>>> on 8/9/01 5:13 AM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote:
>>>
>>>> We definitely need a solution, but I was thinking of something a
>>>> little more
>>>> general for the services. Paths with a leading '/' are treated as
>>>> absolute
>>>> paths whereas something without will be treated relative the
>>>> application
>>>> root. This won't really affect anything but the general solution of
>>>> absolute/relative paths should be be resolved in fulcrum at the
>>>> service
>>>> level. This require a bit of work in fulcrum.
>>>
>>> That won't work because paths currently start with a /template by
>>> default
>>> and will break existing TR.props. Having them be just "template" would
>>> be
>>> even more confusing to people because it wouldn't look like a path.
>>
>> I said it would require some work. What we have is confusing, I think
>> people
>> generally associate a leading '/' with an absolute path and the absence
>> of
>> leading '/' to be a relative path.
>
>
> what about renaming the property from 'template' to 'templatePath'
>
> if it's a path, then call it a path.
>
> $0.02
I think you are missing the point. It isn't a property called 'templates' it
is a PATH called 'templates'.
Look in your tr.props file.
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
