PDA

View Full Version : API Doc issues



westy
16 Feb 2011, 9:43 AM
You're probably aware of some of these, but thought I'd mention them just in case.


No way of selecting Ext page from tree, only from a link within a page.
Lots of broken links, or elements in the tree broken;
e.g. search for 'direct', and select 'directFn' (for TreeLoader); built URL is a bit bonkers, being 'http://localhost/new/ext-js/4-0/api/Ext.tree.TreeLoader#config.directFn'!
(have my virtual setup to 'http://localhost/ext-4.0-pr1/docs/api/' if that helps BTW).


Probably others, and think the last one is quite far reaching.

Enjoying reading what's there though!

Cheers,
Westy

margozzi
16 Feb 2011, 11:14 AM
No docs for Ext.data.XmlStore. XmlStore.js exists, I can see it in the src directory. It doesn't show up in the docs tree control thought XmlReader and Writer do.

tobiu
16 Feb 2011, 12:05 PM
We really need the Tabs back for the API.
Jumping between several open ones saves lots of time.

The title of classes open the link to the source in the same browser window, a new window / tab is prefered.


best regards
tobiu

ibnesayeed
16 Feb 2011, 12:48 PM
The search field above the tree has many issues:


Suggestion population is unpredictable, as it some times grows along typing more letters. E.g. try typing "content" and keep an eye on every keyup.
After typing and then deleting a keyword, suggestion box remains there as it was there before deleting the last letter
Most of the links from search suggestion box are broken
Empty text "Search", does not appear in Firefox but it does appear in Google Chrome

ibnesayeed
16 Feb 2011, 12:52 PM
Plus Plus to multiple tabs and source code in new browser tab/window.

renku
16 Feb 2011, 1:05 PM
While trying to understand Ext.Loader I've bumped into several things:

The documentation of Ext.require() tells me to look at Ext.Loader.require(), but the latter is marked as private.
Documentation for the config options exists in source, but is missing in docs. Clearly just a bug with the documentation generator.
enableCacheBuster config has received a copy-paste documentation from enableDeadlockDetection.
I went looking for the file that contains Ext.Loader, but didn't found one. I found it only contained within ext-core-debug.js and other large files. I would very much like to browse the source of ext-core in its unconcatenated form.
Documentation mentions "if" property - a result of doc-comment placed before if-statement (maybe it should be a normal comment instead).
It's impossible to understand what Ext.Loader.exclude() does by reading the docs. By reading the code I can now understand what it does, but I don't get why? Why does it return a function wrapped inside object? Searching the source code of Ext4 I didn't found a single use of this function.
Related to all this, Ext.onReady is not documented at all. But understanding Ext.onReady is hugely important to understand Ext4 code. No more is it just a shorthand for Ext.EventManager.onDocumentReady - it's instead a shorthand for Ext.Loader.onReady(withDomReady=true).

sg707
16 Feb 2011, 1:36 PM
Not sure if it's just me...but I miss the old layout of the API

nick_p
16 Feb 2011, 1:59 PM
Thanks for all your bug reports. The stand alone documentation is actually an export from a brand new documentation application that will include support for multiple versions of the framework as well as integrated examples, videos and guides, hence the issues you're seeing with some links pointing to localhost.

I'll be addressing all these bugs over the coming days - please continue to report any problems you find or features you'd like to see.

bloudon
16 Feb 2011, 2:49 PM
Add another vote for wanting tabs back. Being able to jump around between multiple class docs without losing scroll state in any one is very useful. Also, the docs themselves now feel too crowded by the surrounding UI cruft - particularly the class tree which isn't wide enough to display some of the longer entries.

renku
16 Feb 2011, 2:57 PM
For the fans of old school, I've generated Ext4 documentation in Ext3 format: http://triin.net/temp/jsduck4/ (My JsDuck tool does certain things better than the official generator, on the other hand it doesn't recognize new Ext4 stuff like mixins.)

While running Ext4 code through JsDuck I've spotted many additional mistakes:


Ext.data.Connection contains <iframe> which screws up the whole page.
Legacy files like Combo-legacy.js have been included when generating the docs. This results in lot of misinformation. For example the whole ComboBox documentation actually comes from Combo-legacy.js file while ComboBox.js is missing a class-level doc-comment.
MessageBoxWindow, CellEditing, RowEditing, Tool, ResizeTracker are also missing class-level doc-comment.
Surface, Sprite, SVG, VML are using /* instead of /**
ScriptTagProxy.js contains @memberOf - should be @member.
/** @scope Ext */ followed by Ext.apply(... is treated as definition of property "apply" on "Ext" object - and so several times.

nick_p
16 Feb 2011, 3:26 PM
Thanks renku, I'll get those issues looked at. Could you let me know the additional functionality JsDuck adds so I can include it in the new docs app?

drian
16 Feb 2011, 3:33 PM
Here's my point of view: the new documentation looks shiny... but honestly, from a developer's point of view, we're only interested in getting the end result. While the new docs look nicer, they lack the functionality and the display of the content itself.

Having a tab panel with a top bar for the buttons to go to config/properties/methods/events is a must as you're forced to scroll to the top everytime you want a quick jump to a specific place.

Also, and this is important, please consider adding a column to specify in what class is defined each inherited function/config - like ext 3 docs have the column "Defined By". When browsing a specific component and checking the config/methods/etc, it should be easy to see from which component that config/property/method/event was inherited.

All in all, the old docs are A LOT more practical and I do consider them a better option to the actual ones.

nick_p
16 Feb 2011, 3:43 PM
drian, this is only a preview release. Rest assured the final documentation will be a big improvement over the old docs. I've made a list of all the issues brought up in this thread so far and will make sure each one is addressed or an explanation provided as to why not. Please keep your suggestions and bug reports coming :)

drian
16 Feb 2011, 3:55 PM
That's some good news, nick.

Also, don't forget to add/change the icons on the left tree grid as it's easier to spot a certain type of component only by checking its icon.

Moreover, in the documentation itself, the right sidebar where the super classes/mixins/sub classes are listed is taking too much space. Often there are only a handfull of classes that go in there and that whole side that is not used takes space. Maybe a floated div displaying that list of classes is more suitable.

gluck!

ibnesayeed
16 Feb 2011, 10:21 PM
Class tree can be shown in a floating panel bound to a button in the toolbar. Or at least a handle to collapse/expand currently allocated column.

+1 to top toolbar.

renku
17 Feb 2011, 12:36 AM
Could you let me know the additional functionality JsDuck adds so I can include it in the new docs app?

Sure. Most of it is outlined in its Github page (https://github.com/nene/jsduck), but the main things are support for Markdown syntax in comments, and inferring more information from source like @class and @extends.

tobiu
17 Feb 2011, 4:12 AM
Ext.AbstractPanel



bodyBorder : Number/Boolean
A shortcut for setting a border style on the body element. The value can either be a number to be applied to all sides, or a normal css string describing borders. Defaults to undefined.

bodyMargin : Number/Boolean
A shortcut for setting a margin style on the body element. The value can either be a number to be applied to all sides, or a normal css string describing margins. Defaults to undefined.

bodyPadding : Number/Boolean
A shortcut for setting a padding style on the body element. The value can either be a number to be applied to all sides, or a normal css string describing padding. Defaults to undefined.

steffenk
17 Feb 2011, 4:52 AM
why these properties? They are all part of style, i'd prefer one bodyStyle property.

tobiu
17 Feb 2011, 6:04 AM
steffen, it has a reason i mark "boolean" red.

you can either specify a number or a string.


best regards
tobias

mw-flow
17 Feb 2011, 7:14 AM
We really need the Tabs back for the API.
Jumping between several open ones saves lots of time.

+1 on Tobias' opinion.

I've seen the ExtJS API docs grow in both functionality and usability over time during 2.x and 3.x. Getting accustomed to the new (and -admittedly- visually smooth) ExtJS 4 API docs page is the one thing, and I'm sure I'll get accustomed to them. However, so far, the ExtJS 4 API docs are several steps backward compared to 3.x and even 2.x as some folks here already have pointed out.

But maybe this is only due to this release being a preview...

Christiand
17 Feb 2011, 7:44 AM
Also, having to scroll back to top to have access to "Config, Properties, Method, Events) buttons is pretty bad. This has been mentioned before, but it's worth another mention!

6dust
17 Feb 2011, 7:47 AM
Would it be possible to add the xtype, where available, to the documentation page? I've never liked having to jump back to the Component page just to look at the list. If I were smart enough, I'd just have them all memorized... :)

iesdeveloper
17 Feb 2011, 8:13 AM
Add my vote for putting the class 'xtype' in the API docs for the specific class it relates to.

That would be very helpful...

mschwartz
17 Feb 2011, 8:44 AM
The UI is shiny new, but has lost a lot of usability. Reloading the entire browser when I click on a link in the tree is not a neat way to show off ExtJS's capabilities.

+1 to going back to the tabbed interface.

(The Ext Core docs were terrible last time I looked. The side tabs made my browser jump all over the place)

+1 also to xtypes on the doc pages. This is a long ago requested change.

nick_p
17 Feb 2011, 11:47 AM
Thanks for the useful comments everyone, I've been knocking bugs off one by one.

The reason the entire page reloads when you click a class is so that you do not need to run a local web server in order to view the docs. The 'static' version of the docs that ship with the framework are designed to work over the 'file://' protocol, unlike older versions. The live version of the docs work as the previous ones did, with full ajax and history support.

There is also a new feature that I hope will be more useful than the old tabbed interface, but you'll have to wait for the next release to see it...

mschwartz
17 Feb 2011, 1:20 PM
Thanks for the useful comments everyone, I've been knocking bugs off one by one.

The reason the entire page reloads when you click a class is so that you do not need to run a local web server in order to view the docs. The 'static' version of the docs that ship with the framework are designed to work over the 'file://' protocol, unlike older versions. The live version of the docs work as the previous ones did, with full ajax and history support.

There is also a new feature that I hope will be more useful than the old tabbed interface, but you'll have to wait for the next release to see it...

Use an iframe at least, so the entire page doesn't have to reload.

;-)

