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 and inheritance. This is done using the checkboxes at the top of
the page. Note that filtering out private
members also filters the API class
navigation tree.
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.
Date: July 26, 2016
Version Number: 1.0.3.76
ORION-892 - Futures should have up/down/child methods to navigate component or element hierarchy
ORION-905 - ST.future.Item should be able to return component futures (via asButton, etc) for lists of components in Modern toolkit
ORION-906 - Grid and dataView futures should provide select/deselect/selected/deselected methods
Total: 4
ORION-1013 - Can't add Generic Web Driver pool
ORION-226 - Browser pool editor does not produce a proper BrowserStack configuration file
ORION-932 - Properly display browser names, versions and platforms for Sauce Labs and BrowserStack capabilities files
ORION-916 - Go to Declaration fails to open editor tab
ORION-927 - Code completion failing because of incorrect cursor position
ORION-555 - Special keys are recorded but not played back
ORION-813 - Click events are not properly translated on touch device browsers
ORION-843 - Link to proxy server settings is missing in 入门 sequence
ORION-910 - License activation does not properly use system-defined proxy (must manually enter)
ORION-690 - Connections fail using self-signed certifcates or custom AD CA
ORION-937 - "Cannot read property 'isVersion' of undefined" error in Studio when app launched from UIWebView (PhoneGap / Cordova)
ORION-1008 - Infinity loading mark on description into test runner, when xit method is used.
ORION-717 - Sencha Studio stuck on Loading Tests
ORION-970 - New test suites are not loaded by the browser if added after the Runner is launched
ORION-978 - Test runner should launch local browsers using loopback address (127.0.0.1) not external address
ORION-1020 - stc throwing "Error: Couldn't connect to selenium server"
ORION-833 - STC throws error after launching on OS X.
ORION-955 - Wrong stc version
Total: 21
Total: 3
Date: June 14, 2016
Version Number: 1.0.2.151
ORION-740 - ST.future.DataView should support modern toolkit
ORION-767 - ST.future.CheckBox should support modern toolkit
ORION-776 - ST.future.Grid/Row/Cell should support modern toolkit
ORION-780 - ST.future.Button should support modern toolkit
ORION-782 - Should provide ST.future.Select class for modern toolkit
ORION-783 - ST.future.Component should support modern toolkit
ORION-784 - ST.future.Field should support modern toolkit
ORION-785 - ST.future.Item should support modern toolkit
ORION-788 - ST.future.TextField should support modern toolkit
ORION-632 - Context menu for files should be common to all file nodes
ORION-864 - Studio should allow user to provide alternate proxy server settings vs those defined in the OS
Total: 15
ORION-651 - ST.textfield() should be able to type() empty string, but throws error.
ORION-810 - ST.Version getRelease() method throw exception
ORION-816 - ST.Element getComponent() fails for Ext JS 4/Sencha Touch
ORION-817 - ST.item.blurred() is not working on modern
ORION-834 - Tests are infinity running after call ST.cell/cellAt/cellBy/cellWith.
ORION-631 - Copies of shellwrapper.sh installed by EA/Beta breaks Sencha Test builds
ORION-659 - Can execute App watch when Cmd Integration is disabled
ORION-793 - App watch is not checked if service is running
ORION-716 - Shortcut name incorrect on Windows - "Sencha Sencha Test"
ORION-857 - Installer doesn't install ST to folder Applications on OS X
ORION-861 - Unable to install Sencha Studio into 'Program Files' directory.
ORION-894 - Destination not writable error at the end of installation
ORION-237 - Inconsistent results of demo workspace
ORION-340 - Studio ignores custom message in matchers.
ORION-341 - Custom matchers without result message crashes test if result is false
ORION-703 - Failed expectation message not meaningful when using Jasmine Spies
ORION-728 - Futures and event player do not work from beforeAll or afterAll
ORION-736 - Calling Jasmine's it() with no test fn does not treat test as disabled
ORION-737 - Expectations in beforeAll functions are not reported
ORION-597 - Prompts for "Sencha Account" should read "Sencha Forum Account" to avoid confusion
ORION-847 - Impossible to activate Trial via provided Activation code.
ORION-875 - Activation error "Cannot activate license: License is corrupted"
ORION-878 - Activation trial is possible with any email
ORION-718 - Sencha Studio stuck on development build
ORION-752 - Page with a "head" tag containing attributes will cause tests and event recorder to fail
ORION-792 - Missing files for unittest in 4.x frameworks
ORION-770 - Default scenario path for all new scenarios created
ORION-802 - Renaming scenario directory to an existing directory results in ENOTEMPTY
ORION-848 - 'cacheBuster' error is observed after entering Location(URL).
ORION-229 - Error if last opened workspace is missing
ORION-230 - Creating a workspace / application from Studio displays red alert badges
ORION-424 - Unable to navigate if too many tabs are open (no overflow handling)
ORION-478 - Tabs cannot be closed until the content is edited in some way
ORION-511 - Studio task has undefined name
ORION-585 - Manual file system updates only work for one new file at a time
ORION-590 - Test summary incorrectly indicates a passed result when only one test case fails
ORION-602 - Socket hang up at createHangUpError when opening applications over HTTPS
ORION-672 - Studio becomes unusable when entering location URL without two slashes or scheme
ORION-674 - Swiping between 2 screenshots isn't working.
ORION-696 - Cant create workspace or open existing one on Windows
ORION-700 - Event recorder doesn't work after creating workspace
ORION-701 - Hidden files and folders should not be displayed
ORION-719 - Studio displays misleading message when connecting to Archive Server with no test runs
ORION-743 - Test page gets wrongly cached on Safari leading to JSON errors and perpetual reload
ORION-757 - Unclear error message if parking lot port is in use
ORION-760 - User is not navigated from test runner to project settings when no location URL is configured
ORION-839 - Sencha Studio is not properly closed on Linux and Windows
ORION-215 - Test describe blocks are run too early - cannot use Ext or app code in them
ORION-490 - Global variables leaks are sometimes wrongly reported due to race condition
ORION-535 - Error when connecting to self-signed cert endpoint
ORION-598 - Cache disable setting in test runner does not affect corresponding Ext JS loader setting
ORION-626 - Sencha Test throws error running tests when Ripple plugin in Chrome is installed
ORION-638 - Package test configuration requires user to specify Location (URL)
ORION-771 - TestRunner does not show parked remote browsers with exactly matching userAgent
ORION-772 - Player timeouts from one spec are sometimes reported under subsequent specs
ORION-620 - Test Runner displays non-JS files and displays wrong results for them in some cases
ORION-641 - Changing scenario's location value has no effect in certain cases
ORION-643 - When selecting an individual test or a group of tests, the master checkbox for the scenario should be unchecked
ORION-653 - Newly added specs are labelled as passed even though they have never run
ORION-738 - Test runner does not always reuse locally parked agents
ORION-791 - STC exits with error "Cannot find module 'process'"
ORION-891 - Unable to run STC, when path to the STC contains 'space'.
Total: 68
Total: 3
Date: March 2, 2016
Version Number: 1.0.1.38
ORION-571 - Should provide ST.future.Element#content() method to wait for exact markup
ORION-572 - Should provide ST.future.Element#text() method to wait for exact textContent
Total: 5
ORION-575 - ST.future.Element text state methods do not work with input element values
ORION-578 - Calling ST future methods inside and() callback does not properly delay the callback's completion
ORION-405 - Studio repeatedly creates parking pages on Linux, Win
ORION-539 - Recorder stuck on Launching
ORION-45 - Test runner shows different result counts for folders for some browsers
ORION-509 - Top-level disabled suites do not appear in the test runner UI.
ORION-97 - Update can be completed when instance of Orion is running
ORION-217 - Many tree node icons do not propagate to their associated tabs
ORION-459 - Two indexing processes can run at the same time
ORION-502 - Uncaught TypeError: j.record.drop appears in ST
ORION-544 - Settings window does not layout correctly after clearing logs
ORION-554 - New added file has folder icon instead of file icon
ORION-557 - Using context menu to create Jasmine suite often instead creates a Scenario node (only on Windows)
ORION-559 - Allowed global variables are not allowed for second and next test run until restart Studio
ORION-565 - Sencha Studio does not properly report failed archive downloads and leaves progress bar
ORION-574 - Navigation tree gains Scenario nodes for files created outside of Studio (found by file system change notification)
ORION-355 - Test selection is reset when run is stopped
ORION-358 - Test results are additive
ORION-392 - Test result summary is not properly reset
ORION-457 - Studio gets stuck in "Loading Tests" state
ORION-521 - Re-running tests will cause opening several browser tabs/windows
ORION-538 - No visual indication when filters are enabled in the test runner
ORION-551 - "Start App Watch?" popup is shown every time a new browser is selected
Total: 29
Date: February 16, 2016
Version Number: 1.0.0
The following bugs were reported by the Sencha Community - a big thanks to everyone who tried out the Beta!
ORION-247 - Unable to configure archive server
ORION-255 - Unable to create/open workspace using Cmd 5.x
ORION-320 - Cannot generate Sencha Touch App
ORION-321 - SenchaTestDemo needs some more examples with older frameworks
ORION-351 - Testing ExtJS 4.2 app - never loads in any browser (just keeps loading)
ORION-426 - Creating test project deletes all comments from app.json