Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-40677] Enable users to save custom functions to a list, similar to the list of LSL functions at the bottom of a script #12320

Closed
1 task
sl-service-account opened this issue Oct 11, 2016 · 1 comment

Comments

@sl-service-account
Copy link

sl-service-account commented Oct 11, 2016

How would you like the feature to work?

-Enable users to save custom global functions so they can select and load these functions back into a script at a later date. It would work in the following manner and save people like myself having to keep a folder full of scripts to back up their functions :

  1. The user writes their global function and then goes to File -> Save to function
  2. Then a window will pop up asking the user to enter the start and end line number of the function they wish to save. So the user could enter start line 1 and end line 10.
  3. They will then be asked to name the function and be able to click a save button
  4. To load the function there would be a drop down box next to the LSL function one at the bottom of the script editor that would allow them to select one of their custom saved functions.
  5. The script editor would then load the selected custom function into the script at the point where the cursor currently is. So if the cursor is resting on line 5 then the script editor will load the custom function in at line 5.
  6. There would also be a export function list feature to backup their function list

Why is this feature important to you? How would it benefit the community?

This would enable users to save their functions and code snippets and import them back into they script in a similar manner to other development software and would save the user from having to keep a running library of backup scripts (like i do) that contain these code snippets.

Links

Related

Original Jira Fields
Field Value
Issue BUG-40677
Summary Enable users to save custom functions to a list, similar to the list of LSL functions at the bottom of a script
Type New Feature Request
Priority Unset
Status Closed
Resolution Unactionable
Reporter Eiko Serrta (eiko.serrta)
Created at 2016-10-11T22:44:12Z
Updated at 2016-10-12T18:50:42Z
{
  'Business Unit': ['Platform'],
  'Date of First Response': '2016-10-12T13:50:42.780-0500',
  'How would you like the feature to work?': '-Enable users to save custom global functions so they can select and load these functions back into a script at a later date. It would work in the following manner and save people like myself having to keep a folder full of scripts to back up their functions :\r\n\r\n1. The user writes their global function and then goes to File -> Save to function\r\n2. Then a window will pop up asking the user to enter the start and end line number of the function they wish to save. So the user could enter start line 1 and end line 10.\r\n3. They will then be asked to name the function and be able to click a save button\r\n4. To load the function there would be a drop down box next to the LSL function one at the bottom of the script editor that would allow them to select one of their custom saved functions. \r\n5. The script editor would then load the selected custom function into the script at the point where the cursor currently is. So if the cursor is resting on line 5 then the script editor will load the custom function in at line 5.\r\n6. There would also be a export function list feature to backup their function list',
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'Target Viewer Version': 'viewer-development',
  'Why is this feature important to you? How would it benefit the community?': 'This would enable users to save their functions and code snippets and import them back into they script in a similar manner to other development software and would save the user from having to keep a running library of backup scripts (like i do) that contain these code snippets.',
}
@sl-service-account
Copy link
Author

Kyle Linden commented at 2016-10-12T18:50:43Z

Hello Eiko,

Thank you for your suggestion. The team has reviewed your request and determined that it is not something we can tackle at this time.
Please be assured that we truly appreciate the time you invested in creating this feature request, and have given it thoughtful consideration among our review team. This wiki outlines some of the reasoning we use to determine which requests we can, or can't, take on: http://wiki.secondlife.com/wiki/Feature_Requests

Thanks again for your interest in improving Second Life.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant