15 Mar 2013 10:52 AM #1
Is it possible to generate an application without copy/paste the SDK ?
I'm used to professional layout where we don't copy/paste stuff, and we don't commit in source control third party libraries.
I executed: sencha.exe -sdk c:\extjs4.2.0GA generate app MyExtJS42App d:\MyExtJS42App
And ended-up with 95.3 MB of junk, the app folder is a total of 1.45 KB, and the sass folder 1.94 KB.
How can I remove all the extra (etc/packages folders), and still compile the SASS?
15 Mar 2013 11:44 PM #2
There are two levels to a Sencha Cmd application that are often merged: apps and workspaces. The ext framework (and packages) reside at the workspace level and do not have to be added to source control.
You could do this:
>sencha -sdk c:\extjs4.2.0GA generate workspace MyWorkspace Sencha Cmd 184.108.40.206 ...
MyWorkspace/ .sencha/ worskpace/ sencha.cfg ext/ packages/
>cd MyWorkspace >sencha -sdk ext generate app App1 app1
MyWorkspace/ .sencha/ ext/ packages/ app1/ .sencha/ app/ sencha.cfg app/ resources/ sass/
For more details see http://docs.sencha.com/ext-js/4-2/#!...mand_workspace
18 Mar 2013 3:53 AM #3
18 Mar 2013 5:08 AM #4
When I execute from MyWorkspace/app1, the following: c:\SenchaCmd220.127.116.11\Sencha\Cmd\18.104.22.168\sencha generate theme myTheme
The MyWorkspace/packages end-up with a folder called myTheme, so I get my packages folder mixed with things that are static (Sencha provided static files) and things that I really care to get in my source control.
I was hoping to get the myTheme generated under app1/packages
29 Jul 2014 5:34 AM #5
Using Sencha Cmd 5, how can I tell the SDK to not copy Ext JS library but instead point to the original location when I generate the workspace and app, or after by hacking some files?
I have the situation where I already have Ext JS commercial version pulled using Maven/Ivy/Gradle or checked in a Git repo, then when I generate a workspace a copy is made, then when I generate an app a third copy is made!
No kidding... am I the only person using source control and that doesn't like to put generated files in it?
2 Aug 2014 3:52 PM #6
Without knowing more about the steps you are taking:
- I already have Ext JS commercial version pulled
- I generate a workspace a copy is made
- then when I generate an app a third copy is made!
If the workspace was generated without an SDK it will simply not have copied one and won't have "ext.dir" set. It sounds like your steps involved the SDK at the time you generated the workspace.
I would check to see what ext.dir is set to at the various steps of the process (perhaps by running "sencha diag show") to see if Cmd has the right value.
Beyond that I'll need very clear steps (specifically knowing what commands you run and in what folders and where the SDK is located etc) to be more than generally helpful here.