Open Power Template 2.x family
PLEASE PROVIDE THE TEMPLATES AND/OR PHP CODE IN THE TASK DESCRIPTION (Not URL-s to them). THAT ALLOWS US TO REPRODUCE THE PROBLEM! OTHERWISE WE ARE NOT ABLE TO HELP YOU!
Remember to hide all the security-related pieces of code from the task description, like passwords, server paths etc. for your own safety. Once we close the task, we cannot edit it anymore!
PLEASE PROVIDE THE TEMPLATES AND/OR PHP CODE IN THE TASK DESCRIPTION (Not URL-s to them). THAT ALLOWS US TO REPRODUCE THE PROBLEM! OTHERWISE WE ARE NOT ABLE TO HELP YOU!
Remember to hide all the security-related pieces of code from the task description, like passwords, server paths etc. for your own safety. Once we close the task, we cannot edit it anymore!
FS#76 - New expression type syntax
Attached to Project:
Open Power Template
Opened by Zyx (Zyx) - Thursday, 09 April 2009, 02:16 GMT-8
Last edited by Zyx (Zyx) - Thursday, 15 April 2010, 02:45 GMT-8
Opened by Zyx (Zyx) - Thursday, 09 April 2009, 02:16 GMT-8
Last edited by Zyx (Zyx) - Thursday, 15 April 2010, 02:45 GMT-8
|
DetailsCurrently, the expression type is chosen with a namespace, for example:
~~~~ <a parse:href="$foo" /> ~~~~ This causes some organization problems, especially if the attribute must be in another namespace. As there will be a possibility to create new expression engines, there must be provided an alternative mechanism to specify the expression type. The proposed solution is to use the attribute value: ~~~~ <foo bar="parse:$foo"/> {parse:$foo} ~~~~ For backward compatibility, there must be left an option that activates the old behaviour (with namespaces). It will be disabled by default. |
This task depends upon
Closed by Zyx (Zyx)
Thursday, 15 April 2010, 02:45 GMT-8
Reason for closing: Implemented
Additional comments about closing: Implemented in OPT 2.1
Thursday, 15 April 2010, 02:45 GMT-8
Reason for closing: Implemented
Additional comments about closing: Implemented in OPT 2.1