Re: [Wikitech-l] GRAPH extension is now live everywhere!

2015-05-06 Thread Yuri Astrakhan
Aleksey, please file a bug report in phabricator with the URL to the page
containing your non-working graph - I have to look at your graph before
figuring out why it is not working.

Bawolff, very cool API usage!  I just wish we allowed api from inside lua
-- so much creative stuff could be done!

On Wed, May 6, 2015 at 6:32 AM, Brian Wolff bawo...@gmail.com wrote:

 On 5/5/15, Yuri Astrakhan yastrak...@wikimedia.org wrote:
  Starting today, editors can use *graph* tag to include complex graphs
 and
  maps inside articles.
 
  *Demo:* https://www.mediawiki.org/wiki/Extension:Graph/Demo
  *Vega's demo:*
 http://trifacta.github.io/vega/editor/?spec=scatter_matrix
  *Extension info:* https://www.mediawiki.org/wiki/Extension:Graph
  *Vega's docs:* https://github.com/trifacta/vega/wiki
  *Bug reports:* https://phabricator.wikimedia.org/ - project tag #graph
 
  Graph tag support template parameter expansion. There is also a Graphoid
  service to convert graphs into images. Currently, Graphoid is used in
 case
  the browser does not support modern JavaScript, but I plan to use it for
  all anonymous users - downloading large JS code needed to render graphs
 is
  significantly slower than showing an image.
 
  Potential future growth (developers needed!):
  * Documentation and better tutorials
  * Visualize as you type - show changes in graph while editing its code
  * Visual Editor's plugin
  * Animation https://github.com/trifacta/vega/wiki/Interaction-Scenarios
 
 
  Project history: Exactly one year ago, Dan Andreescu (milimetric) and Jon
  Robson demoed Vega visualization grammar 
 https://trifacta.github.io/vega/
  usage in MediaWiki. The project stayed dormant for almost half a year,
  until Zero team decided it was a good solution to do on-wiki graphs. The
  project was rewritten, and gained many new features, such as template
  parameters. Yet, doing graphs just for Zero portal seemed silly. Wider
  audience meant that we now had to support older browsers, thus Graphoid
  service was born.
 
  This project could not have happened without the help from Dan Andreescu,
  Brion Vibber, Timo Tijhof, Chris Steipp, Max Semenik,  Marko Obrovac,
  Alexandros Kosiaris, Jon Robson, Gabriel Wicke, and others who have
 helped
  me develop,  test, instrument, and deploy Graph extension and Graphoid
  service. I also would like to thank the Vega team for making this amazing
  library.
 
  --Yurik
  ___
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org
  https://lists.wikimedia.org/mailman/listinfo/wikitech-l


 Hmm cool.

 One of the interesting things, is you can use the API as a data
 source. For example, here is a pie graph of how images on commons
 needing categories are divided up

 https://commons.wikimedia.org/w/index.php?title=Commons:Sandboxoldid=159978060
 (One could even make that more general and have a template, which
 given a cat name, would give a pie graph of how the subcategories are
 divided in terms of number).

 --bawolff

 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Conpherence enabled? (was [Wikitech-ambassadors] Tech newsletter (2015, week 19))

2015-05-06 Thread Alex Monk
How do I prevent people from contacting me via this?

On 6 May 2015 at 03:33, MZMcBride z...@mzmcbride.com wrote:

 Legoktm wrote:
 On 05/04/2015 08:07 AM, Guillaume Paumier wrote:
* You can now chat with other users
  https://www.mediawiki.org/wiki/Conpherence in Phabricator. [1]
  https://phabricator.wikimedia.org/T91392
 
 Uh, why? Where was this actually discussed with more than 4 people? We
 already have IRC and mailing lists, so why do we need yet another
 communication system? Are we going to be enabling Phriction next?
 
 Please turn it off.

 I briefly played around with Conpherence yesterday. I'm not sure I'd call
 it chat software and I'm not sure it's intended as such. It felt like
 forum software, from what I can tell.

 Initial pain points/oddities:

 * the conversations/threads don't auto-refresh
 * every message triggers a separate e-mail notification by default
 * messages can include fancier formatting, but it wasn't apparent how to
   preview a message before sending

 I'm inclined to agree that e-mail and IRC (and Phabricator's Maniphest
 with its quoting functionality and the wikis and the mailing lists and...)
 are sufficient for Wikimedia development. That said, I can understand the
 view of this being just another tool and, y'know, if you don't like it,
 don't use it and all that. I've re-opened the discussion at
 https://phabricator.wikimedia.org/T91392 as I think whether we enable
 Conpherence needs further thought and consideration.

 MZMcBride

 P.S. I'm also lightly reminded of Zawinski's law about every program
 expanding in size until it includes e-mail. :-)



 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Hi-DPI/Retina display density bracketing for $.devicePixelRatio()?

2015-05-06 Thread Brion Vibber
On Wed, May 6, 2015 at 2:29 AM, Jon Robson jdlrob...@gmail.com wrote:

 As stated on the bug I'd like us to get to a point where we don't have to
 think about this. Ideally a JavaScript dev should be able to create an oojs
 ui image element that is compatible with this. A server side function
 should also exist for creating this.


Ooh sounds like now I have a project. :D


 On 6 May 2015 6:57 am, Prateek Saxena psax...@wikimedia.org wrote:

  On Tue, May 5, 2015 at 3:20 AM, Brion Vibber bvib...@wikimedia.org
  wrote:
   Do folks have any preference for whether I should add that as a
 separate
   function like $.bracketedDevicePixelRatio() or just directly bracket
 the
   output of the $.devicePixelRatio wrapper function?
 
  $.bracketedDevicePixelRatio() as a separate function, please :)
 
  Even though most uses of $.devicePixelRatio() are to get thumbnail
  sizes (as you noted), I don't think we should change the existing
  functionality. Adding a separate method seems easy enough [1] and
  won't break cases where its being used for UI calculations.


Excellent...

-- brion


 
  —prtksxna
 
  [1] as I can see in https://gerrit.wikimedia.org/r/#/c/208820/
 
  ___
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org
  https://lists.wikimedia.org/mailman/listinfo/wikitech-l
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Hi-DPI/Retina display density bracketing for $.devicePixelRatio()?

