Search Type: Posts; User: kkrohe

Page 1 of 2 1 2

Search: Search took 0.02 seconds.

  1. Thanks for the report! I have opened a bug in our bug tracker.
  2. Replies
    7
    Views
    215
    Thanks for the report! I have opened a bug in our bug tracker.
  3. Replies
    7
    Views
    215
    Might be an issue with the class loader used to run js code in rhino not having sencha.jar added to it. We use the x-extend-classpath task in our app build-impl.xml templates to make code in...
  4. The ignoreDisabled flag controls how the metadata generator process unused classes during creation of bootstrap.json, which is the manifest used in dev mode.

    Since that option should only affect...
  5. Which optimization bugs are you referring to?
  6. I pushed this issue to the bug stack. Looks like Cmd 5.0.2 introduced some sorting fixes that were incompatible with the way Ext 5.0.0.970 was trying to influence the sort order.

    The Cmd 5.1.0 GA...
  7. Replies
    6
    Views
    474
    If you're using Cmd 5.0 or newer, the controls for adjusting output paths are now in app.json. In that file, there's an "output" object that specifies the shape of the output resources in the build...
  8. The following steps should help in getting the markup file separated from the app directory.


    1) Update the "indexHtmlPath" in app.json to be the relative path from app.json to the index.html (or...
  9. Replies
    9
    Views
    1,328
    The watch code is wired up in ant to allow extension with custom tasks. To do that, all you need to do is provide a custom ant target in build.xml for the dummy app :



    <target...
  10. We had some performance related fixes that didn't make it in until after the RC build (4.0.0.161), so I'd recommend trying again with the GA release when it becomes available, which should be any day...
  11. MVC dependencies will only be detected when the compiler is able to locate the framework being used. Usually, the compiler finds the framework by leveraging configuration data from a Cmd Application...
  12. Seems like two issues involved here.


    One is the upgrade from extjs 4.1 to 4.2. For a Sencha Cmd app, we need to run the
    'sencha app upgrade <path-to-framework>' variant of the upgrade command...
  13. This is a bug recently introduced in the 3.1.0 release. We've already got a fix in that will
    make it into the upcoming 3.1.1 release, but the fix is simple enough that you should be able
    to...
  14. Actually, the patch needs to go before the line that converts the archivedVersion variable into its name string representation:



    each(archivedVersions, function...
  15. It's possible this is a caching issue. You might try clearing the cache, along with running a 'localStorage.clear()' statement in the debugger console.

    Production builds use a version of the...
  16. I'm suspecting that this is a configuration issue with the workspace settings for this application.

    You mentioned that this is is an ExtJS 4.2 application, but in the attached logs I'm seeing...
  17. This is a bug in the delta patch generator. Currently, the ignores filter is not
    used to filter out which files are needing delta patches generated, and the issue
    here is that the .svn folders in...
  18. Can you show what the folder structure of your application looks like with respect to the framework that your app is using? I'm suspecting that Cmd is detecting that the framework directory is a...
  19. Thanks for the report! I have opened a bug in our bug tracker.
  20. It seems to have failed to detect the name of the framework being used by the application. This is controlled by the app.framework property in the .sencha/app/sencha.cfg file, which should be...
  21. The actual compile command execution for both extjs and touch applications is handled in the app-build target of the plug-in structure.

    For all Sencha Cmd v3 applications, there is a .sencha/app...
  22. You might need to clear the cache / local storage on the client browser. Looks like it's having problems resolving all the changes to the production build and the initial production load didn't...
  23. Sounds like the new files don't have any Ext.define() calls that the compiler can parse.

    When the compiler scans the .js files in the class path, the primary thing it does is map out declarations...
  24. Another possible issue could be that the compiler is sorting the sch-all-debug.js file very early, but is sorting the sch-symbols file correctly (the debug output will show this happening if this is...
  25. Yeah, that's what I was suspecting might happen and is the reason for needing the extra require tags in sch-symbols.

    It would help if you could post the resources that are generating the 404...
Results 1 to 25 of 41
Page 1 of 2 1 2