Stefano Mazzocchi wrote:
One concern is to come up with a unified template language. This implies:
1) understanding the features we want (and we don't want!) from a template language
2) come up with a syntax
3) implement it
Another and completely separate concern is how to factor out existing bits so that #3 is easier.
You are attacking #3 before attacking #1 and #2 and that's why everybody here is feeling frustration: there is no consensus on #1
I don't think so. There were tons of mails and IMHO we agreed on a list of features (maybe a final summary is missing)
and #2 so
IIRC we aggreed that we like the current syntax of JXTemplate. Exception: We deprecate the #{} notation in favour of ${xpath:....}.
attacking #3 now is more harmful than useful.
hmmm, IMO #1 and #2 was done ...
-- Reinhard
