Difference between revisions of "Template talk:LSL Function"
Jump to navigation
Jump to search
m (→TODO) |
|||
| Line 2: | Line 2: | ||
While this todo list is specific for LSL Functions, it doubles as the suggestion table for LSL Events, Constants and Conditionals. | While this todo list is specific for LSL Functions, it doubles as the suggestion table for LSL Events, Constants and Conditionals. | ||
* New hidden category sorting LSL topics by bug count. -- Easy | * #var:type collision between templates, causes errors in the documentation. Rename variable -- Annoying | ||
* New hidden category sorting LSL topics by bug count. -- Easy (Done I think) | |||
* Move all parameters to variables to work around 1.12 parser changes. -- Easy | * 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 | * fix func-id for pre-release documentation & LSL_Functions/ID sort. -- Annoying | ||
| Line 8: | Line 9: | ||
* Disable category inclusion for requests? | * 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 | * 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? | * Change History section to a table? - Bad Idea | ||
---- | ---- | ||
Revision as of 11:57, 1 March 2009
TODO
While this todo list is specific for LSL Functions, it doubles as the suggestion table for LSL Events, Constants and Conditionals.
- #var:type collision between templates, causes errors in the documentation. Rename variable -- Annoying
- New hidden category sorting LSL topics by bug count. -- Easy (Done I think)
- 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? - Bad Idea
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.