Seboss
17 Feb 2011, 2:19 PM
Please bring back the expand/collapse all buttons. Documentation items have to be expanded to be searchable by the browser.

nick_p
24 Feb 2011, 5:09 PM
The majority of the bugs brought up in this thread so far have been fixed in the PR2 release which should have just gone live.

Please post any more bugs you find with the API Docs or new feature suggestions here. I'm looking forward to implementing as many as I can before final release of Ext 4.

The only issue not yet addressed is multiple tabs and ajax loading of pages, rather than a full page refresh when clicking a class. This should be fixed by the Beta 1 release.

CasualNetworks
24 Feb 2011, 6:29 PM
Just a couple of small things... Tested in both Chrome and Firefox

Dead Link
http://dev.sencha.com/deploy/ext-4.0-pr2/docs/api/Ext.Object.html
http://dev.sencha.com/deploy/ext-4.0-pr2/docs/api/Ext.String.html
http://dev.sencha.com/deploy/ext-4.0-pr2/docs/api/Ext.Number.html

Blank Page - Given how much this one is used, probably a big deal
http://dev.sencha.com/deploy/ext-4.0-pr2/docs/api/Ext.Component.html

This is under the Ext Root, rather than Ext.Updater
Ext.Updater.BasicRenderer

Christiand
24 Feb 2011, 6:53 PM
The majority of the bugs brought up in this thread so far have been fixed in the PR2 release which should have just gone live.


good, the config option, properties, method, event stick on top and have clickable overhelp. nice touch ! I'm starting to like this. Also, you changed the font(?), this one is way easier on the eye.

mikejthompson
24 Feb 2011, 7:29 PM
Links to Exp.Component point to http://dev.sencha.com/deploy/ext-4.0-pr2/docs/api/Ext.Component.html which is an empty page.

firefoxSafari
24 Feb 2011, 8:16 PM
The width on the west side looks off. It even results in a double scrollbar in IE8.

muratyildiz
25 Feb 2011, 3:39 AM
There is nothing related to Ext.form.ComboBox. Ext.form.ComboBox.html file is 0 KB.

muratyildiz
25 Feb 2011, 3:45 AM
Many of api files are 0 KB.

24862

westy
25 Feb 2011, 6:06 AM
Hmm, mouse over the links on the main page, http://dev.sencha.com/deploy/ext-4.0-pr2/docs/

Many are correct, but some still not right, Component directs to localhost:3000 for example.
When mousing around I keep seeing paths of http://dev.sencha.com/deploy/ext-4.0-pr2/docs/../path too, which is a little odd.

firefoxSafari
25 Feb 2011, 8:22 PM
I'm not having much luck with the pr2 docs in IE8.

http://dev.sencha.com/deploy/ext-4.0-pr2/docs/

None of the labels for the west side navigation show up in IE8. Looks ok in FF. There is a JavaScript error.

Ext.get("expandAllMembers") is null
class_docs.js line 208

sebascabot
25 Feb 2011, 9:24 PM
I open the new API Doc for the time(ext4.0-pr2), and then
move right away to Ext.core.Element, I frenetically click the first link I saw,
'Ext.Fx' link in the second paragraph and got a blank page. Not very helpful ;-(

I'm not complaining here, I appreciate all the improvement,
but I hit an error so fast it leave a bad impression.

Congratulation for Ext4, it's an amazing piece of software and thanks for sharing.

Bye.

CasualNetworks
27 Feb 2011, 4:54 PM
Ext.form.FormPanel > autoDestroy > Description

Notice the "(defaults to true). Defaults to false."

"If true the container will automatically destroy any contained component that is removed from it, else destruction must be handled manually (defaults to true). Defaults to false."

gevik
28 Feb 2011, 1:19 AM
How do I generate the docs myself? ext-doc? or something else?

renku
28 Feb 2011, 1:39 AM
As far as I know, Sencha is planning to release the documentation tool eventually, but at the moment it's not publicly available. Mostly for the reason that it's still a work in progress.

For now you can use my JsDuck (https://github.com/nene/jsduck) tool. Although it produces the docs in Ext3-style, but if you pull the latest version from Github, you'll get the support for most Ext4 syntax. (Maybe I should publish a gem of the latest version...)

Anyway... it seems that Sencha doc-generator and JsDuck are joining some forces - so you shouldn't be that far off using JsDuck.

gevik
28 Feb 2011, 5:41 AM
it seems that Sencha doc-generator and JsDuck are joining some forces

Can you explain more please?

renku
28 Feb 2011, 6:18 AM
I'm not sure I have much more to tell. The whole issue is still quite open.

Maybe Nick can give some more insight...

sg707
28 Feb 2011, 7:14 AM
Just checked out the pr2 and here are some issue w/ API. Not sure if someone posted.

If you typed "obser", you get a huge list of items to choose...but it doesn't give option of "scroll bar"

When I clicked Component, I just get a blank page.

Just curious, is there a hidden ExtJS 4 API that is on sencha server?

icflorescu
28 Feb 2011, 8:04 AM
I'm not sure this is the right place to post this but in Ext.data.Model (http://dev.sencha.com/deploy/ext-4.0-pr2/docs/api/Ext.data.Model.html) usage examples section we have this:


//tells the Proxy to destroy the Model. Performs a DELETE request to /users/123
user.destroy({
success: function() {
console.log('The User was destroyed!');
}
});


Right now (in developer preview 2) there's no destroy() function defined in Model.js; I think calling it will simply fall back to the empty function Ext.Base.destroy().

This may be misleading for some people...

nick_p
28 Feb 2011, 9:41 AM
Thank you all for your bug reports - please keep them coming. I am continuing to address them one by one.

The new documentation app is still under heavy development and wont be publicly released any time soon (if at all). For the meanwhile I'd recommend using JSDuck if you would like to generate your own documentation as it has support for Ext 4. Internally we are looking at using JSDuck to export the documentation to JSON which can then be processed by the new app.

renku
28 Feb 2011, 11:04 AM
To make matters simpler for those interested, I've pushed out 0.4 version of JsDuck to rubygems.org. So you don't need to use the Github version to get Ext4 support.

Seana
28 Feb 2011, 11:06 AM
just another "broken link"

in Ext.panel.Panel in the "overview" section there is a paragraph



Panel also provides built-in expandable and collapsible behavior, along with a variety of prebuilt tool buttons that can be wired up to provide other customized behavior. Panels can be easily dropped into any Container or layout, and the layout and rendering pipeline is completely managed by the framework.

where prebuilt tool buttons Points to
http://dev.sencha.com/deploy/ext-4.0-pr2/docs/api/Ext.panel.Panel.html#tools

However there is no tools heading to point at.

CasualNetworks
28 Feb 2011, 5:09 PM
#1
Hide inherited members - Does not work using forward and back buttons (the box stays checked, but all classes will show) - Tested Chrome 11

#2
Ext.form.Checkbox - Formatting is incorrect, description is on the same line

setValue Sets the checked state of the checkbox, and invokes change detection.( Boolean/String checked) : Ext.form.Checkbox

#3
Does not have a Favicon - Enhancement Request...

CasualNetworks
28 Feb 2011, 5:52 PM
Happened to open the API in Firefox with Firebug open and noticed the following error when looking at the http://dev.sencha.com/deploy/ext-4.0-pr2/docs/

Error 404
http://dev.sencha.com/new/ext-js/4-0/classes.json?_dc=1298943166270

steffenk
1 Mar 2011, 1:49 AM
For me the old style doc is much better:
http://triin.net/temp/jsduck4/

Thanks for mentioning the jsDuck project!

mw-flow
1 Mar 2011, 8:03 AM
For me the old style doc is much better:
http://triin.net/temp/jsduck4/

For me, too.
I so much loved the possibility to have the doc of several classes open simultaneously via the tabs feature in the 3.x API docs.

firefoxSafari
1 Mar 2011, 8:14 AM
For me the old style doc is much better:
http://triin.net/temp/jsduck4/


+1

It would also be great if there was an official way to download them as an AIR application like we could back in the day.

jan.harmsen
1 Mar 2011, 11:07 PM
Panel / FormPanel: no config option 'buttons' in the docs

While config option 'items' (Object / Array) is in the docs, config option 'buttons' is not.
This should get fixed.

Thanks!

icflorescu
2 Mar 2011, 9:34 AM
Ext.data.HasManyAssociation (http://dev.sencha.com/deploy/ext-4.0-pr2/docs/api/Ext.data.HasManyAssociation.html) and Ext.data.BelongsToAssociation (http://dev.sencha.com/deploy/ext-4.0-pr2/docs/api/Ext.data.BelongsToAssociation.html):

I think the examples are a bit fuzzy there. On both documentation pages association fields are defined in models:


Ext.regModel('Product', {
fields: [
{name: 'id', type: 'int'},
{name: 'user_id', type: 'int'},
{name: 'name', type: 'string'}
]
});

Ext.regModel('User', {
fields: [
{name: 'id', type: 'int'},
{name: 'name', type: 'string'}
],

hasMany: {model: 'Product', name: 'products'}
});

and


var Category = Ext.regModel('Category', {
fields: [
{name: 'id', type: 'int'},
{name: 'name', type: 'string'}
]
});

var Product = Ext.regModel('Product', {
fields: [
{name: 'id', type: 'int'},
{name: 'category_id', type: 'int'},
{name: 'name', type: 'string'}
],

associations: [
{type: 'belongsTo', model: 'Category'}
]
});


As far as I know there's no need to explicitly define user_id and category_id fields, they are created automatically if you specify hasMany/belongsTo associations.
In my opinion those fields should be removed, otherwise some people will believe you have to define them in order for the relationship to work.

Also, I've noticed the minimum you have to do to create an association is to define at least the hasMany part. It's a bit unclear when/why you need belongsTo on the other model.
For instance, I'd use both only for aggregations (from the UML perspective).

sg707
2 Mar 2011, 1:21 PM
I think it's good idea to have

belongToModel_id field

This could be a self document code to let the server know that it needs to output that id field

for example

If you ever need to execute

categoryRecord.getProduct()

then it will not format the URI correctly to get the associated Product. Of course, this is assuming that Server did not loaded the "product_id" when invoking Category.load

gevik
2 Mar 2011, 1:50 PM
Thank you all for your bug reports - please keep them coming. I am continuing to address them one by one.

The new documentation app is still under heavy development and wont be publicly released any time soon (if at all). For the meanwhile I'd recommend using JSDuck if you would like to generate your own documentation as it has support for Ext 4. Internally we are looking at using JSDuck to export the documentation to JSON which can then be processed by the new app.

It is very unfortunate that the dev team is thinking about NOT releasing the official doc generator. Basically this means that some of us who are developing components are left with no choice than using third party tools to generate docs for our components :(

Since JSDuck is ready, why not adopt it as the official doc generator? It even has a basic JavaScript lexer/parser for finding the mixins!

BTW, if mixins where documented with a new tag like @mixin then the only thing left to do was to creating a new UI template (the xsl files) and having the old ext-doc to recognize the @mixin tag (easy done in java sources), right?

One thing that puzzles me the most it that, the "in development" doc generator already generates docs for Ext4, so I guess the parser part is mostly ready. Am I correct to say the the remaining work is in the HTML and JavaScript templates?

arthurakay
2 Mar 2011, 2:00 PM
I'm noticing that some config options aren't showing... "dockedItems" being just one of many.

Also, ArrayStore is missing.

nick_p
2 Mar 2011, 2:50 PM
gevik, I did not say that we would definitely not be releasing the docs app, only that we have not yet made a decision. The new docs app is built upon CouchDB, NodeJS, connect and express and still relies upon the old ext-doc project to export the raw docs. In its current form a public release would be more trouble than it's worth, especially with projects like JSDuck already out there.

The entire reason for re-writing the docs app may not yet be apparent as the new functionality has not yet been exposed. With a live, database driven application we can add lots of new functionality such as multiple framework versions, integrated examples, guides, articles, videos and comments, something not possible with the current implementation. This will provide our users with a much richer set of resources to draw upon while working with our products.

For now, JSDuck is being actively maintained and is more than adequate for the task you described - there's nothing wrong with using an 'unofficial' project. One possible feature is a dedicated section of the new docs app for community plugins. Community members could contribute their raw JSDuck JSON exports for inclusion on the official docs app. Such a feature is not at the top of the priority list for now though.

In the meanwhile, please keep your bug fixes, comments and feature suggestions coming!

gevik
2 Mar 2011, 3:52 PM
gevik, I did not say that we ........
In the meanwhile, please keep your bug fixes, comments and feature suggestions coming!

Thank you for clarifying. I am sure the new "doc server" will be a great addition. And thank you for your effort. Could you please let us know how this new tool solves the undocumented parts like the mixin declarations? Does it parse the JS sources like JSDuck or, are we going to see additional doc tags like @mixin in the sources for example?

nick_p
2 Mar 2011, 3:54 PM
At the moment we are using an internally generated class manifest file to determine mixins. Ideally we would be parsing the JS sources like JSDuck though to prevent problems with, for example, forgotten @mixin tags. If we adopt JSDuck, that will be the case.

soulgen
3 Mar 2011, 1:25 AM
In the http://localhost/ext4pr/examples/grid/array-grid.js, line 88:



columnLines: true,
...,


There is a "columnLines" config object of Ext.grid.GridPanel, buat in the API Docs this config object does not described.

firefoxSafari
3 Mar 2011, 10:29 PM
The API docs are broken under IE8. There is a JavaScript error and none of the labels appear on the tree navigation, making it impossible to tell what you're clicking.

Ext.get("expandAllMembers") is null
http://dev.sencha.com/deploy/ext-4.0-pr3/docs/class_docs.js
Line 226

I reported this for PR2 earlier and I was hoping PR3 would fix it but the problem is still there. Is this just happening to me or does everyone else just know to not look at the docs in IE8?

kyr0
4 Mar 2011, 2:29 AM
Ext.container.Viewport in PR3 docs result in a CouchDB error :)

nick_p
4 Mar 2011, 10:00 AM
firefoxSafari - thanks for you IE report - it seems the wget program used to export the static version of the documentation does not recognise conditional IE statements. I'll make sure it addressed by the next release.

firefoxSafari
4 Mar 2011, 1:26 PM
firefoxSafari - thanks for you IE report - it seems the wget program used to export the static version of the documentation does not recognise conditional IE statements. I'll make sure it addressed by the next release.

Excellent - thanks for the update.

LesJ
4 Mar 2011, 1:45 PM
Ext.Base inline doc typos

speciciesName --> speciesName


Ext.define('My.Cat', {
statics: {
speciciesName: 'Cat' // My.Cat.speciciesName = 'Cat'
},

westy
7 Mar 2011, 6:49 AM
Might be in here already, but:

http://dev.sencha.com/deploy/ext-4.0-pr3/docs/api/Ext.Controller.html
->
{"stack":"Error: CouchDB Error: {\"key\":\"Ext.Controller\",\"error\":\"not_found\"}\n at /Users/nick/local/lib/node/.npm/couch-client/0.0.4/package/lib/couch-client.js:183:21\n at Array.forEach (native)\n at /Users/nick/local/lib/node/.npm/couch-client/0.0.4/package/lib/couch-client.js:179:22\n at IncomingMessage. (/Users/nick/local/lib/node/.npm/couch-client/0.0.4/package/lib/couch-client.js:80:45)\n at IncomingMessage.emit (events.js:59:20)\n at HTTPParser.onMessageComplete (http.js:111:23)\n at Socket.ondata (http.js:1183:22)\n at Socket._onReadable (net.js:654:27)\n at IOWatcher.onReadable [as callback] (net.js:156:10)","message":"CouchDB Error: {\"key\":\"Ext.Controller\",\"error\":\"not_found\"}","errno":2}

This running off your local machine Nick? :)

westy
7 Mar 2011, 6:57 AM
Ext.ClassManager.create

- className : String
The class name to create in string dot-namespaced format, for example: 'My.very.awesome.Class', 'FeedViewer.plugin.CoolPager' It is highly recommended to follow this simple convention:

The root and the class name are 'CamelCased'
Everything else is lower-cased


Erm, camel case has a lowercase prefix, think you mean Pascal case?

xjpmauricio
7 Mar 2011, 8:21 AM
Hi, i know we all hate IE, any version of it, i've used IE8 for this, here's how it looks:

25016

really nasty stuff...
The links on the tree are not show. The page get's reloaded when i click on a link? The previous version didn't do this!

mschwartz
7 Mar 2011, 10:01 AM
http://ie6countdown.com/

sg707
7 Mar 2011, 10:35 AM
Missing Controller and ControllerManager API

sg707
7 Mar 2011, 10:37 AM
Ext.Router API missing all methods. I realize it has draw/connect but it doesn't show any method that belong to Ext.Router

nick_p
7 Mar 2011, 1:18 PM
The Application Architecture documentation will be revamped before the final Ext4 release.

gevik
8 Mar 2011, 5:24 AM
@nick_p,

One of the features missing in the Ext3 docs is the ability to see the updates on the documentation.
It would be really very helpful if it was possible to see what has been changed from one version to another.
I think some kind of a diff would be great.

Would it be possible to implement such functionality in the couchdb solution for Ext4?

Regards,
Gevik.

nick_p
8 Mar 2011, 9:48 AM
Gevik that is indeed a feature we are planning - it would be in the form of a colorised list of methods / events / properties / config options to signify additions, removals and renames for each class in the library. Please let me know any other ideas you have for improvements!

gevik
8 Mar 2011, 11:27 AM
nick,

For the purpose developing Ext4Yii I had to write an app that did the diff, so I can see where to update within changes.

If we are going to have a diff, I think I would be more practical if the changes where not included in the documentation since that would only clutter the doc view. There is enough information on a single class page already. Not to forget that incorporating the changes in the doc pages will not be easy (speaking from experience). Why? simply because we do not record the changes in the source files. You could ask the sencha dev team to mark something as "deprecated/removed" and wait for them to forget to update the comments it in the next version.

Now what is the purpose of a diff? It is basically to see what changed from the previous version to the current version. I think it would be more practical to have this as a separate page (a list perhaps) that is included as part of the release notes. The diff is not something you want to see each time you open the docs. (It would have been great if we could see what changed from pr2 to pr3 for example).

As I have partially done this before, I had to check the following to produce a practical diff.

For each config, property, function, and event.
[1] find the items that are not in previous version (the new stuff)
[2] find the items that are not in this version (the removed or deprecated stuff) (reverse compare)
[3] find the items that exist in both versions but are not the same (updated stuff)

Now the first two is relatively easy to program, but the last one takes more effort since you have to
compare the function parameters and the return types, if any.

[4] last but not least, you have to compare the descriptions and report if they are not the same, which would qualify for "description changed"

The difficulty of creating the diff really depends on which programming language you choose to implement it with. My first two attempts where in Java and PHP but last decided to do it in C# because you have LINQ and closures (especially LINQ)

This was my 2 cents,
I hope I did not waste you time.

Regards,
Gevik.

nick_p
8 Mar 2011, 11:35 AM
Thanks Gevik, that's a useful summary. The diff would be on a separate page to the rest of the documentation and ideally will allow you to pick which versions of the framework to compare, for example the diff between versions 2 -> 4.

Thanks

jan.harmsen
8 Mar 2011, 10:50 PM
[PR3] Ext.Base.statics() inline doc - various errors:

1. typo 'specicies' instead of 'species' (has already been reported)

2. Missing 'extend' statement for class My.SnowLeopard
For the example to work as stated, My.SnowLeopard needs to extend My.Cat, code needs to be:


Ext.define('My.SnowLeopard', {
extend: 'My.Cat',
statics: {
speciesName: 'Snow Leopard' // My.SnowLeopard.speciesName = 'Snow Leopard'
},

constructor: function() {
this.callParent();
}
});

3. .clone() used on wrong object (needs to be katty instead of kitty)
for the example to work as described, it needs to be


var cutie = katty.clone();

PV-Patrick
8 Mar 2011, 11:55 PM
In the comboBox description, there is the following:

A ComboBox works in a similar manner to a traditional HTML <select> field. The difference is that to submit the valueField (http://dev.sencha.com/deploy/ext-4.0-pr3/docs/api/Ext.form.ComboBox.html#valueField), you must specify a hiddenName (http://dev.sencha.com/deploy/ext-4.0-pr3/docs/api/Ext.form.ComboBox.html#hiddenName) to create a hidden input field to hold the value of the valueField.

However, I don't think hiddenName is used anymore.

IntelligentCode
10 Mar 2011, 7:23 AM
Ext.button.Button
focusCls
overCls
pressedCls

not change

gracethief
13 Mar 2011, 4:15 PM
the API Document can not be normally opened in IE8.Got a warnning there 's a error in the code line 51 of search.js. Open this file in Visual Studio 2010, you can find the "default" property can not be complied by the ing IE.

Ozone
13 Mar 2011, 11:03 PM
In Ext4 pr3 API the callback function of window.show states: "Only necessary is animation was specified".
I guess it should be "if".

Ozone
14 Mar 2011, 1:13 AM
Another trivial typo in the API. Under Ext.regModel it says that regModel is a shortcut for Ext.ModelMgr-registerType. Should be Ext.ModelMgr.registerType

And by the way, count me in the queue of users that misses the tabs in the API madly.

nick_p
14 Mar 2011, 11:20 AM
Thanks gracethief - IE is fixed in the next release which should be out shortly.

Ozone I've taken care of those typos. Tabs are being replaced with a new 'favorites' feature which allows you to 'star' classes you use often and keep them at the top of the class listing. These 'favorite' classes will persist across sessions and I hope it will be a more useful feature than tabs. Of course I'll be listening to feedback from the community.

sg707
14 Mar 2011, 11:52 AM
If you're listening, then I'm voting for tabs too.

sg707
14 Mar 2011, 11:57 AM
Thanks gracethief - IE is fixed in the next release which should be out shortly.

Ozone I've taken care of those typos. Tabs are being replaced with a new 'favorites' feature which allows you to 'star' classes you use often and keep them at the top of the class listing. These 'favorite' classes will persist across sessions and I hope it will be a more useful feature than tabs. Of course I'll be listening to feedback from the community.

I don't think replacing "tabs" with a "favorites" feature is not a good idea. Personally, you should have both. Many times, I would look up the API's method then follow along the return type Class API. Then time to time, I would navigate the tabs back and forth trying to find specific methods I'm looking. For example, I would have Ext, Component, Container as part of my "Favorite". But, I probably won't have "Model", "Store" as part of the favorite. Still, having "Model" and "Store" as a tab base will be very useful.

bloudon
15 Mar 2011, 11:15 AM
Agreeing with sg707. I use tabs jump between items of short term interest. Outside of day to day concerns my work touches on nearly every corner of the Ext API. A "favorites" capability for me would quickly end up being a cumbersome clone of the existing class navigation and still would not do anything about preserving scroll positions and property expansions.

IntelligentCode
15 Mar 2011, 9:21 PM
1.all show and hide function not apply(this,arguments), should this.el.show(this,arguments) this.el.hide(this,arguments)

2.first show if autoRender not fire show Event

3.Ext.tip.ToolTip should disable : function(silent) {
var me = this;

if (me.rendered) {
me.el.addCls(me.disabledCls);
me.el.dom.disabled = true;
me.onDisable();
}

//anyway clearTimers,otherwise first show not disable
this.clearTimers();

me.disabled = true;

if (silent !== true) {
me.fireEvent('disable', me);
}

return me;
}

4.Ext.draw.Component

annotation very funny "'implOrder' config" .....

/**
* Create the Surface instance. Resolves the correct Surface implementation to
* instantiate based on the 'implOrder' config.
*/
createSurface: function() {
var surface = Ext.draw.Surface.newInstance(Ext.apply({}, {
width: this.width,
height: this.height,
renderTo: this.el
}, this.initialConfig),this.implOrder);
this.surface = surface;

function refire(eventName) {
return function(e) {
this.fireEvent(eventName, e);
};
}

surface.on({
scope: this,
mouseup: refire('mouseup'),
mousedown: refire('mousedown'),
mousemove: refire('mousemove'),
mouseenter: refire('mouseenter'),
mouseleave: refire('mouseleave'),
click: refire('click')
});
}

ibnesayeed
15 Mar 2011, 11:44 PM
Clicking on search box suggestions don't always work. For example I was looking for Accordion layout. When i typed "acc", I got it in the suggestion list but clicking on it does nothing except hiding the suggestion itself.

jan.harmsen
16 Mar 2011, 3:26 AM
[PR04] new form examples use deprecated code / Ext 4 Overview guide needs update

Use of
buttons[] section in forms is deprecated in ExtJS 4 as stated by user evant in the following thread:
(see also post by user condor in the same thread below post of evant)

http://www.sencha.com/forum/showthread.php?125519-CLOSED-panel-formPanel-buttons-cannot-be-retrieved-anymore&p=576413

Examples for ExtJS 4 like e.g. 'Contact Us form', 'Shopping Cart Checkout' etc. should not use deprecated ExtJS 3 code.

Also the Ext 4 Overview guide needs to be updated and mention that use of
buttons[] section in forms is now deprecated.

radubrehar
16 Mar 2011, 4:39 AM
Hi Nick and all,

I haven't followed all the discussion (so sorry if repeating some things), but here are my issues with the new docs.

1. When I click a class, it opens a brand new page, so it's a full page load. When this happens, I lose the state of the grid in the left, which is quite annoying. The ext 3 version with the ajax load of documentation is really nice, and besides, it loads faster.
2. The favorites think is nice, but for the moment it doesn't keep state between page loads. I'm sure it will be fixed, but just mentioning.
3. The favorites do not replace the tabs :) again, one more vote for the tabs!

Probably it would be nice to have a config page for the documentation, in which one can opt for the features like: tabs and/or favorites; full page loads or ajax load, etc. This would make everyone happier, allowing usage according to personal habits and likes.

Hope this was useful and thanks for the good work!

Christiand
16 Mar 2011, 8:10 AM
It doesn't have to be TABs thought. Under the new favorites (if user as any) there could be another tree node "Last Visited" containing each item you open.

Seana
16 Mar 2011, 8:14 AM
Nick,
While I do think the favorites (even though it is currently broken) is a nice feature, it is a severe step backwards in functionality from the Tabs & AJAX based document loading of the current ExtJS 3.x API Document viewer style. Being able to have the most used/your favorite api documents available at the top of the list is extremely nice there are a number of things that are still left either un-addressed or inefficient from a users standpoint.


quick switching between docs when figuring out what is happening in Object-B when it is being used by Object-C which in turn is a Mixin for Object-A.
time to look at two API docs is increased, unless loading each Document in a new browser tab.
API Navigation Tree collapses on full page reload (certainly correctable sans tabs)
Switching from one document to another and then back causes you to lose not only the position in the document (like the current ExtJS 3 document viewer) but it also collapses the expanded description panels making the resuming of reading where you left of take longer due to the relocation of said collapsed items.


All in all by themselves these issues are minor annoyances, however added together and ran into repeatedly time and time again will cause a reduction in the time we as developers are utilizing to develop and increase the amount of time we spend trying to research what needs to be accomplished. The over all style of the Docs is greatly improved, however for me personally the usability of the docs has, sadly, severely decreased.

dolittle
16 Mar 2011, 8:35 AM
go to:
http://dev.sencha.com/deploy/ext-4.0-pr4/docs/api/Ext.chart.Mask.html
click on "Hide inherited members"
The line below "Methods" disappears.

korax
16 Mar 2011, 9:36 AM
I have to echo the general sentiment that the docs are somewhat hobbled by the removal of tabs. "Favorites" are interesting, and could be useful, but are a poor replacement for tabs.

gubespam
16 Mar 2011, 3:02 PM
Links to "Ext.define", as appear in the doc for Ext.extend, are broken. They correctly link to the Ext.define.html file, but the file itself contains a CouchDB error message, rather than the expected documentation.

IntelligentCode
16 Mar 2011, 7:21 PM
Ext.picker.Date Don't support TableLayout

SebTardif
17 Mar 2011, 4:59 AM
In IE 8, Preview 4, the [Sort By] do not work see: http://dev.sencha.com/deploy/ext-4.0-pr4/docs/

IntelligentCode
18 Mar 2011, 6:13 AM
25220

willy9532
18 Mar 2011, 2:14 PM
Please look at this

http://dev.sencha.com/deploy/ext-4.0-pr4/docs/api/Ext.container.Viewport.html

drian
19 Mar 2011, 1:23 AM
The pop-ups showing the fist of configs/properties/methods/events/mixins/subclasses aren't resized to fit the screen.

On a resolution of 1280x1024 they don't fit properly (the pop-up div gets cut off on the right side).

25238

vmadman
21 Mar 2011, 5:36 AM
http://dev.sencha.com/deploy/ext-4.0-pr5/docs/api/Ext.form.ComboBox.html

This is not loading properly.

tangix
21 Mar 2011, 6:07 AM
Tried using the new API docs in PR5 in FF4-RC1 but search seems to be broken.

To chime in with many others - I am seriously missing the tabbed interface! The new interface is painfully slow and complex to use compared to previous version :-(

sdruckerfig
21 Mar 2011, 10:10 AM
The example for pluck() should be:

Ext.Array.pluck(Ext.query("p"), "className");

instead of:

Ext.pluck(Ext.query("p"),"className");

Also, for Ext.Array.every(), I think "falsy" is misspelled. It should be "falsey"

wemerson.januario
21 Mar 2011, 12:32 PM
Please Tab Navigationnnn, It horrible use it without tabsssss! Thankssss

korax
21 Mar 2011, 12:37 PM
An unclosed <em> tag in the second <code> block of the Ext.panel.Panel page results in the page from that point being italicized, including config options, properties, methods, etc:

// Don<em>'t want content to crunch against the borders

Page affected: http://dev.sencha.com/deploy/ext-4.0-pr5/docs/api/Ext.panel.Panel.html

elwhiz
21 Mar 2011, 1:03 PM
PR4 Search not working.

Nickname
21 Mar 2011, 11:37 PM
Hi everyone,

does anyone keep track of what was reported and what is fixed?

I do understand that Sencha fear a bug tracking system because of the innemerous reports, that will not describe a bug, rather than a wrong usage of the framework. But after reading 11 pages in this "collecting docs issue" thread I am not sure if a bug tracker would be better ;)

And before the question pops up, yes I know what "preview" means, but some basic features of the docs, like the not working search since pr3/pr4 or the missing docs of Ext.Controller*/Ext.Loader.require() is a big problem (at least for me).
On one page I read, that the "application" documentation gets a fresh start. I can just "vote" for that on the next pr6 release, because the new app feature is the base for every application and I can really test new stuff and the combination of serveral widgets, if my basis is stable.

To support you on your way to a stable ExtJs4 here are the docs issues I found so far:

- no docs for Ext.Controller
- no docs for Ext.ControllerManager
- many old ExtJs3 files in Extjs4 docs? (0 bytes file, see *1)
- Ext.require links to Ext.Loader.require(), this is marked @private -> no docs how to use require
- Ext.Class just describes the preprocessors extend mixins, static, config in the examples, but not as "config options". they are registered as default and should be documentated as config options ("Ext.Class.setDefaultPreprocessors(['extend', 'mixins', 'config', 'statics']);"
- Ext.factory is not documented

Hope this is helping


*1) 0 bytes files, relicts from extjs3?
examples:
Ext/docs/api# find . -name "*\.[wW]indow.html" -exec ls -as {} \;
392 ./Ext.window.Window.html
0 ./Ext.Window.html
Ext/docs/api# find . -name "*oolbar.Item*" -exec ls -as {} \;
0 ./Ext.toolbar.Toolbar.Item.html
4 ./Ext.toolbar.Item.html
Ext/docs/api#

renaudham
22 Mar 2011, 3:15 AM
[I]http://dev.sencha.com/deploy/ext-4.0-pr5/docs/api/Ext.fx.Anim.html:
wording mistake on opacity
to : Object
An object containing property/value pairs for the end of the animation. For example:
to : {
opactiy: 1, // Opaque
color: '#00ff00', // Green
left: 500
}


http://dev.sencha.com/deploy/ext-4.0-pr5/docs/api/Ext.data.LocalStorageProxy.html:
you show load and sync in the code examples but they are not listed in the methods

deadlink:
http://dev.sencha.com/deploy/ext-4.0-pr5/docs/api/Ext.grid.GridViewDDplugin.html

Real logic issue?
http://dev.sencha.com/deploy/ext-4.0-pr5/docs/api/Ext.grid.Feature.html
'Features allow you to manipulate the functionality available within a grid view such as grouping, treegrid, rowbody, rowwrap, etc.'
in the blog it's clearly written that the treegrid is now directly handle via the Treepanel, and not via the grid.
So is it a mistake or it can be both at the same time handle via the tree and the grid? I guess not...

Nickname
22 Mar 2011, 10:02 PM
Deadlink ref:
Ext.loader :: setConfig(): options for configuration refer to "{@link Ext.Loader#config}" (from source)
I think it should be{@link Ext.Loader#configs}

dmackerman
23 Mar 2011, 7:49 AM
Ext.tab.TabPanel has a lot of example code that is not formatted at the top of the screen. IE:


basic tab container. TabPanels can be used exactly like a standard Ext.panel.Panel (http://localhost/extjs/ext-4.0-pr5/docs/api/Ext.panel.Panel.html) for layout purposes, but also have special support for containing child Components (`items (http://localhost/extjs/ext-4.0-pr5/docs/api/Ext.container.Container.html#items)`) that are managed using a CardLayout layout manager (http://localhost/extjs/ext-4.0-pr5/docs/api/Ext.layout.container.Card.html), and displayed as separate tabs. __Note:__ By default, a tab's close tool _destroys_ the child tab Component and all its descendants. This makes the child tab Component, and all its descendants __unusable__. To enable re-use of a tab, configure the TabPanel with `autoDestroy: false (http://localhost/extjs/ext-4.0-pr5/docs/api/Ext.tab.TabPanel.html#autoDestroy)`. __TabPanel's layout:__ TabPanels use a Dock layout to position the TabBar (http://localhost/extjs/ext-4.0-pr5/docs/api/Ext.tab.TabBar.html) at the top of the widget. Panels added to the TabPanel will have their header hidden by default because the Tab will automatically take the Panel's configured title and icon. TabPanels use their header (http://localhost/extjs/ext-4.0-pr5/docs/api/Ext.panel.Panel.html#header) or footer (http://localhost/extjs/ext-4.0-pr5/docs/api/Ext.panel.Panel.html#footer) element (depending on the tabPosition (http://localhost/extjs/ext-4.0-pr5/docs/api/Ext.tab.TabPanel.html#tabPosition) configuration) to accommodate the tab selector buttons. This means that a TabPanel will not display any configured title, and will not display any configured header tools (http://localhost/extjs/ext-4.0-pr5/docs/api/Ext.panel.Panel.html#tools). To display a header, embed the TabPanel in a Panel (http://localhost/extjs/ext-4.0-pr5/docs/api/Ext.panel.Panel.html) which uses `layout:'fit' (http://localhost/extjs/ext-4.0-pr5/docs/api/Ext.container.Container.html#layout)`. __Examples:__ Here is a basic TabPanel rendered to the body. This also shows the useful configuration activeTab (http://localhost/extjs/ext-4.0-pr5/docs/api/Ext.tab.TabPanel.html#activeTab), which allows you to set the active tab on render. If you do not set an activeTab (http://localhost/extjs/ext-4.0-pr5/docs/api/Ext.tab.TabPanel.html#activeTab), no tabs will be active by default. Example usage: var tabs = new Ext.TabPanel({ renderTo : Ext.getBody(), activeTab: 0, items: [ { title: 'Tab 1', html : 'A simple tab' },

Nickname
25 Mar 2011, 3:37 AM
Ext.tree.TreePanel has old extjs3 examples (using Ext.tree.Treeloader() and not the new model/store
see http://dev.sencha.com/deploy/ext-4.0-pr5/docs/api/Ext.tree.TreePanel.html

complete TreePanel docs seem to be "old"

example http://dev.sencha.com/deploy/ext-4.0-pr4/examples/tree/tree.js makes use of store config option.
all new extjs4 config options are not documented

EDIT:
clicking on "view source" on http://dev.sencha.com/deploy/ext-4.0-pr5/docs/api/Ext.tree.TreePanel.html for source of Ext.tree.TreePanel opens the page
http://dev.sencha.com/deploy/ext-4.0-pr5/docs/source/TreePanel1.html#...

the correct html file is shipped with the PR releases; have to call it directly to see sources
http://dev.sencha.com/deploy/ext-4.0-pr5/docs/source/TreePanel.html (without the 1)
and then you have ExtJs4 examples ;)

lukerahl
25 Mar 2011, 2:03 PM
Ext.form.FormPanel Overview > Form Submission > At end of sentence, details has an extra "e".

fdp
26 Mar 2011, 3:51 AM
Ext.form.ComboBox.html show only 2 lines, it stops here:


A ComboBox is like a combination of a traditional HTML text field and a

railsjedi
26 Mar 2011, 2:08 PM
I'm trying to brush up on the MVC stuff for Sencha Touch and having trouble with missing pages on the docs.

Ext.ApplicationManager.html (http://dev.sencha.com/deploy/touch/docs/output/Ext.ApplicationManager.html)

this is linked to in the docs for Ext.regApplication

----

Ext.ControllerMgr.html (http://dev.sencha.com/deploy/touch/docs/output/Ext.ControllerMgr.html)

this is linked to in the docs for Ext.regController

-----

Ext.layout.LayoutManager.html (http://dev.sencha.com/deploy/touch/docs/output/Ext.layout.LayoutManager.html)

this is link to in the docs for Ext.regLayout

seenimurugan
27 Mar 2011, 12:50 PM
CheckboxSelectionModel API says defaults mode to MULTI. But in mode config option it says Defaults to 'SINGLE'.

Nickname
27 Mar 2011, 11:05 PM
A lot of documentation for Ext.draw.* is missing.

Ext.data.SpriteGroup has almost no JsDoc in source and so not specific docs are generated.
Ext.data.Sprite has some documentation, but a lot is missing
(except inherited functions et cetera )

By looking at the source of Ext.draw.*, it does not seem like a integrated extjs devolpment :(

tangix
30 Mar 2011, 2:15 AM
Already beaten to death here but as we are approaching release I am getting worried that Ext JS 4.0 will ship with the new docs UI that is horrible compared to earlier versions. The tabs were simply great!

Major concern in PR-5 is that search is broken in FF4 and the navigation tree seems a bit funky with items appears to be missing when expanding and various redraw issues.

aghextjs
30 Mar 2011, 6:18 AM
One more vote for the tabbed UI for the documentation.

LesJ
30 Mar 2011, 6:31 AM
The tabs were simply great!


You can always open each doc in the browser's tab.

It works just as well.

LesJ
30 Mar 2011, 11:35 AM
See this doc:

file:///C:/download/ext-4.0-beta1/docs/api/Ext.tree.TreePanel.html

TreePanel inherits from Ext.panel.TablePanel, but the doc shows that it inherits from Ext.panel.Panel

lishoulin624@163.com
30 Mar 2011, 2:52 PM
I can not jump to the position of the beta1 API document when I click a hyperlink in top toolbar. But it is ok in pr5 version. I browser it in Google Chrome 10.

LesJ
30 Mar 2011, 3:32 PM
Ext.ComponentLoader - there's no header info in the doc about this class

LesJ
30 Mar 2011, 3:51 PM
Ext.tab.TabPanel - overview is messed up

file:///C:/download/ext-4.0-beta1/docs/api/Ext.tab.TabPanel.html

tangix
30 Mar 2011, 10:31 PM
You can always open each doc in the browser's tab.

It works just as well.
I'll guess it does... Great way to consume more memory on a memory hungry browser. Before all tabs shared the same DOM, now each page will have its separate DOM. Given that I after a days work have 10-15 tabs open in the API (that are on the same Browser Tab) I see some scalability issues.

cmendez21
30 Mar 2011, 11:32 PM
Hi, im reporting an issue , when i want to look at VBOX documentation
(Ext.layout.container.Vbox)

the following appears =

Error: CouchDB Error: {"key":"Ext.layout.container.Vbox","error":"not_found"}

and the documentation can't be seen

qq79067942
31 Mar 2011, 2:10 AM
when the focused.expanded is true and trigger onKeyRight, they can insert the focused'childnode to the Treepanel!

Christiand
31 Mar 2011, 2:31 AM
It would be nice to have Sencha comment and tell us on where they are heading with this new DOC. They haven't said a thing in a while.

Seboss
31 Mar 2011, 3:13 AM
In beta 1, the Ext.grid.RowEditing afteredit event documentation is missing a parameter.
The function signature should be:

afteredit(Ext.grid.Editing editor, Object e)

conorarmstrong
31 Mar 2011, 5:27 AM
beta1,

In docs for Ext.tree.TreePanel config option of rootVisible appears twice

ditto for useArrows and singleExpand

christopherbalz
31 Mar 2011, 9:03 AM
Suggest putting a brief note on the TreeStore doc (http://dev.sencha.com/deploy/ext-4.0-pr5/docs/api/Ext.data.TreeStore.html) to the effect that 'TreeReader' has been removed and developers should use the xml and json readers instead.

See: http://www.sencha.com/forum/showthread.php?128447-Ext4-PR5-quot-Cannot-create-an-instance-of-unrecognized-alias-reader.tree-quot&p=585868&viewfull=1#post585868

nick_p
31 Mar 2011, 12:56 PM
I'm planning on making the 'Favorites' menu on the left a dropdown from which you can select 'Recently viewed' as an alternative view, which will provide the same functionality as the tabs from the old docs.

I'm pretty certain you guys will like the new docs functionality when it's unveiled in all its glory. Inline, functional examples (similar to http://jsfiddle.net/), integrated guides and screencasts, theming docs, different framework versions, stats and search engine crawlability are all in the testing phase and should be available when 4.0 is released. The new docs app is designed to be viewed as a 'live' app rather than on your local machine.

Please keep your bug reports coming, I'm making sure each and every issue is addressed or noted.

magex
31 Mar 2011, 2:13 PM
25440

The TabPanel documentation is not formatted properly for 4.0 beta 1..

prometheus
31 Mar 2011, 2:32 PM
http://dev.sencha.com/deploy/ext-4.0-beta1/docs/api/Ext.state.Stateful.html

jan.harmsen
1 Apr 2011, 2:17 AM
[Beta 1] data.ServerProxy api cfg object: inconsistent action methods


/**
* @cfg {Object} api
* Specific urls to call on CRUD action methods "read", "create", "update" and "destroy".
* Defaults to:<pre><code>
api: {
read : undefined,
create : undefined,
update : undefined,
destroy : undefined
}
* </code></pre>
* <p>The url is built based upon the action being executed <tt>[load|create|save|destroy]</tt>
* using the commensurate <tt>{@link #api}</tt> property, or if undefined default to the
* configured {@link Ext.data.Store}.{@link Ext.data.ServerProxy#url url}.</p><br>
* <p>For example:</p>
* <pre><code>
api: {
load : '/controller/load',
create : '/controller/new',
save : '/controller/update',
destroy : '/controller/destroy_action'
}
* </code></pre>
* <p>If the specific URL for a given CRUD action is undefined, the CRUD action request
* will be directed to the configured <tt>{@link Ext.data.ServerProxy#url url}</tt>.</p>
*/

radubrehar
1 Apr 2011, 5:04 AM
Well, you can't open each doc in a new tab, as the menu links don't have a href, and the mouse wheel click won't open a new tab, but open the link in the same page. And even if it would, it disrupts your user experience, and you don't have the feeling like you're using an app, but just a simple site.

One more vote for the tabbed documentation! It provides an app-like and smooth user experience! Please get them back.

Thanks!

Christiand
1 Apr 2011, 5:07 AM
I'm planning on making the 'Favorites' menu on the left a dropdown from which you can select 'Recently viewed' as an alternative view, which will provide the same functionality as the tabs from the old docs.

that would be good, but "Recently Open" as to always be expanded and on top of favorites IMO

LesJ
1 Apr 2011, 6:25 AM
I'd recommend replacing this thread with a new Documentation Sub-Forum (in addition to Bugs and Help).

There are just too many replies in this thread and I'd prefer to rank individual replies.

It's also more manageable to subscribe to smaller threads.

Ozone
1 Apr 2011, 7:19 AM
We really really need those tabs back - take our word for it! :-(
I'm down like 8-10% in efficiency alone because of the missing tabs (depending on the kind of work and level of uncertaincy / need to look up stuff in the API).

The favorites are nice, but they don't really work right now, and even if they did, they would never be more than a supplement to the tabs. They can definately coexist, so what are your reason for removing the tabs?

By the way, I love the mouseover dropdowns on configs/props/methods/events etc. (they almost makes it up for the lost efficiency on the missing tabs :-) ).

Christiand
1 Apr 2011, 7:34 AM
so what are your reason for removing the tabs?


It's to bad they won't answer. But my best bet, since there is a tab named "Overview" and they plan to add the "Example, Video, Screencast" tabs after the Overview.

Look 6-7 post above



I'm planning on making the 'Favorites' menu on the left a dropdown from which you can select 'Recently viewed' as an alternative view, which will provide the same functionality as the tabs from the old docs.

This should be a good alternative to tabs.

nick_p
1 Apr 2011, 3:10 PM
Please see the new API docs thread at http://www.sencha.com/forum/showthread.php?128826-API-Doc-Issues