2015-05-06 Thread Jon Robson
As stated on the bug I'd like us to get to a point where we don't have to
think about this. Ideally a JavaScript dev should be able to create an oojs
ui image element that is compatible with this. A server side function
should also exist for creating this.
On 6 May 2015 6:57 am, Prateek Saxena psax...@wikimedia.org wrote:

 On Tue, May 5, 2015 at 3:20 AM, Brion Vibber bvib...@wikimedia.org
 wrote:
  Do folks have any preference for whether I should add that as a separate
  function like $.bracketedDevicePixelRatio() or just directly bracket the
  output of the $.devicePixelRatio wrapper function?

 $.bracketedDevicePixelRatio() as a separate function, please :)

 Even though most uses of $.devicePixelRatio() are to get thumbnail
 sizes (as you noted), I don't think we should change the existing
 functionality. Adding a separate method seems easy enough [1] and
 won't break cases where its being used for UI calculations.

 —prtksxna

 [1] as I can see in https://gerrit.wikimedia.org/r/#/c/208820/

 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] iconv/mb_convert expert needed to advise on a patch for T39665

2015-05-06 Thread Stas Malyshev
Hi!

Don't have a good solution, but some ideas:

1. There's http://php.net/manual/en/class.uconverter.php which uses ICU
convertor. It can recognize tons of charsets/encodings
(http://site.icu-project.org/charts/charset) and can filter out bad
characters, though the way to achieve it may be a bit tricky. E.g.:

?php
class MyConverter extends UConverter {
function toUCallback( $reason ,  $source ,  $codeUnits ,  $error) {
$error = 0;
return null;
}
}
$c = new MyConverter(UTF-8, utf-8);
var_dump($c-convert(aa\xC3\xC3\xC3\xB8aa));

(there might be a better way, it's just quick-n-dirty example). Con:
while it's supported by hhvm, it's PHP 5.5+. Can be backported probably
quite easily.

2. recode - http://php.net/manual/en/ref.recode.php.
This:
var_dump( recode(UTF-8..UTF-16,UTF16..UTF-8, aa\xC3\xC3\xC3\xB8aa) );
seems to work fine. Not sure how is recode support for hhvm.

3. Patch libmbfl to add more aliases and missing encodings. Shouldn't be
very hard though I'm not sure what is the policy about patching PHP/HHVM
here.

4. Implement ezy...@php.net's suggestion at working around the glibs
mess by adopting code from
http://code.woboq.org/userspace/glibc/iconv/iconv_prog.c.html. Again,
that would require custom patch for PHP, not sure about hhvm.


-- 
Stas Malyshev
smalys...@wikimedia.org

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GRAPH extension is now live everywhere!

2015-05-06 Thread Jon Robson
I think this is great but I'm still super super concerned about the support
for Embedded directly with graph. I'm concerned as if used this way we
risk making wikitext even more like code and more difficult for others to
edit. Also having it inside the page makes it really difficult to
extract/encourage remixing of the data...

On Wed, May 6, 2015 at 4:32 AM, Brian Wolff bawo...@gmail.com wrote:

 On 5/5/15, Yuri Astrakhan yastrak...@wikimedia.org wrote:
  Starting today, editors can use *graph* tag to include complex graphs
 and
  maps inside articles.
 
  *Demo:* https://www.mediawiki.org/wiki/Extension:Graph/Demo
  *Vega's demo:*
 http://trifacta.github.io/vega/editor/?spec=scatter_matrix
  *Extension info:* https://www.mediawiki.org/wiki/Extension:Graph
  *Vega's docs:* https://github.com/trifacta/vega/wiki
  *Bug reports:* https://phabricator.wikimedia.org/ - project tag #graph
 
  Graph tag support template parameter expansion. There is also a Graphoid
  service to convert graphs into images. Currently, Graphoid is used in
 case
  the browser does not support modern JavaScript, but I plan to use it for
  all anonymous users - downloading large JS code needed to render graphs
 is
  significantly slower than showing an image.
 
  Potential future growth (developers needed!):
  * Documentation and better tutorials
  * Visualize as you type - show changes in graph while editing its code
  * Visual Editor's plugin
  * Animation https://github.com/trifacta/vega/wiki/Interaction-Scenarios
 
 
  Project history: Exactly one year ago, Dan Andreescu (milimetric) and Jon
  Robson demoed Vega visualization grammar 
 https://trifacta.github.io/vega/
  usage in MediaWiki. The project stayed dormant for almost half a year,
  until Zero team decided it was a good solution to do on-wiki graphs. The
  project was rewritten, and gained many new features, such as template
  parameters. Yet, doing graphs just for Zero portal seemed silly. Wider
  audience meant that we now had to support older browsers, thus Graphoid
  service was born.
 
  This project could not have happened without the help from Dan Andreescu,
  Brion Vibber, Timo Tijhof, Chris Steipp, Max Semenik,  Marko Obrovac,
  Alexandros Kosiaris, Jon Robson, Gabriel Wicke, and others who have
 helped
  me develop,  test, instrument, and deploy Graph extension and Graphoid
  service. I also would like to thank the Vega team for making this amazing
  library.
 
  --Yurik
  ___
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org
  https://lists.wikimedia.org/mailman/listinfo/wikitech-l


 Hmm cool.

 One of the interesting things, is you can use the API as a data
 source. For example, here is a pie graph of how images on commons
 needing categories are divided up

 https://commons.wikimedia.org/w/index.php?title=Commons:Sandboxoldid=159978060
 (One could even make that more general and have a template, which
 given a cat name, would give a pie graph of how the subcategories are
 divided in terms of number).

 --bawolff

 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jon Robson
* http://jonrobson.me.uk
* https://www.facebook.com/jonrobson
* @rakugojon
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GRAPH extension is now live everywhere!

2015-05-06 Thread David Gerard
Is there a facility to use this in VE?

On 6 May 2015 at 12:25, Jon Robson jdlrob...@gmail.com wrote:
 I think this is great but I'm still super super concerned about the support
 for Embedded directly with graph. I'm concerned as if used this way we
 risk making wikitext even more like code and more difficult for others to
 edit. Also having it inside the page makes it really difficult to
 extract/encourage remixing of the data...

 On Wed, May 6, 2015 at 4:32 AM, Brian Wolff bawo...@gmail.com wrote:

 On 5/5/15, Yuri Astrakhan yastrak...@wikimedia.org wrote:
  Starting today, editors can use *graph* tag to include complex graphs
 and
  maps inside articles.
 
  *Demo:* https://www.mediawiki.org/wiki/Extension:Graph/Demo
  *Vega's demo:*
 http://trifacta.github.io/vega/editor/?spec=scatter_matrix
  *Extension info:* https://www.mediawiki.org/wiki/Extension:Graph
  *Vega's docs:* https://github.com/trifacta/vega/wiki
  *Bug reports:* https://phabricator.wikimedia.org/ - project tag #graph
 
  Graph tag support template parameter expansion. There is also a Graphoid
  service to convert graphs into images. Currently, Graphoid is used in
 case
  the browser does not support modern JavaScript, but I plan to use it for
  all anonymous users - downloading large JS code needed to render graphs
 is
  significantly slower than showing an image.
 
  Potential future growth (developers needed!):
  * Documentation and better tutorials
  * Visualize as you type - show changes in graph while editing its code
  * Visual Editor's plugin
  * Animation https://github.com/trifacta/vega/wiki/Interaction-Scenarios
 
 
  Project history: Exactly one year ago, Dan Andreescu (milimetric) and Jon
  Robson demoed Vega visualization grammar 
 https://trifacta.github.io/vega/
  usage in MediaWiki. The project stayed dormant for almost half a year,
  until Zero team decided it was a good solution to do on-wiki graphs. The
  project was rewritten, and gained many new features, such as template
  parameters. Yet, doing graphs just for Zero portal seemed silly. Wider
  audience meant that we now had to support older browsers, thus Graphoid
  service was born.
 
  This project could not have happened without the help from Dan Andreescu,
  Brion Vibber, Timo Tijhof, Chris Steipp, Max Semenik,  Marko Obrovac,
  Alexandros Kosiaris, Jon Robson, Gabriel Wicke, and others who have
 helped
  me develop,  test, instrument, and deploy Graph extension and Graphoid
  service. I also would like to thank the Vega team for making this amazing
  library.
 
  --Yurik
  ___
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org
  https://lists.wikimedia.org/mailman/listinfo/wikitech-l


 Hmm cool.

 One of the interesting things, is you can use the API as a data
 source. For example, here is a pie graph of how images on commons
 needing categories are divided up

 https://commons.wikimedia.org/w/index.php?title=Commons:Sandboxoldid=159978060
 (One could even make that more general and have a template, which
 given a cat name, would give a pie graph of how the subcategories are
 divided in terms of number).

 --bawolff

 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




 --
 Jon Robson
 * http://jonrobson.me.uk
 * https://www.facebook.com/jonrobson
 * @rakugojon
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GRAPH extension is now live everywhere!

2015-05-06 Thread Yuri Astrakhan
Jon, graph is designed to support template parameter expansions, and I
found most convenient to place each graph into a separate template page.

David, re VE - https://phabricator.wikimedia.org/T93585

On Wed, May 6, 2015 at 2:27 PM, David Gerard dger...@gmail.com wrote:

 Is there a facility to use this in VE?

 On 6 May 2015 at 12:25, Jon Robson jdlrob...@gmail.com wrote:
  I think this is great but I'm still super super concerned about the
 support
  for Embedded directly with graph. I'm concerned as if used this way
 we
  risk making wikitext even more like code and more difficult for others to
  edit. Also having it inside the page makes it really difficult to
  extract/encourage remixing of the data...
 
  On Wed, May 6, 2015 at 4:32 AM, Brian Wolff bawo...@gmail.com wrote:
 
  On 5/5/15, Yuri Astrakhan yastrak...@wikimedia.org wrote:
   Starting today, editors can use *graph* tag to include complex
 graphs
  and
   maps inside articles.
  
   *Demo:* https://www.mediawiki.org/wiki/Extension:Graph/Demo
   *Vega's demo:*
  http://trifacta.github.io/vega/editor/?spec=scatter_matrix
   *Extension info:* https://www.mediawiki.org/wiki/Extension:Graph
   *Vega's docs:* https://github.com/trifacta/vega/wiki
   *Bug reports:* https://phabricator.wikimedia.org/ - project tag
 #graph
  
   Graph tag support template parameter expansion. There is also a
 Graphoid
   service to convert graphs into images. Currently, Graphoid is used in
  case
   the browser does not support modern JavaScript, but I plan to use it
 for
   all anonymous users - downloading large JS code needed to render
 graphs
  is
   significantly slower than showing an image.
  
   Potential future growth (developers needed!):
   * Documentation and better tutorials
   * Visualize as you type - show changes in graph while editing its code
   * Visual Editor's plugin
   * Animation 
 https://github.com/trifacta/vega/wiki/Interaction-Scenarios
  
  
   Project history: Exactly one year ago, Dan Andreescu (milimetric) and
 Jon
   Robson demoed Vega visualization grammar 
  https://trifacta.github.io/vega/
   usage in MediaWiki. The project stayed dormant for almost half a year,
   until Zero team decided it was a good solution to do on-wiki graphs.
 The
   project was rewritten, and gained many new features, such as template
   parameters. Yet, doing graphs just for Zero portal seemed silly. Wider
   audience meant that we now had to support older browsers, thus
 Graphoid
   service was born.
  
   This project could not have happened without the help from Dan
 Andreescu,
   Brion Vibber, Timo Tijhof, Chris Steipp, Max Semenik,  Marko Obrovac,
   Alexandros Kosiaris, Jon Robson, Gabriel Wicke, and others who have
  helped
   me develop,  test, instrument, and deploy Graph extension and Graphoid
   service. I also would like to thank the Vega team for making this
 amazing
   library.
  
   --Yurik
   ___
   Wikitech-l mailing list
   Wikitech-l@lists.wikimedia.org
   https://lists.wikimedia.org/mailman/listinfo/wikitech-l
 
 
  Hmm cool.
 
  One of the interesting things, is you can use the API as a data
  source. For example, here is a pie graph of how images on commons
  needing categories are divided up
 
 
 https://commons.wikimedia.org/w/index.php?title=Commons:Sandboxoldid=159978060
  (One could even make that more general and have a template, which
  given a cat name, would give a pie graph of how the subcategories are
  divided in terms of number).
 
  --bawolff
 
  ___
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org
  https://lists.wikimedia.org/mailman/listinfo/wikitech-l
 
 
 
 
  --
  Jon Robson
  * http://jonrobson.me.uk
  * https://www.facebook.com/jonrobson
  * @rakugojon
  ___
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org
  https://lists.wikimedia.org/mailman/listinfo/wikitech-l

 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Conpherence enabled? (was [Wikitech-ambassadors] Tech newsletter (2015, week 19))

2015-05-06 Thread Quim Gil
Hi, I think Conpherence helps onboarding new contributors with profiles
different to the rather homogeneous profile predominant in our technical
communities (and well represented by the sample of people active in this
thread and in the related Phabricator task -- myself included).

I invite you to go beyond the 'yet another tool' initial reaction and think
of the reasons beneath its election. It's an interesting and rather deep
discussion about the usefulness of cozy private spaces for a diverse range
of newcomers while they gain the skills and confidence to dive into our
public channels. More on this at
https://phabricator.wikimedia.org/T91392#1264689

On Wed, May 6, 2015 at 3:02 AM, Alex Monk kren...@gmail.com wrote:

 How do I prevent people from contacting me via this?


As of today, there is no way, just like there is no (sane) way of
preventing unknown people from contacting you via email or IRC. You can
point them to the right channels, point them to
https://www.mediawiki.org/wiki/Phabricator/Help#Appropriate_uses_of_Conpherence
, or simply ignore them.

If someone wants to create a task for this request, we can discuss it in
more detail there. I expect it to be less simple than it sounds, though.
Removing a Send Message button from a user profile is simple, but things
get more complicated when thinking of the details.


On 6 May 2015 at 03:33, MZMcBride z...@mzmcbride.com wrote:

  Initial pain points/oddities:
 
  * the conversations/threads don't auto-refresh


In theory they should, but there are some bugs identified upstream, and
maybe our own instance needs fine-tuning. See
https://phabricator.wikimedia.org/T97650


  * every message triggers a separate e-mail notification by default


You can set web notifications only --
https://phabricator.wikimedia.org/settings/panel/conpherence/


  * messages can include fancier formatting, but it wasn't apparent how to
preview a message before sending


Yes, this is a feature missing. I discussed it with the Phabricator
maintainers months ago and they said that it was just legacy (Conpherence
being developed before the preview feature). I have created
https://secure.phabricator.com/T8088
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] RFC meeting this week

2015-05-06 Thread Tim Starling
In the next RFC meeting, we will discuss the following RFCs:

* Request timeouts and retries
https://phabricator.wikimedia.org/T97204

* Re-evaluate varnish-level request-restart behavior on 5xx
https://phabricator.wikimedia.org/T97206

The meeting will be on the IRC channel #wikimedia-office on
chat.freenode.net at the following time:

* UTC: Wednesday 21:00
* US PDT: Wednesday 14:00
* Europe CEST: Wednesday 23:00
* Australia AEST: Thursday 07:00

-- Tim Starling



___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Pywikipedia-l] Connecting to github community

