-
25 Aug 2012 6:46 AM #1
ExtJS 4.1 - Unknown component "Ext.panel.Form" in ExtJS 4.0 docs
ExtJS 4.1 - Unknown component "Ext.panel.Form" in ExtJS 4.0 docs
Folks,
In the documentation of ExtJs 4.0, http://docs.sencha.com/ext-js/4-0/#!/guide/components, it shows a component named Ext.panel.Form in the component tree hierarchy structure.
But when I tried searching for that component in the docs, the component is not available.
I think, that component is should be re-named to Ext.form.Panel in that tree image.
Could someone please take a look at it ?
Thanks--
Bomslang,
Software Engineer,
HTML5 Developer | ExtJS, Sencha Touch, GXT Passionate | Json Supporter
Twitter : @bomslang
----------------------------------------------------------------------------------
# Learn about Sencha Products via it's Documentation : ExtJS | Sencha Touch | GXT
# Check for correct Json here : JSONLint.com
# Want to code Sencha Touch Online ? Try SenchaFiddle.com
# Want to code and test ExtJS Online ? Try http://ext4all.com/ & http://jsfiddle.net/
# Must Read : 20 things to avoid / do when starting with ExtJS or Sencha Touch
-
25 Aug 2012 1:44 PM #2
It is there ...
http://docs.sencha.com/ext-js/4-0/#!/api/Ext.form.Panel
It shows under: Ext.FormPanel or Ext.form.FormPanel
The 4.0 docs may be missing this info .. please use the latest version: (Ext.form.Panel)
http://docs.sencha.com/ext-js/4-1/
http://docs.sencha.com/ext-js/4-1/#!/api/Ext.form.Panel
Scott
-
25 Aug 2012 8:37 PM #3
I am not talking about Ext.form.Panel. I know it's there in the docs of 4.0 as well as 4.1
I am talking about this unknown component - Ext.panel.Form shown in the tree hierarchy.
(http://docs.sencha.com/ext-js/4-1/#!/guide/components)
It's unavailable in the docs, but still shown in the tree hierarchy in the docs.
See this image : http://i49.tinypic.com/zy7l03.jpg
Thanks--
Bomslang,
Software Engineer,
HTML5 Developer | ExtJS, Sencha Touch, GXT Passionate | Json Supporter
Twitter : @bomslang
----------------------------------------------------------------------------------
# Learn about Sencha Products via it's Documentation : ExtJS | Sencha Touch | GXT
# Check for correct Json here : JSONLint.com
# Want to code Sencha Touch Online ? Try SenchaFiddle.com
# Want to code and test ExtJS Online ? Try http://ext4all.com/ & http://jsfiddle.net/
# Must Read : 20 things to avoid / do when starting with ExtJS or Sencha Touch
-
25 Aug 2012 8:49 PM #4
Looks like someone was in a hurry when the created that image .. should be:
Ext.form.Panel, not Ext.panel.Form
Scott.
-
25 Aug 2012 8:55 PM #5
Yes! Can you please report a request to change that, otherwise it could create a confusion among the other developers seeing that component ?
Thanks--
Bomslang,
Software Engineer,
HTML5 Developer | ExtJS, Sencha Touch, GXT Passionate | Json Supporter
Twitter : @bomslang
----------------------------------------------------------------------------------
# Learn about Sencha Products via it's Documentation : ExtJS | Sencha Touch | GXT
# Check for correct Json here : JSONLint.com
# Want to code Sencha Touch Online ? Try SenchaFiddle.com
# Want to code and test ExtJS Online ? Try http://ext4all.com/ & http://jsfiddle.net/
# Must Read : 20 things to avoid / do when starting with ExtJS or Sencha Touch
-
25 Aug 2012 9:07 PM #6
Thanks for the report! I have opened a bug in our bug tracker.
-
25 Aug 2012 9:14 PM #7
Thanks Scott
--
Bomslang,
Software Engineer,
HTML5 Developer | ExtJS, Sencha Touch, GXT Passionate | Json Supporter
Twitter : @bomslang
----------------------------------------------------------------------------------
# Learn about Sencha Products via it's Documentation : ExtJS | Sencha Touch | GXT
# Check for correct Json here : JSONLint.com
# Want to code Sencha Touch Online ? Try SenchaFiddle.com
# Want to code and test ExtJS Online ? Try http://ext4all.com/ & http://jsfiddle.net/
# Must Read : 20 things to avoid / do when starting with ExtJS or Sencha Touch
You found a bug! We've classified it as
EXTJSIV-7086
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote