Page 53 of 68 FirstFirst ... 343515253545563 ... LastLast
Results 521 to 530 of 678

Thread: Documentation Bugs - Ext 2.x

  1. #521
    Ext JS Premium Member
    Join Date
    Mar 2007
    Posts
    216
    Vote Rating
    0
      0  

    Default

    Animal, I just saw your note above about this being a bug in the documentation generator. I guess I'll stop reporting the {@link } related issues I find in the documentation.

  2. #522
    Ext JS Premium Member
    Join Date
    Mar 2007
    Posts
    216
    Vote Rating
    0
      0  

    Default

    Quote Originally Posted by Animal View Post
    I can't reproduce this. In FF anyway, I don't tend to run other browsers.
    I can reproduce it every time running FF 3.0.4. Try constraining the browser window horizontally. I noticed that if I expand the browser window, there is a point where it starts to wrap normally.

  3. #523
    Ext User
    Join Date
    May 2008
    Posts
    55
    Vote Rating
    0
      0  

    Default When data is inconsitent in XTemplate Store - Thanks

    Thanks this helped me where there was data inconsistency in the json feed i received.
    Code:
    <tpl if='[values.XXX]'>...</tpl>
    Quote Originally Posted by Condor View Post
    The Template/XTemplate docs are still incomplete:

    Ext.Template has the following config options:
    compiled (Boolean): true to compile the template immediately (see compile()) (default: false)
    disableFormats (Boolean): true to disable format functions in the template. If the template doesn't contain format functions, setting disableFormats to true will reduce apply time (default: false)
    re (RegExp): The regular expression used to match template variables (default: matches {name}).

    Ext.XTemplate has an extra config option:
    codeRe (RegExp): The regular expression used to match code variables (default: matches {[expression]}).

    Ext.XTemplate has also the ability to execute arbitrary code with <tpl exec="..."></tpl>

    It's also worth a note that the <tpl> tag must conform to:
    Code:
    <tpl (for|if|exec)="value">content</tpl>
    So, the following <tpl> tags are invalid:
    Code:
    <tpl for='.'>...</tpl>
    <tpl if = "true">...</tpl>
    <tpl exec="this.doSomething()" />
    Finally, the Ext.Template docs demonstrate how to use format functions, but this is missing from the Ext.XTemplate docs.
    Regards,
    Accilies

  4. #524
    Ext User
    Join Date
    Jul 2007
    Location
    Florida
    Posts
    9,996
    Vote Rating
    8
      0  

    Default PagingToolbar events undocumented [implemented]


  5. #525
    Ext User
    Join Date
    Oct 2008
    Location
    Toulouse - France
    Posts
    7
    Vote Rating
    0
      0  

    Default Container.add(...)

    Class: Container
    Method: add

    When expanded, a vertical scrollbar is appearing, an the collapse button isn't visible (FF3, IE 6).

  6. #526
    Ext JS Premium Member
    Join Date
    Aug 2007
    Posts
    63
    Vote Rating
    0
      0  

    Default [2.2] Typo in API for RadioGroup [implemented]

    [implemented]

    The constructor public method for RadioGroup reads:

    RadioGroup( Object config )
    Creates a new CheckboxGroup

    Typo.

  7. #527
    Sencha User Ytorres's Avatar
    Join Date
    Jun 2007
    Location
    Rennes, France
    Posts
    285
    Vote Rating
    0
      0  

    Default [implemented]

    [implemented]

    Hi all,

    I don't know if this typo have been already report or not.

    In the documentation, Sample, in the Layout Browser :

    => Basic Ext Layout => Accordion :

    Sample config :

    PHP Code:
    layout'accordion',
    items:[{
        
    title'Panel 1',
        
    html'Content'
    },{
        
    title'Panel 2, // <=== Missing ' here
        id
    'panel2',
        
    html'Content'
    }] 
    "Software is like sex: it's better when it's free" - Linus Torvald
    https://edit.php.net - A tool written with ExtJs for translated Php documentation

  8. #528
    Ext User
    Join Date
    Jul 2007
    Location
    Florida
    Posts
    9,996
    Vote Rating
    8
      0  

    Default Field disabled config [implemented]

    [implemented]

    Class Ext.form.Field
    Package: Ext.form
    Defined In: Field.js
    Class: Field

    disabled : Boolean
    True to disable the field (defaults to false).
    I wasn't aware that disabled fields won't get submitted. The API is a tad sparse in this area. I'll note a few items found from various forum posts:

    Disabled fields do not get submitted.
    http://www.w3.org/TR/html401/interac...html#h-17.12.1

    Previously suggested workarounds:
    1. Use readOnly http://extjs.com/deploy/dev/docs/?cl...ember=readOnly true with cls:'x-item-disabled'. The field isn't really html disabled, it's only "masked" and the value is still sent.
    2. Enable the fields temporarily?
    3. Use a hidden field for the value AND a disabled field for display.


    Perhaps some of the above can get worked into future docs.

  9. #529
    Sencha - Community Support Team Condor's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    24,246
    Vote Rating
    118
      0  

    Default

    [implemented]

    Quote Originally Posted by mjlecomte View Post
    Use a hidden field for the value AND a disabled field for display.
    I would recommend the StaticTextField user extension for that.

  10. #530
    Ext User
    Join Date
    Jul 2007
    Location
    Florida
    Posts
    9,996
    Vote Rating
    8
      0  

    Default

    [implemented]

    Quote Originally Posted by Condor View Post
    I would recommend the StaticTextField user extension for that.
    Thanks for the comment. Not to steer this thread too far off, I bumped one of the related threads here:
    http://extjs.com/forum/showthread.ph...184#post271184

    To clarify my prior post I wasn't suggesting any method, just that I thought that the API could use a few additional remarks about the matter.

    @Condor: please see the linked thread for additional discussion.

Page 53 of 68 FirstFirst ... 343515253545563 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •