Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "RAP/Incubator/ClientScripting"
(enahnced introduction) |
(github link) |
||
| Line 6: | Line 6: | ||
The scripts themselves are written in JavaScript on a SWT-like API. This allows application developer SWT-experience to get started right away, and makes porting between SWT/Java and RAP-ClientScripting fairly easy. Even without any JavaScript-experience, this document should provide you with all the basics. | The scripts themselves are written in JavaScript on a SWT-like API. This allows application developer SWT-experience to get started right away, and makes porting between SWT/Java and RAP-ClientScripting fairly easy. Even without any JavaScript-experience, this document should provide you with all the basics. | ||
| + | |||
| + | The ClientScripting feature is currently in early development, aiming to enable only some specific usecases at first. However, all API published here should be stable and is unlikely (but currently not guarenteed) to change in the future. The project is currently hosted on [https://github.com/tbuschto/rap-clientscripting GitHub]. | ||
== Java API == | == Java API == | ||
| Line 11: | Line 13: | ||
== JavaScript API == | == JavaScript API == | ||
| − | == | + | == Restrictions and Bans == |
== Hints and Best Practices == | == Hints and Best Practices == | ||
Revision as of 10:17, 1 February 2012
Overview
Conventional RAP applications are running almost entirely on a Server, with a thin client only rendering a user interface with some limited interactivity. This has several advantages, but it also means all application-relevant events have to be forwarded to the Server before being processed, causing small delays and traffic. Scenarios where interactions occur with a high frequency, like typing or mouse movements, would therefore be undesirable.
This is where RAP ClientScripting can help. ClientScripting allows developer to handle some of the events directly on the client, without creating any http-requests. This is ideal to customize or enhance the behavior of specific widgets, making it much less often necessary to develop RAP custom-widgets.
The scripts themselves are written in JavaScript on a SWT-like API. This allows application developer SWT-experience to get started right away, and makes porting between SWT/Java and RAP-ClientScripting fairly easy. Even without any JavaScript-experience, this document should provide you with all the basics.
The ClientScripting feature is currently in early development, aiming to enable only some specific usecases at first. However, all API published here should be stable and is unlikely (but currently not guarenteed) to change in the future. The project is currently hosted on GitHub.