As I'm sure we're all aware, the problem with changing the template system is that it'll require a huge amount of work, and it'll offer practically no tangible benefits to front-end users.
Whenever we decide to move forward on a template engine replacement (and we should eventually, because Dwoo is dead), we'll need to decide between Twig, Smarty, or something else. Currently, the way I see it is that Smarty has the advantage that it's closer to Dwoo, so it'll probably be less work to adapt our codebase and documentation. Twig has the advantage that it's more attractive to developers, being newer, trendier, and used by Drupal. But web frameworks evolve pretty fast, so we'll probably need to review the issue at the time we decide to pick up the change again. -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/966001 Title: Switch templating system from dwoo to twig Status in Mahara ePortfolio: Confirmed Bug description: Given that Dwoo is mostly unmaintained now: https://twitter.com/#!/seldaek/status/167546484865241088 we should consider switching to Twig: http://twig.sensiolabs.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/966001/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
