What's the point of having Array documentation

[jay@moduscreate.com]

It's simply cluttering up the docs. When did Sencha decide on documenting JavaScript along with Sencha frameworks?

http://docs-devel.sencha.com/touch/2...ce/Array.html#

[Jamie Avins]

Wow, someone complains that we have TOO MUCH documentation? Hell hath frozen over!

[jay@moduscreate.com]

I'm not complaining that it's too much, just not "Sencha touch-specific" .

[rdougan]

I don't think it is a bad thing. I'm sure there are people coming to ST who have very little JavaScript knowledge.

[jay@moduscreate.com]

I see where you're coming from. I think historically, JavaScript documentation has not really made its way into Sencha products.

Not to mention that browsing to it might confuse end-users initially because of the duplication. I might be an edge case, but when I view docs, I scroll directly to the methods. Jumping directly to Date breaks that flow. :-\ I now have to pay attention to the icon color and the position of "Date" in the doc tree.

[jay@moduscreate.com]

Perhaps they should be moved to a "JavaScript" subtree.

[RWaters]

Perhaps they should be moved to a "JavaScript" subtree.

+1

[edspencer]

Possibly, or into a guide. Docs are so important and we often overlook complete JS newbies. We have an incredibly exciting secret project coming up to address this better but I think there is value in having the native objects documented in the same place