1. #11
    Banned
    Join Date
    Jan 2008
    Posts
    120
    Vote Rating
    0
    israel is on a distinguished road

      0  

    Default


    look my work

    - post deleted by tryanDLS not relevant -
    Last edited by tryanDLS; 31 Jan 2009 at 11:08 AM. Reason: not relevant

  2. #12
    Ext User
    Join Date
    Jul 2007
    Location
    Florida
    Posts
    9,996
    Vote Rating
    5
    mjlecomte will become famous soon enough mjlecomte will become famous soon enough

      0  

    Default


    israel:

    what does that have to do with this thread? what is it at all?

  3. #13
    Sencha User
    Join Date
    Mar 2007
    Posts
    7,854
    Vote Rating
    2
    tryanDLS is on a distinguished road

      0  

    Default


    @israel - you continue to disregard the posting rules here. You have been repeatedly asked to modify your behavior. Maybe a week-long posting vacation will make you see the light.

  4. #14
    Ext User
    Join Date
    Jan 2009
    Posts
    26
    Vote Rating
    0
    shay is on a distinguished road

      0  

    Smile thanks ,mj it works

    thanks ,mj it works


    finally it works!

    to make sure i understood it fully and to help others reading this thread.

    1) i was overnesting by using the "items" property instead of assigning the region directly.
    2)it seems that a panel is not designed to handle multiple items that are also panels. a panel should not be an item in another panel but placed in its own layout region.

    is this correct?

    thanks,
    Shay

  5. #15
    Ext User
    Join Date
    Jul 2007
    Location
    Florida
    Posts
    9,996
    Vote Rating
    5
    mjlecomte will become famous soon enough mjlecomte will become famous soon enough

      0  

    Default


    There's no need to nest something inside another Component. Take a look at Panel in the API, with all of it's exposed resources of events, methods, etc. Why use more memory than needed?

    Sometimes you may need to use "items". The point is you need to properly give the parent container for those items a "layout". So whenever you configure "items" you should probably also be specifying "layout".

    Code:
    var someInstance = new Ext.Panel({
        layout: 'WHAT?',
        items: [
    
        ]
    });

  6. #16
    Ext User
    Join Date
    Jul 2007
    Location
    Florida
    Posts
    9,996
    Vote Rating
    5
    mjlecomte will become famous soon enough mjlecomte will become famous soon enough

      0  

    Default


    Re-read what Animal said above, it may make more sense now. Also read the top of:
    http://extjs.com/deploy/dev/docs/?class=Ext.Container

    I'd read over all of the classes introductions to get a rough lay of the land. The big ones to read for sure are Component, Container, Panel, ...

    I'd also suggest giving the Layout Browser demo a good look over.

film izle

hd film izle

film sitesi

takipci kazanma sitesi

takipci kazanma sitesi

güzel olan herşey

takipci alma sitesi

komik eğlenceli videolar