Expand my Community achievements bar.

SOLVED

Diff. between a Widget vs. Component

Avatar

Former Community Member

Hi,

        What is the difference between a Widget and a Component. For ex:- "text" component is using a widget called "componentStyle".

        Why a component shd. use Widget? What is the speciality of a Widget? 

        In what technology a Widget can be created? Is ExtJs is the prime technology that is being used?

regards

1 Accepted Solution

Avatar

Correct answer by
Level 9

The widget library used by CQ, called ExtJS, provides the highly polished user interface elements that work across all the most important browsers and allow the creation of desktop-grade UI experiences.

Widgets provides controls for authors to input their data, widgets are included in dialog box E.g. textfield, radio buttons, checkboxes etc are widgets

They are written in extjs framework.

Components:

  • are modular units which realize specific functionality to present your content on your website
  • are re-usable
  • are developed as self-contained units within one folder of the repository
  • have no hidden configuration files
  • can contain other components
  • can run anywhere within any CQ system. They can also be limited to run under specific components
  • have a standardized user interface
  • use widgets
  • have an edit behaviour that can be configured

View solution in original post

1 Reply

Avatar

Correct answer by
Level 9

The widget library used by CQ, called ExtJS, provides the highly polished user interface elements that work across all the most important browsers and allow the creation of desktop-grade UI experiences.

Widgets provides controls for authors to input their data, widgets are included in dialog box E.g. textfield, radio buttons, checkboxes etc are widgets

They are written in extjs framework.

Components:

  • are modular units which realize specific functionality to present your content on your website
  • are re-usable
  • are developed as self-contained units within one folder of the repository
  • have no hidden configuration files
  • can contain other components
  • can run anywhere within any CQ system. They can also be limited to run under specific components
  • have a standardized user interface
  • use widgets
  • have an edit behaviour that can be configured