Added a generically generic template for the generic purpose of showing generic text in the usual generic place.
To hell with MVC! Anything that makes reading code is a plus of course, but if it makes WRITING code much more annoying, then it also kills spontaneity.
It's a bit like the language translation system... SMF does it with $txt['item_name'], when really they should do something like txt('Actual text'), and then call a function that checks if a translation is available for that particular string... Maybe a txt('Actual text', 'Context') allowing for multiple strings within different contexts, of course... Things like that. That would make it easier to just write plugins without having to bother about translations, and then anyone can translate any string that way (plus, they don't have to refer to a master file to get the original translation, and if the English version is modified, the translation will need to be updated otherwise the text will now show up in English -- in the current Wedge and SMF, a modified English string won't be updated at all in translated version).
Yes it's a bit slower at parsing time, but it's not a problem with Wedge, because all files are cached, and thus you can parse & run that function at cache time and not at runtime, and then save the cached file to something like 'Something.template.french.php', etc...
Of course, it's too late to do that now...