Re: [jira] Created: (VELOCITY-509) Add new directive #evaluate

2007-01-03 Thread apache
No, the #evaluate directive is to be used as it the following example:

#set( $error = $i18n_tool.getMessage("ERROR123") )
#evaluate( $error )## reder by merging with context

It something like the #parse directive, but the content comes
from a string and not a file.

:) Christoph

Geir Magnusson Jr. wrote:
> Do you mean
> 
>   $foo = "#foreach($a in $b) .. #end"
> 
> ?
> 
> If so, why not just do it that way, rather than add a new directive?
> 
> geir
> 
> 
> On Jan 2, 2007, at 11:47 PM, Will Glass-Husain (JIRA) wrote:
> 
>> Add new directive #evaluate
>> ---
>>
>>  Key: VELOCITY-509
>>  URL: https://issues.apache.org/jira/browse/VELOCITY-509
>>  Project: Velocity
>>   Issue Type: New Feature
>>   Components: Engine
>> Affects Versions: 1.5 beta2
>> Reporter: Will Glass-Husain
>> Priority: Minor
>>  Fix For: 1.6
>>
>>
>> On a separate issue (VELOCITY-504) we came up with the idea of a new
>> directive, #evaluate.  Basically, it would act just like
>> Velocity.evaluate().
>>
>> Users are always asking for this capability (internal evaluation). 
>> Usually we tell them to "use a tool".  Instead, we should just put in
>> a simple directive that would evaluate a VTL string using the current
>> context.
>>
>> Incidentally, this should be the current local context, e.g. if inside
>> a macro or a foreach loop (or worse, both) it should use that
>> context.  See VELOCITY-504 for why this is needed.
>>
>> --This message is automatically generated by JIRA.
>> -
>> If you think it was sent incorrectly contact one of the
>> administrators: https://issues.apache.org/jira/secure/Administrators.jspa
>> -
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [jira] Created: (VELOCITY-509) Add new directive #evaluate

2007-01-03 Thread Geir Magnusson Jr.

Do you mean

  $foo = "#foreach($a in $b) .. #end"

?

If so, why not just do it that way, rather than add a new directive?

geir


On Jan 2, 2007, at 11:47 PM, Will Glass-Husain (JIRA) wrote:


Add new directive #evaluate
---

 Key: VELOCITY-509
 URL: https://issues.apache.org/jira/browse/ 
VELOCITY-509

 Project: Velocity
  Issue Type: New Feature
  Components: Engine
Affects Versions: 1.5 beta2
Reporter: Will Glass-Husain
Priority: Minor
 Fix For: 1.6


On a separate issue (VELOCITY-504) we came up with the idea of a  
new directive, #evaluate.  Basically, it would act just like  
Velocity.evaluate().


Users are always asking for this capability (internal evaluation).   
Usually we tell them to "use a tool".  Instead, we should just put  
in a simple directive that would evaluate a VTL string using the  
current context.


Incidentally, this should be the current local context, e.g. if  
inside a macro or a foreach loop (or worse, both) it should use  
that context.  See VELOCITY-504 for why this is needed.


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the  
administrators: https://issues.apache.org/jira/secure/ 
Administrators.jspa

-
For more information on JIRA, see: http://www.atlassian.com/ 
software/jira




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Created: (VELOCITY-509) Add new directive #evaluate

2007-01-02 Thread Will Glass-Husain (JIRA)
Add new directive #evaluate
---

 Key: VELOCITY-509
 URL: https://issues.apache.org/jira/browse/VELOCITY-509
 Project: Velocity
  Issue Type: New Feature
  Components: Engine
Affects Versions: 1.5 beta2
Reporter: Will Glass-Husain
Priority: Minor
 Fix For: 1.6


On a separate issue (VELOCITY-504) we came up with the idea of a new directive, 
#evaluate.  Basically, it would act just like Velocity.evaluate().  

Users are always asking for this capability (internal evaluation).  Usually we 
tell them to "use a tool".  Instead, we should just put in a simple directive 
that would evaluate a VTL string using the current context.

Incidentally, this should be the current local context, e.g. if inside a macro 
or a foreach loop (or worse, both) it should use that context.  See 
VELOCITY-504 for why this is needed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]