2015-05-06 Thread Amir Ladsgroup
Based on talks in here I think it would be cool if we continue to work on
this but more in a phabricator way.

On Wed, May 6, 2015 at 1:38 AM Yuvi Panda yuvipa...@gmail.com wrote:

 Hello!

 https://github.com/wikimedia/labs-tools-SuchABot did this and more -
 it was a full fledged gerrit - github bridge, relaying commits from
 github - gerrit and comments from github to gerrit and vice versa. I
 used it successfully for a while
 (
 https://github.com/wikimedia/mediawiki-extensions-UploadWizard/pull/3#issuecomment-21207708
 and
 https://github.com/wikimedia/mediawiki-extensions-UploadWizard/pulls?q=is%3Apr+is%3Aclosed
 for list of pull requests merged via that) and works quite nicely.

 I stopped working on it because I got a bit bored, and nobody except
 me seemed to be using it :P Feel free to re-use / ressurect the code!

 Thanks for building this :D

 --
 Yuvi Panda T
 http://yuvi.in/blog

 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Connecting to github community

2015-05-06 Thread Nikolas Everett
On Tue, May 5, 2015 at 4:28 PM, Bryan Davis bd...@wikimedia.org wrote:

 Facebook uses a bot to transfer pull requests from GitHub [5] to their
 Phabricator instance [6] for HHVM.


