ExtReact Docs Help

Introduction Terms, Icons, and Labels Access Levels Member Types Member Syntax Member Flags Class Icons Member Icons Navigation and Features Class Member Quick-Nav Menu Getter and Setter Methods History Bar Search and Filters API Doc Class Metadata Expanding and Collapsing Examples and Class Members Desktop -vs- Mobile View Viewing the Class Source

Introduction

The documentation for the ExtReact product diverges somewhat from the documentation of other Sencha products. The sections below describe documentation for all products except where indicated as unique to ExtReact.

Terms, Icons, and Labels

Many classes have shortcut names used when creating (instantiating) a class with a configuration object. The shortcut name is referred to as an alias (or xtype if the class extends Ext.Component). The alias/xtype is listed next to the class name of applicable classes for quick reference.

ExtReact component classes list the configurable name prominently at the top of the API class doc followed by the fully-qualified class name.

Access Levels

Framework classes or their members may be specified as private or protected. Else, the class / member is public. Public, protected, and private are access descriptors used to convey how and when the class or class member should be used.

Public classes and class members are available for use by any other class or application code and may be relied upon as a stable and persistent within major product versions. Public classes and members may safely be extended via a subclass.
Protected class members are stable public members intended to be used by the owning class or its subclasses. Protected members may safely be extended via a subclass.
Private classes and class members are used internally by the framework and are not intended to be used by application developers. Private classes and members may change or be omitted from the framework at any time without notice and should not be relied upon in application logic.

Member Types

Config - The configuration options for a class.
ExtReact component classes display configuration options as props
Property - Set once a class is instantiated. *See Read Only below.
ExtReact component classes do not list properties as a dedicated member type, but rather as read only props
Method - Actions that can be performed by a class. Methods should be read as instance methods and can only be called from a instance of a given class. Static methods that can be called directly from the class itself will have a static label next to the method name. *See Static below.
Event - Events are specific to the framework event system allowing for classes to programmatically raise an event to be handled by one or more event handler methods. DOM events, while handled by the framework event system, are not specifically described within the API documentation. *For DOM events refer to the event reference page from MDN.
Theme Variable - Variables used by the visual theme engine employed by the framework.
Theme Mixin - Functions used by the visual theme engine employed by the framework and may use values set in various Theme Variables.

Member Syntax

Below is an example class member that we can disect to show the syntax of a class member (the lookupComponent method as viewed from the Ext.button.Button class in this case).

Ext.container.Container

view source

lookupComponent ( item ) : Ext.Component

protected

