Saving and Forking Fiddles
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.
Fiddle 2 introduces a number of improvements and flexibilities when it comes to saving and sharing your work. Your code examples can be saved to the Fiddle server and then the link to your fiddle shared with coworkers or the community, but now with Fiddle 2 you have more control than ever over how each fiddle can be viewed, searched, and edited.
Saved fiddles can be forked creating a new fiddle ID. From there, all aspects of the fiddle may be changed including the title, description, code and folder structure, and save options. Forked fiddles will show you as the fiddle author. However, next to the fiddle title will be a fork icon that when clicked will open the parent fiddle.
If you open an existing fiddle and make changes prior to first forking the fiddle those changes will then be saved to your fork when you click the Fork button.
By default, when you save a fiddle it will be searchable in the search panel. To prevent a fiddle from showing up in the search results:
Save your fiddle by clicking Save (or by using Cmd/Command-S with the editor focused)
Click on the Admin button and choose "Permissions" from the context menu
Uncheck "Search Indexable"
Click Save
The fiddle along with its preferences will now be re-saved. The fiddle will no longer show up in the results in the Search panel.
Fiddles may be password protected to prevent unauthorized access. You can set a password for a fiddle using the steps above in the Search Index section of the guide. Just replace step 3 with:
Note: Password protected fiddles are not removed from the search results. The search results that are password protected will have a key icon to signify they are password protected. If you would like your fiddle to be excluded from search as well as password protected be sure to uncheck "Search Indexable".
Fiddles are normally able to be opened, edited, and re-saved with new changes. However, there are times you don’t want a fiddle to be changed. By locking a fiddle you prevent it from being edited without first acknowledging a confirmation prompt. To lock a fiddle, follow the steps above in the Search Index section and replace step 3 with:
Once locked, you will be shown a confirmation dialog asking if you want to save over your locked fiddle.
Fiddles may be assigned to one or more teams of users with each user having custom run / edit privileges. Creating teams and associating fiddles to a team offers granular control over select fiddles and who users may interact with them. As a user you may create teams of your own as well as be added to teams that other users create.
The Teams panel may be viewed by:
Signing into fiddle
Click on your username
From the context menu choose "Teams"
The Teams panel displays any teams you’ve created or have been added to. The team panel displays:
Name - The name of the team
Creator - The username of the team creator
Public Read - "No" if the fiddles added to this team may be read by anyone outside of the team
Your Permission - Your permission level within the team (more on permission levels below)
[Edit Team] - A gear icon in the last column allowing you to edit the team parameters (if you are the creator or have a permission level of "Full Access")
[Leave Team] - An exit icon in the last column allowing you to leave a team you’ve been added to. You cannot leave a team you created.
You can search for existing teams by name using the search field at the top of the Teams panel.
To create a new team, click on the "Create" button on the top-right of the Teams panel. Enter the desired team name and click “Ok”. The edit Team window for the new team will be shown. From here you can disable public read access to any fiddle added to the team by unchecking the “Allow Public Read” checkbox.
To rename a team open the Teams panel and click on the Edit Team (gear) icon next to the team you’d like to edit. In the edit Team window change the team name in the "Name" field and click the “Save” button.
Click on the gear (edit team) icon next to the team you’re adding a new user to (the edit Team window will also be shown just after creating a new team). In the edit Team window click on the "Add User" button top-right. Enter the fiddle username of the user you want to add, choose a permission level for the user, and click “Choose User”.
Users may be assigned the following permission levels:
No Access
Read
Read + Write
Read + Write + Delete
Full Access
All permission levels apply to the fiddles associated to the team except for "Full Access". The “Full Access” level gives the user permission to read, write, and delete fiddles as well as add, modify, and remove users from the team.
Un-checking the "Allow Public Read" checkbox is effectively the same as adding all users with the “No Access” permission. User must then be whitelisted by adding them to the team and giving them at least the Read access.
Team creators and users with "Full Access" permissions may add and remove users from a team. To remove a user open the Teams panel and click on the edit team (gear) icon. In the edit Team window click on the [X] next to the user you want to remove. Click on “Yes” in the Remove Item confirmation dialog.
You may opt to leave a team you’ve been added to by opening the Teams panel and clicking on the exit (Leave Team) icon. Next, click "Yes" on the Leave Team confirmation dialog.
To add a saved fiddle to one or more teams:
Click on the "Admin" button and then select “Teams” from the context menu.
Click the "Add to Team" button in the top-right.
Select the target team from the "Team" combo field in the Find Team window (typing in the field will filter the teams list)
Click "Choose Team"
The team or teams your fiddle belongs to will display in the Fiddle Teams window.
Open the fiddle whose teams you want to manage
Click on the "Admin" button in the left toolbar and choose “Teams”
In the Fiddle Static Groups window click on the "X" next to the team you want to remove the fiddle from
Click "Yes" in the Remove From Team confirmation prompt
Fiddles may be added to one or more user-defined groups. Groups are "albums" of fiddles that provide additional user-defined organization for your fiddles (for permissions management see Teams). In addition to user-defined groups there are default Dynamic groups that automatically curate the fiddles included in the group based on select, pre-defined search criteria
The Groups panel may be viewed by:
Signing into fiddle
Click on your username
From the context menu choose "Groups"
The Groups panel displays any teams you’ve created or have been added to. The Group panel displays:
Name - The name of the group
Creator - The username of the group creator
Public - "No" if the group should not be visible to other users
[Show Fiddles] - An expand icon in the last column that shows the fiddles in the group
[Edit Group] - A gear icon in the last column that opens the edit Group window
[Delete Group] - An X icon in the last column that deletes a group
You can filter the groups using the "search…" field above the groups grid. The search is performed on the group name.
To create a new group, click on the "Create" button on the top-right of the Groups panel. Enter the desired group name and click “Ok”.
To rename a group open the Groups panel and click on the Edit Group (gear) icon next to the group you’d like to edit. In the edit Group window change the group name in the "Name" field and click the “Save” button.
To delete a group open the Groups panel and click on the Delete Group (X) icon next to the group you’d like to delete. Click "Yes" in the Delete Group confirmation dialog.
To add a saved fiddle to one or more groups:
Click on the "Admin" button and then select “Groups” from the context menu.
Click the "Add to Group" button in the top-right.
Select the target group from the "Group" combo field in the Find Group window (typing in the field will filter the groups list)
Click "Choose Group"
The group or groups your fiddle belongs to will display in the Fiddle Static Groups window.
Open the fiddle whose groups you want to manage
Click on the "Admin" button in the left toolbar and choose “Groups”
In the Fiddle Static Groups window click on the "X" next to the group you want to remove the fiddle from
Click "Yes" in the Remove From Group confirmation prompt
Fiddle | Terms of Use