I gotta say I wasn't thrilled with it. It just felt all disjointed a
broken. As much as I like the idea of lowering the barrier to entry it felt
like a bait and switch. I saw github issues and sent a pull request and was
bounced to some other system where I needed yet another account. At least
with our setup its clear up front what you are getting into.

A two way synch bot like that spoke as the proper user would be pretty
awesome.

Nik
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GRAPH extension is now live everywhere!

2015-05-06 Thread Marielle Volz
Right now you can only manually edit the JSON blob in VE (as in wikitext),
but we have a Google Summer of Code intern working on VE support this
summer!

https://phabricator.wikimedia.org/tag/mediawiki-extensions-graph-ve/
On May 6, 2015 12:28 PM, David Gerard dger...@gmail.com wrote:

 Is there a facility to use this in VE?

 On 6 May 2015 at 12:25, Jon Robson jdlrob...@gmail.com wrote:
  I think this is great but I'm still super super concerned about the
 support
  for Embedded directly with graph. I'm concerned as if used this way
 we
  risk making wikitext even more like code and more difficult for others to
  edit. Also having it inside the page makes it really difficult to
  extract/encourage remixing of the data...
 
  On Wed, May 6, 2015 at 4:32 AM, Brian Wolff bawo...@gmail.com wrote:
 
  On 5/5/15, Yuri Astrakhan yastrak...@wikimedia.org wrote:
   Starting today, editors can use *graph* tag to include complex
 graphs
  and
   maps inside articles.
  
   *Demo:* https://www.mediawiki.org/wiki/Extension:Graph/Demo
   *Vega's demo:*
  http://trifacta.github.io/vega/editor/?spec=scatter_matrix
   *Extension info:* https://www.mediawiki.org/wiki/Extension:Graph
   *Vega's docs:* https://github.com/trifacta/vega/wiki
   *Bug reports:* https://phabricator.wikimedia.org/ - project tag
 #graph
  
   Graph tag support template parameter expansion. There is also a
 Graphoid
   service to convert graphs into images. Currently, Graphoid is used in
  case
   the browser does not support modern JavaScript, but I plan to use it
 for
   all anonymous users - downloading large JS code needed to render
 graphs
  is
   significantly slower than showing an image.
  
   Potential future growth (developers needed!):
   * Documentation and better tutorials
   * Visualize as you type - show changes in graph while editing its code
   * Visual Editor's plugin
   * Animation 
 https://github.com/trifacta/vega/wiki/Interaction-Scenarios
  
  
   Project history: Exactly one year ago, Dan Andreescu (milimetric) and
 Jon
   Robson demoed Vega visualization grammar 
  https://trifacta.github.io/vega/
   usage in MediaWiki. The project stayed dormant for almost half a year,
   until Zero team decided it was a good solution to do on-wiki graphs.
 The
   project was rewritten, and gained many new features, such as template
   parameters. Yet, doing graphs just for Zero portal seemed silly. Wider
   audience meant that we now had to support older browsers, thus
 Graphoid
   service was born.
  
   This project could not have happened without the help from Dan
 Andreescu,
   Brion Vibber, Timo Tijhof, Chris Steipp, Max Semenik,  Marko Obrovac,
   Alexandros Kosiaris, Jon Robson, Gabriel Wicke, and others who have
  helped
   me develop,  test, instrument, and deploy Graph extension and Graphoid
   service. I also would like to thank the Vega team for making this
 amazing
   library.
  
   --Yurik
   ___
   Wikitech-l mailing list
   Wikitech-l@lists.wikimedia.org
   https://lists.wikimedia.org/mailman/listinfo/wikitech-l
 
 
  Hmm cool.
 
  One of the interesting things, is you can use the API as a data
  source. For example, here is a pie graph of how images on commons
  needing categories are divided up
 
 
 https://commons.wikimedia.org/w/index.php?title=Commons:Sandboxoldid=159978060
  (One could even make that more general and have a template, which
  given a cat name, would give a pie graph of how the subcategories are
  divided in terms of number).
 
  --bawolff
 
  ___
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org
  https://lists.wikimedia.org/mailman/listinfo/wikitech-l
 
 
 
 
  --
  Jon Robson
  * http://jonrobson.me.uk
  * https://www.facebook.com/jonrobson
  * @rakugojon
  ___
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org
  https://lists.wikimedia.org/mailman/listinfo/wikitech-l

 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] 1.25.0-rc.0 now available

