Difference between revisions of "User talk:Azymn/Boilerplate:Skill tree"

ADVERTISEMENT
From Diablo Wiki
Jump to: navigation, search
(Skill Navigation)
Line 2: Line 2:
 
Ooh, I like those. Defo look better than the first one I made :P --[[User:Vipermagi|Vipermagi]] 15:24, 14 March 2009 (CET)
 
Ooh, I like those. Defo look better than the first one I made :P --[[User:Vipermagi|Vipermagi]] 15:24, 14 March 2009 (CET)
 
<br/><br/>
 
<br/><br/>
I made a few more examples. I like my third one the most. It's compact, and includes all info. The main thing to note is that I'd like ALL nav boxes to retain 80% width! Besides that, what do the rest of you guys think? --[[User:Leord|Leord]] 13:49, 16 March 2009 (CET)
+
:I made a few more examples. I like my third one the most. It's compact, and includes all info. The main thing to note is that I'd like ALL nav boxes to retain 80% width! Besides that, what do the rest of you guys think? --[[User:Leord|Leord]] 13:49, 16 March 2009 (CET)
 
<br/><br/>
 
<br/><br/>
Thanks for the feedback guys.  80% width is fine with me, the only issue we may face is how long certain skill tree names will be with the Pirate, Ninja, and Unicorntaur classes coming in the expansion.  But we can handle that when the time comes, so I took Leord's 3rd suggestion and pared it down for our current needs.  Anything else we want to tinker with at this point?  --[[User:Azymn|Azymn]]
+
::Thanks for the feedback guys.  80% width is fine with me, the only issue we may face is how long certain skill tree names will be with the Pirate, Ninja, and Unicorntaur classes coming in the expansion.  But we can handle that when the time comes, so I took Leord's 3rd suggestion and pared it down for our current needs.  Anything else we want to tinker with at this point?  --[[User:Azymn|Azymn]]
 
<br/><br/>
 
<br/><br/>
 +
:::I am happy. No need to tinker more. I also think that they won't use uber-long class names or skill tree names, so I think we can go with this. Lets use this on all skills and skill trees.
 +
 +
:::What I want to do, before we can implement any of what we discussed on ICQ, is to make sub-templates for each tree, that we insert at the bottom of this navbox. With a template attribute it's linked in. Do you understand what I mean? It's not vital at this point, but this extra piece of navigation will include all (known) skills of the tree you are currently looking at.
 +
 +
:::Alternatively... It could be all the skills of a certain class, if that does not look cluttered. --[[User:Leord|Leord]] 18:34, 18 March 2009 (CET)

Revision as of 17:34, 18 March 2009

Skill Navigation

Ooh, I like those. Defo look better than the first one I made :P --Vipermagi 15:24, 14 March 2009 (CET)

I made a few more examples. I like my third one the most. It's compact, and includes all info. The main thing to note is that I'd like ALL nav boxes to retain 80% width! Besides that, what do the rest of you guys think? --Leord 13:49, 16 March 2009 (CET)



Thanks for the feedback guys. 80% width is fine with me, the only issue we may face is how long certain skill tree names will be with the Pirate, Ninja, and Unicorntaur classes coming in the expansion. But we can handle that when the time comes, so I took Leord's 3rd suggestion and pared it down for our current needs. Anything else we want to tinker with at this point? --Azymn



I am happy. No need to tinker more. I also think that they won't use uber-long class names or skill tree names, so I think we can go with this. Lets use this on all skills and skill trees.
What I want to do, before we can implement any of what we discussed on ICQ, is to make sub-templates for each tree, that we insert at the bottom of this navbox. With a template attribute it's linked in. Do you understand what I mean? It's not vital at this point, but this extra piece of navigation will include all (known) skills of the tree you are currently looking at.
Alternatively... It could be all the skills of a certain class, if that does not look cluttered. --Leord 18:34, 18 March 2009 (CET)