flexy enhancement

From: Date: Thu, 10 Jul 2003 10:34:05 +0000
Subject: flexy enhancement
References: 1 2 3  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-18125@lists.php.net to get a copy of this message
I like flexy. It answers some of the design questions I was still trying to make. I like the fact the page data used to expand {} embedded tags comes from object fields. http://pear.php.net/manual/en/package.html.html-template-flexy.tag.variable.php shows how variable detection is done so that loop variables are rendered properly. I would want to hijack this behaviour so as class methods were defined, any parameters to the method were also not prefixed with $t-> In my code I track a stack out output directors showing which method (if any) is to receive html (and now if I merge with flexy) translated php. Hopefully flexy will be able to handle calling a method to arbitrate output instead of just outputing to single target. http://pear.php.net/manual/en/package.html.html-template-flexy.tag.method.php it seems that embedded method calls are all on $t-> (the object passed for outputObject; wht scope might there be for global php-native functions? I can't think of a need but just wnted your thoughts as it is something I am struggling with. From my point of view I dont want the designer to easily take on too much power; from my view the designer is just designing page for the programmer to use. From your point of view I think you are letting the designer be able to do some basic php. (No conflict here). However http://pear.php.net/manual/en/package.html.html-template-flexy.tag.if.php shows perhaps in some case (from my point of view) the designer may legitimatly embed conditions rather than in every case to delegate the implementation of the condition to an inherited function. Maybe. Flexy seems cool, I will take your hint and start working to integrate. Shame I just got my php parser working so cool, even supporting <% %> type tags without breaking, and having done it so neatly! Sam

« previous php.pear.dev (#18125) next »