Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <3F32161F.5030201@apache.org>
Date: Thu, 07 Aug 2003 11:04:31 +0200
From: Gianugo Rabellino <gianugo@apache.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Getting an X from a FOM_X
References: <003301c35cc1$acffbab0$1e01a8c0@WRPO>
In-Reply-To: <003301c35cc1$acffbab0$1e01a8c0@WRPO>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Reinhard P�tz wrote:

>>But now I have a need to add the "getRealPath" method to the context, 
>>only because Linotype uses it extensively and I wanted to 
>>port it to the 
>>FOM. Is there a particular reason why it shouldn't be there? 
> 
> I think because Stefano considered it as hack - see his comment:
> 
> /*
>  * Yeah, I know that hardwiring those is hacky as hell. But I'll try to
>  * fix this with link translation later on.
>  */
> var home = cocoon.context.getRealPath("/") + "samples/linotype/";

I think that actually Stefano was blaming hardwiring configuration info 
right in the code instead than getting them from somewhere, not the 
getRealPath stuff.

Ciao,

-- 
Gianugo Rabellino
Pro-netics s.r.l. -  http://www.pro-netics.com
Orixo, the XML business alliance - http://www.orixo.com
     (Now blogging at: http://blogs.cocoondev.org/gianugo/)