"The online version of ext2.0a1 does not have a src/ folder. All links to the source code are redirected to the front page." [link]

Originally Posted by tjcrowder

Seemingly throughout the docs, I see things like this:

Code:

{@link Ext.Element Element}

...rather than an actual link to the item listed. And yet in other places, the links work fine. I don't recall this from the alpha1 docs, but it's all over the beta1 docs. The Panel.header and Panel.footer properties are examples, but again, it's a general thing.

BTW, you're doing great work on the docs, folks. Substantial improvements between alpha1 and beta1, really obvious progress.

Class Ext.ComponentMgr

incorrect return type for method get [link]
-- should be Ext.Component

Class Ext.data.Connection

missing closing quote in anchor tag found in description of event requestexception [[post=76278]link[/[post]]

Ext.data.Store's "find" method has this in the summary at the top: "Returns a new collection that has been filtered." It actually returns the index of the record, or -1 (which it correctly says later under "Return"). [link]

Description needs to be updated: "The Store class encapsulates a client side cache of Ext.data.Record objects which provide input data for widgets such as the Ext.grid.GridPanel, or the Ext.form.ComboBox." [link]

Class Ext.Element

Inconsistencies with get/setLeft/Top [link This is NOT bug, but rather a design decision.]

Since it's optional, can the default value for the loadScripts parameter in the update method be specified? [link]

Docs show trackMouseOver as a config entry, but show it defaults to true, which is not the case. [link] - It is inherited from Panel and overridden in EditorGrid to false because it causes errors in FF. It has now been hidden so it should not show up as a valid EditorGrid config.

"Also, what is the difference between 'applyTo' and 'renderTo' and how are they different from the 'el' option? I tried both of these and received errors." [link] - This actually applies to Ext.Component

"The documentation for both the constructor and getKey() should point out that the default getKey function is:" [link]

Code:

function(o) {
return o.id;
}

Over in this thread Jack said he'd added some further params suggested by papasi to the Ext.util.MixedCollection.each method, and indeed the latest source has those new params (index and length), but the docs still talk about the "first and only" parameter... [link]

Class Ext.util.Observable

typo in addListener method's delay config [link]
-- "delay {Number} The number of milliseconds to delay the invocation of the handler after te event fires." ("te" should be "the")

NB: Due to the asynchronous nature of remote server requests, the returned data will not be available to the line immediately following the load() call. To process the returned data, use the callback option, or an {@link #event-update update} event handler.

options.params formatting: "If tt>true any <>script> tags embedded in the response text will be extracted and executed. ...."

Docs for configs discardUrl, nocache, text and scripts are missing. The indentation of the options that are present is not quite right too.

Usage example at top has: "mgr.update("http://myserver.com/index.php", "param1=1&param2=2");" -- It doesn't look like that parameter pattern is supported by the update docs. Either the example is wrong or the update method docs are missing something. [link] - Both formats are supported, but to avoid confusion, I changed the example to the newer config format

_________________________________________________

Samples / Examples

Forms - Customizing:Search Field [link]
-- "Typing in Test will give a 2 page result, but when clicking next page, you would see the total pages changing from 2 to 84." [link]

LayoutManagers - Complex: in the Center Panel tab, the "Toggle the west region" link does nothing.

LayoutManagers - Customizing:Portals

Originally Posted by tjcrowder

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.

_________________________________________________

Misc / Requests

"Also, is there going to be a "Print Friendly" link on each page like the 1.1.1 docs? Sometimes it is handy to print out a section." [link]

"Additional Tree-related issues: (these are from an Ext newbie trying to learn this stuff)" [link]

There's no description at all for the TreeNode and AsyncTreeNode (same in version 1.x docs). Describe the use and difference between the two. Please don't leave it to the user to figure it out for themselves.

The description of AsynchTreeLoader.loader says that it 'defaults to the loader defined on the tree'. How do you define a loader for the tree? There's no options, properties, or methods of a Tree to do that.

If you can create a checkbox for a tree node, how can you assign a value to that checkbox?

Originally Posted by neshaug

It seems like there is alot more config options for components than I can find in the Ext 2.0 docs. I can find many examples that uses: region, minSize, split, margins, el and contentEl. I think I have seen more too, and the advice I get if it's used in an example I should to, but it would be nice to know what these options do.. I've searched the forums and I can't find any relevant posts about it, but I've just started with Ext so I am sorry if this is something obvious I just don't get..

Originally Posted by SeaSharp

It would be nice if the online documentation system reported its minor version number in the top of page banner. This was the reason for my doc bug report above not having a version in the title.

Something like "Ext 2.0 (beta 1) - API Documentation"

Originally Posted by splintor

BTW, the help system can be improved so it is possible to build diret links to a config option, property or method. I would think something like http://extjs.com/deploy/dev/docs/?cl...xt.Window-html would work, but it doesn't. It seems to put the page in an eternal "Loading" mode.

Class Ext.ComponentMgr

Originally Posted by dhurlburtusa

Documentation for methods in Ext.ComponentMgr are missing.
registerType(xtype, cls) and create(config, defaultType).
The shorthand for Ext.ComponentMgr.registerType = Ext.reg is not documented.

Maybe these are intended to be private methods and shorthands although registerType seems essential to adding new components and user extensions.

Class Ext.form.BasicForm

Originally Posted by tjcrowder

The summary for BasicForm talks about overriding the onSubmit method if you want to do a "normal" form submission, but the onSubmit method isn't documented and is marked "private" in the source.

Class Ext.form.FormPanel

Originally Posted by tjcrowder

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.

Originally Posted by tjcrowder

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).

FYI -- the 2.0 docs are known to be not fully complete as of today (they are about 80-90% right now for new 2.0 stuff), but some things we just haven't gotten to yet. However, I hope that some of you 1.0 "old-timers" will appreciate how much there is now vs. when 1.0 alpha came out...

Also, there are still some doc issues from 1.1 that have not yet been addressed that will also carry over to 2.0, so if you can, please verify first that it's not already listed in the 1.1 thread: http://extjs.com/forum/showthread.php?t=10476

The 1.1 doc issues will all be addressed prior to 2.0 final release, so with 2.0, hopefully we'll get to a pretty clean slate and be able to keep it that way. Thanks for your patience, and please continue letting us know about any issues you find!

(PS: I'll update this thread when the 2.0 docs are "content-complete".)