source: trunk/web/addons/job_monarch/lib/extjs-30/src/widgets/layout/CardLayout.js @ 625

Last change on this file since 625 was 625, checked in by ramonb, 15 years ago

lib/extjs-30:

  • new ExtJS 3.0
File size: 5.2 KB
Line 
1/*!
2 * Ext JS Library 3.0.0
3 * Copyright(c) 2006-2009 Ext JS, LLC
4 * licensing@extjs.com
5 * http://www.extjs.com/license
6 */
7/**
8 * @class Ext.layout.CardLayout
9 * @extends Ext.layout.FitLayout
10 * <p>This layout manages multiple child Components, each fitted to the Container, where only a single child Component can be
11 * visible at any given time.  This layout style is most commonly used for wizards, tab implementations, etc.
12 * This class is intended to be extended or created via the layout:'card' {@link Ext.Container#layout} config,
13 * and should generally not need to be created directly via the new keyword.</p>
14 * <p>The CardLayout's focal method is {@link #setActiveItem}.  Since only one panel is displayed at a time,
15 * the only way to move from one Component to the next is by calling setActiveItem, passing the id or index of
16 * the next panel to display.  The layout itself does not provide a user interface for handling this navigation,
17 * so that functionality must be provided by the developer.</p>
18 * <p>In the following example, a simplistic wizard setup is demonstrated.  A button bar is added
19 * to the footer of the containing panel to provide navigation buttons.  The buttons will be handled by a
20 * common navigation routine -- for this example, the implementation of that routine has been ommitted since
21 * it can be any type of custom logic.  Note that other uses of a CardLayout (like a tab control) would require a
22 * completely different implementation.  For serious implementations, a better approach would be to extend
23 * CardLayout to provide the custom functionality needed.  Example usage:</p>
24 * <pre><code>
25var navHandler = function(direction){
26    // This routine could contain business logic required to manage the navigation steps.
27    // It would call setActiveItem as needed, manage navigation button state, handle any
28    // branching logic that might be required, handle alternate actions like cancellation
29    // or finalization, etc.  A complete wizard implementation could get pretty
30    // sophisticated depending on the complexity required, and should probably be
31    // done as a subclass of CardLayout in a real-world implementation.
32};
33
34var card = new Ext.Panel({
35    title: 'Example Wizard',
36    layout:'card',
37    activeItem: 0, // make sure the active item is set on the container config!
38    bodyStyle: 'padding:15px',
39    defaults: {
40        // applied to each contained panel
41        border:false
42    },
43    // just an example of one possible navigation scheme, using buttons
44    bbar: [
45        {
46            id: 'move-prev',
47            text: 'Back',
48            handler: navHandler.createDelegate(this, [-1]),
49            disabled: true
50        },
51        '->', // greedy spacer so that the buttons are aligned to each side
52        {
53            id: 'move-next',
54            text: 'Next',
55            handler: navHandler.createDelegate(this, [1])
56        }
57    ],
58    // the panels (or "cards") within the layout
59    items: [{
60        id: 'card-0',
61        html: '&lt;h1&gt;Welcome to the Wizard!&lt;/h1&gt;&lt;p&gt;Step 1 of 3&lt;/p&gt;'
62    },{
63        id: 'card-1',
64        html: '&lt;p&gt;Step 2 of 3&lt;/p&gt;'
65    },{
66        id: 'card-2',
67        html: '&lt;h1&gt;Congratulations!&lt;/h1&gt;&lt;p&gt;Step 3 of 3 - Complete&lt;/p&gt;'
68    }]
69});
70</code></pre>
71 */
72Ext.layout.CardLayout = Ext.extend(Ext.layout.FitLayout, {
73    /**
74     * @cfg {Boolean} deferredRender
75     * True to render each contained item at the time it becomes active, false to render all contained items
76     * as soon as the layout is rendered (defaults to false).  If there is a significant amount of content or
77     * a lot of heavy controls being rendered into panels that are not displayed by default, setting this to
78     * true might improve performance.
79     */
80    deferredRender : false,
81   
82    /**
83     * @cfg {Boolean} layoutOnCardChange
84     * True to force a layout of the active item when the active card is changed. Defaults to false.
85     */
86    layoutOnCardChange : false,
87
88    /**
89     * @cfg {Boolean} renderHidden @hide
90     */
91    // private
92    renderHidden : true,
93   
94    constructor: function(config){
95        Ext.layout.CardLayout.superclass.constructor.call(this, config);
96        this.forceLayout = (this.deferredRender === false);
97    },
98
99    /**
100     * Sets the active (visible) item in the layout.
101     * @param {String/Number} item The string component id or numeric index of the item to activate
102     */
103    setActiveItem : function(item){
104        item = this.container.getComponent(item);
105        if(this.activeItem != item){
106            if(this.activeItem){
107                this.activeItem.hide();
108            }
109            this.activeItem = item;
110            item.show();
111            this.container.doLayout();
112            if(this.layoutOnCardChange && item.doLayout){
113                item.doLayout();
114            }
115        }
116    },
117
118    // private
119    renderAll : function(ct, target){
120        if(this.deferredRender){
121            this.renderItem(this.activeItem, undefined, target);
122        }else{
123            Ext.layout.CardLayout.superclass.renderAll.call(this, ct, target);
124        }
125    }
126});
127Ext.Container.LAYOUTS['card'] = Ext.layout.CardLayout;
Note: See TracBrowser for help on using the repository browser.