App Builder

Index of ContentsApp views

An App Builder app can have one or more app views in which you can place whatever app controls. The first app view in the views list are considered the app home, and it's the view which are show when the app start. An app must have at least one view (the home) but can have other views which you can use to store the app options, show the app about, etc.

In order to show an specific view of your app you can use the ShowView action or the ShowDialog action. This first one just replace the app current view with the view you specified in the action. The second one show the specified view as a modal dialog, in the front of the current app view. In this last case you need to provide a way to close the dialog view and for that you can use the CloseDialog action.

App views properties

When you click an app view in the designer, whe object inspetor show you various app view properties. In fact you can define special CSS style for the app view in three possible states: normal, hover and focused. These CSS styles are applied later in the appropiate app view state. However I want to point you into the app view Animation property. You can choose a CSS animation from the object inspector Animation list, and this animation are performed when your app view are show to the user. You can choose from a bunch of animations ready to use, and, these are perfect if you are developing an app which show various views in a sequence, for example, some kind of presentation in your app.

Master views

Every application have a Master view by default. This view is equal than the others, except their controls are draw in every other application's views who have set their "DrawMaster" variable/option to "True". Masters views are useful because we can place a Push button control into it, for example, and then such control appear automatically in every app's view that we wanted.

Master view events are executed before normals views events. Master view style are set before normals views too, so normal views styles overrides Master view styles. Master view controls are draw before normals views too. Master views does not have an "Event" variable, like any other view. If you use the Master "Click" event, for example, the "Event" variable available is the current view "Event" variable.

App views events

All the app views exposes some events which you can use in order to prepare your desired behaviour when an app view is show, clicked (or tap), double clicked (or double tap), etc. Below you can found the description of all the available app events. You can also take a look at the App events and control events.

Show event

This event is fired when an app view is shown. This default (first) app view launch this event when is shown, and also all other app views fired this event when are shown using something like the ShowView action.

This event is supported in all platforms including web browsers.

Click event

This event is fired when an app view receive a click or tap from the user. Note that almost all app controls have their own "Click" event.

This event is supported in all platforms including web browsers.

DblClick event

This event is fired when an app view receive a double click or double tap from the user. Note that almost all app controls have their own "DblClick" event.

This event is supported in all platforms including web browsers.

SwipeLeft event

This event is fired when an app view receive the swipe left gesture from the user.

This event is supported in all platforms including web browsers.

SwipeRight event

This event is fired when an app view receive the swipe right gesture from the user.

This event is supported in all platforms including web browsers.

MouseUp event

This event is fired when the mouse is up on the app view part of the browser screen.

This event is supported in all platforms including web browsers.

MouseDown event

This event is fired when the mouse is down on the app view part of the browser screen.

This event is supported in all platforms including web browsers.

MouseEnter event

This event is fired when the mouse enter in the app view part of the browser screen. This event is more useful if your app is not scaled, that is, do not occupy all the web browser screen. Note that almost all app controls have their own "MouseEnter" event.

This event is supported when your app is running in a web browser.

MouseLeave event

This event is fired when the mouse leave the app view part of the browser screen. This event is more useful if your app is not scaled, that is, do not occupy all the web browser screen. Note that almost all app controls have their own "MouseEnter" event.

This event is supported when your app is running in a web browser.

ContextMenu event

This event is fired when the user right click over the app view for a context menu. You can disabled the default browser context menu by use the PreventDefault action.

This event is supported when your app is running in a web browser.

KeyUp event

This event is fired when the user press up a key. The [ViewName.Event] variable store the key event, so, for example, we can access the pressed key code like: [ViewName.Event.keyCode].

KeyDown event

This event is fired when the user press down a key. The [ViewName.Event] variable store the key event, so, for example, we can access the pressed key code like: [ViewName.Event.keyCode].