Forum:Switch infobox V2

From the RuneScape Wiki, the wiki for all things RuneScape
Jump to: navigation, search
Forums: Yew Grove > Switch infobox V2
Archive
This page or section is an archive.
Please do not edit the contents of this page.
This thread was archived on 25 December 2013 by Suppa chuppa.

Switch infoboxes suffer from a number of flaws such as forcing us to replicate the entire infobox for one or two parameters and creating an ugly mess on mobile browsers. Whilst it might be possible to fix the first issue with a variation on the current switch infobox, mobile browsers is the main reason behind this remake.

Joey and I have recently been on a new version and it's nearly ready for deployment. We've also added a new template for inline switching allowing us to switch one or more parameters without having to replicate the entire infobox. The two templates are:

  • User:Cqm/switch infobox - User:Cqm/switch infobox/example.
  • User:Cqm/switch inline - User:Cqm/switch inline/example.

I couldn't find an example of switching a single parameter to demonstrate the inline version in the quick look I took, although I did stumble across a benefit of the inline version: the combat stats collapsible section stays in the state you left it between switches.

The known bugs can be seen User:Cqm/switch infobox/example#Bugs. If you find any more, please let me know.

In addition to the obvious request to implement this version of the switch infobox, I'd also like to remove navboxes from wikiamobile. Whilst one concern is the lack of collapsing, the amount of room they take up on pages like SoF verges on ridiculous. They're just not designed with mobile browsers in mind and I suspect there's nothing that will make them suitable.

Discussion

Support - as cqm 18:09, 2 Dec 2013 (UTC) (UTC)

YES - If navboxes absolutely must be removed, I'd say go ahead. Most tables don't bode well at all with the mobile skin. MolMan 18:12, December 2, 2013 (UTC)

For clarification, this is removing all navboxes rather than removing them on a page by page basis. cqm 18:29, 2 Dec 2013 (UTC) (UTC)
I know, and I assume you just have a simple css or script that will do this? MolMan 18:30, December 2, 2013 (UTC)
Of course Wink cqm 18:52, 2 Dec 2013 (UTC) (UTC)

Oppose - I have some experience with mobile browsers and both navboxes and switchfoboxes look absolutely fine. Even if the former are rather bulky, they are far too handy to just remove on mobile browsers. People using these obviously inferior (to normal computers) browsers shouldn't be considered at all IMHO, because wikis are designed for normal lap- and desktops; not the Ipad/Ipod/whatever the difference may be/Ipud nonsense. As for using switchfobox for only separate line, that could work for the examples with the monsters, but I imagine the "classic" switchfobox working better in all other instances, like on Veldaban, Zemouregal and Vanstrom to name a few. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 19:02, December 2, 2013 (UTC)

