Documentation for Open Tooling in Modern and Classic Ext JS 7

[djbushby]

The current documentation is an indiscriminate mix of error-riddled Classic and Modern using CMD.

The CMD MyApp with view/main is very different from npm MyExtGenApp with view/home (that looks like spaghetti code)

https://docs.sencha.com/extjs/7.0.0/...hitecture.html
does not help to understand MyExtGenApp, even if it was updated to 7.0.0.97

I don't mind paying for an error-free online self-paced course of pdfs/htmls and fiddles/code that go from hello-world to a routed npm app with aws amplify and appsync.
Anyone making a Modern Ext JS 7 tutorial?

[branflake2267]

The current documentation is an indiscriminate mix of error-riddled Classic and Modern using CMD.

The CMD MyApp with view/main is very different from npm MyExtGenApp with view/home (that looks like spaghetti code)

https://docs.sencha.com/extjs/7.0.0/...hitecture.html
does not help to understand MyExtGenApp, even if it was updated to 7.0.0.97

I don't mind paying for an error-free online self-paced course of pdfs/htmls and fiddles/code that go from hello-world to a routed npm app with aws amplify and appsync.
Anyone making a Modern Ext JS 7 tutorial?

Thanks for sharing your feedback. I agree I want to make the docs better. I've started some big initiatives here to improve the docs and changes are in the works. I've also queued up the goal to provide a good code lab/tutorial to work though with modern app development. I've filed DOCS-552 internally.

I'm checking around to see what the options are currently and will get back soon.

Thanks,
Brandon Donnelson
Sencha Product Manager

[Necro-Engineering]

I second this request... one of my top 3 frustrations with Sencha is the lack of training/tutorials (without a cost). We live in an era where documentation, community and training are expectations for products like this, with no cost or minimal cost associated. We're fine paying for the product, but to then stack on high costs for training or documentation on how to use that product just doesn't fit todays world where you can get semesters worth of training for $10 on Udemy or other sites. This worked well in the 90s and early 2000s but those days are gone. For a world class product like Sencha, training and education around it should come for free which will foster more growth. It's a cost of doing business.

I hope Sencha re-evaluates this and reconsiders their position on online/web based training.

[branflake2267]

I second this request... one of my top 3 frustrations with Sencha is the lack of training/tutorials (without a cost). We live in an era where documentation, community and training are expectations for products like this, with no cost or minimal cost associated. We're fine paying for the product, but to then stack on high costs for training or documentation on how to use that product just doesn't fit todays world where you can get semesters worth of training for $10 on Udemy or other sites. This worked well in the 90s and early 2000s but those days are gone. For a world class product like Sencha, training and education around it should come for free which will foster more growth. It's a cost of doing business.

I hope Sencha re-evaluates this and reconsiders their position on online/web based training.

Thanks so much for the feedback! I agree with you! I've sparked the push to make our documentation even easier, better and more efficient to use! We have a new focus in this area, so keep your eyes peeled more to come soon.

Thanks,
Brandon Donnelson
Sencha Product Manager

[djbushby]

Hi Brandon,
I created half a dozen fiddles and put then in folders at https://github.com/classbasics/ExtJS7 with commented javascript files and README.md as the index.
Although they do some basics it is more a conglomerate of various useful parts without direction.

I was thinking of making fiddles based on the API folder structure (https://docs.sencha.com/extjs/7.0.0/modern/Ext.html), but it is like learning from a shredded dictionary.

Problems I have is that the docs quality varies, and my trial & error patience is limited:
Information and working fiddles: https://docs.sencha.com/extjs/7.0.0/...tab.Panel.html
One sentence information and non-working fiddle: https://docs.sencha.com/extjs/7.0.0/...CheckItem.html
One sentence: https://docs.sencha.com/extjs/7.0.0/...ind.Multi.html

Any suggestions?

Maybe your documentation should be available for the community to fix.
A typo I mentioned over a month ago hasn't been fixed (https://www.sencha.com/forum/showthr...-typo-miniumal).
Should my 'eyes are peeled' for more errors to come.

How about you set up the structure full of 'To do sections', invite participants, moderate outcomes, explain reasons for excluding work.
As it takes more than a month to respond to a typo, waiting for Sencha approval for participant contributions, would not be agile.

Damien

[djbushby]

Hi Brandon,

I slept on my 'typo' comment and considered that some of my document bugs have been elevated to be fixed.
So I checked the Ext JS 6 docs to see if other typos have been fixed.
My first search
https://www.sencha.com/forum/showthread.php?332571 (30/11/2016)
replied: 'Thanks for the report! I have opened a documentation bug in our bug tracker.' (2/12/2016)
I initially thought that response was very good.
The code bug 'sortabl:true' is still there (https://examples.sencha.com/extjs/6....ink/#form-grid) almost 3 years later.
Damien

[djbushby]

Interesting that the code bug 'sortabl:true' (https://examples.sencha.com/extjs/6....ink/#form-grid) is in the Details-View, but the code actually works (Company is sortable).
This means that you have to update code bug and/or documentation bug.

On 17 Jul 2019 I reported that 7.0.0 documentation was pointing to 6.2 examples, which at the time I thought was okay (https://www.sencha.com/forum/showthread.php?472093)
For a larger example, see the Basic Grid Example.
https://docs.sencha.com/extjs/7.0.0/...nts/grids.html

As it turns out the 7.0.0 document (https://docs.sencha.com/extjs/7.0.0/...nts/grids.html) that points to 6.2 code (For a larger example, see the Basic Grid Example) made 'sortable: false'.
Maybe that was just to show a bad UI, but not a bug.

[branflake2267]

I'm hoping we can open our docs up, although we need to prep a bit more before we can get there. Our docs generator is open to invites at the moment. It's a bit rough around the edges still as it was built for internal use only. We are getting closer to having it ready to open it up, but haven't gotten there yet. We're talking about the guides, and opening them up, but I haven't gotten the green light yet. If you're interested let me know.

The bugs, if I can route that through support, they can enter them, and the team can act on them. They have been logging your reports and changing them. Could you log the issue above in a bug? Send me the link if you don't get any body to add it. (There are some bugs in the docs-generator, not sure it's here...)

[djbushby]

I logged the typo 'sortabl' as a bug.

I would be interested in assisting with the guides, there just needs to be a QA system so I can fix my own mistakes.

I haven't been looking at the docs recently as I was unsure if there would be corrections anytime soon.

[branflake2267]

I logged the typo 'sortabl' as a bug.

I would be interested in assisting with the guides, there just needs to be a QA system so I can fix my own mistakes.

I haven't been looking at the docs recently as I was unsure if there would be corrections anytime soon.

I looked for the type in 7.0 and didn't see the sortabl issue. Were you want to to fix that in the older version? I'll check on the options for access to our guides.

We have been working on changes that have been filed, and I'm scheduling some for 7.1. There is a focus on them, although the release slowed us down and we have a few bigger guides in front to tune too. That said, it's important to me to fix the docs, and I appreciate your feedaback.