User talk:NieA7/DPLSandbox
DPL[edit]
Nice to see someone else poking around in DPL! :)
As for the problem with "Hammer" vs "Hammer Master", I'd suggest you update the template to accept values like "Hammer", "Sword", "Axe", "Daggers", "Bow", etc. and have the {{Weapon infobox}} parse the correct attribute itself. I.e. "Hammer" parses to "Hammer Mastery". This should be easily doable.
Otherwise, you'll have to create a big "ifeq"-statement, where every item that comes out of {{#dpl: title=%PAGE% | include={Weapon infobox}:Attribute}}
will be changed to "Hammer", "Sword", etc. Personally I would put it into the {{Weapon infobox}} myself.
If you have any questions on ParserFunctions, you'd best talk to Anja, she's more knowledgeable regarding ParserFunctions. Any other questions regarding DPL: try me, Rezyk or the DPL-manual itself. I'm still learning to work with the code myself, but it's becoming clearer and clearer. :) -- (CoRrRan / talk) 16:34, 17 July 2007 (UTC)
- Ah, it's a damn pipe to get conditional formatting! I was pratting about with =, no wonder it didn't work. Thanks for cleaning it up :)
- As for the rest of it, it's going to take a vast update to the weapon infobox (and all the weapons) to get this as good as the current list, so using parser functions there would probably be the best way of going about things (though if done it would make the weapon pages themselves rather unfriendly to edit - loads of hidden values). I should probably work out what's needed first, then see how technically difficult/desirable in the grand scheme of things it would all be. When I'm learning something I tend to find other peoples stuff and take it apart, hence me nicking your sandbox to begin with ;) I'll carry on poking about - it's pretty useful, but with weapons being as they are (Ogre Slaying Knife anyone?) it might not be practical... --NieA7 16:44, 17 July 2007 (UTC)
- The idea is to keep the information in the {{weapon infobox}} as few as possible. After all, you will always have a link to the weapon itself in the first column of your DPL. So don't worry too much about too many arguments. If I were you, I'd just try to recreate the Unique items list as it is at the moment first, and mod the template accordingly. -- (CoRrRan / talk) 16:50, 17 July 2007 (UTC)
- And don't forget that I used
{{#ifeq:
instead of{{#if:
. Take a look here Help:ParserFunctions for more info. -- (CoRrRan / talk) 16:52, 17 July 2007 (UTC)- Yeah, I can see why the infobox should be kept as small as possible. The trouble is that while Rezyk's edits work well in getting all the stats in the table, they don't replicate the List of Prophecies unique items: in that list all the components are in separate columns so they can be sorted (took ages to unify that), with DPL here everything is lumped together in one column and can't be sorted. I'll have a fiddle when I get a chance and see if they can be split with things as they currently stand, or whether changes somewhere will be necessary. --NieA7 13:43, 18 July 2007 (UTC)
- And don't forget that I used
- The idea is to keep the information in the {{weapon infobox}} as few as possible. After all, you will always have a link to the weapon itself in the first column of your DPL. So don't worry too much about too many arguments. If I were you, I'd just try to recreate the Unique items list as it is at the moment first, and mod the template accordingly. -- (CoRrRan / talk) 16:50, 17 July 2007 (UTC)