Template talk:Method

Could an editor make this template skip the redirect in the object part and make it link directly to the "RBX.lua.Object_(Object)" page? Sometimes, the page with the same name as the object's name is a disambiguation page or something else. Some examples are the Toolbar page(used with plugins) and the Instance page (a disambiguation page). Instead, they should link to the RBX.lua.Object_(Object) page directly.

JulienDethurens 

31 January 2012

The objects argument

I strongly disagree with considering a method (or a property, or an event) as belonging to many different objects, as that is not possible and is not the case. I believe we should just make a different page for each of them, just like what we do already with certain of them. Considering them as being the same method is just wrong. --JulienDethurens 19:13, 7 April 2012 (EDT)

Messed up template...?

Methods don't show the "In Object" category for some reason... Flurite - 11:46, 9 April 2012 (UTC)

You're right... Yet, I was sure I had checked if everything was fine. Gonna fix it, sorry. --JulienDethurens 14:58, 9 April 2012 (EDT)

Fixed. --JulienDethurens 15:05, 9 April 2012 (EDT)

Deprecation

I'm putting this here, but it'd also apply to the {{Event}} and the {{Property}} templates...

What about we add a deprecated argument to templates?

We could make it put a line through the name of the member.

Putting a line through the name of deprecated items seem to be how we mark stuff as deprecated on this wiki (it is done in the function dump, and the deprecated template does it too). And it would also allow us to give a different style to all the deprecated members on the wiki in only three edits if we ever feel a need to do so.

Good or bad idea? --JulienDethurens 20:31, 25 April 2012 (EDT)

I don't why this isn't already here. I recommend a status option, with a value of either preliminary or deprecated. I also suggest holding off until we get around to making CSS changes, because doing this will be ridiculously easy with CSS.

The status option is a good idea. An object will never be both deprecated and preliminary. And we can know if it is one or the other with the {{ifeq}} template. Such arguments, even if they're not even being used, can be useful, since, in the future, we might want to use them. --JulienDethurens 20:45, 25 April 2012 (EDT) ; edited 20:45, 25 April 2012 (EDT)