Difference between revisions of "Template talk:LSL Function"
Jump to navigation
Jump to search
(→TODO) |
|||
| Line 15: | Line 15: | ||
* Get/Set Caveat separation for sub-templates #var:caveats_set, #var:caveats_get, will aid in using the templates for constants. -- Tedious | * Get/Set Caveat separation for sub-templates #var:caveats_set, #var:caveats_get, will aid in using the templates for constants. -- Tedious | ||
* Change History section to a table? - Tedious. History section format and layout needs standardizing first. | * Change History section to a table? - Tedious. History section format and layout needs standardizing first. | ||
---- | |||
Modernization of Generic: | |||
* Setup bug counting in category thingy | |||
---- | ---- | ||
Revision as of 22:12, 2 February 2010
TODO
While this todo list is specific for LSL Functions, it doubles as the suggestion table for LSL Events, Constants and Conditionals.
- See Also-Examples should be moved into Examples section -- Will need better name.
- Split Issues into Issues and Bugs, put bugs into Caveats - Done for functions & constants.
- Rename Caveats to "Take Note" or "Be Aware"
- Promote Issues subsction into Notes. -- Easy
- JIRA Search link. In notes? -- Easy - done for functions & constants.
- #var:type collision between templates, causes errors in the documentation. Rename variable -- Half Done
- New hidden category sorting LSL topics by bug count. -- Easy (Done for functions)
- Move all parameters to variables to work around 1.12 parser changes. -- Easy
- fix func-id for pre-release documentation & LSL_Functions/ID sort. -- Annoying
- Common Mistakes section?
- Disable category inclusion for requests?
- Get/Set Caveat separation for sub-templates #var:caveats_set, #var:caveats_get, will aid in using the templates for constants. -- Tedious
- Change History section to a table? - Tedious. History section format and layout needs standardizing first.
Modernization of Generic:
- Setup bug counting in category thingy
An item may live on the list for a long time because
- It's half baked. These are marked with question marks. Typically there are good reasons not to implement them, there are many ways of implementing it, or there isn't a pressing need.
- It would take a lot of work to implement. Some items may involve editing hundreds of pages.
Changes to the uniform style are typically tried out on the Events first, there aren't that many of them and making multiple changes doesn't hurt the wiki as much as making a change to either Functions or Constants. Conditionals is often forgotten during the update cycle.