Results 1 to 2 of 2

Thread: Sencha Cmd 5.0.2 Beta is Now Available

  1. #1
    Sencha User dongryphon's Avatar
    Join Date
    Jul 2009
    Location
    Kansas
    Posts
    1,748

    Default Sencha Cmd 5.0.2 Beta is Now Available

    Hi All,

    We just posted a beta build of Sencha Cmd 5.0.2 that should address many of the issues folks have had with 5.0.1.

    The release notes with download links can be found here:

    http://cdn.sencha.com/cmd/beta/5.0.2...ase-notes.html

    This build is focused on several issues related to the dynamic loader and how that interacted with debuggers on some browsers. As well as problems when adding "ext-all-debug.js" (or similar) to the js array to reduce the number of loaded files.

    To upgrade to Cmd 5.0.2 you will need to also re-copy the Ext JS folder into your workspace. The easiest way to do that is to delete it and run:

    Code:
      C:\Temp\ws502>rd /q /s ext
      C:\Temp\ws502>sencha -sdk ..\ext-5.0.1 generate workspace .
      Sencha Cmd v5.0.2.250
      [ERR] Directory C:\Temp\ws502\ext not recognized as a framework
    This will generate the error message above about the missing "ext" folder but will proceed to copy the subset of files needed by the workspace. This ensures that you have the "ext-*.js" files in the build folder of Ext JS needed for the next step.

    New apps will have two entries in their "js" array, but if you have an existing app, you will need to run "sencha app upgrade" to update the ".sencha" folder as well as (optionally) add the following missing entry to the "js" array in your app.json file:

    Code:
        "js": [
            {
                "path": "${ext.dir}/build/ext-all-rtl-debug.js"  // new default for generated apps
            },
            {
                "path": "app.js",
                "bundle": true
            }
        ],
    Given the above steps, you will have a complete "ext" folder in the workspace as well as an app that uses the complete build instead of loading files individually from the framework.

    The release notes document the other fixes since 5.0.1 as well as one minor new feature to allow you to control the cache busting behavior of the loader. See the app.defaults.json file for documentation on the "loader" object but this object can be useful for development and production. For example, you could add these to your app.json:

    Code:
        "development": {
            "loader": {
                "cache": true
            }
        },
        "production": {
            "loader": {
                "cache": "${build.timestamp}"
            }
        }
    For development builds, this will remove the "_dc" cache buster from script tag src attributes. This will make breakpoints survive reloads correctly in many debuggers. Be sure to disable caching in the debugger itself if you add this.

    For production builds, setting "cache" to a specific string will cause all script tags to have that "_dc" parameter which allows caching across reloads of the same build (a Good Thing) while also breaking wrong caching if you run a new build at the same URL.

    Please let us know how this update works for you and if it resolves these loader issues.
    Don Griffin

    "Use the source, Luke!"

  2. #2
    Sencha User dongryphon's Avatar
    Join Date
    Jul 2009
    Location
    Kansas
    Posts
    1,748

    Default

    To clarify the role of the *ext-all-debug-rtl.js* file in the *js* array:

    That particular build of Ext JS contains all of the sources (including RTL support) and is human readable. This is so that everything is available for easy development use. That entry is identified as belonging to the Ext JS framework and is removed by the build process since the required pieces of the framework are included in the "bundle" file.

    If you do not have this entry, Cmd will generate the new *loadOrder* data structure and load all of the framework files individually as you require them. This means you can easily debug into framework code but loading so many files may not be desirable (if you are using the IE debugger, for example).
    Don Griffin

    "Use the source, Luke!"

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •