Re: Mobile Project Structure
On 7 June 2012 00:03, Luciano Resende luckbr1...@gmail.com wrote: On Wed, Jun 6, 2012 at 11:22 AM, Luciano Resende luckbr1...@gmail.com wrote: Today, the mobile trunk seems to have the application to it's root folder. That assumes we only support one device (in this case Android). I want to produce an iOS version of the client, and would try to refactor some of the code over the weekend to something more flexible. I was thinking on something more like : /photoark -- this is where the application and resources, etc would live /client-android -- this is the android client generated by phonegap /client-ios -- this is the ios client generated by phonegap I haven't tried the Android Phonegap, but in iOS/Xcode project, draging/linking the html5 application www (in this case photoark) folder is enough to get the application happy. How does this work on the Android side ? So, I'll try to work on this over the weekend, and just to make sure we don't loose any trunk contents, I'll move that to client-android-native, which we can then port anything to the phonegap application folder and delete when we are done with it. +1 I think we also need to agree on the SDK and other versions of android we are going to support. This will help others to build and run the project without much trouble Suho -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: Mobile Project Structure
Hi, I agree with you. Since this is built on top of phone gap www (i.e the folder with html/javascript application) folder is the heart of the app. If we have www folder we can easily port it in to any platform. So the version control must be done mainly for that folder. When talking about android if we have www folder and we want to create an android app out of it developer can create hello world android phongap app as in the phonegap site and once it is working he can replace the current www folder with photark www folder to see the functionality of photark app. Since the trunk is available as a android app it has become more complex. It is frequently causes build errors due to android SDK version problems, android maven integration problems, etc. Previously I fixed some build errors and provided a patch but today new revision is not building again. It also causes problems for developers. Say I am developing using Android SDK 4.x. Someone is developing 2.x. Both face problems when developing together. So the solution I suggest is to keep our main attention to /photoark -- this is where the application and resources, etc as Luciano suggest. Then each developer/mentor can keep Android/iOS app in their local enlivenment and sync it's resource folder with the trunk. Then everyone will be aware of the project status. We can mark some milestones and it will be enough to update /client-android -- this is the android client generated by phonegap /client-ios -- this is the ios client generated by phonegap for each milestone. Thoughts are welcome. Regards, Prabahth On Wed, Jun 6, 2012 at 11:52 PM, Luciano Resende luckbr1...@gmail.com wrote: Today, the mobile trunk seems to have the application to it's root folder. That assumes we only support one device (in this case Android). I want to produce an iOS version of the client, and would try to refactor some of the code over the weekend to something more flexible. I was thinking on something more like : /photoark -- this is where the application and resources, etc would live /client-android -- this is the android client generated by phonegap /client-ios -- this is the ios client generated by phonegap I haven't tried the Android Phonegap, but in iOS/Xcode project, draging/linking the html5 application www (in this case photoark) folder is enough to get the application happy. How does this work on the Android side ? -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: Mobile Project Structure
Since this is built on top of phonegap it is developed as a html/JavaScript application. So It is common to every platform. Here the phonegap web application (i.e www folder in android app) is meant by by application and resources. Reference: http://phonegap.com/ As you said android platform is very fragmented. So we must put our concentration on the web app which runs on top of phonegap. Not as a android app itself. On Thu, Jun 7, 2012 at 12:27 AM, Avdhesh Yadav a...@avdheshyadav.com wrote: On Wed, Jun 6, 2012 at 11:52 PM, Luciano Resende luckbr1...@gmail.com wrote: Today, the mobile trunk seems to have the application to it's root folder. That assumes we only support one device (in this case Android). I want to produce an iOS version of the client, and would try to refactor some of the code over the weekend to something more flexible. I was thinking on something more like : /photoark -- this is where the application and resources, etc would live What do you mean by application and resources?.Do you mean common artificats both in ios and android ? /client-android -- this is the android client generated by phonegap /client-ios -- this is the ios client generated by phonegap I haven't tried the Android Phonegap, but in iOS/Xcode project, draging/linking the html5 application www (in this case photoark) folder is enough to get the application happy. How does this work on the Android side ? Not tried but i think it should work with android also?But we need to check One thought is that both the platforms are very different from look and feel to programming model.We should share minimum things and keep things separate as much as possible to avoid glitches.Specially Android platform is very fragmented(lot of versions and s many devices from different manufacturers) compared to IOS. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ -- Avdhesh Yadav http://www.avdheshyadav.com http://twitter.com/yadavavdhesh
Re: Mobile Project Structure
On Wed, Jun 6, 2012 at 11:57 AM, Avdhesh Yadav a...@avdheshyadav.com wrote: On Wed, Jun 6, 2012 at 11:52 PM, Luciano Resende luckbr1...@gmail.comwrote: Today, the mobile trunk seems to have the application to it's root folder. That assumes we only support one device (in this case Android). I want to produce an iOS version of the client, and would try to refactor some of the code over the weekend to something more flexible. I was thinking on something more like : /photoark -- this is where the application and resources, etc would live What do you mean by application and resources?.Do you mean common artificats both in ios and android ? The HTML 5 application which uses phonegap js library to access device specific resources such as the photos, addressbook, etc. /client-android -- this is the android client generated by phonegap /client-ios -- this is the ios client generated by phonegap I haven't tried the Android Phonegap, but in iOS/Xcode project, draging/linking the html5 application www (in this case photoark) folder is enough to get the application happy. How does this work on the Android side ? Not tried but i think it should work with android also?But we need to check One thought is that both the platforms are very different from look and feel to programming model.We should share minimum things and keep things separate as much as possible to avoid glitches.Specially Android platform is very fragmented(lot of versions and s many devices from different manufacturers) compared to IOS. They are different when building native application, but that is abstracted away by phonegap which then give us the flexibility to build generic application. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: Mobile Project Structure
On Wed, Jun 6, 2012 at 11:22 AM, Luciano Resende luckbr1...@gmail.com wrote: Today, the mobile trunk seems to have the application to it's root folder. That assumes we only support one device (in this case Android). I want to produce an iOS version of the client, and would try to refactor some of the code over the weekend to something more flexible. I was thinking on something more like : /photoark -- this is where the application and resources, etc would live /client-android -- this is the android client generated by phonegap /client-ios -- this is the ios client generated by phonegap I haven't tried the Android Phonegap, but in iOS/Xcode project, draging/linking the html5 application www (in this case photoark) folder is enough to get the application happy. How does this work on the Android side ? So, I'll try to work on this over the weekend, and just to make sure we don't loose any trunk contents, I'll move that to client-android-native, which we can then port anything to the phonegap application folder and delete when we are done with it. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
