Search Type: Posts; User: dongryphon

Page 1 of 5 1 2 3 4

Search: Search took 0.03 seconds.

  1. I downloaded the app and tested it with the soon to be released beta builds (using "extend": "theme-classic") and it all seems to be working now. I can build the theme (if I add "toolkit": "classic"...
  2. The problem with the generator leaving "${}" has been fixed (SDKTOOLS-1116).

    There is a problem (not yet fixed) using the alternate names ("ext-theme-foo" instead of...
  3. Replies
    In Ext JS you don't wrap those fellows in a "config:{}" block.. try removing it.
  4. It is a handy dev-mode function. To clarify undocumented == private really, but probably could document it. I remember adding it for the very reason you mentioned -- also "please let my debugger...
  5. The plan is definitely to support both flavors of responsiveConfig on modern toolkit. The plugin flavor will take a bit of adaptation (as in, "not there yet") but the mixin was designed to work with...
  6. Replies
    We use that technique for the charts package, so it is definitely appropriate.
  7. That issue was related to internally misusing Ext.EventObject (a bug now fixed in 5.1.1) and so not quite the same as being described here.

    Although... the snippet posted here is similarly...
  8. The Ext.EventObject fellow is no longer a singleton instance in 5.x+. That approach created a raft of subtle problems when events would fire re-entrantly (such as focus and blur) and was replaced by...
  9. I will have a look at #1. Thanks for the details!

    For #2 the way themes come together for Ext JS 6 is like Ext JS 4.2/5/5.1 and not like Sencha Touch. In particular we use Cmd packages to contain...
  10. The //<debug> tag is used in non-production builds (so development and testing). It predates Sencha Cmd so was preserved. There is no //<production> processor so that block will simply be retained...
  11. @devnullable and @sjoerdl - To make any progress it will help to see some code snippets. The class you added and how you require it from other places. Also when you say "no picked up" what...
  12. The first idea I'd check is if "framework": "ext" is being set properly... The second is if the "packages/ext-locale" folder is present in the "ext" folder in your workspace.
  13. I will open a bug for this - thanks for trying the beta!
  14. I believe this is an issue in Sencha Touch the "views", "controllers" etc configs do not properly respect root namespaces.

    You might try:

  15. Replies
    You could also do a post-build fix up of the import statements in the CSS file using or just some shell code. In Cmd 6 we will be replacing the...
  16. I will open a Feature Request for this since it cannot currently be disabled.
  17. Cmd should pick up changes to Sass (and JS) in required packages or themes. This ability has improved in Cmd since app watch was introduced in Cmd 4 so maybe that is where the discrepancies stem...
  18. Please try Cmd 5.1.3 - we believe it fixes this problem -
  19. See
  20. If a resource is in some package and is needed by that package (be it a theme or otherwise), you would do this:


    For non-images, there is no API in place...
  21. I believe this is caused by the "cache buster" not respecting the file:// protocol
  22. Thanks for the report! I have opened a bug in our bug tracker.
  23. If there is no 404 error reported, I would suspect a syntax error.
  24. This should be fixed in Cmd 5.1.3 -
  25. Greetings All -

    I am pleased to announce that we have posted Sencha Cmd 5.1.3 for general use.

    The release notes can be found at
Results 1 to 25 of 118
Page 1 of 5 1 2 3 4