Touch UI Concepts - Granite UI, Coral UI

Touch enabled UI being the standard UI for AEM, is based on Coral UI and Granite UI. (not an open source project.)

Coral UI : We can classify this further as Javascript components offering functionality and CSS-only components
Granite UI: Components built with Coral UI to provide UI widgets.

Example of Coral UI as Javascript component:

  • Components/functionalities like accordion/tabs which we usually/previously would have done using HTML markup with some jQuery plugins to bring out the final outcome as accordion/tabs. 
  • In Coral UI, the same is exposed to us via tags named <coral-accordion>, <coral-accordion -item> and other related tags for a particular feature.

Example of Coral UI as CSS-only component:

  • Dialog fields which are in the form of HTML input tag (say pathbrowser/pathfield), has classes named coral-InputGroup, coral-InputGroup-input(targeting input tag), coral-InputGroup-button(targeting the button with icon -> click of which lets us select a path) which has attributes contributing to the look and feel of the field.

Granite UI component example:
  • ResourceType/components that we use to form a touch UI dialog constitute a Granite UI component.
  • It is not limited to dialog fields, instead there is more to it. (Ex: Granite UI admin components build on foundation components, say Global Navigation, Search Panel.) 
  • By the term "Granite UI components built with coral UI", it means that CSS class/selectors exposed to us via Coral UI is made use of in the Granite UI component.
    • In this case, for a pathfield/pathbrowser component, classes mentioned above is used while framing the input tag.

Granite UI components available at

  • /libs/granite/ui/components/foundation are components based on coralui2.
    • Clientlibs are available in the category named "granite.ui.foundation", "granite.ui.foundation.admin"
  • /libs/granite/ui/components/coral/foundation are components based on coralui3
    • Clientlibs are available in the category named "granite.ui.coral.foundation"

Changes on CoralUI3 being API streamlining, removing deprecated feature with respect to previous version. Details on differences to be covered in next post.

Screenshots for reference:
<coral-columnview> component: Sites console in column view makes use of Coral.ColumnView component.


Granite UI pathbrowser component making use of css-only Coral UI: (in the form of selectors)

 coral-InputGrop-input :  selector targeting input
coral-InputGroup-button : selector targeting button
coral-Icon--folderSearch : responsible for displaying the folder icon along with the class -coral-Icon.

Reference: Adobe Helpx links on Granite UI and Coral UI

Comments

Post a Comment

Popular posts from this blog

Embedding Third party dependency/OSGi bundle in AEM application hosted in AEMasCS

Image
This post illustrate the ways of embedding third party dependency in AEM maven project. Steps are mentioned considering the project structure to be followed for AEMasCS while the same can be followed for classic versions too.  Before we begin, I would like to explain the scenario of including a dependency in our AEM maven project.  When we would like to make use of an API that is not already available in our project, we look for that in maven-central repository and specify the dependency in main pom.xml and desired module's pom.xml file. (Lets say, AWS S3 Java SDK V2 dependency) Upon updating the project in the IDE, we would see our class files (making use of those APIs) are compiled/build successfully without any errors.  Now, in the context of AEM/OSGi environment, when the same package and hence the bundle is deployed to AEM instance, dependencies that we added new might not be resolved/available in the OSGi as a bundle. Something like the below This indicates that the added dep
Read more

OSGI Factory Configuration implementation

OSGI Factory configuration is used to have many instances of an OSGI config (represented/identified via an identifier) for the single OSGI service/PID. Most often used OOB Factory configurations for example: Logger Factory/writer configuration (for log statements) Service user Mapper service Amendment (for using service resource resolver in projects) Few sample real time use case for the need of OSGI factory config: For multi tenant projects, if we have generic service used across tenants with properties/attributes specific to tenant. For single tenant, generic service targeting all locales with properties/attributes specific to locale. (where generic service -> holds logic in the lines of calling third party service for retrieving/updating information.) Implementation: ( In terms of OSGI R6 annotations ): Create Object Class Definition(OCD) defining desired properties for the OSGI service. - OSGIFactoryConfigOCD.java OSGI Service/Factory service to retrieve
Read more

Creation of Template Types for Editable templates

Image
In this post, we will create templates types which is the base for creating editable templates. Before getting to the subject directly, have added an introduction about templates in general. Template is the base for creating pages. Starting AEM 6.2, we have categorisation for templates - Static and Editable templates. Static templates :  This has been available for several versions of AEM/CQ Created using "Create Template" option with base page component as resourceType (which is responsible for rendering the page structure).  Template ( base page component as resourceType ) -> Page This cannot be edited as such. Since it just holds a reference to base page component, any changes to the page (other than authorable components), would need a change in base page component which is ultimately a work of developer. (calls for a code change) Allowed components are configured using Design mode (list being saved to etc/designs/projectfolder/templatename/jcr:content)
Read more