Event execution on the client side in X Evolution 3

Official Content

In GeneXus X Evolution 3 there are new commands that are executed on the client side.

Since previous versions the user events which do not need to perform actions in the server are executed in the client (in the browser).

In GeneXus Evolution 3 more commands are executed client side, not only those which do not need to connect to the server.

We call client side events in this context, to the events which are executed using a javascript routine that executes in the client (and the other part executes in the server), but the page does not refresh at all, and the execution is done asynchronously.

For those events that all the lines of code are executed client side, the entire event is executed in the client. This changes the behavior of the event so it does not execute a Refresh of the entire page, as is characteristic of client-side events.

Note that this is independent from Web User Experience property because when Web User experience= Smooth, all the events are executed client side.

1. Creation and Refresh of web components

In GeneXus Evolution 3, the web components creation and refresh is also executed client-side. This implies that if a user event only includes the creation of a web component or the refresh of a web component, this event is executed in the client. The result is that the corresponding web component is loaded or refreshed but the container object does not execute Start, Refresh or Load Events.

More specifically, if you have the following code, it does not force a full refresh of the page, only the WebComponent1 refreshes.

Event "CreateWebComponent"
    //Here code that also executes client side
    webcomp1.object = WebComponent1.create(&param1,&param2) //webcomp1 is a Web Component control
EndEvent

or

Event "RefreshWebComponent"
    //Here code that also executes client side
    WebComponent1.Refresh()
EndEvent

2. For Each Line Command

In GeneXus Evolution 3, the For Each Line Command is executed client-side as long as the code inside the command is executed client-side. The event which includes the command is executed client-side if all the code can be executed that way.

In summary, the following commands are executed client-side in GeneXus Evolution 3:

Note that this functionality is independent from Web User Experience property.

Note:

The Enter event in web panels in GeneXus Evolution 3 is considered as a user event.

 



Was this page helpful?
What Is This?
Your feedback about this content is important. Let us know what you think.