We have just completed our first tour of using JavaScript to customize WaveMaker applications. We started with events. The custom JavaScript we write in our application is invoked in response to events. When working with server response data, we must always wait until the onSuccess or onResult events to ensure the service call has returned.
We also studied wm.Variable, the non-visual variable component. Unlike JavaScript variables, wm.Variable can be bound to other components and manipulated via code. We can use wm.Variable to customize widget datasets and filter live variables. Finally, we looked at the references available to use. From the API reference to the completions available to us in Studio and the console, there are multiple ways to learn more.
In the next chapter, we will continue our use of JavaScript to customize the user experience. We'll look at some advanced techniques such as creating components at runtime. We will also discuss examples of common operations such as...