Difference between revisions of "Template talk:Character Profile"
From PSU Cyril Wiki
m |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 8: | Line 8: | ||
*Yeah. I did look into adding the ability for multiple characters, but two solutions I saw were using a second template which people repeat for each character a la the "Luck row" template, or using an <nowiki>{{#if:}}</nowiki> function, which for the life of me I couldn't get to work because it requires the same | symbols that tables do >.< - If I could work out how to avoid that conflict, it'd be a breeze to implement. - [[User:Miraglyth|Miraglyth]] 15:28, 25 November 2006 (PST) | *Yeah. I did look into adding the ability for multiple characters, but two solutions I saw were using a second template which people repeat for each character a la the "Luck row" template, or using an <nowiki>{{#if:}}</nowiki> function, which for the life of me I couldn't get to work because it requires the same | symbols that tables do >.< - If I could work out how to avoid that conflict, it'd be a breeze to implement. - [[User:Miraglyth|Miraglyth]] 15:28, 25 November 2006 (PST) | ||
| − | :Yeah. Trying to work this one out, I've made a complete embarrasment of myself as seen in "Recent Changes". If you use {{}} to group the "then" argument necessary, the {{ and }} appear on the table and look stupid. But if you don't use them, the table pretty much breaks. | + | :Yeah. Trying to work this one out, I've made a complete embarrasment of myself as seen in "Recent Changes". If you use {{}} to group the "then" argument necessary, the <nowiki>{{</nowiki> and <nowiki>}}</nowiki> appear on the table and look stupid. But if you don't use them, the table pretty much breaks. |
:If it becomes necessary >.< then I would go with an additional template. That said, I believe the table's formatting for expert types will be a far more important within a week. - [[User:Miraglyth|Miraglyth]] 16:26, 25 November 2006 (PST) | :If it becomes necessary >.< then I would go with an additional template. That said, I believe the table's formatting for expert types will be a far more important within a week. - [[User:Miraglyth|Miraglyth]] 16:26, 25 November 2006 (PST) | ||
| + | * Columns still require tweaking, but yeah. I've had to do this stuff before, so I still kinda knew how to get around it. - [[User:Tycho|Tycho]] 04:15, 26 November 2006 (PST) | ||
| + | |||
| + | *Agh, nuu~ | ||
| + | :I did try using 20px/25px width columns before putting this template together. It still just looks really elongated and ugleh. I did try messing about with making it a new row (which would mean a 9-row table for 4 characters >.<) but you can see how badly that went on my User: page. | ||
| + | :At the moment I'm thinking of minor redesigns so it doesn't shrink for users with 1024x768 resolutions. Because really that just shouldn't happen. In the meantime, let me fix a couple of glitches on the <noinclude> section of this and use your <nowiki>{{bar}}</nowiki> method to restore my setup which will in turn fix the erroneous empty rows that currently exist. - [[User:Miraglyth|Miraglyth]] 06:29, 26 November 2006 (PST) | ||
| + | |||
| + | *Done. - [[User:Miraglyth|Miraglyth]] 08:15, 26 November 2006 (PST) | ||
Latest revision as of 16:15, 26 November 2006
Thoughts?
- Actually this is only a suggestion for the time being. PSUPedia is a wiki about the game, not it's players. Thus making a template for something like this isn't necessarily "on topic" as far as the wiki goes.
- That said, I have noticed a few people who had cloned the profile in my User page, something which if becomes semi-common practise, would benefit from standardisation such as this. Basically looking for input on whether this is a good idea or not. - Miraglyth 10:54, 25 November 2006 (PST)
- As long as people think it's convenient, it's great, I guess. As long as we're not going to tell people "NO STOP YOU SHOULD USE THE TEMPLATE" or something there shouldn't really be any problems about this. On a sidenote, there isn't really an easy way to use this template for multiple characters without getting the bold description row multiple times as well. One possible way to get around this would be to use parser functions to allow the first line to be turned on/off using parameters or something. I've also considered using different templates for the two lines, but that'd probably be more of a pain. - Tycho 13:37, 25 November 2006 (PST)
- N.B.:
| Name | Race | Gender | Level | Type | HU | RA | FO | FI | GT | WT | FF | FG | FT | PT | AF | AT | FM | GM | MF |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Ethan | Minority | Futa | OVER 9000! | Annoying |
- Yeah. I did look into adding the ability for multiple characters, but two solutions I saw were using a second template which people repeat for each character a la the "Luck row" template, or using an {{#if:}} function, which for the life of me I couldn't get to work because it requires the same | symbols that tables do >.< - If I could work out how to avoid that conflict, it'd be a breeze to implement. - Miraglyth 15:28, 25 November 2006 (PST)
- Yeah. Trying to work this one out, I've made a complete embarrasment of myself as seen in "Recent Changes". If you use {{}} to group the "then" argument necessary, the {{ and }} appear on the table and look stupid. But if you don't use them, the table pretty much breaks.
- If it becomes necessary >.< then I would go with an additional template. That said, I believe the table's formatting for expert types will be a far more important within a week. - Miraglyth 16:26, 25 November 2006 (PST)
- Columns still require tweaking, but yeah. I've had to do this stuff before, so I still kinda knew how to get around it. - Tycho 04:15, 26 November 2006 (PST)
- Agh, nuu~
- I did try using 20px/25px width columns before putting this template together. It still just looks really elongated and ugleh. I did try messing about with making it a new row (which would mean a 9-row table for 4 characters >.<) but you can see how badly that went on my User: page.
- At the moment I'm thinking of minor redesigns so it doesn't shrink for users with 1024x768 resolutions. Because really that just shouldn't happen. In the meantime, let me fix a couple of glitches on the section of this and use your {{bar}} method to restore my setup which will in turn fix the erroneous empty rows that currently exist. - Miraglyth 06:29, 26 November 2006 (PST)
- Done. - Miraglyth 08:15, 26 November 2006 (PST)
