Child pages
  • Specification (.spec file)
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Webcomponents need meta data to be able to function in a (form) designer

On the web are some specs arising like:

http://www.openajax.org/member/wiki/OpenAjax_Metadata_1.0_Specification_Widget_Overview (thanks to Paul for pointing us to this one)

But i think this overly complex when using angular directives...

 

For example if our field component can be expressed as:

<datafield dataProviderID="record.order_id" toolTipText="hello world"/> (which is expanded to regular html by angular)

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:

datafield.spec
{
	dataProviderID: dataprovider,
	toolTipText: string,
	x: int,
	y: int,
	w: int,
	h: int,
	bgColor: color
}

Basically the stuff our content spec describes for element types.

 

For the prototy we could even generate these for all default "servoy" components.

  • No labels