Probably should mention that Cmd compiles from sources and not a running instance. This workflow from v2 was quite a problem for lots of folks... it was tricky to have to run your app in order to build your app.

Probably should mention that Cmd compiles from sources and not a running instance. This workflow from v2 was quite a problem for lots of folks... it was tricky to have to run your app in order to build your app.

Does it still analyse what classes are actually referenced, to build the minimum set it can?

I must say this looks like a step back for us. Yes, actually loading the site from the filesystem required some messing about with symlinked directories to make the structure the same as the web site, and this may not be simple for some, but it's quite a nice way of producing a list of all referenced classes that can then be built.

Having all the source in the single html is not really going to work for us.
We already have the concept of a bootstrap file, into which goes the path configuration that clients may want to tinker with.

Does it still analyse what classes are actually referenced, to build the minimum set it can?

Definitely yes - that is the whole purpose of a build.

The difference is that Cmd does this by reading your sources and parsing them into syntax trees and then looks for "requires" and "uses" (and the rest) to determine dependencies. Unlike v2, Cmd respects conditional dependencies as well, that is those wrapped in <debug> or <if> comments like so:

My application is properly laid out in the suggested MVCS structure, but references some common code too, and some code from another product.
Is this something that would be supported by Cmd v3, and if so how, by analysing a directory structure, or a config file perhaps?

As I said, I do not use Architect (and am not about to start), but surely this layout should be supported?

My application is properly laid out in the suggested MVCS structure, but references some common code too, and some code from another product.
Is this something that would be supported by Cmd v3, and if so how, by analysing a directory structure, or a config file perhaps?

Yes, the Cmd compiler can accept paths to folders on the command line (called the "classpath") and these can be configured if you use Cmd to generate a temporary app and copy its ".sencha" folder to your app.

Originally Posted by westy

As I said, I do not use Architect (and am not about to start), but surely this layout should be supported?

Use of Sencha Architect is not required for Cmd. Cmd is a lower level tool but has similar conventions by default.

Cmd provides some high level commands that assume the app structure it generates but even that is not required to use the commands that accept paths. Also, many of the particulars of a generated app can be configured in the ".sencha/app/sencha.cfg" file or via Ant properties when using the generated build script.