2015-05-06 Thread Chad
All,

I'm proud to announce 1.25.0-rc.0, the first release candidate in the
1.25.0 series. The tarball links for it are below, the tag is in Git[0].

Please note that this is a release candidate and not a final release, there
may still be outstanding issues you might encounter.

Developers: please have a look at the release and make sure it's working,
especially with your extensions. The REL1_25 branches for core and
extensions are where you want any patches to be included.

Open tasks with the 1.25 release project associated:
https://phabricator.wikimedia.org/maniphest/query/AcRAxmlMljqe/#R

**

Download:
https://releases.wikimedia.org/mediawiki/1.25/mediawiki-core-1.25.0-rc.0.tar.gz
http://download.wikimedia.org/mediawiki/1.25/mediawiki-1.25.0-rc.0.tar.gz

GPG signatures:
http://download.wikimedia.org/mediawiki/1.25/mediawiki-core-1.25.0-rc.0.tar.gz.sig
http://download.wikimedia.org/mediawiki/1.25/mediawiki-1.25.0-rc.0.tar.gz.sig

Public keys:
https://www.mediawiki.org/keys/keys.html

-Chad

[0] I messed up tagging, so if you fetched core during the hour-ish
that I had the wrong tag, you may need to delete the local tag prior
to fetching. 4badf14 is the correct sha1.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] 2015-05-06 Scrum of Scrum notes

2015-05-06 Thread Grace Gellerman
https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-05-06
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GRAPH extension is now live everywhere!

2015-05-06 Thread Yuri Astrakhan
Sorry, I meant do NOT save, when trying dynamic graph preview.

If anyone is interested, or as a student project - a simple sandbox
implementation task: https://phabricator.wikimedia.org/T98312

On Wed, May 6, 2015 at 10:28 PM, Yuri Astrakhan yastrak...@wikimedia.org
wrote:

 You currently can use dynamic graph-as-you-type in mediawiki.org for
 Graph testing:
 * navigate to any Graph namespace graph, e.g.
 https://www.mediawiki.org/wiki/Graph:Sample
 * Go to edit source
 * Click Preview
 Now any change you make to the definition is dynamically reflected in the
 graph.  Please do save. I would love for this to eventually be done in the
 VE.

 Eugene, this is an excellent idea, but graphs are no different from other
 templates. I think this should be solved for all templates, to allow
 template sharing between projects.


 On Wed, May 6, 2015 at 8:24 PM, Eugene Zelenko eugene.zele...@gmail.com
 wrote:

 Hi, Yuri!

 I think will be reasonable to allow transclusion of graphs (or their
 parts, for example without text labels) from Commons. This will allow
 to share graphs between projects.

 Eugene.

 On Wed, May 6, 2015 at 5:51 AM, Yuri Astrakhan yastrak...@wikimedia.org
 wrote:
  Jon, graph is designed to support template parameter expansions, and I
  found most convenient to place each graph into a separate template page.
 
  David, re VE - https://phabricator.wikimedia.org/T93585
 
  On Wed, May 6, 2015 at 2:27 PM, David Gerard dger...@gmail.com wrote:
 
  Is there a facility to use this in VE?
 
  On 6 May 2015 at 12:25, Jon Robson jdlrob...@gmail.com wrote:
   I think this is great but I'm still super super concerned about the
  support
   for Embedded directly with graph. I'm concerned as if used this
 way
  we
   risk making wikitext even more like code and more difficult for
 others to
   edit. Also having it inside the page makes it really difficult to
   extract/encourage remixing of the data...
  
   On Wed, May 6, 2015 at 4:32 AM, Brian Wolff bawo...@gmail.com
 wrote:
  
   On 5/5/15, Yuri Astrakhan yastrak...@wikimedia.org wrote:
Starting today, editors can use *graph* tag to include complex
  graphs
   and
maps inside articles.
   
*Demo:* https://www.mediawiki.org/wiki/Extension:Graph/Demo
*Vega's demo:*
   http://trifacta.github.io/vega/editor/?spec=scatter_matrix
*Extension info:* https://www.mediawiki.org/wiki/Extension:Graph
*Vega's docs:* https://github.com/trifacta/vega/wiki
*Bug reports:* https://phabricator.wikimedia.org/ - project tag
  #graph
   
Graph tag support template parameter expansion. There is also a
  Graphoid
service to convert graphs into images. Currently, Graphoid is
 used in
   case
the browser does not support modern JavaScript, but I plan to use
 it
  for
all anonymous users - downloading large JS code needed to render
  graphs
   is
significantly slower than showing an image.
   
Potential future growth (developers needed!):
* Documentation and better tutorials
* Visualize as you type - show changes in graph while editing its
 code
