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.
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.
static
label next to the
method name. *See Static below.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).
Let's look at each part of the member row:
lookupComponent
in this example)( item )
in this example)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
).PROTECTED
in
this example - see the Flags section below)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.view source
in the example)item : Object
in the example).undefined
a "Returns" section
will note the type of class or object returned and a description (Ext.Component
in the
example)Available since 3.4.0
- not pictured in
the example) just after the member descriptionDefaults to: false
)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.
classInstance.method1().method2().etc();
false
is returned from
an event handler- 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
- Indicates a class member of type config
- 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.
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.
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.
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.
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:
Ext.button.Button
class has an alternate class name of Ext.Button
). Alternate class
names are commonly maintained for backward compatibility.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.
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:
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.
Enhanced Installation Support - Version 4.3.6 provides seamless installation support across all major platforms, including Windows, macOS, and Linux. Follow platform-specific installation guidelines for setup.
Theme Tab Support - Support for the Theme Tab has been added, aiding in the quick styling of applications and components. Utilize this feature to enhance your application's visual design efficiently.
Froala Component Support - Starting from Ext JS 7.8, the Froala Component is supported in the classic toolkit. Ensure your applications leverage this integration for enhanced text editing features.
Application Upgrade Feature - The application upgrade feature has been enhanced to allow seamless updates to the latest Ext JS versions. Use this feature to keep your applications up-to-date with minimal effort.
Start Menu Inclusion Fix - Sencha Architect was not included in the Windows start menu and did not initiate automatically. This option has now been enabled to ensure Sencha Architect is listed in the start menu and initiates automatically upon installation.
Architect 4.3.5 supports creating applications on the latest Ext JS 7.8 & older versions of the framework.
Architect can now utilize Cmd 7.8 For details.
Architect 4.3.4 supports creating applications on the latest Ext JS 7.7 & older versions of the framework. Check out our change log for a complete list of changes.
By default, the latest version will be shipped in the installer, whereas all the older versions will be downloaded on users demand keeping the installer lightweight.
Architect can now utilize Cmd 7.7 For details, refer to Cmd 7.7 features.
Architect 4.3.2 supports creating applications that support a single version of Ext JS 7.6 framework. Check out our change log for a complete list changes.
Architect can now utilize Cmd 7.6 For details, refer to Cmd 7.6 features.
Sencha Architect 4.3.0 supports creating applications with the latest Ext JS 7.4 framework that contains new features.
Architect provides support for building apps with the following features:
Architect 4.3.0 can now utilize Cmd 7.4 For details, refer to Cmd 7.4 features.
Architect 4.2.7 supports creating applications with the latest Ext JS 7.1 framework.
Architect can now utilize Cmd 7.1 For details, refer to Cmd 7.1 features.
Architect 4.2.6 supports creating applications with the latest Ext JS 7.0 framework.
Architect can now utilize Cmd 7.0 For details, refer to Cmd 7.0 features.
Sencha Architect 4.2.5 support Ext JS 6.7 that contains new features. Architect provides support for building apps with the following components:
Architect can now utilize Cmd 6.7 For details, refer to Cmd 6.7 features.
We’re excited to announce that Sencha Architect 4.2.4 is now generally available, providing support for Ext JS 6.6 and Cmd 6.6. With Architect 4.2.4, you can visually build apps using new Ext JS 6.6 components such as Time Panel and Time Field, and use the new beautiful Graphite theme, and build projects with Cmd 6.6. This release will enable you to quickly build sophisticated web applications using Ext JS 6.6.
Visually build Ext JS views using new Ext JS components
You can use Architect to drag and drop new Time Panel and Time Field components and generate application code. You get access to all of the configuration parameters of components, set layouts, add custom configs, add events and create overrides with minimal manual coding.
Easily apply built-in Graphite accessible theme to your app
Architect 4.2.4 supports the new accessible Graphite theme. You can easily drag and drop the theme, apply it to your application, and customize the theme.
Easy migration to Ext JS 6.6 framework
Architect provides options to easily upgrade applications built using older versions of the framework to Ext JS 6.6. You can upgrade to the latest version of the Ext JS framework when you right click on ‘Library’ in the Resources section of Sencha Architect.
Architect 4.2.3 supports Ext JS 6.5.3 and Cmd 6.5.3.
Check out our change log for a complete list changes.
Architect can now utilize Ext JS 6.5.3. Ext JS 6.5.3 contains many new features.
Architect can now utilize Cmd 6.5.3. For details, pl. refer to Cmd 6.5.3 features.
Architect 4.x supports all Sencha premium packages, so that you can use D3, Calendar, Pivot Grid, and Exporter in either modern and classic toolkit based applications. With Architect 4.2.3, you can easily import premium add-ons in your Architect project.
Architect 4.2 provides support for Ext JS 6.5 and Cmd 6.5, adds a new modern project template, and includes some new menu items for easier project management.
Check out our change log for a complete list changes.
Architect can now utilize Ext JS 6.5.0. Ext JS 6.5.0 contains many new features, especially within the modern toolkit.
Architect can now utilize Cmd 6.5.0. Cmd 6.5.0 now supports ES6 syntax, dynamic package loading, and a whole lot more.
Users can now stop app watch when it is unnecessary to run after each save. Users can also restart app watch when there are build issues.
Note: App watch is automatically started on project open.
Users can now remove and add again Sencha Cmd from their project with a single click. Sometimes there can be problems that are solved by removing and adding Cmd back again.
Note: This removes all Sencha Cmd related files such as app.json
and others.
Users can now select their offline licenses via file picker instead of manually placing their files.
Architect's electron wrapper has been updated to version 1.6.2.