Page History

...

which is expanded by angular to real html. So every

Every webcomponent gets a number of parameters/objects pushed to the webcomponent instance:

• svy-model: This has object contains all the properties set in the designer or at runtime (if they are data driven like a dataprovider property), it reflects the model object defined in the spec.
• svy-handlers: This has object contains all the event functions that are set in the designer like "onclick" or "ondatachange"
• svy-api: On this object the webcomponents needs to add has contains all the functions for the api calls that which the server can call. Like , like a requestFocus function.

There are a couple of special environment parameters/objects:

• svy-apply: This is a special method that a webcomponent can use to let the server know a property (of the model) is changed. So the value can be applied also on the server (pushed into the record), If a component has fields that uses ng-model then the contains a function to tell the server the dataprovider type properties have to be delegated to deeper/persistent model. When invoked the dataprovider value's are delegated from server component model to the record. To ease the component coding an shortcut can be used, when a component uses "ng-model" directive, the additional directive "svy-autoapply" can be used in the html template instead of coding it out in the webcomponent javascript file.servoyApi: This is a component that holds some special servoy api functions to call, currently to prevent having the component logic calling to svy-apply function.
• svy-servoyApi: an object which provides Servoy environment functions to be used at client side logic, currently it contains "setFormVisibility(form,visible,[relation]);"