* Visual Editor's plugin
* Animation 
  https://github.com/trifacta/vega/wiki/Interaction-Scenarios
   
   
Project history: Exactly one year ago, Dan Andreescu (milimetric)
 and
  Jon
Robson demoed Vega visualization grammar 
   https://trifacta.github.io/vega/
usage in MediaWiki. The project stayed dormant for almost half a
 year,
until Zero team decided it was a good solution to do on-wiki
 graphs.
  The
project was rewritten, and gained many new features, such as
 template
parameters. Yet, doing graphs just for Zero portal seemed silly.
 Wider
audience meant that we now had to support older browsers, thus
  Graphoid
service was born.
   
This project could not have happened without the help from Dan
  Andreescu,
Brion Vibber, Timo Tijhof, Chris Steipp, Max Semenik,  Marko
 Obrovac,
Alexandros Kosiaris, Jon Robson, Gabriel Wicke, and others who
 have
   helped
me develop,  test, instrument, and deploy Graph extension and
 Graphoid
service. I also would like to thank the Vega team for making this
  amazing
library.
   
--Yurik
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
  
  
   Hmm cool.
  
   One of the interesting things, is you can use the API as a data
   source. For example, here is a pie graph of how images on commons
   needing categories are divided up
  
  
 
 https://commons.wikimedia.org/w/index.php?title=Commons:Sandboxoldid=159978060
   (One could even make that more general and have a template, which
   given a cat name, would give a pie graph of how the subcategories
 are
   divided in terms of number).
  
   --bawolff
  
   ___
   Wikitech-l mailing list
   Wikitech-l@lists.wikimedia.org
   

Re: [Wikitech-l] jQuery UI, opensearch API, categories and autocompletion -- oh my!

2015-05-06 Thread Jon Robson
Florian set up something similar to this that you may be interested in:
https://en.m.wikipedia.org/wiki/Barack%20Obama?mobileaction=alpha#/categories/add

On Wed, May 6, 2015 at 6:31 PM, Jack Phoenix j...@countervandalism.net
wrote:

 Hi all,

 I'm trying to build an autocompletion thingy that suggests categories based
 on user input using the opensearch API [1]. It sounds like a relatively
 simple thing and I was able to hack something that somewhat works in a few
 minutes...there's just one gotcha: this thing is supposed to suggest
 nothing but categories, so I don't need nor want the Category: label (or
 its localized equivalent) to show up.
 I've been able to manipulate the result set so that whenever the user
 clicks on a suggestion, whatever gets inserted into the input is
 correct...but what is *displayed* to the user still includes the
 Category: part in it. The various ways how I've been able to remove the
 Category: part from the value have been more or less hacky and
 inefficient.

 What am I doing wrong here [2]? How can I totally strip out the Category:
 part and pretend it doesn't exist and never did?

 [1] https://www.mediawiki.org/wiki/API:Opensearch
 [2] https://www.mediawiki.org/wiki/User:Jack_Phoenix/AutocompleteTest

 Thanks and regards,
 --
 Jack Phoenix
 MediaWiki developer
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jon Robson
* http://jonrobson.me.uk
* https://www.facebook.com/jonrobson
* @rakugojon
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] jQuery UI, opensearch API, categories and autocompletion -- oh my!

2015-05-06 Thread Brad Jorsch (Anomie)
On Wed, May 6, 2015 at 1:31 PM, Jack Phoenix j...@countervandalism.net
wrote:

 I'm trying to build an autocompletion thingy that suggests categories based
 on user input using the opensearch API [1].


Sounds like https://en.wikipedia.org/wiki/Wikipedia:HotCat


 How can I totally strip out the Category:
 part and pretend it doesn't exist and never did?


Hit api.php?action=querymeta=siteinfosiprop=namespaces to get the
localized name of the Category namespace. Or you should be safe just
removing everything up to the first colon.


-- 
Brad Jorsch (Anomie)
Software Engineer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GRAPH extension is now live everywhere!

2015-05-06 Thread Yuri Astrakhan
You currently can use dynamic graph-as-you-type in mediawiki.org for
Graph testing:
* navigate to any Graph namespace graph, e.g.
https://www.mediawiki.org/wiki/Graph:Sample
* Go to edit source
* Click Preview
Now any change you make to the definition is dynamically reflected in the
graph.  Please do save. I would love for this to eventually be done in the
VE.

Eugene, this is an excellent idea, but graphs are no different from other
templates. I think this should be solved for all templates, to allow
template sharing between projects.


On Wed, May 6, 2015 at 8:24 PM, Eugene Zelenko eugene.zele...@gmail.com
wrote:

 Hi, Yuri!

 I think will be reasonable to allow transclusion of graphs (or their
 parts, for example without text labels) from Commons. This will allow
 to share graphs between projects.

 Eugene.

 On Wed, May 6, 2015 at 5:51 AM, Yuri Astrakhan yastrak...@wikimedia.org
 wrote:
  Jon, graph is designed to support template parameter expansions, and I
  found most convenient to place each graph into a separate template page.
 
  David, re VE - https://phabricator.wikimedia.org/T93585
 
  On Wed, May 6, 2015 at 2:27 PM, David Gerard dger...@gmail.com wrote:
 
  Is there a facility to use this in VE?
 
  On 6 May 2015 at 12:25, Jon Robson jdlrob...@gmail.com wrote:
   I think this is great but I'm still super super concerned about the
  support
   for Embedded directly with graph. I'm concerned as if used this
 way
  we
   risk making wikitext even more like code and more difficult for
 others to
   edit. Also having it inside the page makes it really difficult to
   extract/encourage remixing of the data...
  
   On Wed, May 6, 2015 at 4:32 AM, Brian Wolff bawo...@gmail.com
 wrote:
  
   On 5/5/15, Yuri Astrakhan yastrak...@wikimedia.org wrote:
Starting today, editors can use *graph* tag to include complex
  graphs
   and
maps inside articles.
   
*Demo:* https://www.mediawiki.org/wiki/Extension:Graph/Demo
*Vega's demo:*
   http://trifacta.github.io/vega/editor/?spec=scatter_matrix
*Extension info:* https://www.mediawiki.org/wiki/Extension:Graph
*Vega's docs:* https://github.com/trifacta/vega/wiki
*Bug reports:* https://phabricator.wikimedia.org/ - project tag
  #graph
   
Graph tag support template parameter expansion. There is also a
  Graphoid
