|
|
| Line 1: |
Line 1: |
| == How To ==
| | #REDIRECT [[Remote Scripting Setup]] |
| | |
| === Set Up a Web Development Machine ===
| |
| | |
| === Import and Compile an Object Library ===
| |
| | |
| === Debug in a Browser ===
| |
| | |
| == Further Guidance ==
| |
| | |
| === Best Practices ===
| |
| | |
| === Common Upgrade Issues ===
| |
| | |
| === Things You Can't Do In Web ===
| |
| | |
| It's important to understand the thick client and web client are essentially two different user interfaces for Grooper. While the functionality is similar, there are necessarily differences in how Grooper is programed to function installed and running using a machine's operating system versus how Grooper is programed to function using web calls.
| |
| | |
| Due to this, there are certain things that scripts may have been able to accomplish in the thick client that they '''''cannot''''' in the web client '''''or''''' will need to be rewritten with web functionality in mind.
| |
| | |
| ==== Field Entry and Exit in Data Model Scripts ====
| |
| | |
| The web client does not register an event for when a '''Data Field''' is entered or when it is exited in a '''Review''' step's '''Data Viewer'''. Therefore, you cannot script events based around field entry or exit in the web client.
| |
