@debdas
>So to do this we must need those PHP files and access the remote database that reside in our server. How can I do this?
The migration path depends upon how well your php webapp is architectured now. For example if the webapp architecture has a clean separation between application control and processing from presentation logic then the process is:
1) define a web services api and create it in PHP to interact the current control/biz logic tier
2) use the UI template code as much as possible a guide for conversion to javascript and creation of the app’s UI. Since MobiOne UIs are HTML5, CSS, and JavaScript you will use JavaScript to dynamically update the UI
If there is not such a clean separation then there are few more challenges as you will effectively need to refactor the code or completely rewrite it to separate the UI from the webapp, leaving only the business functionality on the server exposed as web services.
Something to consider is that frequently mobile apps are more narrowly focused and simpler than their full blown web site. The interaction model is lower when you have to interact on a small screen, with your finger over a cellular connection. Thus, you may find there are completely different set of requirements…
If you don’t plan to use the MobiOne Visual Designer then I I would propose that you consider using an IDE such as MyEclipse for file management and editing. Then use the MobiOne Test Center for rapid testing and debugging of your webapp. Note: we are planning a much richer development model for MobiOne that will help you work with the frameworks of your choice with provide. It should be available this summer.