Please feel free to fill in questions below - staff will be around to answer them at 4pm UTC on Thursday.
303
pages
ALL POSTS
1
Technobliterator wrote:
Brief question, is:
Brief question, is:
<title source="name"><default>{{PAGENAME}}</default><format>[[File:FFXIV {{{name}}} Icon.png|{{{name}}} icon.]] {{{name}}}</format></title>
allowed?
Yes. However on mobile we will only display the title. In order to ensure good look on mobile we are removing everything, but text from title fields (on mobile).
(Edited by Shareif)
Ahh, good idea. Fair enough.
(Edited by Technobliterator)
1
- Preset themes
- Theming is one of the biggest headaches of portable infoboxes. Great apps such as Winamp or VLC often come preset with themes and this is one of the best ways to showcase how great they can look. Are there any plans to have a discrete number of preset themes?
The truth is … I’m Iron Man. Ekhem. I mean yes, we have plans for these. We will experiment with alternative layouts and themes in built-in theming tool for infoboxes.
We intended to introduce them sooner, but thanks to user feedback we found out that collapsible sections and tabbers are more needed :)
(Edited by Shareif)
0
Odd question: Tabbers inside PIBs can be used for images. On one game wikia that I can think of, they use this to show different images of a given character based on which game this character appeared in. They also use images of the game title as their sorting element. Can images be used as Tabber "titles"?
(Edited by FishTank)
I have only one question right now: When is the mobile skin preview on Desktop edit mode going to get fixed to match what the actual mobile skin renders?
(Edited by Fandyllic)
Thanksgiving morning for office hours? Seriously?
(Edited by Fandyllic)
Fandyllic wrote: Thanksgiving morning for office hours? Seriously?
They're not based in the US. :P
(Edited by Technobliterator)
1
Fandyllic wrote:
Thanksgiving morning for office hours? Seriously?
Thanksgiving morning for office hours? Seriously?
Cheers from Poland!
(Edited by Shareif)
TOR wrote:
Great question! We may have a library of components of some sort in the future.
However, knowing the fierce independence of some of our communities, and drawing on my Wikipedia experience with Wikimedia Commons, I’m gonna say it’s probably not quite the silver bullet it appears to be. ;)
We’re probably going to wait and see how dev wiki evolves and is used, now that it is a de facto global repository of JS scripts -- and there’s actually a way to sort of easily import them to your wiki, plus an incentive to use the global scripts to not have to go through JS review as often.
So if you care about this idea, head over to dev.wikia.com and help out over there -- or better yet, convince your wiki friends to start using global JS scripts from dev. We'll be watching and taking notes. :)
Another user and I have populated a whole page full of Lua modules (w:c:dev:luamods), and I crafted extensive guides to help create lua modules. We are even using some global modules from there in this wikia. One idea is to provide a highly customizable bare-bones framework that users can import and change at will.
I think that lua scripts are quite good because there's no need to convince anyone that they work. They can see loads of unit tests (see w:c:dev:links/testcases) that can help with "sane" testing. The only thing that is missing is some kind of LUA review system trusted users, e.g. code-editors review. Something similar to the JS review so that users don't get served problematic modules altered by ignorant users . Alternatively high use scripts can simply be protected or or added as libraries like mw.ustring, e.g. mw.quote.
There a quite a few javascripts I've created and submitted, but stopped this until we have a proper JS review in place. Maybe one day we'll eventually have a more vibrant coder community there.
(Edited by Dessamator)
Technobliterator wrote:
Alright, let's have a go at something that may or may not be easier to answer...
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 just thought of a better syntax that won't change existing infoboxes, and will still do what you want:
<infobox> <group layout="horizontal" collapse="open"> <header>Tony stark </header> <data><default>War machine</default></data> <data><default>Iron Man</default></data> <header>Hope</header> <data><default>Dark Goddess </default></data> <data><default>Lady death</default></data> </group>
The idea is that headers separate horizontal groups by serving as delimiters. That way you can still collapse the whole thing. So in the "code" above, we would have two horizontal groups...
Currently the first header is swallowed, not sure if that's a bug or feature.
(Edited by Dessamator)