import a sencha architect project into eclipse with phonegap - eclipse

I have a small sencha 2 project complete and want to import it into eclipse with phonegap. I want to keep the MVC file structure, how do I set up my android project in eclipse to accomplish this?

Check the starting guide in the Phonegap docs on this link:
http://docs.phonegap.com/en/2.4.0/guide_getting-started_android_index.md.html#Getting%20Started%20with%20Android
After following the Android guide, put your Sencha stuff in the www folder in your Eclipse project. Your www folder should look something like this:
app
|-controller
|-model
|-store
|-view
index.html
app.js
sencha-touch.js
sencha-touch.css
Check the Sencha docs for using and creating builds for your app:
http://docs.sencha.com/touch/2-1/#!/guide/building
Good luck!

Related

Flutter - Bundle assets with web plugin

I'm adding web support to a Flutter plugin which doesn't follow the federated style. I have followed this link and created a new project for the web plugin.
I need to bundle some JavaScript files with my plugin. I tried placing them on the lib/ folder and referencing them from the generated HTML (using dart:html) as packages/my_plugin/jsfile.js.
This works perfectly fine on debug builds, but it doesn't on release builds.
What I'm doing wrong?
Thank you.

Integrating jitsi in java-fx

I am developing an video calling application using javafx. And I need to integrate jitsi video GUI into javafx Swing node.
Is it possible or Do I have to use 'libjitsi' and implement GUI in javafx ?
Any suggestions would be appreciated.
If you're asking about how to embed Swing content into JavaFX, you can use a SwingNode.
It worked for me (I added a Swing PDF player in a JavaFX application)
Here is an example of how to perform this : http://docs.oracle.com/javafx/8/embed_swing/jfxpub-embed_swing.htm
This might be very late but still, I am posting the answer as seems to be a genuine question.
To use JavaFX with jitsi, developing with eclipse steps are as follows.
First, you require to install an addon of JavaFX in eclipse e. g. EFX
After adding above addon add JavaFX SDK to the project. The link: https://www.tutorialkart.com/javafx/install-javafx-in-eclipse-ide/
Then add the package entries to the manifest.mf files {in the package where you are executing} and felix.run.properties file.
And the project will run smoothly. Another thing if using a class with the superclass of Application then keep it in the different jar file add the entries of the jar to the build.xml(in copy jar section) and add the package entries to the manifest.mf files {in the package where you are executing} and felix.run.properties file.

Deployable using mgwt and gwt-phonegap

I have just setup a project/run the gwt project(Eclipse) by looking into the wiki. Even I know about the standalone phonegap project build.But I don't understand how to create APK/IPA/windows deployable by using gwt-phonegap. Is there any tutorial available for explaining this?
Create an APK is a different history. You should create an Android project and include the compiled gwt and mgwt project into them (folder assets/www).
That urls might be useful:
https://developer.android.com/training/basics/firstapp/index.html?hl=it
https://developer.android.com/training/basics/firstapp/index.html?hl=it
http://docs.phonegap.com/en/2.1.0/guide_getting-started_android_index.md.html

are you unable to use plugins in build.phonegap.com since version 3.0?

I was using build.phonegap.com in it's simplest way. That is: no sdk and no phonegap framework installed on my computer; no git or svn repository used. I just upload a zip with my html, css and js files.
But now I need to use the File plugin.
I found several posts (here and elsewhere) taking about using the CLI to add plugins and to build remotely since phonegap 3.0 (which doesn't use the config.xml to add plugins anymore, but instead it uses the CLI).
If you just used to upload a zip file to build.phonegap.com, are you now unable to use plugins since phonegap 3.0??
If that virtue is gone, what is now the simplest way for doing it? I currently use Aptana 3.0. Do I have to install Eclipse and install the phonegap framework? Do I have to create git of svn repository? Is that now the simplest way for using plugins in the cloud-based build service?
Is there a way to use the build.phonegap.com service with phonegap 2.x?? I have not found it yet.
This is taking me out of schedule for the imminent delivery of an ongoing project.
Please advise.
Put the config.xml in the www directory. And then upload only www.zip on build.phone.com.
In phonegap 2.x plugins like File were part of the core, so there was no need to include them through the config.xml file.
In phonegap 3.x every plugin has to be included through the config.xml file. BUT for plugins to work, the root index.html header must have a
<script src="phonegap.js"></script>
phonegap.js is provided (kind of injected) by the build.phonegap.com service, so I don't have to have it on my source code.
The script tag was the only thing I was missing.

Cordova (Phonegap) build undo my code changes in Eclipse

Once I create my Phonegap project through the CLI with:
cordova create hello com.example.hello "HelloWorld"
add the android platform and import the project to my Eclipse, every time I run a cordova build android command, it undo/reverts the code that I changed on Eclipse, looks like it always gets reverted to the original project structure created by Cordova CLI, maybe I missed something in the documentation... any ideas?
UPDATE
Ok.. So the plan will be, I will develop my app using the root files, i.e., within hello/www/* (instead of the files within hello/platforms/android/assets/www/*) because Phonegap will override any changes to the ones for specific platforms as part of its build process. My development workflow then involves TextMate to edit HMTL/CSS/JS and then running cordova prepare under the project's folder in order to update the files in my Eclipse project.
Anyway.. just sharing my solution workaround to the cumbersome development process for Phonegap + Android because, IMHO, the documentation around this technology sucks...