service to convert graphs into images. Currently, Graphoid is used
 in
   case
the browser does not support modern JavaScript, but I plan to use
 it
  for
all anonymous users - downloading large JS code needed to render
  graphs
   is
significantly slower than showing an image.
   
Potential future growth (developers needed!):
* Documentation and better tutorials
* Visualize as you type - show changes in graph while editing its
 code
* Visual Editor's plugin
* Animation 
  https://github.com/trifacta/vega/wiki/Interaction-Scenarios
   
   
Project history: Exactly one year ago, Dan Andreescu (milimetric)
 and
  Jon
Robson demoed Vega visualization grammar 
   https://trifacta.github.io/vega/
usage in MediaWiki. The project stayed dormant for almost half a
 year,
until Zero team decided it was a good solution to do on-wiki
 graphs.
  The
project was rewritten, and gained many new features, such as
 template
parameters. Yet, doing graphs just for Zero portal seemed silly.
 Wider
audience meant that we now had to support older browsers, thus
  Graphoid
service was born.
   
This project could not have happened without the help from Dan
  Andreescu,
Brion Vibber, Timo Tijhof, Chris Steipp, Max Semenik,  Marko
 Obrovac,
Alexandros Kosiaris, Jon Robson, Gabriel Wicke, and others who have
   helped
me develop,  test, instrument, and deploy Graph extension and
 Graphoid
service. I also would like to thank the Vega team for making this
  amazing
library.
   
--Yurik
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
  
  
   Hmm cool.
  
   One of the interesting things, is you can use the API as a data
   source. For example, here is a pie graph of how images on commons
   needing categories are divided up
  
  
 
 https://commons.wikimedia.org/w/index.php?title=Commons:Sandboxoldid=159978060
   (One could even make that more general and have a template, which
   given a cat name, would give a pie graph of how the subcategories are
   divided in terms of number).
  
   --bawolff
  
   ___
   Wikitech-l mailing list
   Wikitech-l@lists.wikimedia.org
   https://lists.wikimedia.org/mailman/listinfo/wikitech-l
  
  
  
  
   --
   Jon Robson
   * http://jonrobson.me.uk
   * https://www.facebook.com/jonrobson
   * @rakugojon
   ___
   Wikitech-l mailing list
   Wikitech-l@lists.wikimedia.org
   

Re: [Wikitech-l] jQuery UI, opensearch API, categories and autocompletion -- oh my!

2015-05-06 Thread Jack Phoenix
On Wed, May 6, 2015 at 9:06 PM, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:

 On Wed, May 6, 2015 at 1:31 PM, Jack Phoenix j...@countervandalism.net
 wrote:

  I'm trying to build an autocompletion thingy that suggests categories
 based
  on user input using the opensearch API [1].


 Sounds like https://en.wikipedia.org/wiki/Wikipedia:HotCat


Something like that, although not quite complicated. HotCat's current
version is ~3k lines of code, my JS is ~40 lines.


 How can I totally strip out the Category:
  part and pretend it doesn't exist and never did?
 

 Hit api.php?action=querymeta=siteinfosiprop=namespaces to get the
 localized name of the Category namespace. Or you should be safe just
 removing everything up to the first colon.


Yeah, probably better to avoid the extra HTTP request.

In any case, I managed to solve my issue for the time being, or so I
think. Defining a response callback and fiddling with the API-supplied
data there seems to do the trick:
https://www.mediawiki.org/w/index.php?title=User%3AJack_Phoenix%2FAutocompleteTesttype=revisiondiff=1644379oldid=1644324
It does still feel a tad bit hacky to me, so if some JavaScript guru knows
of the proper way to do this, feel free to let me know! But at least now I
can safely throw out some old and icky code in favor of this new code. :)


Thanks and regards,
--
Jack Phoenix
MediaWiki developer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GRAPH extension is now live everywhere!

2015-05-06 Thread Jonathan Morgan
This is wicked exciting. Thanks to everyone involved!

- J

On Tue, May 5, 2015 at 1:24 PM, Yuri Astrakhan yastrak...@wikimedia.org
wrote:

 Starting today, editors can use *graph* tag to include complex graphs and
 maps inside articles.

 *Demo:* https://www.mediawiki.org/wiki/Extension:Graph/Demo
 *Vega's demo:* http://trifacta.github.io/vega/editor/?spec=scatter_matrix
 *Extension info:* https://www.mediawiki.org/wiki/Extension:Graph
 *Vega's docs:* https://github.com/trifacta/vega/wiki
 *Bug reports:* https://phabricator.wikimedia.org/ - project tag #graph

 Graph tag support template parameter expansion. There is also a Graphoid
 service to convert graphs into images. Currently, Graphoid is used in case
 the browser does not support modern JavaScript, but I plan to use it for
 all anonymous users - downloading large JS code needed to render graphs is
 significantly slower than showing an image.

 Potential future growth (developers needed!):
 * Documentation and better tutorials
 * Visualize as you type - show changes in graph while editing its code
 * Visual Editor's plugin
 * Animation https://github.com/trifacta/vega/wiki/Interaction-Scenarios

 Project history: Exactly one year ago, Dan Andreescu (milimetric) and Jon
 Robson demoed Vega visualization grammar https://trifacta.github.io/vega/
 
 usage in MediaWiki. The project stayed dormant for almost half a year,
 until Zero team decided it was a good solution to do on-wiki graphs. The
 project was rewritten, and gained many new features, such as template
 parameters. Yet, doing graphs just for Zero portal seemed silly. Wider
 audience meant that we now had to support older browsers, thus Graphoid
 service was born.

 This project could not have happened without the help from Dan Andreescu,
 Brion Vibber, Timo Tijhof, Chris Steipp, Max Semenik,  Marko Obrovac,
 Alexandros Kosiaris, Jon Robson, Gabriel Wicke, and others who have helped
 me develop,  test, instrument, and deploy Graph extension and Graphoid
 service. I also would like to thank the Vega team for making this amazing
 library.

 --Yurik
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jonathan T. Morgan
Community Research Lead
Wikimedia Foundation
User:Jmorgan (WMF) https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)
jmor...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] jQuery UI, opensearch API, categories and autocompletion -- oh my!

2015-05-06 Thread Jack Phoenix
Hi all,

