FANDOM

A FANDOM user
  Loading editor
  • Hi Ckwng,

    Sorry to bother you, back in July you wrote a small module for me that combines ShipCardKai and ShipBattleCardKai into one called ShipCardComboKai (original thread here: [[1]])

    It was working very well up until the start of 2017, from that point, all the card overlays are very small instead of their full size cards, you can see this here on my shipgirls wiki: [[2]]

    If possible, could you look at this when you have some available time and see if you can restore the original functionality?

    Thanks again.

    Edit: Unsure if you did something, but it's all good now. (Thank you if you did fix it)

      Loading editor
  • You got to it a bit before I did, but I suggest we have:
    The 16inch guns after the 51cm guns (because different metric system, better to separate).
    Also have the Fighter section before the seaplane section (because consistency across wikia).
    I did the normal arsenal the way i described but didn't touch the modules list side of the arsenal.
    You have the final say, and I will edit the page(s) in the order of your final decision.

      Loading editor
    • I put the 16inch guns before 41cm because 406mm < 410mm... I agree with the fighters, will make the change.

        Loading editor
    • A FANDOM user
        Loading editor
  • I tried importing the Audio template to another wiki, but it doesn't seem to work. It seems like I need to import the audio button image as well, but how do I do that?

      Loading editor
  • Hi, I'm sorry if my edits didn't conform with this wiki policies or break the code.

    Still, I think for the icons, the images should not link into the image page nor trigger image popups. I try to unlink them, and give alt text that should show a tooltip when hovered (but apparently didn't work if both are implemented, it's either unlink only or tooltip only).

    Regards.

    ArdWar TalkContributions 10:02, May 28, 2016 (UTC)

      Loading editor
    • This is by design, sorry. If you want use unlinked icons, you should make those changes outside of those modules you edited, as those are used by the entire site. If you need help with that, feel free to ask, and let me know what you want to do.

        Loading editor
    • A FANDOM user
        Loading editor
  • Hi, Ckwng!

    A user recently nominated KanColle for inclusion in our gaming footers program. Would you be interested?

    Best regards,

    Raylan

      Loading editor
  • We've a Discord channel for us event staffers who will be primarily involved with editing the wikia during the event. We also have Skype as a backup channel, should some be unable to use Discord.

    I believe this would be helpful to you during the event, since we can avoid things like double-editing etc.

    The respective thread can be found here: http://kancolle.wikia.com/wiki/Thread:421660

    Thank you for your hard work and let's make this event a great one!

      Loading editor
    • A FANDOM user
        Loading editor
  • About your issue in the to-do list, here is a working (?) example I got:

    function getQuery() {
        var query = {};
        for (var part of window.location.search.substring(1).split("&")) {
            var kv = part.split("=");
            if (kv.length === 2) {
                query[kv[0]] = kv[1];
            }
        }
        return query;
    }
    
    (function(mw, $) {
    
        "use strict";
    
        $(document).ready(function() {
    
            function scrollTo(content, selector) {
                var element = content.find(selector).get(0);
                if (element) {
                    element.scrollIntoView();
                }
            }
    
            var initial_hash = window.location.hash && window.location.hash !== "" ? window.location.hash : true,
                initial_tab = getQuery().tab,
                switch_hash = null,
                outer_element = $(initial_hash).get(0);
    
            function switchToTab(tab, hash) {
                $("ul.tabs li a span:contains('" + tab + "')").parent().trigger("click");
                switch_hash = hash;
            }
    
            function processTabBody(content) {
                var $content = $(content);
                if ($content.attr("class") === "tabBody selected") {
                    $content.ready(function() {
    
                        if (initial_hash) {
                            if (initial_tab) {
                                switchToTab(initial_tab, initial_hash);
                                initial_tab = null;
                            } else {
                                if (!outer_element) {
                                    scrollTo($content, initial_hash);
                                }
                                initial_hash = null;
                            }
                        } else {
                            if (switch_hash) {
                                scrollTo($content, switch_hash);
                                switch_hash = null;
                            }
                        }
    
                        $content.find(".tabview_link a").each(function() {
                            $(this).click(function(link_element) {
                                link_element.preventDefault();
                                var href = $(this).attr("href"),
                                    parts = href.split("/").pop().split("#"),
                                    tab = parts[0],
                                    hash = "#" + parts[1];
                                window.location.hash = hash;
                                switchToTab(tab, hash);
                                scrollTo($(".tabBody.selected"), hash);
                            });
                        });
    
                    });
                }
            }
    
            mw.hook("wikipage.content").add(processTabBody);
    
        });
    
    }(mediaWiki, jQuery));
    

    Using Sandbox/Quests as an example, it should:

    May need some more testing / have some edge cases.

      Loading editor
    • Wow, thanks, I'll take a look at this later.

        Loading editor
    • getQuery() is tripping up the resource minifier, particularly the for (... of ...) line. It's expecting a semi-colon somewhere for some reason.

      What exactly creates a URL that has tab=___ anyway? AFAIK tabview doesn't do that...

        Loading editor
    • for (... of ...) is ECMAScript6, maybe it wants ECMAScript5, so

      function getQuery() {
          var query = {};
          var parts = window.location.search.substring(1).split("&");
          for (var i = 0; i < parts.length; ++i) {
              var part = parts[i];
              var kv = part.split("=");
              if (kv.length === 2) {
                  query[kv[0]] = kv[1];
              }
          }
          return query;
      }
      

      the tab=___ part in the query is arbitrary, I just use it to link to a non-default tab from any external link (i.e. not tabview_link, suppose you want to link to G3 inside the Modernization tab from some other unrelated page; all three features are independent: initially it scroll using a given hash in the default tab, or switch to a tab using a given name in the query and then scroll using a given hash, and then there is switching/scrolling using tabview_link). Though query isn't supported that well by MW (can't just write [[Sandbox/Quests?tab=Modernization]]) and also any change to window.location.search will refresh the page (if I start changing it to reflect the current tab), so probably should use a part of the hash instead, with some arbitrary convention like [[Sandbox/Quests#Modernization/G3]] (should switch to the Modernization tab and then scroll to G3). Or just drop this feature (only scroll in the default tab for external links and switch/scroll for tabview_link, unable to link to a non-default tab externally).

        Loading editor
    • A FANDOM user
        Loading editor
  • Is it possible to make it display correctly in monobook skin?

      Loading editor
  • Hi, was thinking that it might be a good idea amongst regular wiki editors to maybe throw in their wiki todo list in a bid to:

    • Know roughly who has what on their agenda in terms of wiki work,
    • Potentially collaborate on portions where listed/appropriate,
    • May be allow others who wants to be wiki contributors but sees wiki as already "complete" and that there is nothing left for them to do.

    The idea started off as a brainstorm with IloveSuiseiseki and provided that if in theory we all threw in our todo list, it might be a way to entice more people to know what needs addressing and where they may want to help out (totally on their own preferences of course).

    I don't know what is the best way to phrase this but here is just a bid to try and present an idea that the wiki was never complete to begin with and with the ever expanding Kancolle franchise, notably with KanColle Kai, KanColle Android and possibly Kancolle arcade the regular editors may end up being stretched thin whilst new editors are constantly under the belief that there is nothing that needs work on.

    tl;dr please let me know on your thoughts about this idea as well as がか if possible. For now I am keeping the todo list on my own namespace as Kancolle Wiki:Projects and if we can somehow get enough editors to pitch in whatever that needs working on may be we can move that Todo list off my namespace and into some more general namespace.

    Thanks!

      Loading editor
    • I do have a to-do list; converting the World X pages' enemy comps to the template we use for events, centralizing map drops into a lua module so it can be synchronously displayed on both World X and <ship_name> (or at the very least, something like the Category:Stock equipment categories), and commenting and documenting the hell out of the Lua system. Just don't have the motivation to wiki right now; should recover by the time the spring event comes along >_>

        Loading editor
    • A FANDOM user
        Loading editor
  • Hi, about that EnemyShipListKai. I personally have two gripes about it: - the list is too long. Though if we could break those down into individual pages like by class that would be nice. - the colouring is somewhat icky for me.

    Overall the idea does look nice but not sure on the extendibility. Also I suggest we should push the idea to Gaka's messagewall where I mentioned of getting more people (at least for what is to be the remains of wiki editors are) to have their final say about it.

      Loading editor
    • View all 6 replies
    • Ah just that the editors (especially those who aren't familiar with it or those who are new to it all) may find it a bit overwhelming.

      I'll have a good look at it later on. Thanks for this! now if other regular Enemy Vessel editors notice these so that they can quickly adapt if and when it gets rolled out.

        Loading editor
    • Can always bury instructions as html comments in the wikitext like the AIA had before? Might help.

        Loading editor
    • A FANDOM user
        Loading editor
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message
Community content is available under CC-BY-SA unless otherwise noted.