Documentation Bugs - Ext 2.x

The doc for the GridPanel's 'cm' config says it accepts a type of 'Store' instead of 'ColumnModel'.

(I assume each report should be done separately, rather than a list in a single post.)

The documentation for Ext.form.FormPanel is missing the getForm method.

Ext.form.FormPanel's documentation should discuss the 'items' config option as it relates to FormPanel (see this thread). It's currently inheriting the Component documentation, which doesn't help you figure out what it's going to do with the configs and specifically how it's going to map configs to classes.

In the summary for Ext.form.FormPanel, I recommend adding a link to Ext.form.Action.Submit so users can readily see the format for the JSON return data for the response to the default form submission feature (which is really cool).

The summary for Ext.form.Action.Submit ends with:

Quote:

---

A response packet must contain a boolean errors property. The , portOfLoading: "This field must not be null" } }

Other data may be placed into the response for processing the the {Ext.form.BasicForm}'s callback or event handler methods.

---

Looks like it could be an issue related to embedded HTML or something.

Quote:

---

Originally Posted by tjcrowder

(I assume each report should be done separately, rather than a list in a single post.)

---

it's ok to combine multiple reports into a single post as long as your references are clear. ;)

WRT the issue already listed in the main post about Ext.reg not being documented (original post), it's used in the examples (examples/layout/portal.js). Recommend either documenting it or using the longhand version in examples. ExtJS is way out in front of other frameworks in terms of the examples provided, this is merely a nit being picked.

Quote:

---

Originally Posted by mystix

it's ok to combine multiple reports into a single post as long as your references are clear. ;)

---

Ah, okay, thanks. I was thinking in terms of marking the subject lines "solved" or something, but of course we're using strikeout and your main list for that, aren't we?

Sorry for the pepper-posting. :-)

Quote:

---

Originally Posted by tjcrowder

Sorry for the pepper-posting. :-)

---

*sneeze* ~o)

There are some properties and other things used in the Portal layout example (examples/layout/portal.js) that aren't documented in the API documentation (or in many cases the code):

1. Panel.body property. Looking at Panel.js, there's an accessor method for it called getLayoutTarget, but that's got a comment above it saying it's private. It's documented now in beta1.

2. ddScrollConfig (both it and its members). Seems to be used by the ScrollManager for this and that, recommend adding it either in the ScrollManager summary or to the description of the register method (or both).

3. Panel.bwrap property.

4. DragSource.proxy property.