Page 1 of 5 123 ... LastLast
Results 1 to 10 of 44

Thread: Documentation Bugs - Ext Core 3.1

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Ext JS Premium Member tim.sporcic's Avatar
    Join Date
    May 2008
    Location
    Plano, TX
    Posts
    38
    Vote Rating
    0
      0  

    Default Documentation Bugs - Ext Core 3.1

    Looks good. Definitely pushes into JQuery's happy space. Documentation is very good, but has a few rough spots:

    Core Manual: URL encode/decode examples use Ext.encode/decode instead of Ext.urlEncode/urlDecode

    API Doc: Ext.Template doc says at the top to look at Ext.util.Format for the format functions, but that class in not in Core

  2. #2
    Ext User
    Join Date
    Jan 2008
    Posts
    103
    Vote Rating
    0
      0  

    Default

    Manual

    CSS Clases & Styling header should be CSS Classes & Styling.

    The example following CSS Classes & Styling shows <div type="myCls">, should be <div class="myCls">.

    Under CSS Classes & Styling, following the screenshot of Firebug, the last sentence: lets should be let's.

    Under CSS Classes & Styling, the last sentence in the toggleClass description has a typo: "If it isn't applied to the element it will be, it is is then it will be removed." "it is is" should be "if it is."

    Are the RED boxes under the Animations section suppose to do anything?

    I'm assuming the Template docs are not finished?

    Under Ext.Extend, the last sentence in the override description contains a typo: "properties/functions to add t othe prototype"

    In the Element section, under Html Fragments, after the beforeBegin markup, "Suprised?" is misspelled.

    I know I saw some other minor things. I'll try to post more as I find them.

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

    Default

    For time being post all of the doc related remarks in this thread.

    Please make sure to indicate if it is the Manual or the API Docs and specify a section/class to help locate what you reference is.

  4. #4
    Sencha User mystix's Avatar
    Join Date
    Mar 2007
    Location
    Singapore
    Posts
    6,236
    Vote Rating
    5
      0  

    Default

    Manual


    1. Typo:
      Quote Originally Posted by Element > Animations;
      Ext Core has animation plugins available that give you a robust set of preconfigured animations that are alredy applied as methods to Ext.Element so you can do cool things like this:
    2. Incomplete description
      Quote Originally Posted by Utility > Type Detection;
      isEmpty
      Checks whether the passed value is empty, i.e. which includes undefined, null, or an empty string, or an empty array.

  5. #5
    Ext JS Premium Member tim.sporcic's Avatar
    Join Date
    May 2008
    Location
    Plano, TX
    Posts
    38
    Vote Rating
    0
      0  

    Default

    API Docs:
    Ext object documentation is missing the select() method
    Element object documentation is missing the update() method

  6. #6
    Ext User deanna's Avatar
    Join Date
    Aug 2007
    Location
    Alabama
    Posts
    306
    Vote Rating
    0
      0  

    Default Note on the Ext Core manual

    First off, this is a great thing to have and it is well done. I found a few things working through it. I am only in the 2nd section, so if you like I will keep posting notes as I go. This is what I have found so far:


    PHP Code:
    // Entire document is searched
    Ext.select('div:nth-child(2)'); 
    Ext.select isn't in the api docs
    ----

    PHP Code:
    var el Ext.get('myElementId');
    el.addClass('error'); 
    After executing this code, the font color in the paragraph above will change to red. This page has a CSS rule which changes all elements with a class of error to the color red. The CSS rule looks like this:
    class error is missing from the style sheets
    -----

    PHP Code:
    <div type="myCls">Hello</div
    type instead of class
    ------
    PHP Code:
    var el Ext.get('elId');
    var 
    dhConfig = {
        
    tag'p',
        
    cls'myCls',
        
    html'Hi I have replaced elId'
    };

    // creates a new node and appends it to 'elId'.
    el.createChild(dhConfig); 
    It doesn't replace elId, it creates a child to it.

    ------

    PHP Code:
    // wraps elId with the newly create element
    Ext.fly('elId').wrap({
        
    tag'p',
        
    cls'myCls',        
        
    html'Hi I have replaced elId'
    }); 
    Doesn't replace elId, wraps around it. That message will actually be before it.

    -----

    For both Select and Query

    Select takes a query and returns an array of dom nodes.
    Confusing, I know what you mean, but if I didn't I would be scratching my head. Change to something like,
    First argument is a css3 selector string and the return is an array of dom nodes.
    ----
    HTML Fragments

    No concept explained. Examples leave you wondering what the overall concept of the relative parameters mean.

    Something should say the where string is in relation to the openning(begin) or closing(end) tags of the element.

    HTML Fragments relate to opening and closing tags. The opening tag is referred to as the begin, and the closing as the end. beforeBegin would place the fragment before the opening tag, afterBegin would place the fragment after the opening tag. beforeEnd would place the fragment directly before the closing tag, and afterEnd would immediately follow it.
    -----

    insertHTML, why does it default to DOM node return, seems rest of calls default to Element? Should be consistent. Not a documentation problem, but library consistency.

    ----

    The document doesn't follow the left hand menu after Element->Manipulation

    ----

    Need a bit more on the diff between remove (element) and removeNode(domNode). What happens if I remove a dom node that has an attached element?

    Removing an element also removes the DOM Node it is associated with. Removing a Dom Node does not remove any associated Elements and will cause them to break if used after the DOM Node is removed.
    ----
    PHP Code:
    Ext.fly('myEl').on('click', function(et) {
        
    // perform an action on click of myEl
        // e is an Ext.EventObject describing what occured
        // t is the target HTMLElement
    }); 
    Ext Core normalizes the arguments of all Dom events. The event handler which is tied to the event will always receive a normalized event object (Ext.EventObject) and the target HTMLElement.
    Shouldn't this be an Ext.Element instead of HTMLElement?


    ------

    HTMLElement and Dom Node are used interchangeably, Dom Node would be clearer.

    ------

    PHP Code:
    var myDiv Ext.get('myDiv');
    myDiv.on("click"handleClick);
    //or
    Ext.EventManager.on('myDiv''click'handleClick);
    Ext.EventManager.addListener('myDiv''click'handleClick); 
    shouldn't this be included
    PHP Code:
    Ext.get('myDiv').on("click",handleClick); 
    -----

  7. #7
    Sencha User carol.ext's Avatar
    Join Date
    Jun 2007
    Location
    Littleton, Colorado, USA
    Posts
    708
    Vote Rating
    36
      0  

    Default [3.0 beta core] Ext.select

    Ext.select() is not documented in 3.0 beta core API. The tabs example uses it. I searched source to find that it is shorthand for Ext.Element.select. I guess I should know that from 2.x

    tabs.js:
    PHP Code:
    Ext.select('.tab-buttons-panel').on('click', function(et) { 
    CompositeElementLite.js
    PHP Code:
    Ext.select Ext.Element.select
    [Edit] Thanks MJ for moving to correct thread. deanna already mentioned this one earlier in this thread
    Last edited by carol.ext; 6 Apr 2009 at 8:32 AM. Reason: note added about duplicate

  8. #8
    Ext User
    Join Date
    Mar 2008
    Posts
    7
    Vote Rating
    0
      0  

    Default Typo

    There is a typo in Element -> Advanced Event Handler -> buffer

    "hanlder" should handler


    Great stuff!

    cheers
    Pedro

  9. #9
    Sencha Premium Member Kazuhiro Kotsutsumi's Avatar
    Join Date
    Sep 2007
    Location
    Japan
    Posts
    82
    Vote Rating
    1
      0  

    Default Ext.encode and Ext.util.JSON.encode not move.

    Hi.

    Ext.encode and Ext.util.JSON.encode is not move.

    Ext Core is not implement Ext.isDate.

    JSON.js LINE:111
    Code:
            }else if(Ext.isDate(o)){

  10. #10
    Sencha Premium Member Kazuhiro Kotsutsumi's Avatar
    Join Date
    Sep 2007
    Location
    Japan
    Posts
    82
    Vote Rating
    1
      0  

    Default

    Class Ext.Template in compile method is JS Error.

    LINE:112-115
    Code:
    function fn(m, name){
        name = "values['" + name + "']";
        return "'"+ sep + name + " == undefined ? '' : " + name + args + ")" + sep + "'";
    }
    arg is not defined.

Page 1 of 5 123 ... 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
  •