Categorization issue
You really need to remove this line from this template:
<includeonly>[[Category:Properties]] __NOTOC__ </includeonly>
It's causing all the objects to be listed under the Properties category. Which is rather silly behavior.
Incorrect example
The example is wrong! It should be:
{{Property
|name = Name
|property = [[String]] ''object's name''
|description = The name of the object.
|object = Global
}}
Multiple Object Linking
If there is a property that belongs to multiple objects it lists them as one. Can we remedy this? Camoy • Contribs (December 25 2010)
The "Property" row
What purpose does it serve? Would it not be better to replace it with a "Type" row?
- Hey! I precisely came on this talk page to suggest that. I don't see the point of re-writing the property's name on that row and everything. I believe it should be renamed to "Type". 1 February 2012
- Hum, so I believe someone should change that... Right now, I'm changing it to only contain the type on every property page I come across, to make changing easier. 9 February 2012
- Erm, could some editor do the other changes I suggested below, and also make the "Type" row use the Type template? 12 February 2012
- Hum, so, yeah, these changes still need to be done... 15 February 2012
- It still needs to be done... 17 February 2012
- Can someone just unprotect this template and the Event one? :/ 17 February 2012
- Is anyone actually reading this? >_> 19 February 2012
- Is anyone actually reading this? >_>
- Can someone just unprotect this template and the Event one? :/
- It still needs to be done...
- Hum, so, yeah, these changes still need to be done...
- Erm, could some editor do the other changes I suggested below, and also make the "Type" row use the Type template?
- Hum, so I believe someone should change that... Right now, I'm changing it to only contain the type on every property page I come across, to make changing easier.
The "In Object" row
I believe the "In Object" row should be edited to link to RBX.lua.{{{name}}} (Object)|{{{name}}} instead of just {{{name}}}. And this is true not only for properties, but for events too. I already did it for the methods template, but the event and the properties template are locked.
Changing this would not only remove the "redirect from blahblah" thing everytime users navigate through the wiki, but it would also fix errors such as when you link to the Instance page, which is a disambiguation page, which requires the user to click 'Instance Object', etc etc..
- Oh, and perhaps we could also rename the "In Object" row to "Member Of"? That's just a suggestion, though. 9 February 2012
cellpadding and cellspacing
The cellpadding and the cellspacing attributes shouldn't be used. Can an editor replace them with CSS?
- btw, this also applies to the Event and the Method templates. 9 February 2012
- Cellpadding can't sensibly be replaced with CSS without access to the stylesheet. Sorry.
Changes
Can some editor unprotect this template and the event one? There are many edits I'd want to do to it, as well as the event one. :/
- Thanks NXTBoy. Anyways, I suggested that we might want to rename "In Object" to "Member Of". Should we do it? That's what the object browser uses, and I feel it would be slightly more correct than "In Object", because "Member Of" makes it clear it is a member of a class, while "In Object" is less straight about what exactly it is. As for the cellspacing and cellpadding attributes, well, we can replace them without access to the CSS stylesheet, but that'd require editing the style attribute for every single table cell, so I think it'd be better to just forget that idea. 19 February 2012
- Oh, and there's also the event template that I wanted to edit. Actually, I want to do the same changes. I think I had also thought of other changes for these, but I probably forgot them. Also, I think we need to find a solution for the link in the title when using duplicates. As an example, if you look here, you'll notice there is a link in the property's name. That's because the page it is on isn't the page it links to, even though it should be. The reason is that we put it on a subpage. Should there be a link argument or something? 19 February 2012
- Ugh, I've just learnt that using : in MediaWiki actually indents by using a dd element, and now, it breaks my heart everytime I use it in talk pages, because that is actually supposed to be used for something else.. :/ Anyways, the same changes need to be done on the event template. 19 February 2012
- Ugh, I've just learnt that using : in MediaWiki actually indents by using a dd element, and now, it breaks my heart everytime I use it in talk pages, because that is actually supposed to be used for something else.. :/ Anyways, the same changes need to be done on the event template.
- Oh, and there's also the event template that I wanted to edit. Actually, I want to do the same changes. I think I had also thought of other changes for these, but I probably forgot them. Also, I think we need to find a solution for the link in the title when using duplicates. As an example, if you look here, you'll notice there is a link in the property's name. That's because the page it is on isn't the page it links to, even though it should be. The reason is that we put it on a subpage. Should there be a link argument or something?