Child pages
  • WebLayouts

Versions Compared

Key

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

...

Code Block
languagejs
titlelayout spec file definition
{
	"name": "String componentnamelayout name",
	"displayName": "String more descriptive name that is shown in the designer",
	"version": the version, the same as for the components (integer),
	"definition": "A reference to the jsjson file of this layout",
	"icon": "A reference to the icon shown in designer",
	"contains": ["Specifies an array of components/layouts which can be added to this layout container"],
	"topContainer": "Used to determine whether this layout container can be added directly into the root of the form",
	"tagType":"The tag type for HTML output. The default value is 'div'",
	"model": {
		 "propertyName": type description, optional default value - the model properties are generated
					     on the tag as HTML attributes
         "tagType": "string"  // optional attribute if the tagType should be configurable in the developer
	}
}

 

It is worth to mention that the 'tagType' property is a bit more special. It is a top level property which specifies the default value for the tagType, but it can also be a model property. In this case, it shows in the properties view and the user is able to change its value.

The json config file is for the default properties (class="row") which are not changeable by the servoy developer (if the model area of the spec file doesn't  specify them) but also for making composite layouts, so you can drop full structures at once.

 

Code Block
languagejs
titlelayout json definition file
{
	"layoutName":"The real name of the toplevel layout if this layout component is a composition of layouts (optional)",
	"class":"The css class to be applied to the layout container (optional)"
	"children": "An array of child components/layouts with their default values (optional)"
}

...