You found a bug! We've classified it as
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
The details are so great that we can fix everything via reading your mind...
Perfection as a goal is a nice idea that can point one in a specific direction. However, since "perfection" is an ever changing (evolving?) and moving target, one must admit that perfection
can never be obtained...
When in doubt, check the d4mn source code!
And here are my terms...
- I don't care if you use my source code. (Known as "Code.")
- I don't care if I get any monetary compensation.
- I do care to receive credit for Code provided. So, please keep my name in the comments for Code provided.
- Code is provided without warranty "AS-IS" and I claim absolutely no warranty nor liability to the quality, security, and run-ability on any platform.
- By using Code, you accept all risk inherit with Code regardless if Code has known and yet to be discovered bugs.
- You are welcome to change and improve the Code to best meet your needs.
- I don't care if you use the Code in a commercial or open-source project.
- You are not required to contact me prior to using the Code.
Sencha Premium Member
follow-up comment (and a question)
1st -- I can confirm this problem also exists for us.
BUT -- that's not really why I'm posting. I was just searching for an explanation of what the difference is between 'Controller Actions' and 'Application Actions' and stumbled across this post.
We've been using SA for some time now. Part of the problem we've had is that we had no prior experience w/ ExtJS, and so our entire experience has been through the lens of SA. The result is we have occasional gaps in our knowledge of the framework. And the 'Application Action' is a perfect example of this.
We regularly create controller actions (by clicking the Actions drop down from the Config panel). We always select 'Controller Action' but have wondered for sometime what the alternate 'Application Action' means. Could someone shed some light? Or even better -- if someone could point me to some either online of offline (ie: books) documentation we could read...that would be even better.
I think the SA/ExtJS system is fantastic. But it's somewhat lacking in the documentation area -- which causing tremendous wasted time trying to figure out how the pieces all fit together.
I should mention we already own the ExtJS in action book from Garcia (the latest edition) AND the ExtJS 1st Look. The Garcia stuff is great (along with his fantastic videos) . But there is NO good documentation on Sencha Architect !!!
elgs: thanks for the report. This seems to be an issue of user feedback from Architect that is insufficient.
If you give your application action a name in the config panel, you'll get codegen for it. A name is required, and we're not communicating that effectively via Architect - I've added a bug to our tracker for us to improve that as well as our messaging/validation. Apologies for the confusion!
Sencha Architect Development Team
Originally Posted by email@example.com
We're definitely working hard to improve our documentation - we understand it's in need of improvement in several areas!
To answer your question on when to use what action:
In truth, you can use either one. However, architecturally it makes more sense to use an Application Action for events that happen application-wide and aren't unique to a specific subsection of your app (e.g. just one controller). In a small application, you may rarely find a difference between the two, to be honest.
Sencha Architect Development Team