Documentation Bugs - Ext 2.x

[tjcrowder]

Hi folks,

Callling someElement.setLeft(someElement.getLeft()) will move the element slightly under FF and other Gecko browsers, but not under IE and several others. This is because setLeft uses different units than the units getLeft returns by default. The same is true of setTop/getTop. (See this thread for details.) This will not get fixed in 2.x because Jack is concerned about compatibility issues at this stage, so it really needs to be quite clearly documented, specific documentation recommendations here.

[mscdex]

There is a typo in the description of Ext.Panel's setTitle method: "Sets the title text for the panel and optioanlly the icon class."

[gimler]

Ext.Tree.TreePanel stateevents beforemove is now beforemovenode ;(

[joeaudette]

related documentation issue:

There is no mention of the hideable property in the documentation for ColumnModel

Thanks,

Joe

[splintor]

In the Complex Layout sample, in the Center Panel tab, the "Toggle the west region" link does nothing.

[architect]

Hello,
on the API 2.0 page, you used a component called "TwinTriggerField" for the search field. I can't find any documentation about it. Is it part of the RC1 or not?

Thanks in advance

[aconran]

architect -

Yes, TwinTriggerField is part of RC1. It can be found in source/widgets/form/TriggerField.js It is not a public class to be used directly. Others can extend it to implement a field that requires 2 triggers such as the SearchField implementation. This should probably be documented.

[BlackICE1979]

Class Ext.data.Connection
extraParams should be params

[jan1234]

I think the explanation off the iconCls configure option of Ext.tree.TreeNode is too short.

It should describe the following:

When using the iconCls option like this in javascript:

var node = new Ext.tree.TreeNode({iconCls: 'my-icon-class'});

Define your custom icons like this in css:

.x-tree-node-collapsed .my-icon-class {
    background-image: url('collapsed.gif');
}
.x-tree-node-expanded .my-icon-class {
    background-image: url('expanded.gif');
}
.x-tree-node-leaf .my-icon-class {
    background-image: url('leaf.gif');
}
.x-tree-node-loading .my-icon-class {
    background-image: url('loading.gif');
}

[mjlecomte]

General suggestion: Why not keep a reference to deprecated code in the current docs? Use a different CSS style or marker to identify outdated code. Seems like it would be helpful.

Back to the docs:


Ext.Ajax

Several properties not itemized in the docs per the example.

// Basic request
Ext.Ajax.request({
   url: 'foo.php',
   success: someFn,
   failure: otherFn,
   headers: {
       'my-header': 'foo'
   },
   params: { foo: 'bar' }
});

// Simple ajax form submission
Ext.Ajax.request({
    form: 'some-form',
    params: 'foo=bar'
});

// Default headers to pass in every request
Ext.Ajax.defaultHeaders = {
    'Powered-By': 'Ext'
};

// Global Ajax events can be handled on every request!
Ext.Ajax.on('beforerequest', this.showSpinner, this);