Hmm, I think Jifty should make a release at the same time as the TD release since the new TD introduces one minor backward-incompatibility in Jifty::View::Declare::Helpers, where @Template::Declare::Tags::EXPORT no longer contains the list of tag subroutines generated on the fly.TD now directly installs the tag subs into the caller's package (or the package specified explicitly via the "package" option) instead of exporting things via @EXPORT. I've introduced @Template::Declare::Tags::TagSubs to hold the required information. Not sure if there's a better way to do this.
Can you declare a new T::D version # in Template/Declare.pm and make jifty depend on it, so folks working from SVN don't hurt themselves?
The other biggest show stopper for TD's CPAN release is probably the poor documentation...which is not a very enjoyable task ;) Well, help welcome, commits welcome! Cheers, agentz _______________________________________________ jifty-devel mailing list [email protected] http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ jifty-devel mailing list [email protected] http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
