Sencha Architect 4.0

[Julie Followell]

I upgraded from Sencha architect 4.2 beta to official 4.3.2 release by following these instructions How to upgrade Sencha Architect to 4.3.2. Now when I open my Modern projects I am getting the error 'Design view: framework error: cannot read property 'add' of undefined' in the log panel and the deign view of the panel is blank. Code shows OK. My Classic app opens and shows the design view just fine. Unfortunately our subscription has lapsed so I cannot raise a case with Sencha. Does anyone have any suggestions? What additional info can I provide?

Its weird - once the app is open in the Architect one can eventually get it to display the design view by viewing code and then viewing design tab again. It might take several attempts at alternating between code and design and clicking on different parts of a panel. Once it displays properly it will continue to display OK till you close and open the architect again, and then you have to start all over with the clicking around.

Sencha Architect 4.0

Download - https://bytlly.com/2yVsTE

Create the Workspace for the ExtJS
Command: sencha generate workspace path where workspace needs to be generated
This would copy all the necessary files to the workspace. It takes few minutes to build the workspace
Here, below is the screen shot of the workspace

This maintenance release contains improvements and fixes for many issues reported by our friend in the community. Many issues relate to the whole sencha app upgrade process, the meaning of "merge conflicts" and cases where Cmd did not handle those conflicts cleanly. Framework Packages Packages were introduced in Sencha Cmd 3.1.0. In that release, there was only one location for packages and that was set by workspace.package.dir to be $workspace.dir/packages. This meant that Ext JS 4.2's (many) packages would be copied to that folder. In this release, frameworks can now contain their packages and these are no longer copied out of the framework when the framework is introduced to the workspace. This detail was handled by Sencha Cmd, so this applies to Ext JS 4.2.0 as well as Ext JS 4.2.1. This is handled during framework upgrade and Sencha Cmd will remove the framework's packages from the workspace.packages.dir. Upgrades The general method for upgrading an application is sencha app upgrade and while that remains true in this release, you now have more control over the process. If you have multiple applications in a workspace, for example, you need to decouple the framework and application upgrades. By default, sencha app upgrade now operates as if you specified sencha app upgrade --noframework and proceeds to upgrade the current application to the current framework. This presupposes that you have already upgraded the framework as part of a upgrading a different application in the workspace. If you have created packages, you can upgrade them like so from the package folder:sencha package upgrade NOTE: If you are not upgrading frameworks, you may have to manually delete the "ext-*" packages from the "packages" folder and the "ext" folder as well. Then run the following to copy the framework and packages to the workspace:sencha -sdk /path/to/extjs generate workspace . app.js The majority of upgrade issues revolved around the "app.js" file. In previous releases, Sencha Cmd would add entries to "app.js" during code generation calls like sencha generate model (but also for controllers and the rest). Further, the location of this file differed by framework. Due to the complications this approach creates and the fact that often these updates are not wanted on the application, these commands no longer update"app.js". You will need to add the newly created controllers, views, stores, etc. to the appropriate class. In many cases this will be on one of your controllers and not your application. To make applications consistent across frameworks, and compatible-by-default with Sencha Architect, "app.js" now resides in the root folder of generated applications. The sencha app upgrade command will move this file from the "app" folder for Ext JS applications. Merge Conflicts With Sencha Cmd 3.0, we introduced tracking of generated code to allow upgrades to reconcile changes you may have made with changes to the "standard" flavor of certain key files. This is tracked in ".sencha/app/codegen.json". When generating code, if there is a file in the way, Cmd will use this data to do a 3-way merge with the version Cmd originally produced as the base, the version in the way as "Custom" and the new version as "Generated". In the case of overlapping changes, Cmd will report s "MERGE CONFLICT" in the log and write the standard (at least to many source control systems) conflict indicators in the file:> Custom In this release we have fixed several cases where merge conflicts were falsely reported during sencha app upgrade (which regenerates certain core files like "app.js") and cases where subsequent steps of the upgrade would wrongly try to use a file containing merge conflicts. There are two strategies for handling merge conflicts:

• Your source control comparison tools
• Call a merge tool of your choice during the upgrade process to resolve conflicts as they occur.

The use of source control to review the resulting changes from an upgrade is not new. The best practice here (as always) is to perform upgrades with a clean working tree (no pending changes). This will allow you to discard or revert whatever you need. Using a Third-party Merge Tool New in this release is the ability to configure an external merge tool to be called during the upgrade process. You can do this in a personal configuration file in your HOME directory. For example: C:\Users\Me>md .senchaC:\Users\Me>cd .senchaC:\Users\Me\.sencha>md cmdC:\Users\Me\.sencha>cd cmdC:\Users\Me\.sencha\cmd>notepad sencha.cfg For example, you add these entries like those below to use the Perforce Visual Merge tool:cmd.merge.tool=C:\\Program Files\\Perforce\\p4merge.execmd.merge.tool.args=$cmd.merge.tool.args.p4merge For further details, consult the comments in the "sencha.cfg" file in your install folder of Sencha Cmd. The support for personal Sencha Cmd configuration files is also documented in that same file. New Features

Compiler (2) SDKTOOLS-449 Compiler should support allow stdout as an output target SDKTOOLS-476 Compiler -classpath switch should allows tags to be added to the files in the path

Misc (2) SDKTOOLS-389 The framework should be able to add to the workspace repository for app builds SDKTOOLS-448 Cmd should load per-user and version-independent config files in addition to base configuration Total: 4 Bugs Fixed

