* Roan Kattouw <roan.kattouw(a)gmail.com> [Mon, 15 Mar 2010 20:17:06 +0100]: Why sajax is discouraged to use? I hope that it won't be dropped, because it's small and has very little setup overhead. CategoryTree and my own extension uses it. Will v1.16 release include jQuery? 1.15 has a lot of installations, too. Can't there be sajax to jQuery compatibility layer (implementing sajax functions "indirectly" via jQuery)? Dmitriy

* Roan Kattouw <roan.kattouw(a)gmail.com> [Tue, 16 Mar 2010 11:38:11 +0100]: Let's hope that won't alter much the actual usage of it. Sometimes newer versions of extensions have important fixes, but unfortunately these extensions versions may be incompatible with older versions of MediaWiki, at the same time. It probably will be harder to backport. Ok, nevermind. Dmitriy

* Platonides <Platonides(a)gmail.com> [Wed, 17 Mar 2010 15:40:40 +0100]: older to Sure, I do. However, the old core was privately patched, so custom patches has to be ported to new core. Also, newer versions of extensions sometimes work with new core, sometimes they don't. Sorry, I've probably asked too much. Dmitriy

* Platonides <Platonides(a)gmail.com> [Wed, 17 Mar 2010 18:43:38 +0100]: patch Unfortunately, not every hack is possible to implement via the hook. For example, user groups are weak, there is no Group class or at least a good group management in User: CMS needs that. One should introduce new hooks, but you have to convince lead developers that your hook is really worth to be included into the core. Some hacks probably should be done via the class extensions (by replacing them in Autoloader), I've heard that PHP 5.3.x allows to dynamically add new methods: http://blog.agilephp.com/2009/03/31/real-programming-with-php-53-part-2-jav… I know that Parser already nicely allows to use extended class via the $wgParserConf['class'], but some other classes aren't so easy to extend. But, I am not sure that extension of classes would not break on core upgrade . Dmitriy