FANDOM

FishTank

aka Isaac

Staff
  • I live in San Antonio, Texas, US
  • I was born on November 18
  • My occupation is Editor Experience Specialist at Fandom
  • I am male
  • Bio I don't always help Fandom users; but when I do, it's as an anthropomorphic fish in an armored military vehicle.
  • [Show More]

Re: "top" vs prepending

That is an implementation decision that Simant (who has been inactive for years) and Dantman (still reachable by email) made long ago. I'm not quite certain myself. WindStar7125 Divine Mangekyō Sharingan VolteMetalic 18:23, October 16, 2018 (UTC)

Didn't answer this, but yes, your proposed solution you left on my talk page seems totally fine. WindStar7125 Divine Mangekyō Sharingan VolteMetalic 21:37, January 1, 2019 (UTC)

Help

Yes! I would love the help! I sent you a message on Community Central, thanks !

18px The Perverted Copy Wheel Eye of Justice 18px 17:56, January 26, 2019 (UTC)

For clarity, whenever people ask for the infoboxes from here, i just use the same response, which is to stop people blindly copypasting the infoboxes from here and expecting them to work. :D —Sajuuk 01:21, January 27, 2019 (UTC)

Re: tired property

Why is it more useful? It's only used for episodes, whereas Property:Japanese release is used for everything; books, movies, games, etc. By having two properties dedicated to release dates, two searches need to be performed to find out what was released in, for example, January 2010. If a person only wants to know the release dates of episodes, they can narrow the results of Property:Japanese release to Category:Episodes/Concept:Episodes. ~SnapperTo 08:05, January 31, 2019 (UTC)

I'm not denying the usefulness of only having the release information for a specific media type. But, as I said, you can limit your search parameters to the media type you're interested in. It's not strictly necessary to separate them preemptively in anticipation of wanting that precision. To use your apples and oranges example, it would be like having one store that sells the apples and then another store that sells the oranges. It's useful from an organizational standpoint to have the separate resources for each produce, but if I ever want to buy both I need to visit two stores. Ideally, I would visit one store and limit my fruit needs to Fruit::Apple or Fruit::Orange. You may have the concern that the typical reader won't know how to limit their needs for a specific media type's release information, but that's why we have articles like List of Animated Media and List of video games: to provide a narrowed assortment of information.
Now you make the fair point that there's not much need to ever want to know the release information of all media types simultaneously; after all, apples and oranges don't pair well in the same pie. But that's not to say there's no need. For instance, if I wanted to have an area on the Main Page that shows the five most recent releases, I'd need only:
Japanese release::<CURRENTMONTHNAME CURRENTDAY, CURRENTYEAR |limit=5 |sort=Japanese release
If your media-specific properties were used instead, I'd need a query for every media type, which would likely also give me far more than the five results that I want. Unless you know of a way to list results by a specific value rather than a specific property? Like say:
Japanese release::<ANYPROPERTY::CURRENTMONTHNAME CURRENTDAY, CURRENTYEAR
In the likely event that my arguments haven't swayed you, maybe you can at least agree that both styles of properties have their uses: have a combined property like I prefer and have the specific property like you prefer; in the infobox you'd use [[Japanese airdate::{{{japanese airdate}}}]][[Japanese release::{{{japanese airdate}}}| ]]. ~SnapperTo 19:13, January 31, 2019 (UTC)
I'm happy with whatever works, whether using both properties or doing union searches. I made Template:Main Page/Today a couple months ago and and the centralized date property was the least cumbersome way for me to do that. So long as that template continues to provide the desired information, I have no objections to whatever you want to implement. ~SnapperTo 19:41, January 31, 2019 (UTC)

Thread

Are you going to answer these two issues users had some time ago (and this reply of mine to your query)? I perfectly understand that you are quite busy, but we've been waiting awhile for your response (and I'd also like to move ahead with the implementation of the other infoboxes you had in store)... WindStar7125 Divine Mangekyō Sharingan VolteMetalic 12:40, March 21, 2019 (UTC)

Names in Technique Infobox

Heyo, sorry to bother you. Could you please change the infobox for techniques so that the Japanese name is "KanjilinebreakRomaji" instead of "Kanji (Romaji)"? • Seelentau 愛 09:18, March 26, 2019 (UTC)

Infoboxes

Hello, it's been a long time. Are you going to deploy all of the newer infoboxes you proposed so long ago? That process has been stopped halfway. WindStar7125 Divine Mangekyō Sharingan VolteMetalic 07:27, June 22, 2019 (UTC)

Infobox Help

Would it be possible to use the portable infoboxes that are used currently on Narutopedia on another fandom wikia? And if so, how might I go about accomplishing that? DazzlingEmerald (talk) 01:48, July 12, 2019 (UTC)

Community content is available under CC-BY-SA unless otherwise noted.