custom-widgets

Custom & Pluggable Widgets in MDL

Built-in Pluggable Widgets

GALLERY

Card-layout list with optional template content and filters.

gallery galleryName (
  datasource: database from Module.Entity sort by Name asc,
  selection: single | multiple | none,
  DesktopColumns: 3,
  TabletColumns: 2,
  PhoneColumns: 1
) {
  template template1 {
    dynamictext title (content: '{1}', contentparams: [{1} = Name], rendermode: H4)
    dynamictext info  (content: '{1}', contentparams: [{1} = Email])
  }
  filter filter1 {
    textfilter   searchName  (attribute: Name)
    numberfilter searchScore (attribute: Score)
    dropdownfilter searchStatus (attribute: status)
    datefilter   searchDate  (attribute: CreatedAt)
  }
}

• template block -> mapped to content property (child widgets rendered per row)
• filter block -> mapped to filtersPlaceholder property (shown above list)
• selection: none omits the selection property (default if omitted)
• DesktopColumns, TabletColumns, PhoneColumns control responsive grid columns (default: 1 each, omit if default)
• Children written directly under GALLERY (no container) go to the first slot with mdlContainer: "template"

COMBOBOX

Two modes depending on the attribute type:

-- Enumeration mode (Attribute is an enum)
combobox cbStatus (label: 'Status', attribute: status)

-- Association mode (Attribute is an association)
combobox cmbCustomer (
  label: 'Customer',
  attribute: Order_Customer,
  datasource: database Module.Customer,
  CaptionAttribute: Name
)

• Engine detects association mode when datasource is present (hasDataSource condition)
• CaptionAttribute is the display attribute on the target entity
• In association mode, mapping order matters: DataSource must resolve before Association (sets entityContext)

Charts (Mendix Charts.mpk)

Charts are pluggable widgets authored by their package id. Install Charts.mpk into the project's widgets/ folder first (any Charts-based app has it); exec auto-generates the .def.json.