I'm trying to build an autocompletion thingy that suggests categories based
on user input using the opensearch API [1]. It sounds like a relatively
simple thing and I was able to hack something that somewhat works in a few
minutes...there's just one gotcha: this thing is supposed to suggest
nothing but categories, so I don't need nor want the Category: label (or
its localized equivalent) to show up.
I've been able to manipulate the result set so that whenever the user
clicks on a suggestion, whatever gets inserted into the input is
correct...but what is *displayed* to the user still includes the
Category: part in it. The various ways how I've been able to remove the
Category: part from the value have been more or less hacky and
inefficient.

What am I doing wrong here [2]? How can I totally strip out the Category:
part and pretend it doesn't exist and never did?

[1] https://www.mediawiki.org/wiki/API:Opensearch
[2] https://www.mediawiki.org/wiki/User:Jack_Phoenix/AutocompleteTest

Thanks and regards,
--
Jack Phoenix
MediaWiki developer
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GRAPH extension is now live everywhere!

2015-05-06 Thread Eugene Zelenko
Hi, Yuri!

I think will be reasonable to allow transclusion of graphs (or their
parts, for example without text labels) from Commons. This will allow
to share graphs between projects.

Eugene.

On Wed, May 6, 2015 at 5:51 AM, Yuri Astrakhan yastrak...@wikimedia.org wrote:
 Jon, graph is designed to support template parameter expansions, and I
 found most convenient to place each graph into a separate template page.

 David, re VE - https://phabricator.wikimedia.org/T93585

 On Wed, May 6, 2015 at 2:27 PM, David Gerard dger...@gmail.com wrote:

 Is there a facility to use this in VE?

 On 6 May 2015 at 12:25, Jon Robson jdlrob...@gmail.com wrote:
  I think this is great but I'm still super super concerned about the
 support
  for Embedded directly with graph. I'm concerned as if used this way
 we
  risk making wikitext even more like code and more difficult for others to
  edit. Also having it inside the page makes it really difficult to
  extract/encourage remixing of the data...
 
  On Wed, May 6, 2015 at 4:32 AM, Brian Wolff bawo...@gmail.com wrote:
 
  On 5/5/15, Yuri Astrakhan yastrak...@wikimedia.org wrote:
   Starting today, editors can use *graph* tag to include complex
 graphs
  and
   maps inside articles.
  
   *Demo:* https://www.mediawiki.org/wiki/Extension:Graph/Demo
   *Vega's demo:*
  http://trifacta.github.io/vega/editor/?spec=scatter_matrix
   *Extension info:* https://www.mediawiki.org/wiki/Extension:Graph
   *Vega's docs:* https://github.com/trifacta/vega/wiki
   *Bug reports:* https://phabricator.wikimedia.org/ - project tag
 #graph
  
   Graph tag support template parameter expansion. There is also a
 Graphoid
   service to convert graphs into images. Currently, Graphoid is used in
  case
   the browser does not support modern JavaScript, but I plan to use it
 for
   all anonymous users - downloading large JS code needed to render
 graphs
  is
   significantly slower than showing an image.
  
   Potential future growth (developers needed!):
   * Documentation and better tutorials
   * Visualize as you type - show changes in graph while editing its code
   * Visual Editor's plugin
   * Animation 
 https://github.com/trifacta/vega/wiki/Interaction-Scenarios
  
  
   Project history: Exactly one year ago, Dan Andreescu (milimetric) and
 Jon
   Robson demoed Vega visualization grammar 
  https://trifacta.github.io/vega/
   usage in MediaWiki. The project stayed dormant for almost half a year,
   until Zero team decided it was a good solution to do on-wiki graphs.
 The
   project was rewritten, and gained many new features, such as template
   parameters. Yet, doing graphs just for Zero portal seemed silly. Wider
   audience meant that we now had to support older browsers, thus
 Graphoid
   service was born.
  
   This project could not have happened without the help from Dan
 Andreescu,
   Brion Vibber, Timo Tijhof, Chris Steipp, Max Semenik,  Marko Obrovac,
   Alexandros Kosiaris, Jon Robson, Gabriel Wicke, and others who have
  helped
   me develop,  test, instrument, and deploy Graph extension and Graphoid
   service. I also would like to thank the Vega team for making this
 amazing
   library.
  
   --Yurik
   ___
   Wikitech-l mailing list
   Wikitech-l@lists.wikimedia.org
   https://lists.wikimedia.org/mailman/listinfo/wikitech-l
 
 
  Hmm cool.
 
  One of the interesting things, is you can use the API as a data
  source. For example, here is a pie graph of how images on commons
  needing categories are divided up
 
 
 https://commons.wikimedia.org/w/index.php?title=Commons:Sandboxoldid=159978060
  (One could even make that more general and have a template, which
  given a cat name, would give a pie graph of how the subcategories are
  divided in terms of number).
 
  --bawolff
 
  ___
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org
  https://lists.wikimedia.org/mailman/listinfo/wikitech-l
 
 
 
 
  --
  Jon Robson
  * http://jonrobson.me.uk
  * https://www.facebook.com/jonrobson
  * @rakugojon
  ___
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org
  https://lists.wikimedia.org/mailman/listinfo/wikitech-l

 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l

 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] jQuery UI, opensearch API, categories and autocompletion -- oh my!

2015-05-06 Thread Krinkle
 On 6 May 2015, at 20:26, Jack Phoenix j...@countervandalism.net wrote:
 
 On Wed, May 6, 2015 at 9:06 PM, Brad Jorsch (Anomie) bjor...@wikimedia.org
 wrote:
 
 On Wed, May 6, 2015 at 1:31 PM, Jack Phoenix j...@countervandalism.net
 wrote:
 
 How can I totally strip out the Category: [..]
 
 Hit api.php?action=querymeta=siteinfosiprop=namespaces to get the
 localized name of the Category namespace. Or you should be safe just
 removing everything up to the first colon.
 
 
 Yeah, probably better to avoid the extra HTTP request.
 

Namespace information and variants thereof are readily available via mw.config 
wgNamespaceIds.

You can manually remove any values with id 14 (category), or use mw.Title to do 
it for you.

As for the UI library, I'd recommend using the jquery.suggestions module in a 
MediaWiki context. Avoid jQuery UI.

This is already used for page inputs (e.g. search), and user name inputs (e.g. 
Special:Log).

Creating an instance of it for categories should be straight forward.

You can use mediawiki.searchSuggest or mediawiki.userSuggest as starting point:
https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki/mediawiki.userSuggest.js
 
https://github.com/wikimedia/mediawiki/blob/master/resources/src/mediawiki/mediawiki.userSuggest.js

-- Krinkle

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l