Hello,
Sometimes in LocalSettings.php or in extensions settings one want to do simple computations on the namespaces or related to the Git branch in a development environment. Unfortunately this is not (resp. no more) really possible, because LocalSettings.php is loaded before GlobalFunctions.php and Setup.php.
Is it a good practice to do that? If yes, is it possible to either:
* "tag" some static functions in some classes to avoid these to include hooks and other global functions and variables (loaded later), and/or
* move before (in loading order) some global functions and variables to make them usable (e.g. wfDebugLog, wfRunHooks, $wgCanonicalNamespaceNames)
?
Details for namespaces: $wgCanonicalNamespaceNames is defined in Setup.php, making MWNamespace::getCanonicalNamespaces() and MWNamespace::getValidNamespaces() unusable in LocalSettings.php to e.g. compute namespaces where an extension could be enabled <https://github.com/mementoweb/mediawiki/pull/2>.
Details for Git version: until two months it worked, but some wfDebugLog was introduced (defined in GlobalFunctions.php), making it unusable in LocalSettings.php.
~ Seb35 [^_^]
Hi should we upgrade jQuery UI to 1.11.1 since mediawiki droped support for javascript for internet explorer 6 and might drop javascript for internet explorer 7.
in light of the recent conversation about superprotect
and about what community could or should do to get things done
specifically i'd like to see links to documentation on gadget & extension writing
right inside of 'gadgets' and 'beta' tabs
somewhere in big fat banner at the bottom of each of these tabs
'want to add your gadget/beta feature? _learn more_ & _get involved_, or _request an idea_'
please give that a kick -- where? how?
... file a bug with betafeatures extension to modify its text, or can it be modified on-wiki ?
... edit relevant mediawiki:* page for gadgets for each project manually so that it includes a link to [[:mw:Gadget kitchen]] ??
... structurise the gadgets place for it to become more useable as a directory ??
--
svetlana
Hello,
I'm trying to install parsoid on Ubuntu 12. I installed nodejs from
source, but when I try and install parsoid via apt-get it fails saying
that it depends on nodejs (>= 0.8.0) even though node --version returns
v0.10.31!
Anyone have any ideas what could be wrong?
Cheers,
Aran
On 28 August 2014 11:22, Max <max(a)koehler-kn.de> wrote:
> You're welcome. Do you guys have a grunt workflow set up? I'd love to help
> out.
>
Yes, here for OOjs UI
<http://git.wikimedia.org/blob/oojs%2Fui.git/HEAD/Gruntfile.js> – we'd
definitely welcome suggestions and patches. :-)
J.
--
James D. Forrester
Product Manager, Editing
Wikimedia Foundation, Inc.
jforrester(a)wikimedia.org | @jdforrester
Kaldari, RobLa, Trevor and I met yesterday to discuss the template RFC [1].
Sadly Gabriel was not present. Kaldari and I are very concerned that
we are blocking standardisation of a generic template library on the
completion of Knockoff.
Trevor, Kaldari and I identified that two things need to happen for
the templating solution that currently lives in Mantle [2] to core:
1) We need some JavaScript API for using templates (in current form
all we have is a standard way to ship templates from the server to the
frontend). Trevor is working on a template widget for oojs which will
make this possible
2) We need a standard template language
3) Better namespacing for templates - we identified that we will need
to find better ways of uniquely identifying templates [3].
We questioned whether point 2 should be blocking, as we recognised
that even if we decide to standardise on Knockoff in future, it should
be trivial to write a script that converts Hogan/Handlebars template
language to Knockoff. The Mantle ResourceLoader module in current form
is template agnostic and currently works with both Hogan and
Handlebars, so in theory should make it easy to transition from one
template language to another.
On this basis, I think the next step would be for the oojs development
team to get a template widget up that can be used by Mantle.
[1] https://www.mediawiki.org/wiki/Requests_for_comment/HTML_templating_library
[2] https://www.mediawiki.org/wiki/Extension:Mantle
[3] https://bugzilla.wikimedia.org/show_bug.cgi?id=69916
On 27 August 2014 12:14, Max <max(a)koehler-kn.de> wrote:
> There's a grunt task called grunticon that does #2.
> https://github.com/filamentgroup/grunticon
Max,
That's a pretty awesome find; thank you!
J.
--
James D. Forrester
Product Manager, Editing
Wikimedia Foundation, Inc.
jforrester(a)wikimedia.org | @jdforrester
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2014.08. This bundle is compatible with MediaWiki 1.23.x and
MediaWiki 1.22.x releases.
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.08.tar…
* sha256sum: f4663910facd2b34d4afb1af930f66adad22b2746f9395f7706f07751e633857
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://bugzilla.wikimedia.org
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Babel, CLDR, CleanChanges and LocalisationUpdate ==
* Only localisation updates.
== Translate ==
=== Noteworthy changes ===
* Breaking change: Dropped support for MediaWiki 1.21 (2014.05 is the
latest version of MLEB as a whole which supports 1.21)
* Avoid losing translators' edits: improved handling of expired
sessions ({{bug|69314}}).
** Status has yellow background if the translation has not been saved.
** Show an alert to the user if session has expired.
** Prevent saving translations as an anonymous user accidentally.
* Restore progress icon for the current translation page (regression
from MLEB 2014.07).
* Update associated translation pages when moving translation units.
* Show definition diff for all messages if available, not just for
outdated messages.
* Special:AggregateGroups: Group selector is now input field with
autocompletion instead of combobox.
* Special:PageMigration: Don't add the created pages to watchlist.
* Special:PagePreparation: This is a new special page to assist in
preparing pages for translation
== UniversalLanguageSelector ==
* Change the autonym for Algerian Arabic.
* Localisation updates.
==== Input Methods ====
* Tibetian-ewts: Use of unicode NFC instead of NFD.
* Fixed description in Bengali Probhat layout.
==== Fonts ====
* Added Comic Neue font. It is available for English and other
languages using the latin alphabet.
* Updated UnifrakturMaguntia font to the latest version.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
On Tuesday, August 26, 2014, MZMcBride <z(a)mzmcbride.com> wrote:
> Legoktm wrote:
> >This is now at [[dev.wikimedia.org]]? That sounds like a much better
> >name than "build", which I thought was going to be some CI automated
> >builds server from your email title :)
>
dev.wikimedia.org it is, yes. Moving on, please.
We
> already have a publishing platform that we can and should leverage and it
> lives at www.mediawiki.org
>
This is basically decided as well. However, we still need the best of our
technical knowledge to solve this problem: how to extract API documentation
from source code repositories and import it to wiki pages. Your ideas and
help are welcome -- see the ongoing discussion at
http://fab.wmflabs.org/T491
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil