Child pages
  • Specification (.spec file)

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For example if our field component can be expressed as:

Code Block
<datafield dataProviderID="record.order_id" toolTipText="hello world" onAction="true"/>

...

 

We only need to know the list of all parameters/properties and which types they are, so a beaninfo spec. (json) as below would suffice:

Code Block
titledatafield.spec
{
	dataProviderID: "dataprovider",
	toolTipText: "string",
	x: "int",
	y: "int",
	w: "int",
	h: "int",
	bgColor: "color",
	onAcion: "function"
}

Basically the stuff our content spec describes for element types.

...

For the prototy we could even generate these for all default "servoy" components, like datafield, databutton,etc.