Sencha Cmd V3 Beta

[dongryphon]

*** Updated Nov 6, 2012 *** http://www.sencha.com/forum/showthre...-Now-Available - Sencha Cmd v3.0 GA Announcement

*** Updated Oct 25, 2012 *** http://www.sencha.com/forum/showthre...-Now-Available

*** Updated Oct 5, 2012 *** http://www.sencha.com/forum/showthre...-Now-Available

*** Updated Sep 27, 2012 *** http://www.sencha.com/forum/showthre...-Now-Available

The new Sencha Cmd v3 beta is out and ready!

Many things have changed under the covers, so check out the blog:

http://www.sencha.com/blog/all-new-sencha-cmd

All new Guides for Ext JS but also Cmd in general can be found here:

http://docs.sencha.com/ext-js/4-1/#!/guide/command

The Sencha Touch specific guides will ship with RC1.

The download links are:

http://cdn.sencha.com/senchacmd/Senc...ux-x64.run.zip
http://cdn.sencha.com/senchacmd/Senc...-linux.run.zip
http://cdn.sencha.com/senchacmd/Senc...50-osx.app.zip
http://cdn.sencha.com/senchacmd/Senc...indows.exe.zip

When discussing v3 issues please be sure to include the full version number to help expedite resolution.

You will need to download Ext JS 4.1.1a (see below) or 4.1.2a (support portal) to use Sencha Cmd.

Ext JS 4.1.1a is available on the CDN:

Commercial - http://cdn.sencha.com/ext-4.1.1a-commercial.zip
GPL - http://cdn.sencha.com/ext-4.1.1a-gpl.zip


Thanks and enjoy!

[dongryphon]

The plan is to release Cmd v3 GA along with Sencha Touch 2.1 GA.

[mono blaine]

Final Edit:

OK, after three hours of struggling I finally got it work.

Need to mention a few things:

• You cannot use ExtJS 4.1.1 or ExtJS 4.1.2 ([ERROR] Failed to determine framework name. Please ensure this command was issues from either a framework or application directory). The version must be either 4.1.1a or 4.1.2a.
• Forget about SDK Tools. Pretend you've never heard of it. When you see the word SDK in docs, it is simply the contents of extjs.4.***.zip. Nothing else. No tools.

******************************
Well apparently I was confused with the terms "SDK" and "SDK Tools". The SDK mentioned in docs is just the package file that contains extjs sources and relevant files, I guess.

But I still get the following error:

C:\inetpub\wwwroot\extjs>sencha generate app MyApp MyApp
Sencha Cmd v3.0.0.140
[ERROR] Failed to determine framework name. Please ensure this command was issues from either a framework or application directory

I feel so dumb.

***************************************
Using Windows 7 x64 Pro,

> Sencha SDK Tools is installed in "C:\SenchaSDKTools2b3",
> Sencha Cmd is installed in "C:\SenchaCmd"

However sencha command does not work as expected (contrary to docs)

C:\>sencha
Sencha Cmd v3.0.0.140

C:\SenchaSDKTools2b3>sencha
[WARN] The current working directory (C:\SenchaSDKTools2b3) is not a recognized Sencha SDK or application folder. Running in backwards compatible mode.

Why is that so?

[Wedgybo]

The links appear to be broken

[dongryphon]

Sorry for the glitches there. Build 140 had a packaging/deployment problem. Build 141 (the current links) took a few minutes to deploy out.

I just checked the links and they are working now. Please try the above and see if you have the same problems.

[dongryphon]

Well apparently I was confused with the terms "SDK" and "SDK Tools". The SDK mentioned in docs is just the package file that contains extjs sources and relevant files, I guess.

Yes, that is one reason for the picking "Sencha Cmd" as the name.

Sorry for the confusion around the name change but hopefully the new name will make communication less ambiguous.

[Wedgybo]

Working now! Cheers

[jay@moduscreate.com]

Yes, that is one reason for the picking "Sencha Cmd" as the name.

Sorry for the confusion around the name change but hopefully the new name will make communication less ambiguous.

And what an awesome name it is

[dongryphon]

OK, after three hours of struggling I finally got it work.

Need to mention a few things:

• You cannot use ExtJS 4.1.1 or ExtJS 4.1.2 ([ERROR] Failed to determine framework name. Please ensure this command was issues from either a framework or application directory).

I am glad there was success at the end, but sorry for the confusion. I have updated the first post on this thread accordingly to help others avoid the same issue.

Thanks for taking a look. Now that you are past that, any initial thoughts?

[mono blaine]

I am glad there was success at the end, but sorry for the confusion. I have updated the first post on this thread accordingly to help others avoid the same issue.

Thanks for taking a look. Now that you are past that, any initial thoughts?

Well, the project I'm currently working on is based on v4.1.1 so I need to test and upgrade to 4.1.1a (apparently there are significant changes in css files) first in order to examine the tool completely. However, even the idea of creating an empty project with all required resources by just a single command is amazing.

Another thing I really liked is the "integrated soul of a compiler". For example, the extra trailing commas in an object initializer gives runtime errors in IE7/IE6. Normally it could only be detected at runtime, (After packaging and deployment, generally when the project is published) and that sucks. However Sencha Cmd catches all these kinds of errors. That's a great improvement for me

By the way, sencha generate model command puts the fields in a config object (see code below). Is it intentional / a preferred approach?

Ext.define('MyApp.model.MyModel', {
    extend: 'Ext.data.Model',
    
    config: {
        fields: [
            { name: 'id', type: 'int' },
            { name: 'name', type: 'string' },
            { name: 'ratio', type: 'float' }
        ]
    }
});