Trace: • Workscreen Parameters
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
jvx:client:gui:save_settings [2018/02/01 13:18] admin |
jvx:client:gui:save_settings [2020/06/26 11:50] (current) cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ~~Title: Saving Parameters/Settings~~ | ~~Title: Saving Parameters/Settings~~ | ||
| - | Occasionally, settings have to be saved directly at the client so that they can be accessed at a later point in time, or after a new launch of the application. | + | Occasionally, settings have to be saved directly to the client so that they can be accessed at a later point in time or after a new launch of the application. |
| - | Usernames are a good example. After successful login the username is saved at the client and is then used to populate the input field at the next launch of the application. | + | Usernames are a good example. After successful login, the username is saved at the client and is then used to populate the input field at the next launch of the application. |
| To handle the parameters or settings, the following methods are provided by the launcher: | To handle the parameters or settings, the following methods are provided by the launcher: | ||
| Line 16: | Line 16: | ||
| Since the launcher is responsible for saving the data, the application does not need to consider technology dependencies. | Since the launcher is responsible for saving the data, the application does not need to consider technology dependencies. | ||
| - | We would usually have to differentiate between a launch of the application in a web browser, as Web Start (signed, not signed, html) or on the desktop, to decide how data is saved. The web browser administers client data as cookies, and a desktop application either uses configuration files or the registry, depending on the operating system. | + | We would usually have to differentiate between a launch of the application in a web browser, as web start (signed, not signed, html), or on the desktop to decide how data is saved. The web browser administers client data as cookies, and a desktop application either uses configuration files or the registry, depending on the operating system. |
| - | The application and especially the developer, do not have to take these differences into consideration. | + | The application, and especially the developer, do not need to take these differences into consideration. |