Page History

...

Types are defining internal types that are used by this webcomponent for one or more of its properties.  (for example a tabpanel component has a tab type that describes one tab inside the tabpanel). They have the same support as under model:{}, there is no support for api or handlers on those types again because they are just container objects that push data to the webcomponent from the server.

...

Besides that the type description can be a simple (property) types like:

...

string: A plain string property 

...

tagstring: A string that can have tags inside it (so it will be processed by servoy to have tags replaced before it gets to the client)

...

color: A color property (#FFFFFF)

...

point: A point representation \{x:10,y:20\}

...

dimension: A dimension representation \{width:100,height:200\}

...

insets:

...

font:

...

border:

...

boolean: true/false

...

scrollbars:

...

byte: 

...

double: A floating point number

...

float: A floating point number

...

int: A number

...

long: A number

...

short: A number

...

values: Fixed values can have real/display values.

...

dataprovider: Servoy maps this on a record or scope variable, This can be a complex object: \{ 'type':'dataprovider', 'ondatachange': \{ 'onchange':'onDataChangeMethodID', 'callback':'onDataChangeCallback'\}\} if support for ondatachange is needed.

...

valuelist: Servoy maps this on a valuelist referene

...

form: This property will hold a url point to a form (like a tab in a tabpanel)

...

format: format property, this must be specified with a complex object like: \{'for':'dataProviderID' ,'type':'format'\} so that we know which dataprovider property must be used to map this format property on

...

relation: Servoy maps this on a relation reference

...

media:

custom type descriptions any of the default provided property types can be used.

The function description in the handlers section can be just "function" or a more complex type describing the arguments and return type

...