Child pages
  • Packaging

Versions Compared

Key

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

...

Name: componentname/componentname.spec
Web-Component: True

----

The MANIFEST.MF file can include libraries dependancies. In case web components of the same package requires the same library dependancies let the MANIFEST.MF file to include the libraries dependancies instead of including the same library in the .spec file of each web component.

JS-ClientLibs: packagename/lib/filename.js;name=libraryname;version=3.3.1, packagename/lib/anotherfile.js;name=anotherlibrary;version=3.3.1
JS-DesignLibs: packagename/lib/filename.js;name=libraryname;version=3.3.1, packagename/lib/anotherfile.js;name=anotherlibrary;version=3.3.1
CSS-ClientLibs: packagename/lib/filename.css;name=cssname;version=3.3.1
CSS-DesignLibs: packagename/lib/filename.css;name=formdesignercss;version=3.3.1

If DesignLibs are user in the Form editor only. Is possible to customize the look & feel of web components in the form designer to improve the experience in the editor. For instance would be possible to define a min-height and min-width for the web-component so that can be selectable in the form editor.

By default, a package and its contents is displayed in the HTML editor palette for each of the two types of forms: Responsive-Layout and Absolute-Layout. In order to include a package only when editing one type of form, the MANIFEST.MF file should also contain one of the two lines below

Responsive-Layout: True

Absolute-Layout: True