SEAL Script suggestions QOL-improvements

[FilipSteijner]

Hi i have a few suggestions for some nice quality of life improvements in SEAL script.

* Highlighting a text and pressing CTRL + F to automatically fill the find-textbox with the highlighted string.

* CTRL + S to save the open script.

* When trying to close the SEAL app, a confirm popup if the open script has unsaved changes.

* Some sort of cache if SEAL were to unexpectedly crash or you get logged out and has unsaved changes.

* Option to run script without being connected to a server, just to debug the code (not important but would be nice).

* Since we are working with many different versions of servers it would be nice to see in the editor at what version certain commands was added (again not super important but would be nice).

* Ability to show images in the "Parameters" view to show some examples for users.

* Ability to attach files, to include examples for users.

* Built in "are you sure" confirmation window/modal where user has to insert a specific string to confirm, instead of just ok/cancel or yes/no. (maybe this is already possible with custom code? but would be great with a template in the sealScript-interface).

* Access to the SEAL-interface modals, instead of default javascript confirm/popup, which cannot contain much text before its unreadable.

[FilipSteijner]

EDIT:
Forgot to also mention that if previous connected servers could get saved in a list would also be nice to have. And last successful connected host is pre populated as the host when clicking "Click here to connect". (basically same way as workstation is behaving)