A core part of Smarty is a language remapping from html/smarty to php (which is outside the scope of both of our projects as they stand), that's why I refer to both our projects as incomplete, however I have the same vision you do that you'll be able to drop in php.js and then be able to drop in a smarty template. I do this right now, actually... in production. The trick is, though that because Smarty used their irritating eval() + regex strategy pre 3.0 there are a huge range of legal syntaxes that are supported. This is the more 'complete' version I speak of, one that is less rigid. Or one that implements native js caching. My port is missing a few macros but these are easily implementable, and it supports extension through mootools (I implement my framework as a subclass of this base smarty parser), but all the parsing logic is done, tested and had some stress put on it. But I'm sure if we put our heads together we can come up with some way to cross pollenate, even if it were just limited to a shared testing environment...
let me know what you think.
-abbey
I'm currently testing my framework ad-hoc using a hand assembled HTML harness, so I don't have much in the way of a stack... I'll construct a few simple tests for features I'm working on and commit them to my repo... I'll hit you back once that's done.
-abbey