15 Apr 2013 2:07 AM #1
Native packaging for external project?
I've got a project at hand that developed since the Sencha Touch 1.x days. Right now it is running on 2.0.1. Back when it was started it was not created with any Sencha Tool (Architect, SDK Tools) so there are no project-related files as there are now with Cmd. I was wondering if it is possible to convert it to a Cmd project. Or would it be easier to just use Phonegap or similar instead. Have you had any similar case?
I already tried with Sencha SDK Tools but could not create an .apk file for example, although there were no errors.
Would be nice to hear your thoughts on this one. Thanks!
16 Apr 2013 3:00 PM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
Because Cmd is what will be used for future of Sencha Touch I would bite the bullet, get it migrated into a Cmd app and go from there.
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services email@example.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
18 Apr 2013 7:20 AM #3
Thanks for your reply Mitchell, that is what I thought as well. I already tried to copy the data into a blank project and changed the paths of some files, however at some point I ran into an error I could not solve. Is there a starting point, sort of like a best practise, to migrate that project properly?
3 May 2013 3:49 AM #4
Is there no one who knows how to get this started?
23 May 2013 3:30 AM #5
So I guess there is no way of migrating an app that was initially developed without Sencha SDKTools/Sencha CMD...
23 May 2013 7:17 AM #6
I started with ST2.0 about a year ago (with SDKTools...). Now all my projects are on ST2.2 and are packed with CMD. As I don't trust its upgrade capabilities any longer, I upgrade all my projects manually:
- rename the project (f.e. from "myproject" to "myproject-save")
- generate a new project (with the name "myproject")
- replace the app folder with the one from "myproject-save"
- copy the ux folder (if available)
- copy the resources
- adapt the app.js, app.json, index.html, packager.json, resources/sass/app.scss with the parts from "myproject-save"
3 Jun 2013 11:28 PM #7
Ah thanks, I almost forgot about this post. I'll give it a try soon.
I know it is not easy to provide a distinct solution for every project. That is why I aimed for a more general explanation to start with and maybe help others, too.
10 Jun 2013 4:34 AM #8
OK, I did as you recommended but ran into this error:
[ERR] BUILD FAILED[ERR] com.sencha.exceptions.BasicException: The following error occurred while executing this line: [ERR] C:\****\app2\.sencha\app\build-impl.xml:249: com.sencha.exceptions.ExScript: Wrapped com.sencha.exceptions.ExArg: Cannot get canonical path for " C:\****\app2\lib" (x-app-build#290) runAppBuild (x-app-build:290) [anonymous] (x-app-build:562) x_app_build (x-app-build:560) <script> (anonymous:1) [ERR] at com.sencha.tools.compiler.sources.ClassPathScope. [ERR] addPaths(ClassPathScope.java:68) [ERR] [ERR] Total time: 54 seconds [ERR] com.sencha.exceptions.BasicException: The following error occurred while executing this line: C:\****\app2\.sencha\app\build-impl.xml:249: com.sencha.exceptions.ExScript: Wrapped com.sencha.exceptions.ExArg: Cannot get canonical path for " C:\****\app2\lib" (x-app-build#290) runAppBuild (x-app-build:290) [anonymous] (x-app-build:562) x_app_build (x-app-build:560) <script> (anonymous:1)
Any clue what I need to adapt?
6 Sep 2013 12:08 AM #9