Build (4) SDKTOOLS-384 Package build needs to produce package-all.scss file for non-theme packages SDKTOOLS-446 Application commands should warn instead of fail when Cmd version does not match exactly SDKTOOLS-450 Sencha.cfg properties are not overrideable via ant "-D" switches SDKTOOLS-477 Default help target for applications and packages should not require that Ant be in the PATH

Compiler (4) SDKTOOLS-383 Application build should include package SASS variables in (forward) dependency order SDKTOOLS-461 Auto-dependency scanner does not recognize ftype and ptype references SDKTOOLS-462 Auto-dependency scanner does not recognize "defaults" object configuration SDKTOOLS-475 Compiler 'circular requires' error should be downgraded to a warning Generator (2) SDKTOOLS-483 Paths for manifest.js and shortcuts.js are incorrect in a app's theme.html file SDKTOOLS-486 App generation needs to preserve Architect-generated files Misc (11) SDKTOOLS-281 Preprocessor option "feature logger" cannot be controlled by build properties SDKTOOLS-297 Generated app.js file contains redundant loader configuration SDKTOOLS-360 sencha app upgrade --noframework can produce false merge conflicts SDKTOOLS-367 When generating a Touch app, the Loader's path to the framework is wrong SDKTOOLS-392 App builds for all frameworks/versions should consistently use build.properties SDKTOOLS-414 No error message indicating that embedded version of Compass/Sass require Ruby 1.8 or 1.9 SDKTOOLS-421 App build process skips resource copy under certain conditions SDKTOOLS-443 Commented out script tags can break page compiler SDKTOOLS-445 Required package properties are not inherited by secondary packages during builds SDKTOOLS-447 System proxy settings are not picked up by upgrade or package commands SDKTOOLS-480 sencha app upgrade from Touch 2.1 to 2.2 misses some files Sass (1) SDKTOOLS-426 Themes cannot control the image paths if they are not built using Cmd Slicer (1) SDKTOOLS-478 Screenshot-runner has invalid check for duplicate slicer paths Upgrade (2) SDKTOOLS-460 sencha app upgrade will corrupt certain files after detecting a merge conflict SDKTOOLS-484 Touch app upgrades generate merge conflicts Total: 25 Known Issues

Compiler (1) SDKTOOLS-327 Sencha Touch applications cannot use optimizer

Misc (1) SDKTOOLS-487 app refresh creates empty folder Total: 2 Release Notes for Sencha Cmd 3.1.1 Date: April 5, 2013
Version Number: 3.1.1.274
Windows - Mac OS X - Linux/64 - Linux/32

Ext JS: This version of Sencha Cmd 3.1 is not compatible with Ext JS 4.1.x but this will be corrected in the next release. For this release, only Ext JS 4.2.0.488 is supported. Sencha Touch: This version of Sencha Cmd 3.1 is compatible with Sencha Touch 2.1+ however the new optimizer and package features (discussed below) are not yet supported for Sencha Touch applications. Class Optimizer This release of Sencha Cmd introduces the optimize command on the Compiler. The initial optimization provided is to rewrite class declarations into a more optimal form. This is beneficial because compiled code avoid many run-time checks and process things synchronously (vs. asynchronously as with the Sencha class system). This results is significantly fewer function calls and memory allocation required to load the JavaScript code of the framework and application. Packages The biggest new feature of Sencha Cmd 3.1 is that of packages. These are in many ways similar to applications from a build perspective. Like applications, packages contain:

• JavaScript
• SASS
• Resources

Packages come in three basic flavors: theme, code and locale. All package types can contain any of the above assets. They primarily differ in how applications use them. For theme and locale packages, only one of each can be active during a given build. An application may require multiple theme and locale packages, but only one will be activated for a build based on build properties. The defaults are stored in your .sencha/app/sencha.cfg file and these can be specified on the command line to override the default. Packages live at the top of the application/workspace in a "./packages" folder. That is, package "foo" is stored in "./packages/foo". In this release, only Ext JS 4.2 applications or other packages can use packages. In order to use a package, an application "requires" it in its app.json file: "name": "foo", "type": "code", "version": "1.0.0", "compatVersion": "1.0.0", "requires": [ "name": "bar", "version": "1.1.0" ] Packages can require other packages in their "package.json" file in the same way. Guides describing all of the particulars of packages will be available soon. New Features

Compiler (1) SDKTOOLS-324 Compiler should optimize class declarations

Misc (5) SDKTOOLS-268 Code generators should support 3-way merge to facilitate user modification of generated code SDKTOOLS-269 Model generator should support regeneration to modify the fields SDKTOOLS-270 Model generator should be compatible with Sencha Architect SDKTOOLS-272 Plugin infrastructure should allow for multiple independent plugins SDKTOOLS-325 Ability to generate, build and consume packages Total: 6 Bugs Fixed

Compiler (3) SDKTOOLS-302 Can't configure compile options for Touch builds SDKTOOLS-316 Compiler incorrectly translates empty for loop SDKTOOLS-317 Compiler incorrectly optimizes hex numbers

Misc (5) SDKTOOLS-151 Windows (Win7) new build tools make build causes error when using image resources file itself SDKTOOLS-245 Signing fails in Mac OS with Sencha CMD 3.0.0.190 (Freshly Generated App) SDKTOOLS-271 Code generators incompatible with Sencha Architect should report error if run from an Architect project SDKTOOLS-285 Missing auto dependency on identifier property for touch models SDKTOOLS-311 Slicer is not producing proper image slices for Neptune Total: 8 Release Notes for Sencha Cmd 3.0.2 Date: December 26, 2012
Version Number: 3.0.2.288

aa06259810