Hierarchy
Ext.layout.ContainerLayoutExt.layout.FitLayoutExt.layout.CardLayout
Files
CardLayout.js

This layout manages multiple child Components, each fitted to the Container, where only a single child Component can be\nvisible at any given time. This layout style is most commonly used for wizards, tab implementations, etc.\nThis class is intended to be extended or created via the layout:'card' Ext.Container.layout config,\nand should generally not need to be created directly via the new keyword.

\n\n\n

The CardLayout's focal method is setActiveItem. Since only one panel is displayed at a time,\nthe only way to move from one Component to the next is by calling setActiveItem, passing the id or index of\nthe next panel to display. The layout itself does not provide a user interface for handling this navigation,\nso that functionality must be provided by the developer.

\n\n\n

In the following example, a simplistic wizard setup is demonstrated. A button bar is added\nto the footer of the containing panel to provide navigation buttons. The buttons will be handled by a\ncommon navigation routine -- for this example, the implementation of that routine has been ommitted since\nit can be any type of custom logic. Note that other uses of a CardLayout (like a tab control) would require a\ncompletely different implementation. For serious implementations, a better approach would be to extend\nCardLayout to provide the custom functionality needed. Example usage:

\n\n\n

var navHandler = function(direction){\n    // This routine could contain business logic required to manage the navigation steps.\n    // It would call setActiveItem as needed, manage navigation button state, handle any\n    // branching logic that might be required, handle alternate actions like cancellation\n    // or finalization, etc.  A complete wizard implementation could get pretty\n    // sophisticated depending on the complexity required, and should probably be\n    // done as a subclass of CardLayout in a real-world implementation.\n};\n\nvar card = new Ext.Panel({\n    title: 'Example Wizard',\n    layout:'card',\n    activeItem: 0, // make sure the active item is set on the container config!\n    bodyStyle: 'padding:15px',\n    defaults: {\n        // applied to each contained panel\n        border:false\n    },\n    // just an example of one possible navigation scheme, using buttons\n    bbar: [\n        {\n            id: 'move-prev',\n            text: 'Back',\n            handler: navHandler.createDelegate(this, [-1]),\n            disabled: true\n        },\n        '->', // greedy spacer so that the buttons are aligned to each side\n        {\n            id: 'move-next',\n            text: 'Next',\n            handler: navHandler.createDelegate(this, [1])\n        }\n    ],\n    // the panels (or \"cards\") within the layout\n    items: [{\n        id: 'card-0',\n        html: '<h1>Welcome to the Wizard!</h1><p>Step 1 of 3</p>'\n    },{\n        id: 'card-1',\n        html: '<p>Step 2 of 3</p>'\n    },{\n        id: 'card-2',\n        html: '<h1>Congratulations!</h1><p>Step 3 of 3 - Complete</p>'\n    }]\n});\n

\n\n

Defined By

Config options

Ext.layout.CardLayout
view source

deferredRender : Boolean

True to render each contained item at the time it becomes active, false to render all contained items\nas soon as the ...

True to render each contained item at the time it becomes active, false to render all contained items\nas soon as the layout is rendered (defaults to false). If there is a significant amount of content or\na lot of heavy controls being rendered into panels that are not displayed by default, setting this to\ntrue might improve performance.

Defaults to: false

Hierarchy

Files

Config options

Properties

Methods

Parameters

Returns

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Parameters

Returns

Parameters

Parameters

Parameters

Parameters

Parameters