Hi all!
I am thinking about a new idea about a content tree extension of
web/desktop/computer Wiki. When I use mobile phone to access website of
Wikipedia, I can fold and unfold a content item of the content tree. That's
very convenient. However, when I use computer to access Wiki, there is no
such feature, I can not fold or unfold a content item. So shall we add this
feature from mobile Wiki to the web/computer Wiki? In other words, let the
user able to fold and unfold any content item at any level of the content
tree. For example, I search Taipei, I get 1. History, 2. Geography, 1.1
First settlements, and 1.2 Japaneses rule ect. So I would like to able to
unfold 1. History, and 1.1 First settlements, or I just unfold 1. History
and fold 1.1 First Settlements to see 1.2 Japanese rule which is unfolded.
So I would like to fold and unfold any level content items to further the
visit quality. The mobile side wiki also can improve, since it can only
fold and unfold the first level content item.
Also,add a go-back button which let the user go back to the content tree
from any content item of any level in the content tree.
Eallan
A draft version of the MediaWiki Developer Summit 2015 (San Francisco,
January 26-27) is available at
https://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015#Schedule
You will see some slots pre-scheduled for three main topics: Mobile,
Editing, and Service Oriented Architecture. There are some pre-scheduled
sessions proposed by the Architecture Committee and the Product team, plus
the opening and wrap-up sessions.
There are many slots available, and at this point almost everything is
flexible and negotiable. To book your session, check
https://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015#How_to_sched…
As an experiment, we are linking all sessions to a corresponding
Phabricator task. The goal is to ease documentation and discussion before
and after the summit, linking each session to related tasks and projects.
This is also a way to add the preparation of the session to your personal
and team backlogs.
Allocate time to prepare your sessions, and encourage discussion and
collaboration before and after the event. Let's make the most out of this
unique MediaWiki gathering!
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Please join us for the following tech talk:
*Tech Talk**:* A developer's-eye view of API client libraries: how to
choose them, how to make them, how to make them better
*Presenter:* Frances Hocutt
*Date:* January 6
*Time:* 1830 UTC
<http://www.timeanddate.com/worldclock/fixedtime.html?msg=tech+talk%3A+API+c…>
Link to live YouTube stream <http://www.youtube.com/watch?v=hz__duVeaWY>
*IRC channel for questions/discussion:* #wikimedia-office
Google+ page
<https://plus.google.com/u/0/b/103470172168784626509/events/c8fnclmkeam2gbrn…>,
another
place for questions
*Talk description: *This talk will cover why developers do (and don't) use
any of the
wide variety of client libraries available to get and post data
through the MediaWiki API. We'll talk about writing tools with an eye
to developer experience, go through the "gold standard" for MediaWiki
API client libraries
(https://www.mediawiki.org/wiki/API:Client_code/Gold_standard) and the
thinking behind it, and share some of the resources available for both
library writers and library users.
If you write or maintain an API client library, you'll learn about
what you can do to help your library get out of the way and let
developers who work with it spend their mental energy on putting
together exciting projects, not on fighting with tools. If you work
with the MediaWiki API (write bots, do research, maintain wikis),
you'll learn what to consider when you're choosing a framework for
your project. Either way, you'll start to appreciate all the factors
beyond a library's code that make the difference between fun and easy
development and a frustrating slog.
Hi everyone!
I've seen that Graphviz extension is being developed again! The old version
could parse the following graph:
<graphviz>
digraph W {
rankdir = LR ;
node[fontsize=10, fontcolor="blue", shape="none", style=""] ;
node [URL="/mw/index.php?title=\N"] ;
"User:MediaWiki default"
"User:MediaWiki default" [tooltip="MediaWiki default"] ;
"User:MediaWiki default" [fontcolor="#BA0000"];
"User:Us0"
"User:Us0" [tooltip="Us0"] ;
"User:Us0" [fontcolor="#BA0000"];
"User:Admin"
"User:Admin" [tooltip="Admin"] ;
"User:Admin" [fontcolor="#BA0000"];
"User:MediaWiki default" -> "Main Page" [ penwidth=2.0968239556951 label=1] ;
"User:Us0" -> "Main Page" [ penwidth=10.340079843406 label=6] ;
"User:Admin" -> "Main Page" [ penwidth=5.7720138182848 label=3] ;}</graphviz>
It seems that the new version doesn't understand any parameters except the
-> links. I'm having an error:
Error: No valid link was found at the end of line 2.
At Imagemap_body.php I see a lot of madness going on: regular expressions
and other horrible things. It seems that now Graphviz extension supports
only a little fraction of the dot language. Is that because of Imagemap?
Cheers,
-----
Yury Katkov
Hallo,
If I link to a section (anchor) that doesn't exist, for example [[Valentina
Tereshkova#There's no such section]], the link will still be blue.
Did anybody ever consider showing them in a different color, for example?
I cannot find anything like that in Phabricator.
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
Hi,
I've received the following email from Phabricator for a commit that
seems to have been made 3-4 years ago. Trying to access the commit, I
get "Permission denied"
My questions are:
1. What is Diffusion?
2. Why can't I see the commit?
3. Why did I recieve this email, even though I am not allowed to see the commit?
Thanks and a happy new year,
Strainu
----- Mesaj original -----
De la: Strainu <no-reply(a)phabricator.wikimedia.org>
Către:
Cc:
Trimis: Miercuri, 31 Decembrie 2014 20:25:14
Subiect: [Diffusion] [Committed] rTHER576d6ad454cb: Adding
flickrripper_strainu.py (upload bot for Flickr groups of WLM2011
Strainu committed rTHER576d6ad454cb: Adding flickrripper_strainu.py
(upload bot for Flickr groups of WLM2011 (authored by Strainu).
Adding flickrripper_strainu.py (upload bot for Flickr groups of WLM2011
git-svn-id: https://svn.toolserver.org/svnroot/p_erfgoed@395
3e45a915-b2e0-c146-c98e-857251466b57
AFFECTED FILES
USERS
Strainu (Author)
COMMIT
https://phabricator.wikimedia.org/rTHER576d6ad454cb
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Strainu
Hallo,
I am a bit of advocate for VisualEditor in my home Wikipedia (Hebrew), and
I ran into a user with a curious problem: He is an experienced editor, and
he was positive about trying to edit with VE, but it didn't work for him.
After a bit of poking around I found that he has a common.js in his user
space that had a syntax error. He probably tried to add some user script
once, did it incorrectly, and didn't bother to continue. This didn't break
any other JS-based features, at least not in a way that he noticed, but it
did break VE.
It's possible that he's not the only one.
Is there a way to lint all the user-space JS pages to see that user don't
break their own environments? Even a basic syntax check would be nice. One
could say that users should be responsible for their user spaces, but in
practice some users just copy some code without understanding what they
did, and this can help them get rid of cruft.
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
I have posted a new RFC [0] related to the "librarization" project [1]
that Kunal, Chad, Aaron, myself and others have been working on for
the last quarter. The intent of the RFC is to establish a reasonable
set of guidelines for how to manage a library project. The core idea
behind the librarization project and this RFC is that MediaWiki will
benefit from a more strict separation of components and many of those
components solve general programming problems that will also be of
interest to non-MediaWiki developers.
The project has done some initial work to pull CSSJanus and CDB out of
MediaWiki and make them available as Composer managed libraries. We
then added these libraries as requirements in the MediaWiki
composer.json manifest and updated mediawiki/vendor.git per the
Composer managed libraries RFC [2]. The new RFC attempts to provide a
roadmap for additional projects undertaken by the WikiMedia community
in this direction. The current draft focuses mainly on the
infrastructure that a new library project will need to use (git
hosting, code review, issue tracking) and the policy decisions that
need to be made (license, code style). There is some discussion of the
actual mechanics of extracting a library but they are a bit handwavy
prior to the point of having the classes that are to be extracted
isolated in the includes/libs directory.
I'd appreciate feedback on the RFC either here on the mailing list or
on the RFC's talk page. I'm especially interested to hear constructive
input on which sections may be too proscriptive and which may err in
the opposite direction and be too loose.
[0]: https://www.mediawiki.org/wiki/Requests_for_comment/Guidelines_for_extracti…
[1]: https://www.mediawiki.org/wiki/Library_infrastructure_for_MediaWiki
[2]: https://www.mediawiki.org/wiki/Requests_for_comment/Composer_managed_librar…
Bryan
--
Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org>
[[m:User:BDavis_(WMF)]] Sr Software Engineer Boise, ID USA
irc: bd808 v:415.839.6885 x6855
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2014.12. This bundle is compatible with MediaWiki 1.23.8 and
MediaWiki 1.24.1 releases.
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2014.12.tar…
* sha256sum: 5a0e00d27e2a81b896de4015a8f0933f24ea3409e554b0ba7f2e3c27ec27430f
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://phabricator.wikimedia.org/
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Babel, CleanChanges and LocalisationUpdate ==
* Localisation updates only.
== CLDR ==
* Fixed incorrect version.
== Translate ==
* Due to MediaWiki core plural rule changes, Translate extension
contains interface translations which are not compatible with any
released version of MediaWiki. If you are using Translate in the
affected languages, (See
https://blog.wikimedia.org/2014/11/04/updates-in-mediawiki-internationaliza…
for more details and list of affected languages) you might want to
consider using MLEB 2014.09 instead. The issue manifests as incorrect
plural forms used in the interface for certain numbers.
* T76184: Improvements in ElasticSearch TTM. Query results are now
more reliable and consistent.
* T49044: Fixed issue with button with long text in Special:Translate.
== UniversalLanguageSelector ==
* As a part of refactoring ULS design, world map from ULS has been
removed. You can track progress of task at
https://phabricator.wikimedia.org/T85519
* Removed support for MediaWiki <= 1.21.
=== Fonts ===
* Removed ComicNeue font for non-supported languages.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com