The standard switchfobox does not load whatsoever in wikiamobile: like here MolMan 19:05, December 2, 2013 (UTC)
Oh. At any rate, we shouldn't care for the reasons I stated. Can't we disable wikiamobile? User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 19:18, December 2, 2013 (UTC)
No. MolMan 19:20, December 2, 2013 (UTC)
Using the statistics shown [[w:User_blog:Kirkburn/Browsers_on_Wikia_-_a_Fall_2013_update|here]] you are suggesting that we make infoboxes, the tables that appear at the top of the page and take up 100% of the page width, unusable for a third of our viewers? Are you serious? cqm 21:58, 2 Dec 2013 (UTC) (UTC)
Yes. Mobile users know they won't have as good an experience using, well, just about anything on the internet as they would on a normal computer and we shouldn't try to optimise stufff or them which takes more than very little work. It's like helping people who didn't bringth their flashlight into a dark cave stay away from luminophobic monsters rather than those who did bring one, as they were supposed to (what a stupid analogy). Let's focus on improving switchfoboxes for regular browsers isntead, shall we. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 06:39, December 3, 2013 (UTC)
So in other words, because they aren't using a computer, they don't deserve to be able to use the wiki? That is not good business practice, refusing to fix a problem because the problem only affects mobiles. If you refuse to fix a malfunctioning door because it's only on a Tesco Express store and not one of the main Tesco supermarkets then you will lose customers What I've done Ciphrius Kane Talk 07:00, December 3, 2013 (UTC)
I'm just saying one shouldn't expect something to work properly when viewed via crap. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 17:15, December 3, 2013 (UTC)
One should also expect a wiki to be able to work on the fly. --Mikal (talk) 00:20, December 4, 2013 (UTC)
Hen e the existence of laptops. Internet was not made for mobile phones. We shouldn't try to make it so. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 07:32, December 4, 2013 (UTC)
I'm preeeetty sure the internet wasn't made for encyclopedias about online video games either, yet we still use it for that. Just because it wasn't meant to do something that doesn't mean we shouldn't make it do something. That's Medieval logic. Ancient talisman.png Oil4 Talk 08:34, December 4, 2013 (UTC)
I vote we just ignore FSWE and his vote--Mikael (talk) 15:23, December 4, 2013 (UTC)
You aren't seriously advocating that we go through the trouble of enabling something on phones, right? Internet - on PHONES? This isn't Star Trek. #Inbe4ThisIsStarTrek (@Jake: RS:NOT#DEMOCRACY) User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 15:34, December 4, 2013 (UTC)
Viagra wasn't meant to be a bedroom performance enhancer either. Just because something has deviated from its original purpose does not mean it should be undone What I've done Ciphrius Kane Talk 16:43, December 4, 2013 (UTC)
I had to google that. Thanks for the nightmares. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 17:42, December 4, 2013 (UTC)
Exactly, which means we can just easily ignore you as the rules of democracy don't matter :D--Mikael (talk) 20:03, December 4, 2013 (UTC)
Are you trying to be funny? Or do you really not understand how consensus works? As dumb as you may think fartwall's opinions are, they carry weight, and it is up to whoever closes this to decide exactly how much weight that is. MolMan 14:46, December 5, 2013 (UTC)
(and my opinions are very dumb) User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 15:34, December 5, 2013 (UTC)
Fswe, mobile devices weren't made for anything but phone calls back when they were invented, but then all of a sudden these hipster folks started sending some kinds of telegram-like things, THROUGH THE AIR! And then they added 2G/3G browsers to the phones, and that's when the feces got absolutely bonkers. Then they made smartphones with wifi-internet, and then basically everything was possible with phones. I'm just saying, if you're not adapting to new technologies, like the smartphone (dun dun dunnnnnn), you're not going to survive very long as a site. Besides, this new change is able to fix a few problems (such as keeping the cb stats collapsed) in non-mobile browsers too. I can't see what's the downside to this exactly. JOEYTJE50TALKpull my finger 15:30, December 8, 2013 (UTC)
Removing navboxes will make navigating quite harder on those fec--, I mean, devices. It seems like we'd be giving them an even greater disadvantage. Monsters like the SoF one excluded, of course. ;) As for the "switch parameter", I repeat, sure, that could be implemented on the entire wiki, if it has proven useful enough. PS. If we as a website must adapt to a device that isn't made for this, we're doing something wrong. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 17:00, December 8, 2013 (UTC)
You're saying smartphones and tablets aren't made for browsing the internet? Hmm... very interesting view you have... (especially check the first link, it kinda proves the opposite). JOEYTJE50TALKpull my finger 17:39, December 8, 2013 (UTC)
Yess... a smartphone is made for... phoning. Also, I think you mean something else by "tablet" than I do. Here's my idea of a tablet, but after some googling, I see what you mean; some kind of aberrition with an identity crisis, unable to decide whether it's a smartphone or a laptop. Poor thing. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 08:44, December 9, 2013 (UTC)
Okay you've convinced me. Let's drop support for smartphones and tablets. We do need to support these new fancy "transportable keyboardless portable touchscreen computers", and their smaller variants (the ones that are also able to serve as phone) though. Oh by the way, we should drop support for computers too. This is what a computer looks like. Those aren't made for browsing the internet. And laptops? This is a lap top. So, you're right. We should just stop uploading these pages to the Wikia servers. That's not what servers are for. Besides, why are we using the internet to play games? The internet is meant to be used to transfer data between CERN scientists. JOEYTJE50TALKpull my finger 09:52, December 9, 2013 (UTC)
Support. Juey is on to something here! Adventurer's log Wahisietel (Talk) Quest map icon.png 11:03, December 9, 2013 (UTC)
Lawl. Best computer. Btw, puto means "deem, regard as, find" and not calculate. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 17:40, December 9, 2013 (UTC)
Yes, TI graphing calculators are probably some of the most complete computers there are. They do have some horrible functions though, such as playing games like Mario or Snake (via the blue Apps button). That's just horrible, because computers aren't meant to play games with. And according to wiktionary, computo means [[wiktionary:computo#Latin|to calculate]]. Anyway, Extreme strong oppose adding this, and support closing this wiki, and moving to a written format. Computers aren't made to be used for playing games, so we shouldn't make a wiki that's compatible with computers. I'm glad you agree, Fswe.
PS: Paper is made from wood, and wood isn't made to be written on. We should probably just stick with verbal wikis instead. Atleast the voice was made to be used for sharing information between individuals. JOEYTJE50TALKpull my finger 17:56, December 9, 2013 (UTC)

Do whatever - Matt (t) 22:01, December 2, 2013 (UTC)

Sure - If you fix them for monobook. Neither one really works. Suppa chuppa Talk 22:30, December 2, 2013 (UTC)

User:Cqm/switch infobox, User:Cqm/switch inline, [[User:Cqm/switch inline/example]], and User:Cqm/switch infobox/example are all working just fine in monobook for me. Matt (t) 22:40, December 2, 2013 (UTC)
Inline certainly doesn't work. And switch infobox has all the text centered, but I guess that's an issue in oasis too. Suppa chuppa Talk 22:45, December 2, 2013 (UTC)
To elaborate, i'm pretty sure it's not supposed to look like this. Suppa chuppa Talk 22:48, December 2, 2013 (UTC)
Lol, it looks like that's broken in oasis too. Suppa chuppa Talk 22:50, December 2, 2013 (UTC)
Oh yeah. I'm seeing positioning problems too. Does the actual functionality work fine, though? Matt (t) 22:51, December 2, 2013 (UTC)
Yeah, that seems to work. Suppa chuppa Talk 22:51, December 2, 2013 (UTC)

Comment - This is what your first example looks like for me. Ancient talisman.png Oil4 Talk 09:02, December 3, 2013 (UTC)

Looks like that for me too. Adventurer's log Wahisietel (Talk) Quest map icon.png 10:11, December 3, 2013 (UTC)
Seems to align properly in Monobook brw. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 17:15, December 3, 2013 (UTC)
Looks somewhat better now, but a bit still gets covered up on smaller monitors, such as the one I view the wiki with. Adventurer's log Wahisietel (Talk) Quest map icon.png 20:55, December 4, 2013 (UTC)
The smaller monitors issue was something I wasn't entirely sure existed, but seems to be due to a minimum width applied to the combat stats of the monster infobox from what I can tell. If you see it on any other infoboxes (feel free to test) please let me know. As far as I can tell the bug displayed in Oli's screenshot is fixed.
Also, imgur is loading somewhat intermittently for me at the moment, so I'd appreciate the images being uploaded somewhere else as it makes bugs a bit easier to fix Wink. cqm 00:43, 5 Dec 2013 (UTC) (UTC)
It looks good to me now. Ancient talisman.png Oil4 Talk 08:41, December 5, 2013 (UTC)
It's still (slightly) broken. Adventurer's log Wahisietel (Talk) Quest map icon.png 11:04, December 6, 2013 (UTC)
Can you take a look at User:Cqm/Scrapbook 1. I think it's just the monster infobox that's bugged (some of the ones Vanstrom uses are the NPC infobox). cqm 11:26, 6 Dec 2013 (UTC) (UTC)
I'm not sure what I'm looking at? There isn't an infobox there, just buttons that switch between text saying "content 1" and "content 2"... Adventurer's log Wahisietel (Talk) Quest map icon.png 16:35, December 8, 2013 (UTC)
Sorry, User:Cqm/Scrapbook 1/1. I have far too many of these things... cqm 16:52, 8 Dec 2013 (UTC) (UTC)
Yeah, NPC seems to work fine, it seems to just be the monster infobox that's broken. Adventurer's log Wahisietel (Talk) Quest map icon.png 17:01, December 8, 2013 (UTC)

Comment - [http://community.wikia.com/wiki/User_blog:TranStanley/Updates_to_the_Wikia_Mobile_experience This] might be relevant for mobile. Ancient talisman.png Oil4 Talk 08:28, December 6, 2013 (UTC)

The updates are more or less a small redesign with an editor and a couple of features thrown in for wow effect. There's nothing that impacts this forum as far as I'm aware. cqm 16:12, 8 Dec 2013 (UTC) (UTC)

Comment - I've changed a few things that were in the bugs list. JOEYTJE50TALKpull my finger 17:39, December 8, 2013 (UTC)

Support - It works well, and almost all browsers support it now. The fix for IE8- makes it work in those browsers too, so I can't see any problems with using this. I never thought it would be this fast that we could basically ignore IE8 and lower when adding/changing features. The internet is growing up so fast :'D *sniff* JOEYTJE50TALKpull my finger 17:39, December 8, 2013 (UTC)

Support - I hate editing the current switch infoboxes. Getting it working with mobile is awesome too, and well worth it alone.

  1. REDIRECT User:Fewfre/signature.css

Closed - Most of the bugs seem to have been ironed out, and there is consensus to implement the new versions of the infoboxes. There isn't any point to keeping this open for any longer, so Cqm can go ahead and do so when he desires. Suppa chuppa Talk 22:26, December 25, 2013 (UTC)