Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <41F37797.20800@nada.kth.se>
Date: Sun, 23 Jan 2005 11:08:23 +0100
From: Daniel Fagerstrom <danielf@nada.kth.se>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [RFC] Plugable Expressions
References: <41EB9567.60908@nada.kth.se> <41F113F4.5080302@mobilebox.pl>
 <41F25D26.5060903@nada.kth.se> <41F2A6C8.6020301@mobilebox.pl>
In-Reply-To: <41F2A6C8.6020301@mobilebox.pl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Leszek Gawron wrote:
> Daniel Fagerstrom wrote:
> 
>> They should, but I don't see how that is related to getNode/getValue? 
>> jx:set/@value uses getNode and jx:set/* executes the body and put the 
>> result in a DOM.
> 
> I see. I wasn't aware of the exact implementation here. Sorry for the 
> noise.
> 
> I have finally started to implement jx:call macro="${name}".
> 
> Some time ago we discussed about implementing an "internal taglib 
> design". What I mean every instruction was implemented as separate tag 
> (no new tags could be introduced). Parser would not depend on a specific 
> set of tags.

I'm working on that as you can see in Parser, the only thing that is 
left to be done is that jx:define need to run some code both in the 
start and the and tag. I have some ideas about what to do about that but 
  am not sure yet.

> Every Instruction in current JXTG apart from jx:macro could 
> be implemented completely separately. jx:macro depends on jx:parameters 
> parsed separately so the Parser needs to know the dependency details. 
> Same goes for future jx:call/jx:parameter. Could we do something about 
> that?

Hopefully but I don't know how yet, I'll research it further.

/Daniel