303
pages
ALL POSTSOffice Hours - December 10, 2015
<p>Office Hours from December 3 were bumped to December 10, due to scheduling issues.
</p><p>Please feel free to fill in questions below - staff will be around to answer them at 4pm UTC on Thursday.
</p>
(Edited by FishTank)
<p>@FishTank 
I think it would be horribly hilarious, if you were asked to answer questions for the Office Hours, instead.
</p>
I think it would be horribly hilarious, if you were asked to answer questions for the Office Hours, instead.
</p>
(Edited by Fandyllic)
<p>Since I might be able to ask another question for answer tomorrow...
</p><p>Could we get an improved version (doesn't need to be extensively better) of <i>Wikipedia:Comparable Lua functions to wikitext</i> for the Wikia version of Lua?
</p><p>By improvements, I mean some better examples... the one for #switch is pretty bad.
</p>
(Edited by Fandyllic)
<div class="quote"><i>Fandyllic wrote:
Since I might be able to ask another question for answer tomorrow... <p>Could we get an improved version (doesn't need to be extensively better) of <i>Wikipedia:Comparable Lua functions to wikitext</i> for the Wikia version of Lua? </p><p>By improvements, I mean some better examples... the one for #switch is pretty bad. </p> </i></div>
<p>Not sure how that is relevant to portability. You could import that page to dev.wikia, and we can improve any examples you believe are "pretty bad". Also, could you explain how the switch example is pretty bad? </p><p>P.S. There is a somewhat similar page here: </p><p>http://dev.wikia.com/wiki/Lua_templating/Converting_Wikitext_templates </p>
Since I might be able to ask another question for answer tomorrow... <p>Could we get an improved version (doesn't need to be extensively better) of <i>Wikipedia:Comparable Lua functions to wikitext</i> for the Wikia version of Lua? </p><p>By improvements, I mean some better examples... the one for #switch is pretty bad. </p> </i></div>
<p>Not sure how that is relevant to portability. You could import that page to dev.wikia, and we can improve any examples you believe are "pretty bad". Also, could you explain how the switch example is pretty bad? </p><p>P.S. There is a somewhat similar page here: </p><p>http://dev.wikia.com/wiki/Lua_templating/Converting_Wikitext_templates </p>
(Edited by Dessamator)
<p>Okay, maybe just expand the dev page with more examples. The dev page switch example is loads better than the Wikipedia one.
</p><p>As far as I'm concerned, Lua info is about portability until it's obviously not. Does that make sense?
</p>
(Edited by Fandyllic)
<div class="quote"><i>Fandyllic wrote:
Okay, maybe just expand the dev page with more examples. The dev page switch example is loads better than the Wikipedia one.</i></div>
<p>I'm not exactly sure which examples need expanding because that is more like a reference and less of a step by step guide. There are loads of pages documenting lua / scribunto : </p> <p></p><blockquote>As far as I'm concerned, Lua info is about portability until it's obviously not. Does that make sense?</blockquote> <p>While I do generally agree, there are currently 0 portable tools that currently take advantage of lua. </p>
Okay, maybe just expand the dev page with more examples. The dev page switch example is loads better than the Wikipedia one.</i></div>
<p>I'm not exactly sure which examples need expanding because that is more like a reference and less of a step by step guide. There are loads of pages documenting lua / scribunto : </p> <p></p><blockquote>As far as I'm concerned, Lua info is about portability until it's obviously not. Does that make sense?</blockquote> <p>While I do generally agree, there are currently 0 portable tools that currently take advantage of lua. </p>
(Edited by Dessamator)
2
<div class="quote"><i>Customizing different media outputs
Currently, .portable-infobox styling only applies to desktop. How can (or will we be able to) create vibrant experiences for other media (like (but not limited to) mobile) without breaking Portability?</i></div>
<p>Current mobile skin is very minimalistic and, to be frank, very technical. We will be working on defining designs and style guide for mobile skin in 2016. During that process we will be exploring to what degree we want to introduce custom theming. More to come next year! </p>
Currently, .portable-infobox styling only applies to desktop. How can (or will we be able to) create vibrant experiences for other media (like (but not limited to) mobile) without breaking Portability?</i></div>
<p>Current mobile skin is very minimalistic and, to be frank, very technical. We will be working on defining designs and style guide for mobile skin in 2016. During that process we will be exploring to what degree we want to introduce custom theming. More to come next year! </p>
(Edited by Shareif)
2
<div class="quote"><i>Groups
Alright, let's have a go at something that may or may not be easier to answer... Any plans for <group>s within <groups>? I've brought up this idea before on Community Central, but the idea where you can wrap a group within a group, in order to prevent issues where people can't make a whole collapsible section with multiple rows of horizontal <data> tags.</i></div>
<p>That's a tough one. We want to support collapsible, horizontal groups, but on the other hand we do not want to increase complexity by introducing nested groups. When we find solution to it, we will implement it. So, if you have any ideas how to tackle it, please share! Your input is very welcome. </p>
Alright, let's have a go at something that may or may not be easier to answer... Any plans for <group>s within <groups>? I've brought up this idea before on Community Central, but the idea where you can wrap a group within a group, in order to prevent issues where people can't make a whole collapsible section with multiple rows of horizontal <data> tags.</i></div>
<p>That's a tough one. We want to support collapsible, horizontal groups, but on the other hand we do not want to increase complexity by introducing nested groups. When we find solution to it, we will implement it. So, if you have any ideas how to tackle it, please share! Your input is very welcome. </p>
(Edited by Shareif)
0
<div class="quote"><i>Charts
<p>Charts are one of the most used elements in wikia. But most of the implementations are not mobile friendly. Current solutions on Wikia include Extension:Timeline,Module:Chart, and javascript generated charts. Most of these are not portable, but at least Extension:Graph seems to be a more powerful and portable version heavily used by WMF. </p> Any chance of backporting that extension or if that's not possible what tips would staff have for improving them on mobile ?</i></div>
<p>Oh, you just hit the spot with this one, as we are all huge data nerds :D We will think about unified graphing engine in 2016. Probably after first approached to data storing/querying solution. </p><p>We will make sure that solution we pick will work great on mobile. </p>
<p>Charts are one of the most used elements in wikia. But most of the implementations are not mobile friendly. Current solutions on Wikia include Extension:Timeline,Module:Chart, and javascript generated charts. Most of these are not portable, but at least Extension:Graph seems to be a more powerful and portable version heavily used by WMF. </p> Any chance of backporting that extension or if that's not possible what tips would staff have for improving them on mobile ?</i></div>
<p>Oh, you just hit the spot with this one, as we are all huge data nerds :D We will think about unified graphing engine in 2016. Probably after first approached to data storing/querying solution. </p><p>We will make sure that solution we pick will work great on mobile. </p>
(Edited by Shareif)
0
<div class="quote"><i>Infobox preview tool
<p>First of all, I have to say that Staff did fantastic work with the previewer. But it is a power user tool. </p> Is there any chance of having a preset for invocation, and also the ability to send that data to visual or code-editor for easy publishing e.g. to draft page, without copy & pasting, and maybe set the template field to an arbitrary page (this is useful for Mentoring:Requests)?</i></div>
<p>Thank you for kind words. Its great to hear you like our tool. We will be working on extending our infobox editing tools in 2016 aiming at making them usable for broader audience. However, I cannot guarantee that they will be an extension of the current tool. </p>
<p>First of all, I have to say that Staff did fantastic work with the previewer. But it is a power user tool. </p> Is there any chance of having a preset for invocation, and also the ability to send that data to visual or code-editor for easy publishing e.g. to draft page, without copy & pasting, and maybe set the template field to an arbitrary page (this is useful for Mentoring:Requests)?</i></div>
<p>Thank you for kind words. Its great to hear you like our tool. We will be working on extending our infobox editing tools in 2016 aiming at making them usable for broader audience. However, I cannot guarantee that they will be an extension of the current tool. </p>
(Edited by Shareif)
1
<div class="quote"><i>Does Wikia have some ideas percolating for how to deal with big multi-column tables on mobile? Perhaps some new non-HTML type way to mark up tables that could possible break up rows into PI-style stacked data presentation?
I suppose a very clever lua module could be made to do this...</i></div>
<p>We just started playing with it. First step was to implement scrollable tables using material design patterns. The next step... changing data to infobox-like styles :) </p><p>You can see how the 'new' tables look like here: http://fallout.wikia.com/wiki/Fallout_4_unique_weapons </p>
I suppose a very clever lua module could be made to do this...</i></div>
<p>We just started playing with it. First step was to implement scrollable tables using material design patterns. The next step... changing data to infobox-like styles :) </p><p>You can see how the 'new' tables look like here: http://fallout.wikia.com/wiki/Fallout_4_unique_weapons </p>
(Edited by Shareif)