On 18/03/18 03:09, K. Peachey wrote:
Just make it MonoBookV5? *runs*, or more realistically V2 then progressively get rid of the orginal MonoBook?
The problem with splitting things up like that is then you need to deal with transitions from a v1 to a v2, which make everyone's lives more difficult, and especially create more work for and confuse reusers. As long as we can maintain a relatively smooth transition within the original, sticking to that is much more ideal - which is why, while I've gone and totally refactored MonoBookTemplate, I've also endeavoured to ensure the output remains functionally the same, and that all hooks and whatnot also continue to be supported, as dumb as several of them are. (Right now we're still trying to verify it really IS the same, though, so more eyes on that would be appreciated.)
The only other blocker I know of at this point is the other skins that straight-up extend MonoBookTemplate, a practice that made rather more sense back when this was all part of core, but as there only appear to be two of them, it should be pretty straight forward to simply change that behaviour now. (Which I've already gone ahead and done for Modern; Cavendish has apparently also had a task for doing the same for some time, and so shouldn't be far behind.)
-I