Called when a raw config object is added to this container either during initialization of the items config, or when new items are added), or {@link #insert inserted.

This method converts the passed object into an instanced child component.

This may be overridden in subclasses when special processing needs to be applied to child creation.

Parameters

item : Object

The config object being added.

Returns

Ext.Component

The component to be added.

Let's look at each part of the member row:

Expand/Collapse - On the left-hand size of the member row is a control used to expand and collapse each member row to show / hide member details.
Member Name - The name of the class member (lookupComponent in this example)
Method Param - Any required or optional params used by a method (or passed to an event handler method) will be listed next to the method name within parenthesis (( item ) in this example)
Return type - The class instance or javascript object returned by the method or property (Ext.Component in this case). This may be omitted for methods that do not return anything other than undefined or may display as multiple possible values separated by a forward slash / signifying that what is returned may depend on the results of the method call (i.e. a method may return a Component if a get method calls is successful or false if unsuccessful which would be displayed as Ext.Component/Boolean).
Flags - Any flags applicable to the member will be displayed next (PROTECTED in this example - see the Flags section below)
Member Origin - On the right-hand side of the member row is the class where the member was initially described (Ext.container.Container in this example). The source class will be displayed as a blue link if the member originates from the current class and gray if it is inherited from an ancestor or mixed-in class.
Member Source - On the right-hand side below the member origin class is a link to view the member's source (view source in the example)
Params List - Each param for a class method will be listed using the same name found above in parenthesis, the type of class or object expected, and a description of the param (item : Object in the example).
Returns - If a class returns a value other than undefined a "Returns" section will note the type of class or object returned and a description (Ext.Component in the example)
Since (not shown in the example) - Some members will show which version of the product the member was first introduced (i.e. Available since 3.4.0 - not pictured in the example) just after the member description
Default (not shown in the example) - Configs often show the default config value to be applied to a class instance if not overridden (i.e. Defaults to: false)

Member Flags

The API documentation uses a number of flags to further commnicate the class member's function and intent. The label may be represented by a text label, an abbreviation, or an icon.

Required - Required config when instantiating a class
Bindable - The config has a setter which allows this config to be set via ViewModel binding
All ExtReact props are bindable unless decorated as immutable
Immutable
Immutable ExtReact props may not be use as a configurable prop when instantiating a component
Read Only - The property may be read, but cannot be used to configure / re-configure a class instance at runtime
Singleton - Singleton classes are instantiated immediately once defined and may not be instantiated manually
Static - A static method or property is a method or property belonging to the class itself, not an instance of the class
Chainable - Refers to methods that return the class instance back when called.
This enables chained method calls like: classInstance.method1().method2().etc();
Deprecated - A class or member that is scheduled for removal in a future framework version and is provided in the current version for backwards compatibility.
Deprecated classes and members will have a message directing you to the preferred class / method going forward.
Removed - A removed class or member that exists in documentation only as a reference for users upgrading between framework versions
Template - A method defined within a base class designed to be overridden by subclasses
Abstract - A class or member may be be defined as abstract. Abstract classes and members establish a class structure and provide limited, if any, code. Class-specific code will be furnished via overrides in subclasses.
Preventable - Events marked preventable will not fire if false is returned from an event handler

Class Icons

- Indicates a framework class

- A singleton framework class. *See the singleton flag for more information

- A component-type framework class (any class within the Ext JS framework that extends Ext.Component)

- Indicates that the class, member, or guide is new in the currently viewed version

Member Icons

- Indicates a class member of type config

Or in the case of an ExtReact component class this indicates a member of type prop

- Indicates a class member of type property

- Indicates a class member of type method

- Indicates a class member of type event

- Indicates a class member of type theme variable

- Indicates a class member of type theme mixin

- Indicates that the class, member, or guide is new in the currently viewed version

Just below the class name on an API doc page is a row of buttons corresponding to the types of members owned by the current class. Each button shows a count of members by type (this count is updated as filters are applied). Clicking the button will navigate you to that member section. Hovering over the member-type button will reveal a popup menu of all members of that type for quick navigation.

Getter and Setter Methods

Getting and setter methods that correlate to a class config option will show up in the methods section as well as in the configs section of both the API doc and the member-type menus just beneath the config they work with. The getter and setter method documentation will be found in the config row for easy reference.

ExtReact component classes do not hoist the getter / setter methods into the prop. All methods will be described in the Methods section

History Bar

Your page history is kept in localstorage and displayed (using the available real estate) just below the top title bar. By default, the only search results shown are the pages matching the product / version you're currently viewing. You can expand what is displayed by clicking on the button on the right-hand side of the history bar and choosing the "All" radio option. This will show all recent pages in the history bar for all products / versions.

Within the history config menu you will also see a listing of your recent page visits. The results are filtered by the "Current Product / Version" and "All" radio options. Clicking on the button will clear the history bar as well as the history kept in local storage.

If "All" is selected in the history config menu the checkbox option for "Show product details in the history bar" will be enabled. When checked, the product/version for each historic page will show alongside the page name in the history bar. Hovering the cursor over the page names in the history bar will also show the product/version as a tooltip.

Search and Filters

Both API docs and guides can be searched for using the search field at the top of the page.

On API doc pages there is also a filter input field that filters the member rows using the filter string. In addition to filtering by string you can filter the class members by access level, inheritance, and read only. This is done using the checkboxes at the top of the page.

The checkbox at the bottom of the API class navigation tree filters the class list to include or exclude private classes.

Clicking on an empty search field will show your last 10 searches for quick navigation.

API Doc Class Metadata

Each API doc page (with the exception of Javascript primitives pages) has a menu view of metadata relating to that class. This metadata view will have one or more of the following:

Alternate Name - One or more additional class name synonymns (in Ext JS 6.0.0 the Ext.button.Button class has an alternate class name of Ext.Button). Alternate class names are commonly maintained for backward compatibility.
Hierarchy - The hierararchy view lists the inheritance chain of the current class up through its ancestor classes up to the root base class.
Mixins - A list of classes that are mixed into the current class
Inherited Mixins - A list of classes that are mixed into an ancestor of the current class
Requires - All classes required to be defined for the class to be instantiated
Uses - A list of classes potentially used by the class at some point in its lifecycle, but not necessarily requried for the class to initially be instantiated
Subclasses - Classes that extend the current class

Expanding and Collapsing Examples and Class Members

Runnable examples (Fiddles) are expanded on a page by default. You can collapse and expand example code blocks individually using the arrow on the top-left of the code block. You can also toggle the collapse state of all examples using the toggle button on the top-right of the page. The toggle-all state will be remembered between page loads.

Class members are collapsed on a page by default. You can expand and collapse members using the arrow icon on the left of the member row or globally using the expand / collapse all toggle button top-right.

Desktop -vs- Mobile View

Viewing the docs on narrower screens or browsers will result in a view optimized for a smaller form factor. The primary differences between the desktop and "mobile" view are:

Global navigation will be located in a menu on the left-hand side accessible via the hamburger menu icon. The menu houses the following (on most pages):
- The name of the current product (as a link to the product landing page)
- The Sencha icon used to navigate back to the documentation home page
- The product menu drop-down button
- Headers of navigation trees for the API docs and guides
Current context navigation and tools is located on the right-hand side accessible via the gear icon. The context menu houses teh following:
- The global search input field
- (API doc) A "Filters" header with the member filter, expand / collapse all examples button, expand / collapse all member rows button, the access level filter checkboxes, and the counts of each member
- (API doc) A "Related Classes" header containing the menu of metadata related to the current class
- (Guides) The table of contents for the guide

Viewing the Class Source

The class source can be viewed by clicking on the class name at the top of an API doc page. The source for class members can be viewed by clicking on the "view source" link on the right-hand side of the member row.

History :

ExtAngular 7.1.0

Show private classes

top

Requirements Creating a New Angular Application with Ext JS Components Adding Ext JS to an Existing Angular Application Adding ext-angular Configuring Webpack Configuring package.json Updating index.html HTML Doctype Viewport Meta Tag Launching your Application ESLint Using Ext JS Components in Angular Importing Components Configuring Components Handling Events The event Using HTML Elements and Non-ExtAngular Components Inside of ExtAngular Components

Guide for Ext JS Customers

Ext JS customers can use ExtAngular components in Angular applications with the available @sencha/ext-angular library. This guide documents the steps needed to add Ext JS components to Angular applications.

Requirements

Node 8.11+
npm 6+
Angular 9.1.7+
Webpack 4+

Creating a New Angular Application with Ext JS Components

If you're starting from scratch, we recommend cloning the ext-angular monorepo and copying one of the boilerplates to create a new application:

ExtAngular Boilerplate

For example, to use the boilerplate:

git clone https://github.com/sencha/ext-angular.git
cp -r ext-angular/packages/ext-angular-boilerplate /path/to/new/app

Then, follow the instructions in the boilerplate's README.md to setup and run your new application.

Adding Ext JS to an Existing Angular Application

If you need to add Ext JS components to an existing Angular application, follow the steps below:

Adding ext-angular

Sencha provides a set of packages that help integrate Ext JS into Angular. Add them to your Angular application by installing them from npm:

npm install --save @sencha/ext-angular
npm install --save @sencha/ext @sencha/ext-modern @sencha/ext-modern-theme-material
npm install --save-dev @sencha/ext-angular-webpack-plugin html-webpack-plugin webpack-filter-warnings-plugin
npm install --save webpack webpack-cli webpack-dev-server
npm install --save css-loader file-loader html-loader node-sass raw-loader sass-loader style-loader
npm install --save @ngtools/webpack

Configuring Webpack

ExtAngular requires a webpack plugin to bundle and optimize the ExtAngular components you use in your application. Add it to your webpack config as follows:

const AngularCompilerPlugin = require('@ngtools/webpack').AngularCompilerPlugin
const ExtWebpackPlugin = require('@sencha/ext-angular-webpack-plugin')
const WebpackShellPlugin = require('webpack-shell-plugin-next')
const path = require('path')
const HtmlWebpackPlugin = require('html-webpack-plugin')
const { BaseHrefWebpackPlugin } = require('base-href-webpack-plugin');
const webpack = require("webpack")
const FilterWarningsPlugin = require('webpack-filter-warnings-plugin')
const portfinder = require('portfinder')

module.exports = function (env) {
  var browserprofile
  var watchprofile
  var buildenvironment = env.environment || process.env.npm_package_extbuild_defaultenvironment
  if (buildenvironment == 'production') {
    browserprofile = false
    watchprofile = 'no'
  }
  else {
    if (env.browser == undefined) {env.browser = true}
    browserprofile = JSON.parse(env.browser) || true
    watchprofile = env.watch || 'yes'
  }
  const isProd = buildenvironment === 'production'
  var basehref = env.basehref || '/'
  var buildprofile = env.profile || process.env.npm_package_extbuild_defaultprofile
  var buildenvironment = env.environment || process.env.npm_package_extbuild_defaultenvironment
  var buildverbose = env.verbose || process.env.npm_package_extbuild_defaultverbose
  if (buildprofile == 'all') { buildprofile = '' }
  if (env.genProdData == undefined) {env.genProdData = false}
  var genProdData = env.genProdData ? JSON.parse(env.genProdData) : false
  var mode = isProd ? 'production': 'development'

  portfinder.basePort = (env && env.port) || 1962
  return portfinder.getPortPromise().then(port => {
    const plugins = [
      new AngularCompilerPlugin({
        tsConfigPath: './tsconfig.json',
        entryModule: "src/app/app.module#AppModule",
        mainPath: "./src/main.ts",
        skipCodeGeneration: true
      }),
      new HtmlWebpackPlugin({
        template: "index.html",
        hash: true,
        inject: "body"
      }),
      new BaseHrefWebpackPlugin({ baseHref: basehref }),
      new ExtWebpackPlugin({
        framework: 'angular',
        port: port,
        emit: true,
        browser: browserprofile,
        genProdData,
        watch: watchprofile,
        profile: buildprofile, 
        environment: buildenvironment, 
        verbose: buildverbose,
        prodFileReplacementConfig: [
          {
            "replace": "src/environments/environment.ts",
            "with": "src/environments/environment.prod.ts"
          }
        ],
        theme: 'theme-material',
        packages: []
      }),
      new WebpackShellPlugin({
        onBuildEnd:{
          scripts: ['node extract-code.js'],
          blocking: false,
          parallel: true
        }
      }),

      new webpack.ContextReplacementPlugin(
          /\@angular(\\|\/)core(\\|\/)fesm5/,
          path.resolve(__dirname, 'src'),{}
      ),
      new FilterWarningsPlugin({
          exclude: /System.import/
      })
    ]
  return {
    mode,
    entry: {
      polyfills: "./polyfills.ts",
      main: "./main.ts"
    },
    context: path.join(__dirname, './src'),
    output: {
      path: path.resolve(__dirname, 'build'),
      filename: "[name].js"
    },
    module: {
      rules: [
        {test: /\.css$/, loader: ['to-string-loader', "style-loader", "css-loader"]},
        {test: /\.(png|svg|jpg|jpeg|gif)$/, use: ['file-loader']},
        {test: /\.html$/,loader: "html-loader"},
        {test: /\.ts$/,  loader: '@ngtools/webpack'},
        //{test: /\.scss$/,loader: ["raw-loader", "sass-loader?sourceMap"]}
      ]
    },
    plugins,
    node: false,
    devtool: "source-map",
    devServer: {
      contentBase: './build',
      historyApiFallback: true,
      hot: false,
      host: '0.0.0.0',
      port: port,
      disableHostCheck: false,
      compress: isProd,
      inline: !isProd,
      stats: {
        assets: false,
        children: false,
        chunks: false,
        hash: false,
        modules: false,
        publicPath: false,
        timings: false,
        version: false,
        warnings: false,
        colors: {
          green: '\u001b[32m'
        }
      }
    }
  }
})
}

Note: If you're using html-webpack-plugin, make sure it comes before ExtWebpackPlugin in the plugins array so that tags for ext.js and ext.css are included in the resulting index.html.

For more information on configuring the ExtWebpackPlugin for Angular, see Building with Webpack.

You can also use the webpack configuration file in the ExtAngular Boilerplate for reference

Configuring package.json

Configure package.json to mimick the following example from the ext-angular-boilerplate:

{
  "name": "@sencha/ext-angular-boilerplate",
  "version": "7.1.1",
  "description": "ext-angular-boilerplate",
  "scripts": {
    "start": "npm run dev",
    "clean": "rimraf build",
    "dev": "webpack-dev-server --env.environment=development",
    "prod": "npm run build",
    "build": "npm run clean && cross-env webpack --env.environment=production --env.genProdData=true && cross-env webpack --env.environment=production --env.basehref='/'"
  },
  "extbuild": {
    "defaultprofile": "",
    "defaultenvironment": "development",
    "defaultverbose": "no"
  },
  "devDependencies": {
    "@sencha/ext": "~7.1.1",
    "@sencha/ext-angular": "~7.1.1",
    "@sencha/ext-modern": "~7.1.1",
    "@sencha/ext-modern-treegrid": "~7.1.1",
    "@sencha/ext-modern-theme-material": "~7.1.1",
    "@sencha/ext-angular-webpack-plugin": "~7.1.1",
    "@sencha/ext-ux": "~7.1.1",

    "@angular/common": "^9.1.7",
    "@angular/compiler": "^9.1.7",
    "@angular/compiler-cli": "^9.1.7",
    "@angular/core": "^9.1.7",
    "@angular/forms": "^9.1.7",
    "@angular/http": "^9.1.7",
    "@angular/platform-browser": "^9.1.7",
    "@angular/platform-browser-dynamic": "^9.1.7",
    "@angular/router": "^9.1.7",
    "core-js": "^3.2.1",
    "zone.js": "^0.10.2",

    "typescript": "^3.5.3",
    "@types/core-js": "^2.5.2",
    "@types/node": "^12.7.5",
    "rimraf": "^3.0.0",
    "cross-env": "^5.2.1",

    "@ngtools/webpack":"^8.3.4",
    "portfinder": "^1.0.24",
    "css-loader": "^3.2.0",
    "file-loader":"^4.2.0",
    "html-loader": "^0.5.5",
    "node-sass": "^4.11.0",
    "raw-loader": "^1.0.0",
    "sass-loader": "^7.1.0",
    "style-loader": "^1.0.0",

    "html-webpack-plugin": "^3.2.0",
    "base-href-webpack-plugin": "^2.0.0",
    "webpack-filter-warnings-plugin": "^1.2.1",

    "webpack": "^4.40.2",
    "webpack-cli": "^3.3.9",
    "webpack-dev-server": "^3.8.1"
  },
  "dependencies": {},
  "private": false,
  "main": "",
  "repository": {
    "type": "git",
    "url": "git+https://github.com/sencha"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "bugs": {
    "url": "https://github.com/sencha"
  },
  "homepage": "https://github.com/sencha"
}

Updating index.html

If you're using html-webpack-plugin, the JavaScript and CSS resources generated by ExtWebpackPlugin for angular will automatically be added to your index.html file at build time. If not, you'll need to add them manually:

<!doctype html>
<html>
<head>
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
    <link href="ext-angular/ext.css" rel="stylesheet">
    ...
</head>
<body>
    ...
    <script type="text/javascript" src="ext-angular/ext.js"></script>
    ...
</body>

HTML Doctype

The HTML5 doctype declaration is required for ExtAngular components to display properly. Please make sure that this declaration is present at the top of your HTML document:

<!doctype html>

Viewport Meta Tag

ExtAngular requires a viewport meta tag. This should be added to the <head> element in your index.html.

<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">

Launching your Application

To launch your app, add the following to your main.ts file (your webpack entry point):

import { enableProdMode } from '@angular/core'
import { bootstrapModule } from '@sencha/ext-angular/esm5/lib/ext-angular-bootstrap.component';
import {AppModule} from './app/app.module';
import { environment } from './environments/environment'

if (environment.production) {enableProdMode()}
bootstrapModule(AppModule);

Here AppModule is your applications root module. You would need a bootstrap component and a bootstrap service to successfully launch your application with the created folder. You can use these in your applications root module to launch your application as follows:

declare var Ext: any
import { NgModule } from '@angular/core'
import { ExtAngularModule } from '@sencha/ext-angular'
import { ExtAngularBootstrapService } from '@sencha/ext-angular/esm5/lib/ext-angular-bootstrap.service'
import { ExtAngularBootstrapComponent } from '@sencha/ext-angular/esm5/lib/ext-angular-bootstrap.component'
import { AppComponent } from './app.component'

@NgModule({
  imports:         [ExtAngularModule],
  declarations:    [ExtAngularBootstrapComponent, AppComponent],
  providers:       [ExtAngularBootstrapService],
  entryComponents: [AppComponent],
  bootstrap:       [ExtAngularBootstrapComponent]
})
export class AppModule {
  constructor(extAngularService : ExtAngularBootstrapService) {
    extAngularService.setBootStrapComponent(AppComponent)
  }
}

Make sure

ExtAngularBootstrapComponent is imported and added in declarations and bootstrap entries.
ExtAngularBootstrapService is imported and added in providers entry.
You inject ExtAngularBootstrapService service in AppModule constructor and call extAngularService.setBootStrapComponent(AppComponent) where AppComponent is your entry component.

ESLint

If you're using ESLint, add Ext as an allowed global:

"globals": {
    "Ext": true
}

Using Ext JS Components in Angular

Importing Components

The @sencha/ext-angular package makes all Ext JS classes with xtypes available as Angular components. Component names are derived from the capitalized, camel-cased form of the xtype. To make all components available to you Angular app add the following import statement in your applications root module.

import { ExtAngularModule } from '@sencha/ext-angular'

Configuring Components

Angular props are converted to Ext JS configs. Here's a typical use of Ext.grid.Grid:

declare var Ext: any
import { Component } from '@angular/core'

@Component({
  selector: 'app-root-1',
  styles: [``],
  template: `
      <grid title="Users" [store]="this.store">
          <column text="Name" dataIndex="name"></column>
          <column text="Email" dataIndex="email"></column>
      </grid>
  `
})
export class UsersGrid {
  store = Ext.create('Ext.data.Store', {
      fields: ['name', 'email'],
      data: [
        { name: 'Tim Smith', email: 'tim101@gmail.com' },
        { name: 'Jill Lindsey', email: 'jlindsey890@gmail.com' }
      ]
    })
}

In the example above, we set the Grid's title (not data bound, thus no []) and store configs using properties. We set the columns config using column child elements instead of using the columns property. Both forms are acceptible, but we think that using child elements is more intuitive for Angular developers, so this is the form you'll see in all of our examples. ExtAngular automatically knows to map certain child elements like Column to configs on the parent component. Another example of this is Menu:

<button [text]="'Options'">
    <menu>
        <menuttem [text]="'Options 1'"></menuttem>
        <menuttem [text]="'Options 2'"></menuttem>
        <menuttem [text]="'Options 3'"></menuttem>
    </menu>
</button>

Which can also be written as:

<button 
  text="Options"
  [menu]="[
    { text: 'Option 1' },
    { text: 'Option 2' },
    { text: 'Option 3' }
  ]"
></button>

Handling Events

All ExtJS events can be used in ExtAngular as well.

declare var Ext: any
import { Component } from '@angular/core'

@Component({
  selector: 'app-root-1',
  styles: [``],
  template: `
  <sliderfield
    minValue=0
    maxValue=100
    (change)="onChange($event)"
  ></sliderfield>
  `
})
export class MyComponent {
  onChange = (event) => {
    console.log("Value set to " + event.newValue);
  }
}

You can also use a listeners object as is common in traditional Ext JS:

declare var Ext: any
import { Component } from '@angular/core'

@Component({
  selector: 'app-root-1',
  styles: [``],
  template: `
  <sliderfield
    minValue=0
    maxValue=100
    [listeners]="myListeners"
  ></sliderfield>
  `
})
export class MyComponent {
  onChange = (slider, value) => {
    console.log("Value set to " + value);
  }
  myListeners = {
    change: this.onChange
  }
}

The `ready` event

ready event can be used to point to Ext JS component instances:

declare var Ext: any
import { Component } from '@angular/core'

@Component({
  selector: 'app-root-1',
  styles: [``],
  template: `
  <sliderfield
    minValue=0
    maxValue=100
    (ready)="sliderReady($event)"
    (change)="onChange($event)"
  ></sliderfield>
  `
})
export class MyComponent {
  slider:any;
  sliderReady = (event) => {
      this.slider = event.ext;    
  }

  onChange = (event) => {
      console.log("Value set to" + this.slider.getValue());
  }
}

Using HTML Elements and Non-ExtAngular Components Inside of ExtAngular Components

HTML elements are wrapped in an Ext.Component instance when they appear within an ExtAngular Component. This is allows ExtAngular layouts to correctly position non-Angular components. For example...

<panel [layout]="'hbox'">
  <container>
    <span #extitem>
      <div>left</div>
      <div>right</div>
    </span>
  </container>
</panel>

... will result in two divs side-by-side. The component structure created is equivalent to:

Ext.create({
  xtype: 'panel',
  layout: 'hbox'
  items: [
    {
      xtype: 'container',
      items: [
        {
          xtype: 'container',
          width: '100%', height: '100%',
          html: '<span #extitem><div>left</div><div>right</div></span>'
        }
      ]
    }
  ]
});

Contents

Introduction

Terms, Icons, and Labels

Access Levels

Member Types

Member Syntax

Member Flags

Class Icons

Member Icons

Navigation and Features

Class Member Quick-Nav Menu

Getter and Setter Methods

History Bar

Search and Filters

API Doc Class Metadata

Expanding and Collapsing Examples and Class Members

Desktop -vs- Mobile View

Viewing the Class Source

ExtAngular 7.1.0

Contents

Contents

Guide for Ext JS Customers

Requirements

Creating a New Angular Application with Ext JS Components

Adding Ext JS to an Existing Angular Application

Adding ext-angular

Configuring Webpack

Configuring package.json

Updating index.html

HTML Doctype

Viewport Meta Tag

Launching your Application

ESLint

Using Ext JS Components in Angular

Importing Components

Configuring Components

Handling Events

The `ready` event

Using HTML Elements and Non-ExtAngular Components Inside of ExtAngular Components

ExtAngular 7.1.0

Contents

Introduction

Terms, Icons, and Labels

Access Levels

Member Types

Member Syntax

Member Flags

Class Icons

Member Icons

Navigation and Features

Class Member Quick-Nav Menu

Getter and Setter Methods

History Bar

Search and Filters

API Doc Class Metadata

Expanding and Collapsing Examples and Class Members

Desktop -vs- Mobile View

Viewing the Class Source

ExtAngular 7.1.0

Contents

Contents

Guide for Ext JS Customers

Requirements

Creating a New Angular Application with Ext JS Components

Adding Ext JS to an Existing Angular Application

Adding ext-angular

Configuring Webpack

Configuring package.json

Updating index.html

HTML Doctype

Viewport Meta Tag

Launching your Application

ESLint

Using Ext JS Components in Angular

Importing Components

Configuring Components

Handling Events

The ready event

Using HTML Elements and Non-ExtAngular Components Inside of ExtAngular Components

ExtAngular 7.1.0

The `ready` event