Difference between revisions of "User talk:Tvol"
Jump to navigation
Jump to search
HubrisBliss (talk | contribs) |
HubrisBliss (talk | contribs) |
||
| Line 17: | Line 17: | ||
::: The payoff here is that should anyone want to reference the perk's extra info text somewhere else, they don't need to duplicate it, just use transclusion to refer to it, keeping things DRY (a software engineering principle, "Don't Repeat Yourself", but it applies equally well to wikis). This could be used, for example, to display all the info text underneath the ability icon, or next to it, or in a different cell in a table, etc. It's a just-in-case thing but could save headache later. --[[User:Tvol|Tvol]] ([[User talk:Tvol|talk]]) 01:01, 28 January 2017 (UTC) | ::: The payoff here is that should anyone want to reference the perk's extra info text somewhere else, they don't need to duplicate it, just use transclusion to refer to it, keeping things DRY (a software engineering principle, "Don't Repeat Yourself", but it applies equally well to wikis). This could be used, for example, to display all the info text underneath the ability icon, or next to it, or in a different cell in a table, etc. It's a just-in-case thing but could save headache later. --[[User:Tvol|Tvol]] ([[User talk:Tvol|talk]]) 01:01, 28 January 2017 (UTC) | ||
::::All makes sense. Just wanted to avoid adding text in the wrong spot. For now, I'm finding new things to do, but I will plan on adding text later after you have created the respective <code>*/Info</code> pages.<br/>Expect a simple unit navbar at the bottom of the class pages fairly soon. I'm already frustrated trying to jump between them. --[[User:HubrisBliss|HubrisBliss]] ([[User talk:HubrisBliss|talk]]) 01:16, 28 January 2017 (UTC) | ::::All makes sense. Just wanted to avoid adding text in the wrong spot. For now, I'm finding new things to do, but I will plan on adding text later after you have created the respective <code>*/Info</code> pages.<br/>Expect a simple unit navbar at the bottom of the class pages fairly soon. I'm already frustrated trying to jump between them. --[[User:HubrisBliss|HubrisBliss]] ([[User talk:HubrisBliss|talk]]) 01:16, 28 January 2017 (UTC) | ||
| + | ::::Those are some cleeeeean rank icons. Nice! Short-but-sweet unit navbars are in. --[[User:HubrisBliss|HubrisBliss]] ([[User talk:HubrisBliss|talk]]) 02:08, 28 January 2017 (UTC) | ||
Revision as of 02:08, 28 January 2017
Hello there :)
Can you please check if your bot is working as intended? The abilities are getting all full of error messages. Thanks :) Hobbes (talk) 18:33, 27 January 2017 (UTC)
- It is, or rather I am (the bot did the heavy lifting but I wouldn't dream of letting such a complicated regex loose on a wiki :o ). The parse errors weren't caused by the replacement text, but by the calls on the skills pages being "bad". I've cleaned those up. Now I just have to fiddle with the actual template itself more to get it working. (If I can't I'll just regex the crap out of things and fix them. I won't leave stuff broken. :) ) --Tvol (talk) 18:39, 27 January 2017 (UTC)
Class Tree
10-4. I put the current mediocre rank icons up this morning, I think. Certainly looking forward to them being upgraded. I'm so glad you made the Template:Ability (LW2). The old one was atrocious to add to. I just need to learn how to page break properly in the b-info pop-up window.
This is my first wiki edit ever, so I learned a bunch watching your updates. I never would've thought about putting the extra info on a mouse-over, or how to do it. BTW, if you think your question mark is poor, check out what I uploaded, lol.
I'll be filling out more text info for now, and working on the Psi Operative Tree.
Oh, and I just learned about '~~~~'. <Phew>. --HubrisBliss (talk) 23:30, 27 January 2017 (UTC)
.png){kind=link}
- Glad I could teach by doing. :) (Though regexes and Pywikibot helped a lot in sorting those ability templates.) As for the info pop-up, I've never been able to get title text to respect breaks on a wiki. I think it's still possible, but would require tweaking the CSS used by the wiki to add a new class for these images specifically. --Tvol (talk) 23:59, 27 January 2017 (UTC)
- Oh, and I forgot to mention, that this line-break issue is part of the reason I moved the info bits to their own sub-pages. (Or will be moving them.) That way it's easy to transclude those lists elsewhere, in-case there's need of a stop-gap of some sort. --Tvol (talk) 00:12, 28 January 2017 (UTC)
- Specifically, where are you moving the info bits? Not the individual perk templates? i.e. Template:Alpha Mike Foxtrot (LW2), after
| s_info =. If somewhere else, please point me there. --HubrisBliss (talk) 00:37, 28 January 2017 (UTC)- Ah, okay. Here goes my explanation. I'm moving the lists of extra/extended info to sub-pages of their respective templates. This means that for Template:Alpha Mike Foxtrot (LW2), the info text (and just the info text) would be on the page Template:Alpha Mike Foxtrot (LW2)/Info. Note the
/Infopart. Then the template itself should be edited so that it reads{{ {{subst:FULLPAGENAME}}/Info }}and saved. When it is saved, thesubst:part will convert the FULLPAGENAME magic word into raw text, and the result will be, in this example,
- Ah, okay. Here goes my explanation. I'm moving the lists of extra/extended info to sub-pages of their respective templates. This means that for Template:Alpha Mike Foxtrot (LW2), the info text (and just the info text) would be on the page Template:Alpha Mike Foxtrot (LW2)/Info. Note the
- Specifically, where are you moving the info bits? Not the individual perk templates? i.e. Template:Alpha Mike Foxtrot (LW2), after
You do 4 additional points of base damage and 2 additional points of crit damage with your primary weapon.. This will make sure that it references its own Info sub-page correctly no matter where it is used on the wiki. You can see an example at Template:Heavy_Weapons_(LW2) and Template:Heavy_Weapons_(LW2)/Info, as well as more info about transclusion here.
- The payoff here is that should anyone want to reference the perk's extra info text somewhere else, they don't need to duplicate it, just use transclusion to refer to it, keeping things DRY (a software engineering principle, "Don't Repeat Yourself", but it applies equally well to wikis). This could be used, for example, to display all the info text underneath the ability icon, or next to it, or in a different cell in a table, etc. It's a just-in-case thing but could save headache later. --Tvol (talk) 01:01, 28 January 2017 (UTC)
- All makes sense. Just wanted to avoid adding text in the wrong spot. For now, I'm finding new things to do, but I will plan on adding text later after you have created the respective
*/Infopages.
Expect a simple unit navbar at the bottom of the class pages fairly soon. I'm already frustrated trying to jump between them. --HubrisBliss (talk) 01:16, 28 January 2017 (UTC) - Those are some cleeeeean rank icons. Nice! Short-but-sweet unit navbars are in. --HubrisBliss (talk) 02:08, 28 January 2017 (UTC)
- All makes sense. Just wanted to avoid adding text in the wrong spot. For now, I'm finding new things to do, but I will plan on adding text later after you have created the respective
- The payoff here is that should anyone want to reference the perk's extra info text somewhere else, they don't need to duplicate it, just use transclusion to refer to it, keeping things DRY (a software engineering principle, "Don't Repeat Yourself", but it applies equally well to wikis). This could be used, for example, to display all the info text underneath the ability icon, or next to it, or in a different cell in a table, etc. It's a just-in-case thing but could save headache later. --Tvol (talk) 01:01, 28 January 2017 (UTC)