User talk:Anaminus/API Documentation Changes: Difference between revisions
From Legacy Roblox Wiki
Jump to navigationJump to search
>Anaminus |
>NXTBoy |
||
| Line 4: | Line 4: | ||
:I would be tempted to go for {{`|Object}}. API is a reasonable fit as well. {{User:NXTBoy/sig|date=08:26, 5 May 2012 (UTC)}} | :I would be tempted to go for {{`|Object}}. API is a reasonable fit as well. {{User:NXTBoy/sig|date=08:26, 5 May 2012 (UTC)}} | ||
:: I initially went against {{`|Object}} because member pages would be included under the namespace, but they're not "Objects". Thinking about it just now, since a member page would only be a subpage of an object page, {{`|Object}} may work after all. --[[User:Anaminus|Anaminus]] 04:37, 5 May 2012 (EDT) | :: I initially went against {{`|Object}} because member pages would be included under the namespace, but they're not "Objects". Thinking about it just now, since a member page would only be a subpage of an object page, {{`|Object}} may work after all. --[[User:Anaminus|Anaminus]] 04:37, 5 May 2012 (EDT) | ||
==Possible implementation, retaining autonomy== | |||
I've had a go at building a new template backend for a system like this. Unlike the old one, the data goes on the same page as the one presented to the user, and there are no auxiliary pages like /superclass and /properties. Have a look at them at [[User:NXTBoy/Instance]], [[User:NXTBoy/BasePart]], and [[User:NXTBoy/Part]] {{User:NXTBoy/sig|date=09:29, 5 May 2012 (UTC)}} | |||
Revision as of 09:29, 5 May 2012
"API" Namespace
Does "API" make a good name? Does it describe the contents of the namespace? (a reference/documentation of Roblox classes) Alternatives might be "ClassRef", or "ObjectBrowser", I'm not really sure. Any suggestions? --Anaminus 01:41, 5 May 2012 (EDT)
- I would be tempted to go for Object. API is a reasonable fit as well.
- I initially went against Object because member pages would be included under the namespace, but they're not "Objects". Thinking about it just now, since a member page would only be a subpage of an object page, Object may work after all. --Anaminus 04:37, 5 May 2012 (EDT)
Possible implementation, retaining autonomy
I've had a go at building a new template backend for a system like this. Unlike the old one, the data goes on the same page as the one presented to the user, and there are no auxiliary pages like /superclass and /properties. Have a look at them at User:NXTBoy/Instance, User:NXTBoy/BasePart, and User:NXTBoy/Part
