[xwiki-devs] GSoC 2011 - "XWiki Android client"
Dear Thomas Mortagne I am very excited to contribute in open source community through the platform of Google Summer of Code 2011. I have visited the ideas page of “XWiki” at http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/ for GSoC 2011. I am interested in working on “Google Android client” for XWiki. The reason being is my interest in smartphone development. I have previously worked in Windows Phone 7 and to some extent in Blackberry. I want to experience development in other platforms such as Android. I've worked in Java, CSS, HTML and Javascript. I am writing to let you know my understanding of the project and would like your feedback on it. My understanding of the requirements is as follows: - To develop a smartphone application for XWiki. - The application should be able to navigate wiki spaces and pages. - The application should allow offline editing of wiki space and pages and synchronise results on connecting with the repository. - The application should also allow users an option to launch a browser window. I have some knowledge of XML-RPC client/server communication. However, you mentioned you are interested in using REST API for such communication. Does XWiki already have REST API or this API needs to be created as part of this project. Would you please refer me some material to study in this regard? I look forward to your response. Regards Rauf University of Gloucestershire
Hi Rauf, Great you are interested in this project ! On Sun, Mar 20, 2011 at 17:32, Abdul Rauf <[email protected]> wrote:
Dear Thomas Mortagne
I am very excited to contribute in open source community through the platform of Google Summer of Code 2011. I have visited the ideas page of “XWiki” at http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/ for GSoC 2011. I am interested in working on “Google Android client” for XWiki. The reason being is my interest in smartphone development. I have previously worked in Windows Phone 7 and to some extent in Blackberry. I want to experience development in other platforms such as Android. I've worked in Java, CSS, HTML and Javascript.
I am writing to let you know my understanding of the project and would like your feedback on it. My understanding of the requirements is as follows:
- To develop a smartphone application for XWiki. - The application should be able to navigate wiki spaces and pages. - The application should allow offline editing of wiki space and pages and synchronise results on connecting with the repository. - The application should also allow users an option to launch a browser window.
That is for the UI part yes. The user need a way to view the result and there is a lot of ways which are not requiring the same work: - launch the browser to the page (which will be the minimum for this GSOC) - integrate the browser into the application if you have more time - something event more integrated in the application if you have lot of time but i doubt it will be possible ;) Plus any commons sense you are thinking of since you are probably more eperianced than me in mobile development ;) But there is also another side of the project which is to develop a nice android library package that could be used by any other Android app to comunicate with XWiki. More than the featuires what is important is to have a good architecture (maven build, follow Andoird good practices) that will make what you did easy to improve and add other features later by someone else. That's the better way to make XWiki have a good android client in the long run.
I have some knowledge of XML-RPC client/server communication. However, you mentioned you are interested in using REST API for such communication. Does XWiki already have REST API or this API needs to be created as part of this project. Would you please refer me some material to study in this regard?
Yes there is already a very complete REST interface, a lot more complete than the XML-RPC one which is why the project should be based on it.
I look forward to your response.
Regards
Notes: I only did a bit of Android developement mostly to test it so I will not be able to help much on very advanced Android stuff
Rauf
University of Gloucestershire _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
Hi, I wanted to rename this project to Android/iPhone instead of Android only. I tend to think that today FULL native client development on Android or iOS is outdated. There are now libraries like Appcelerator Titanium (http://www.appcelerator.com/) or PhoneGap (http://www.phonegap.com/) that allow to do cross platform development with "native UI" look and feel in Javascript and with very nice web integration. I've done a prototype with Appcelerator and calling REST/JSON apis from it is a breeze and the result is a very nice native looking application. The great advantage is to develope mostly once for both platforms. Also the application is tightly connected to a good mobile skin. Indeed given XWiki's web capabilities, you cannot have of an application developped on top of XWiki working on a mobile without actually calling the application itself in web mode (good example is a livetable). So you can't only interact with the content engine of XWiki. Therefore a good native mobile XWiki application is a front end with nice "mobile" oriented widgets for the home page, the activity stream, the search and maybe others which then link to the native XWiki pages embedded in a mobile skin. Althouth native mobile application + mobile skin are connected they can still be viewed as different projects as the mobile skin can be used on it's own. Ludovic Le 20/03/11 18:00, Thomas Mortagne a écrit :
Hi Rauf,
Great you are interested in this project !
On Sun, Mar 20, 2011 at 17:32, Abdul Rauf<[email protected]> wrote:
Dear Thomas Mortagne
I am very excited to contribute in open source community through the platform of Google Summer of Code 2011. I have visited the ideas page of “XWiki” at http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/ for GSoC 2011. I am interested in working on “Google Android client” for XWiki. The reason being is my interest in smartphone development. I have previously worked in Windows Phone 7 and to some extent in Blackberry. I want to experience development in other platforms such as Android. I've worked in Java, CSS, HTML and Javascript.
I am writing to let you know my understanding of the project and would like your feedback on it. My understanding of the requirements is as follows:
- To develop a smartphone application for XWiki. - The application should be able to navigate wiki spaces and pages. - The application should allow offline editing of wiki space and pages and synchronise results on connecting with the repository. - The application should also allow users an option to launch a browser window. That is for the UI part yes.
The user need a way to view the result and there is a lot of ways which are not requiring the same work: - launch the browser to the page (which will be the minimum for this GSOC) - integrate the browser into the application if you have more time - something event more integrated in the application if you have lot of time but i doubt it will be possible ;)
Plus any commons sense you are thinking of since you are probably more eperianced than me in mobile development ;)
But there is also another side of the project which is to develop a nice android library package that could be used by any other Android app to comunicate with XWiki.
More than the featuires what is important is to have a good architecture (maven build, follow Andoird good practices) that will make what you did easy to improve and add other features later by someone else. That's the better way to make XWiki have a good android client in the long run.
I have some knowledge of XML-RPC client/server communication. However, you mentioned you are interested in using REST API for such communication. Does XWiki already have REST API or this API needs to be created as part of this project. Would you please refer me some material to study in this regard? Yes there is already a very complete REST interface, a lot more complete than the XML-RPC one which is why the project should be based on it.
I look forward to your response.
Regards
Notes: I only did a bit of Android developement mostly to test it so I will not be able to help much on very advanced Android stuff
Rauf
University of Gloucestershire _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
Hi Thomas & Ludovic, Thanks for your quick response and clarifying the project's deliverables. In Android development, I am not that experienced so I would still need your guidance :) I agree with what Ludovic said that now we have cross platform toolkit such as Titanium to write native mobile application for both Android and iPhone. I am new to this cross platform development and would be interested to see some challenges ahead. For example, one challenge I am thinking would probably be performance issue as there is an extra layer becomes involved on top of mobile hardware. @Ludovic: Would you please elaborate what do you mean by Mobile skin? Regards Rauf On 20 March 2011 17:17, Ludovic Dubost <[email protected]> wrote:
Hi,
I wanted to rename this project to Android/iPhone instead of Android only.
I tend to think that today FULL native client development on Android or iOS is outdated. There are now libraries like Appcelerator Titanium ( http://www.appcelerator.com/) or PhoneGap (http://www.phonegap.com/) that allow to do cross platform development with "native UI" look and feel in Javascript and with very nice web integration.
I've done a prototype with Appcelerator and calling REST/JSON apis from it is a breeze and the result is a very nice native looking application. The great advantage is to develope mostly once for both platforms.
Also the application is tightly connected to a good mobile skin. Indeed given XWiki's web capabilities, you cannot have of an application developped on top of XWiki working on a mobile without actually calling the application itself in web mode (good example is a livetable). So you can't only interact with the content engine of XWiki. Therefore a good native mobile XWiki application is a front end with nice "mobile" oriented widgets for the home page, the activity stream, the search and maybe others which then link to the native XWiki pages embedded in a mobile skin.
Althouth native mobile application + mobile skin are connected they can still be viewed as different projects as the mobile skin can be used on it's own.
Ludovic
Le 20/03/11 18:00, Thomas Mortagne a écrit :
Hi Rauf,
Great you are interested in this project !
On Sun, Mar 20, 2011 at 17:32, Abdul Rauf<[email protected]> wrote:
Dear Thomas Mortagne
I am very excited to contribute in open source community through the platform of Google Summer of Code 2011. I have visited the ideas page of “XWiki” at http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/for GSoC 2011. I am interested in working on “Google Android client” for XWiki. The reason being is my interest in smartphone development. I have previously worked in Windows Phone 7 and to some extent in Blackberry. I want to experience development in other platforms such as Android. I've worked in Java, CSS, HTML and Javascript.
I am writing to let you know my understanding of the project and would like your feedback on it. My understanding of the requirements is as follows:
- To develop a smartphone application for XWiki. - The application should be able to navigate wiki spaces and pages. - The application should allow offline editing of wiki space and pages and synchronise results on connecting with the repository. - The application should also allow users an option to launch a browser window.
That is for the UI part yes.
The user need a way to view the result and there is a lot of ways which are not requiring the same work: - launch the browser to the page (which will be the minimum for this GSOC) - integrate the browser into the application if you have more time - something event more integrated in the application if you have lot of time but i doubt it will be possible ;)
Plus any commons sense you are thinking of since you are probably more eperianced than me in mobile development ;)
But there is also another side of the project which is to develop a nice android library package that could be used by any other Android app to comunicate with XWiki.
More than the featuires what is important is to have a good architecture (maven build, follow Andoird good practices) that will make what you did easy to improve and add other features later by someone else. That's the better way to make XWiki have a good android client in the long run.
I have some knowledge of XML-RPC client/server communication. However,
you mentioned you are interested in using REST API for such communication. Does XWiki already have REST API or this API needs to be created as part of this project. Would you please refer me some material to study in this regard?
Yes there is already a very complete REST interface, a lot more complete than the XML-RPC one which is why the project should be based on it.
I look forward to your response.
Regards
Notes: I only did a bit of Android developement mostly to test it so I will not be able to help much on very advanced Android stuff
Rauf
University of Gloucestershire _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
A skin is just a set of static resources and velocity files that, together, create a UI for the web. I imagine indeed that an XWiki that would work on a mobile would need a different UI than that used in browsers. paul Le 20 mars 2011 à 18:46, Abdul Rauf a écrit :
@Ludovic: Would you please elaborate what do you mean by Mobile skin?
On 03/20/2011 06:46 PM, Abdul Rauf wrote:
Hi Thomas& Ludovic,
Thanks for your quick response and clarifying the project's deliverables. In Android development, I am not that experienced so I would still need your guidance :)
I agree with what Ludovic said that now we have cross platform toolkit such as Titanium to write native mobile application for both Android and iPhone. I am new to this cross platform development and would be interested to see some challenges ahead. For example, one challenge I am thinking would probably be performance issue as there is an extra layer becomes involved on top of mobile hardware.
No, that is not an issue, Titanium builds a native application, it's not a framework hosting interpreted applications.
@Ludovic: Would you please elaborate what do you mean by Mobile skin?
Regards Rauf
On 20 March 2011 17:17, Ludovic Dubost<[email protected]> wrote:
Hi,
I wanted to rename this project to Android/iPhone instead of Android only.
I tend to think that today FULL native client development on Android or iOS is outdated. There are now libraries like Appcelerator Titanium ( http://www.appcelerator.com/) or PhoneGap (http://www.phonegap.com/) that allow to do cross platform development with "native UI" look and feel in Javascript and with very nice web integration.
I've done a prototype with Appcelerator and calling REST/JSON apis from it is a breeze and the result is a very nice native looking application. The great advantage is to develope mostly once for both platforms.
I don't like this very much. Doing development in Titanium is good for the end result, bus is bad for the source code. It won't use any of our established tools: no Java, no Maven, no CI builds, no Eclipse, no contributor experience. It will be an unintegrated, unmaintainable application, until committers learn how to use their IDE. On the other hand, writing an application using the Android SDK brings back our infrastructure: Java, Maven, Eclipse, Jenkins. So, what do you prefer, a portable bitrotting application, or an Android-only maintainable application?
Also the application is tightly connected to a good mobile skin. Indeed given XWiki's web capabilities, you cannot have of an application developped on top of XWiki working on a mobile without actually calling the application itself in web mode (good example is a livetable). So you can't only interact with the content engine of XWiki. Therefore a good native mobile XWiki application is a front end with nice "mobile" oriented widgets for the home page, the activity stream, the search and maybe others which then link to the native XWiki pages embedded in a mobile skin.
Althouth native mobile application + mobile skin are connected they can still be viewed as different projects as the mobile skin can be used on it's own.
Ludovic
Le 20/03/11 18:00, Thomas Mortagne a écrit :
Hi Rauf,
Great you are interested in this project !
On Sun, Mar 20, 2011 at 17:32, Abdul Rauf<[email protected]> wrote:
Dear Thomas Mortagne
I am very excited to contribute in open source community through the platform of Google Summer of Code 2011. I have visited the ideas page of “XWiki” at http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/for GSoC 2011. I am interested in working on “Google Android client” for XWiki. The reason being is my interest in smartphone development. I have previously worked in Windows Phone 7 and to some extent in Blackberry. I want to experience development in other platforms such as Android. I've worked in Java, CSS, HTML and Javascript.
I am writing to let you know my understanding of the project and would like your feedback on it. My understanding of the requirements is as follows:
- To develop a smartphone application for XWiki. - The application should be able to navigate wiki spaces and pages. - The application should allow offline editing of wiki space and pages and synchronise results on connecting with the repository. - The application should also allow users an option to launch a browser window.
That is for the UI part yes.
The user need a way to view the result and there is a lot of ways which are not requiring the same work: - launch the browser to the page (which will be the minimum for this GSOC) - integrate the browser into the application if you have more time - something event more integrated in the application if you have lot of time but i doubt it will be possible ;)
Plus any commons sense you are thinking of since you are probably more eperianced than me in mobile development ;)
But there is also another side of the project which is to develop a nice android library package that could be used by any other Android app to comunicate with XWiki.
More than the featuires what is important is to have a good architecture (maven build, follow Andoird good practices) that will make what you did easy to improve and add other features later by someone else. That's the better way to make XWiki have a good android client in the long run.
I have some knowledge of XML-RPC client/server communication. However,
you mentioned you are interested in using REST API for such communication. Does XWiki already have REST API or this API needs to be created as part of this project. Would you please refer me some material to study in this regard?
Yes there is already a very complete REST interface, a lot more complete than the XML-RPC one which is why the project should be based on it.
I look forward to your response.
Regards
Notes: I only did a bit of Android developement mostly to test it so I will not be able to help much on very advanced Android stuff
-- Sergiu Dumitriu http://purl.org/net/sergiu/
On Sun, Mar 20, 2011 at 6:17 PM, Ludovic Dubost <[email protected]> wrote:
Hi,
I wanted to rename this project to Android/iPhone instead of Android only.
I tend to think that today FULL native client development on Android or iOS is outdated. There are now libraries like Appcelerator Titanium (http://www.appcelerator.com/) or PhoneGap (http://www.phonegap.com/) that allow to do cross platform development with "native UI" look and feel in Javascript and with very nice web integration.
I support this approach too, and agree that a pure Android client does not bring much to the table. HTML/CSS/JS is becoming the logical run-time for mobile web-oriented apps. In addition to the integration library like titanium or PhoneGap we might want to look into a mobile dev UI framework like jquery mobile or JoApp (http://joapp.com/) Jerome
I've done a prototype with Appcelerator and calling REST/JSON apis from it is a breeze and the result is a very nice native looking application. The great advantage is to develope mostly once for both platforms.
Also the application is tightly connected to a good mobile skin. Indeed given XWiki's web capabilities, you cannot have of an application developped on top of XWiki working on a mobile without actually calling the application itself in web mode (good example is a livetable). So you can't only interact with the content engine of XWiki. Therefore a good native mobile XWiki application is a front end with nice "mobile" oriented widgets for the home page, the activity stream, the search and maybe others which then link to the native XWiki pages embedded in a mobile skin.
Althouth native mobile application + mobile skin are connected they can still be viewed as different projects as the mobile skin can be used on it's own.
Ludovic
Le 20/03/11 18:00, Thomas Mortagne a écrit :
Hi Rauf,
Great you are interested in this project !
On Sun, Mar 20, 2011 at 17:32, Abdul Rauf<[email protected]> wrote:
Dear Thomas Mortagne
I am very excited to contribute in open source community through the platform of Google Summer of Code 2011. I have visited the ideas page of “XWiki” at http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/ for GSoC 2011. I am interested in working on “Google Android client” for XWiki. The reason being is my interest in smartphone development. I have previously worked in Windows Phone 7 and to some extent in Blackberry. I want to experience development in other platforms such as Android. I've worked in Java, CSS, HTML and Javascript.
I am writing to let you know my understanding of the project and would like your feedback on it. My understanding of the requirements is as follows:
- To develop a smartphone application for XWiki. - The application should be able to navigate wiki spaces and pages. - The application should allow offline editing of wiki space and pages and synchronise results on connecting with the repository. - The application should also allow users an option to launch a browser window.
That is for the UI part yes.
The user need a way to view the result and there is a lot of ways which are not requiring the same work: - launch the browser to the page (which will be the minimum for this GSOC) - integrate the browser into the application if you have more time - something event more integrated in the application if you have lot of time but i doubt it will be possible ;)
Plus any commons sense you are thinking of since you are probably more eperianced than me in mobile development ;)
But there is also another side of the project which is to develop a nice android library package that could be used by any other Android app to comunicate with XWiki.
More than the featuires what is important is to have a good architecture (maven build, follow Andoird good practices) that will make what you did easy to improve and add other features later by someone else. That's the better way to make XWiki have a good android client in the long run.
I have some knowledge of XML-RPC client/server communication. However, you mentioned you are interested in using REST API for such communication. Does XWiki already have REST API or this API needs to be created as part of this project. Would you please refer me some material to study in this regard?
Yes there is already a very complete REST interface, a lot more complete than the XML-RPC one which is why the project should be based on it.
I look forward to your response.
Regards
Notes: I only did a bit of Android developement mostly to test it so I will not be able to help much on very advanced Android stuff
Rauf
University of Gloucestershire _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Wed, Mar 23, 2011 at 12:05, Jerome Velociter <[email protected]> wrote:
On Sun, Mar 20, 2011 at 6:17 PM, Ludovic Dubost <[email protected]> wrote:
Hi,
I wanted to rename this project to Android/iPhone instead of Android only.
I tend to think that today FULL native client development on Android or iOS is outdated. There are now libraries like Appcelerator Titanium (http://www.appcelerator.com/) or PhoneGap (http://www.phonegap.com/) that allow to do cross platform development with "native UI" look and feel in Javascript and with very nice web integration.
I support this approach too, and agree that a pure Android client does not bring much to the table.
HTML/CSS/JS is becoming the logical run-time for mobile web-oriented apps.
In addition to the integration library like titanium or PhoneGap we might want to look into a mobile dev UI framework like jquery mobile or JoApp (http://joapp.com/)
Again that's form an UI point of view only which is not the main concern of my proposal, feel free to add another GSOC project.
Jerome
I've done a prototype with Appcelerator and calling REST/JSON apis from it is a breeze and the result is a very nice native looking application. The great advantage is to develope mostly once for both platforms.
Also the application is tightly connected to a good mobile skin. Indeed given XWiki's web capabilities, you cannot have of an application developped on top of XWiki working on a mobile without actually calling the application itself in web mode (good example is a livetable). So you can't only interact with the content engine of XWiki. Therefore a good native mobile XWiki application is a front end with nice "mobile" oriented widgets for the home page, the activity stream, the search and maybe others which then link to the native XWiki pages embedded in a mobile skin.
Althouth native mobile application + mobile skin are connected they can still be viewed as different projects as the mobile skin can be used on it's own.
Ludovic
Le 20/03/11 18:00, Thomas Mortagne a écrit :
Hi Rauf,
Great you are interested in this project !
On Sun, Mar 20, 2011 at 17:32, Abdul Rauf<[email protected]> wrote:
Dear Thomas Mortagne
I am very excited to contribute in open source community through the platform of Google Summer of Code 2011. I have visited the ideas page of “XWiki” at http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/ for GSoC 2011. I am interested in working on “Google Android client” for XWiki. The reason being is my interest in smartphone development. I have previously worked in Windows Phone 7 and to some extent in Blackberry. I want to experience development in other platforms such as Android. I've worked in Java, CSS, HTML and Javascript.
I am writing to let you know my understanding of the project and would like your feedback on it. My understanding of the requirements is as follows:
- To develop a smartphone application for XWiki. - The application should be able to navigate wiki spaces and pages. - The application should allow offline editing of wiki space and pages and synchronise results on connecting with the repository. - The application should also allow users an option to launch a browser window.
That is for the UI part yes.
The user need a way to view the result and there is a lot of ways which are not requiring the same work: - launch the browser to the page (which will be the minimum for this GSOC) - integrate the browser into the application if you have more time - something event more integrated in the application if you have lot of time but i doubt it will be possible ;)
Plus any commons sense you are thinking of since you are probably more eperianced than me in mobile development ;)
But there is also another side of the project which is to develop a nice android library package that could be used by any other Android app to comunicate with XWiki.
More than the featuires what is important is to have a good architecture (maven build, follow Andoird good practices) that will make what you did easy to improve and add other features later by someone else. That's the better way to make XWiki have a good android client in the long run.
I have some knowledge of XML-RPC client/server communication. However, you mentioned you are interested in using REST API for such communication. Does XWiki already have REST API or this API needs to be created as part of this project. Would you please refer me some material to study in this regard?
Yes there is already a very complete REST interface, a lot more complete than the XML-RPC one which is why the project should be based on it.
I look forward to your response.
Regards
Notes: I only did a bit of Android developement mostly to test it so I will not be able to help much on very advanced Android stuff
Rauf
University of Gloucestershire _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Wed, Mar 23, 2011 at 12:10, Thomas Mortagne <[email protected]> wrote:
On Wed, Mar 23, 2011 at 12:05, Jerome Velociter <[email protected]> wrote:
On Sun, Mar 20, 2011 at 6:17 PM, Ludovic Dubost <[email protected]> wrote:
Hi,
I wanted to rename this project to Android/iPhone instead of Android only.
I tend to think that today FULL native client development on Android or iOS is outdated. There are now libraries like Appcelerator Titanium (http://www.appcelerator.com/) or PhoneGap (http://www.phonegap.com/) that allow to do cross platform development with "native UI" look and feel in Javascript and with very nice web integration.
I support this approach too, and agree that a pure Android client does not bring much to the table.
HTML/CSS/JS is becoming the logical run-time for mobile web-oriented apps.
In addition to the integration library like titanium or PhoneGap we might want to look into a mobile dev UI framework like jquery mobile or JoApp (http://joapp.com/)
Again that's form an UI point of view only which is not the main concern of my proposal, feel free to add another GSOC project.
There is already several peoples interested on that subject and not that the same aspects so we would have several projects.
Jerome
I've done a prototype with Appcelerator and calling REST/JSON apis from it is a breeze and the result is a very nice native looking application. The great advantage is to develope mostly once for both platforms.
Also the application is tightly connected to a good mobile skin. Indeed given XWiki's web capabilities, you cannot have of an application developped on top of XWiki working on a mobile without actually calling the application itself in web mode (good example is a livetable). So you can't only interact with the content engine of XWiki. Therefore a good native mobile XWiki application is a front end with nice "mobile" oriented widgets for the home page, the activity stream, the search and maybe others which then link to the native XWiki pages embedded in a mobile skin.
Althouth native mobile application + mobile skin are connected they can still be viewed as different projects as the mobile skin can be used on it's own.
Ludovic
Le 20/03/11 18:00, Thomas Mortagne a écrit :
Hi Rauf,
Great you are interested in this project !
On Sun, Mar 20, 2011 at 17:32, Abdul Rauf<[email protected]> wrote:
Dear Thomas Mortagne
I am very excited to contribute in open source community through the platform of Google Summer of Code 2011. I have visited the ideas page of “XWiki” at http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/ for GSoC 2011. I am interested in working on “Google Android client” for XWiki. The reason being is my interest in smartphone development. I have previously worked in Windows Phone 7 and to some extent in Blackberry. I want to experience development in other platforms such as Android. I've worked in Java, CSS, HTML and Javascript.
I am writing to let you know my understanding of the project and would like your feedback on it. My understanding of the requirements is as follows:
- To develop a smartphone application for XWiki. - The application should be able to navigate wiki spaces and pages. - The application should allow offline editing of wiki space and pages and synchronise results on connecting with the repository. - The application should also allow users an option to launch a browser window.
That is for the UI part yes.
The user need a way to view the result and there is a lot of ways which are not requiring the same work: - launch the browser to the page (which will be the minimum for this GSOC) - integrate the browser into the application if you have more time - something event more integrated in the application if you have lot of time but i doubt it will be possible ;)
Plus any commons sense you are thinking of since you are probably more eperianced than me in mobile development ;)
But there is also another side of the project which is to develop a nice android library package that could be used by any other Android app to comunicate with XWiki.
More than the featuires what is important is to have a good architecture (maven build, follow Andoird good practices) that will make what you did easy to improve and add other features later by someone else. That's the better way to make XWiki have a good android client in the long run.
I have some knowledge of XML-RPC client/server communication. However, you mentioned you are interested in using REST API for such communication. Does XWiki already have REST API or this API needs to be created as part of this project. Would you please refer me some material to study in this regard?
Yes there is already a very complete REST interface, a lot more complete than the XML-RPC one which is why the project should be based on it.
I look forward to your response.
Regards
Notes: I only did a bit of Android developement mostly to test it so I will not be able to help much on very advanced Android stuff
Rauf
University of Gloucestershire _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne
On Wed, Mar 23, 2011 at 12:10 PM, Thomas Mortagne <[email protected]> wrote:
On Wed, Mar 23, 2011 at 12:05, Jerome Velociter <[email protected]> wrote:
On Sun, Mar 20, 2011 at 6:17 PM, Ludovic Dubost <[email protected]> wrote:
Hi,
I wanted to rename this project to Android/iPhone instead of Android only.
I tend to think that today FULL native client development on Android or iOS is outdated. There are now libraries like Appcelerator Titanium (http://www.appcelerator.com/) or PhoneGap (http://www.phonegap.com/) that allow to do cross platform development with "native UI" look and feel in Javascript and with very nice web integration.
I support this approach too, and agree that a pure Android client does not bring much to the table.
HTML/CSS/JS is becoming the logical run-time for mobile web-oriented apps.
In addition to the integration library like titanium or PhoneGap we might want to look into a mobile dev UI framework like jquery mobile or JoApp (http://joapp.com/)
Again that's form an UI point of view only which is not the main concern of my proposal, feel free to add another GSOC project.
No this has nothing to do with UI. It's about how one sees the development model for the mobile Web. Now I agree it can be viewed as a different project. I'm personally not going to add it because I believe the mobile skin project proposed by Caty is a good enough objective in the scope of the GSoC and that anything else in the mobile area would dilute the effort. And as Ludo stated, the mobile skin is sort of a pre-requisite for any good mobile app. That's just my opinion, if anyone thinks differently he can propose this project of course. Jerome
Jerome
I've done a prototype with Appcelerator and calling REST/JSON apis from it is a breeze and the result is a very nice native looking application. The great advantage is to develope mostly once for both platforms.
Also the application is tightly connected to a good mobile skin. Indeed given XWiki's web capabilities, you cannot have of an application developped on top of XWiki working on a mobile without actually calling the application itself in web mode (good example is a livetable). So you can't only interact with the content engine of XWiki. Therefore a good native mobile XWiki application is a front end with nice "mobile" oriented widgets for the home page, the activity stream, the search and maybe others which then link to the native XWiki pages embedded in a mobile skin.
Althouth native mobile application + mobile skin are connected they can still be viewed as different projects as the mobile skin can be used on it's own.
Ludovic
Le 20/03/11 18:00, Thomas Mortagne a écrit :
Hi Rauf,
Great you are interested in this project !
On Sun, Mar 20, 2011 at 17:32, Abdul Rauf<[email protected]> wrote:
Dear Thomas Mortagne
I am very excited to contribute in open source community through the platform of Google Summer of Code 2011. I have visited the ideas page of “XWiki” at http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/ for GSoC 2011. I am interested in working on “Google Android client” for XWiki. The reason being is my interest in smartphone development. I have previously worked in Windows Phone 7 and to some extent in Blackberry. I want to experience development in other platforms such as Android. I've worked in Java, CSS, HTML and Javascript.
I am writing to let you know my understanding of the project and would like your feedback on it. My understanding of the requirements is as follows:
- To develop a smartphone application for XWiki. - The application should be able to navigate wiki spaces and pages. - The application should allow offline editing of wiki space and pages and synchronise results on connecting with the repository. - The application should also allow users an option to launch a browser window.
That is for the UI part yes.
The user need a way to view the result and there is a lot of ways which are not requiring the same work: - launch the browser to the page (which will be the minimum for this GSOC) - integrate the browser into the application if you have more time - something event more integrated in the application if you have lot of time but i doubt it will be possible ;)
Plus any commons sense you are thinking of since you are probably more eperianced than me in mobile development ;)
But there is also another side of the project which is to develop a nice android library package that could be used by any other Android app to comunicate with XWiki.
More than the featuires what is important is to have a good architecture (maven build, follow Andoird good practices) that will make what you did easy to improve and add other features later by someone else. That's the better way to make XWiki have a good android client in the long run.
I have some knowledge of XML-RPC client/server communication. However, you mentioned you are interested in using REST API for such communication. Does XWiki already have REST API or this API needs to be created as part of this project. Would you please refer me some material to study in this regard?
Yes there is already a very complete REST interface, a lot more complete than the XML-RPC one which is why the project should be based on it.
I look forward to your response.
Regards
Notes: I only did a bit of Android developement mostly to test it so I will not be able to help much on very advanced Android stuff
Rauf
University of Gloucestershire _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Wed, Mar 23, 2011 at 12:32, Jerome Velociter <[email protected]> wrote:
On Wed, Mar 23, 2011 at 12:10 PM, Thomas Mortagne <[email protected]> wrote:
On Wed, Mar 23, 2011 at 12:05, Jerome Velociter <[email protected]> wrote:
On Sun, Mar 20, 2011 at 6:17 PM, Ludovic Dubost <[email protected]> wrote:
Hi,
I wanted to rename this project to Android/iPhone instead of Android only.
I tend to think that today FULL native client development on Android or iOS is outdated. There are now libraries like Appcelerator Titanium (http://www.appcelerator.com/) or PhoneGap (http://www.phonegap.com/) that allow to do cross platform development with "native UI" look and feel in Javascript and with very nice web integration.
I support this approach too, and agree that a pure Android client does not bring much to the table.
HTML/CSS/JS is becoming the logical run-time for mobile web-oriented apps.
In addition to the integration library like titanium or PhoneGap we might want to look into a mobile dev UI framework like jquery mobile or JoApp (http://joapp.com/)
Again that's form an UI point of view only which is not the main concern of my proposal, feel free to add another GSOC project.
No this has nothing to do with UI. It's about how one sees the development model for the mobile Web.
Now I agree it can be viewed as a different project. I'm personally not going to add it because I believe the mobile skin project proposed by Caty is a good enough objective in the scope of the GSoC and that anything else in the mobile area would dilute the effort. And as Ludo stated, the mobile skin is sort of a pre-requisite for any good mobile app. That's just my opinion, if anyone thinks differently he can propose this project of course.
The mobile skin is obviously needed and this project is not here to be an alternative. And I agree with you that if it's only to provide a mobile version of the XWiki UI, mobile skin is better and enough as well as a lot more maintained. I think again you don't understand what this project is really about. As I said in another thread page editing is just a useful demo application of the use of the android xwiki client library which is supposed to be used by any android application which wants to deal with XWiki data to synchronize etc...
Jerome
Jerome
I've done a prototype with Appcelerator and calling REST/JSON apis from it is a breeze and the result is a very nice native looking application. The great advantage is to develope mostly once for both platforms.
Also the application is tightly connected to a good mobile skin. Indeed given XWiki's web capabilities, you cannot have of an application developped on top of XWiki working on a mobile without actually calling the application itself in web mode (good example is a livetable). So you can't only interact with the content engine of XWiki. Therefore a good native mobile XWiki application is a front end with nice "mobile" oriented widgets for the home page, the activity stream, the search and maybe others which then link to the native XWiki pages embedded in a mobile skin.
Althouth native mobile application + mobile skin are connected they can still be viewed as different projects as the mobile skin can be used on it's own.
Ludovic
Le 20/03/11 18:00, Thomas Mortagne a écrit :
Hi Rauf,
Great you are interested in this project !
On Sun, Mar 20, 2011 at 17:32, Abdul Rauf<[email protected]> wrote:
Dear Thomas Mortagne
I am very excited to contribute in open source community through the platform of Google Summer of Code 2011. I have visited the ideas page of “XWiki” at http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/ for GSoC 2011. I am interested in working on “Google Android client” for XWiki. The reason being is my interest in smartphone development. I have previously worked in Windows Phone 7 and to some extent in Blackberry. I want to experience development in other platforms such as Android. I've worked in Java, CSS, HTML and Javascript.
I am writing to let you know my understanding of the project and would like your feedback on it. My understanding of the requirements is as follows:
- To develop a smartphone application for XWiki. - The application should be able to navigate wiki spaces and pages. - The application should allow offline editing of wiki space and pages and synchronise results on connecting with the repository. - The application should also allow users an option to launch a browser window.
That is for the UI part yes.
The user need a way to view the result and there is a lot of ways which are not requiring the same work: - launch the browser to the page (which will be the minimum for this GSOC) - integrate the browser into the application if you have more time - something event more integrated in the application if you have lot of time but i doubt it will be possible ;)
Plus any commons sense you are thinking of since you are probably more eperianced than me in mobile development ;)
But there is also another side of the project which is to develop a nice android library package that could be used by any other Android app to comunicate with XWiki.
More than the featuires what is important is to have a good architecture (maven build, follow Andoird good practices) that will make what you did easy to improve and add other features later by someone else. That's the better way to make XWiki have a good android client in the long run.
I have some knowledge of XML-RPC client/server communication. However, you mentioned you are interested in using REST API for such communication. Does XWiki already have REST API or this API needs to be created as part of this project. Would you please refer me some material to study in this regard?
Yes there is already a very complete REST interface, a lot more complete than the XML-RPC one which is why the project should be based on it.
I look forward to your response.
Regards
Notes: I only did a bit of Android developement mostly to test it so I will not be able to help much on very advanced Android stuff
Rauf
University of Gloucestershire _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Wed, Mar 23, 2011 at 1:36 PM, Thomas Mortagne <[email protected]> wrote:
On Wed, Mar 23, 2011 at 12:32, Jerome Velociter <[email protected]> wrote:
On Wed, Mar 23, 2011 at 12:10 PM, Thomas Mortagne <[email protected]> wrote:
On Wed, Mar 23, 2011 at 12:05, Jerome Velociter <[email protected]> wrote:
On Sun, Mar 20, 2011 at 6:17 PM, Ludovic Dubost <[email protected]> wrote:
Hi,
I wanted to rename this project to Android/iPhone instead of Android only.
I tend to think that today FULL native client development on Android or iOS is outdated. There are now libraries like Appcelerator Titanium (http://www.appcelerator.com/) or PhoneGap (http://www.phonegap.com/) that allow to do cross platform development with "native UI" look and feel in Javascript and with very nice web integration.
I support this approach too, and agree that a pure Android client does not bring much to the table.
HTML/CSS/JS is becoming the logical run-time for mobile web-oriented apps.
In addition to the integration library like titanium or PhoneGap we might want to look into a mobile dev UI framework like jquery mobile or JoApp (http://joapp.com/)
Again that's form an UI point of view only which is not the main concern of my proposal, feel free to add another GSOC project.
No this has nothing to do with UI. It's about how one sees the development model for the mobile Web.
Now I agree it can be viewed as a different project. I'm personally not going to add it because I believe the mobile skin project proposed by Caty is a good enough objective in the scope of the GSoC and that anything else in the mobile area would dilute the effort. And as Ludo stated, the mobile skin is sort of a pre-requisite for any good mobile app. That's just my opinion, if anyone thinks differently he can propose this project of course.
The mobile skin is obviously needed and this project is not here to be an alternative. And I agree with you that if it's only to provide a mobile version of the XWiki UI, mobile skin is better and enough as well as a lot more maintained.
I think again you don't understand what this project is really about. As I said in another thread page editing is just a useful demo application of the use of the android xwiki client library which is supposed to be used by any android application which wants to deal with XWiki data to synchronize etc...
Don't get me wrong, I understand the project and it scope, which can be wider than "just a mobile app" with a generic lib for android. I just don't think it's so interesting for XWiki right now - no offense. To disclose fully my reasoning, I think it's not a good idea to do 2 SoC projects in the mobile area (because even if the projects are not alternatives one to another, they still are both in the mobile area) ; and if I were to chose just one, it would obviously be the mobile skin one which if achieved brings great (and immediate) value. Again that's just my 2cts, others might not think like this. Right now we are in the project ideas phase so I really don't want to discourage anyone to get interested in it, share ideas, etc ; quite the opposite actually, the more insights the better. I just gave my take on the story. Jerome
Jerome
Jerome
I've done a prototype with Appcelerator and calling REST/JSON apis from it is a breeze and the result is a very nice native looking application. The great advantage is to develope mostly once for both platforms.
Also the application is tightly connected to a good mobile skin. Indeed given XWiki's web capabilities, you cannot have of an application developped on top of XWiki working on a mobile without actually calling the application itself in web mode (good example is a livetable). So you can't only interact with the content engine of XWiki. Therefore a good native mobile XWiki application is a front end with nice "mobile" oriented widgets for the home page, the activity stream, the search and maybe others which then link to the native XWiki pages embedded in a mobile skin.
Althouth native mobile application + mobile skin are connected they can still be viewed as different projects as the mobile skin can be used on it's own.
Ludovic
Le 20/03/11 18:00, Thomas Mortagne a écrit :
Hi Rauf,
Great you are interested in this project !
On Sun, Mar 20, 2011 at 17:32, Abdul Rauf<[email protected]> wrote: > > Dear Thomas Mortagne > > > I am very excited to contribute in open source community through the > platform of Google Summer of Code 2011. I have visited the ideas page > of “XWiki” at http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/ for > GSoC 2011. I am interested in working on “Google Android client” for > XWiki. > The reason being is my interest in smartphone development. I have > previously > worked in Windows Phone 7 and to some extent in Blackberry. I want to > experience development in other platforms such as Android. I've worked in > Java, CSS, HTML and Javascript. > > > I am writing to let you know my understanding of the project and would > like > your feedback on it. My understanding of the requirements is as follows: > > > - To develop a smartphone application for XWiki. > - The application should be able to navigate wiki spaces and pages. > - The application should allow offline editing of wiki space and pages > and synchronise results on connecting with the repository. > - The application should also allow users an option to launch a browser > window.
That is for the UI part yes.
The user need a way to view the result and there is a lot of ways which are not requiring the same work: - launch the browser to the page (which will be the minimum for this GSOC) - integrate the browser into the application if you have more time - something event more integrated in the application if you have lot of time but i doubt it will be possible ;)
Plus any commons sense you are thinking of since you are probably more eperianced than me in mobile development ;)
But there is also another side of the project which is to develop a nice android library package that could be used by any other Android app to comunicate with XWiki.
More than the featuires what is important is to have a good architecture (maven build, follow Andoird good practices) that will make what you did easy to improve and add other features later by someone else. That's the better way to make XWiki have a good android client in the long run.
> I have some knowledge of XML-RPC client/server communication. However, > you > mentioned you are interested in using REST API for such communication. > Does > XWiki already have REST API or this API needs to be created as part of > this > project. Would you please refer me some material to study in this regard?
Yes there is already a very complete REST interface, a lot more complete than the XML-RPC one which is why the project should be based on it.
> > I look forward to your response. > > > Regards
Notes: I only did a bit of Android developement mostly to test it so I will not be able to help much on very advanced Android stuff
> > Rauf > > University of Gloucestershire > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs >
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Wed, Mar 23, 2011 at 14:02, Jerome Velociter <[email protected]> wrote:
On Wed, Mar 23, 2011 at 1:36 PM, Thomas Mortagne <[email protected]> wrote:
On Wed, Mar 23, 2011 at 12:32, Jerome Velociter <[email protected]> wrote:
On Wed, Mar 23, 2011 at 12:10 PM, Thomas Mortagne <[email protected]> wrote:
On Wed, Mar 23, 2011 at 12:05, Jerome Velociter <[email protected]> wrote:
On Sun, Mar 20, 2011 at 6:17 PM, Ludovic Dubost <[email protected]> wrote:
Hi,
I wanted to rename this project to Android/iPhone instead of Android only.
I tend to think that today FULL native client development on Android or iOS is outdated. There are now libraries like Appcelerator Titanium (http://www.appcelerator.com/) or PhoneGap (http://www.phonegap.com/) that allow to do cross platform development with "native UI" look and feel in Javascript and with very nice web integration.
I support this approach too, and agree that a pure Android client does not bring much to the table.
HTML/CSS/JS is becoming the logical run-time for mobile web-oriented apps.
In addition to the integration library like titanium or PhoneGap we might want to look into a mobile dev UI framework like jquery mobile or JoApp (http://joapp.com/)
Again that's form an UI point of view only which is not the main concern of my proposal, feel free to add another GSOC project.
No this has nothing to do with UI. It's about how one sees the development model for the mobile Web.
Now I agree it can be viewed as a different project. I'm personally not going to add it because I believe the mobile skin project proposed by Caty is a good enough objective in the scope of the GSoC and that anything else in the mobile area would dilute the effort. And as Ludo stated, the mobile skin is sort of a pre-requisite for any good mobile app. That's just my opinion, if anyone thinks differently he can propose this project of course.
The mobile skin is obviously needed and this project is not here to be an alternative. And I agree with you that if it's only to provide a mobile version of the XWiki UI, mobile skin is better and enough as well as a lot more maintained.
I think again you don't understand what this project is really about. As I said in another thread page editing is just a useful demo application of the use of the android xwiki client library which is supposed to be used by any android application which wants to deal with XWiki data to synchronize etc...
Don't get me wrong, I understand the project and it scope, which can be wider than "just a mobile app" with a generic lib for android. I just don't think it's so interesting for XWiki right now - no offense. To disclose fully my reasoning, I think it's not a good idea to do 2 SoC projects in the mobile area (because even if the projects are not alternatives one to another, they still are both in the mobile area) ; and if I were to chose just one, it would obviously be the mobile skin one which if achieved brings great (and immediate) value. Again that's just my 2cts, others might not think like this. Right now we are in the project ideas phase so I really don't want to discourage anyone to get interested in it, share ideas, etc ; quite the opposite actually, the more insights the better. I just gave my take on the story.
As you said we are in the proposal stage and the point is that there will not be just one project to choose anyway so that's a discussion for later. Of course all proposals does not bring the same value to XWiki itself if I had to vote for only between theses two that it would be the skin but that has nothing to do here. I don't see the point in trying to determine which proposal is the best when it's two very different stuff...
Jerome
Jerome
Jerome
I've done a prototype with Appcelerator and calling REST/JSON apis from it is a breeze and the result is a very nice native looking application. The great advantage is to develope mostly once for both platforms.
Also the application is tightly connected to a good mobile skin. Indeed given XWiki's web capabilities, you cannot have of an application developped on top of XWiki working on a mobile without actually calling the application itself in web mode (good example is a livetable). So you can't only interact with the content engine of XWiki. Therefore a good native mobile XWiki application is a front end with nice "mobile" oriented widgets for the home page, the activity stream, the search and maybe others which then link to the native XWiki pages embedded in a mobile skin.
Althouth native mobile application + mobile skin are connected they can still be viewed as different projects as the mobile skin can be used on it's own.
Ludovic
Le 20/03/11 18:00, Thomas Mortagne a écrit : > > Hi Rauf, > > Great you are interested in this project ! > > On Sun, Mar 20, 2011 at 17:32, Abdul Rauf<[email protected]> wrote: >> >> Dear Thomas Mortagne >> >> >> I am very excited to contribute in open source community through the >> platform of Google Summer of Code 2011. I have visited the ideas page >> of “XWiki” at http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/ for >> GSoC 2011. I am interested in working on “Google Android client” for >> XWiki. >> The reason being is my interest in smartphone development. I have >> previously >> worked in Windows Phone 7 and to some extent in Blackberry. I want to >> experience development in other platforms such as Android. I've worked in >> Java, CSS, HTML and Javascript. >> >> >> I am writing to let you know my understanding of the project and would >> like >> your feedback on it. My understanding of the requirements is as follows: >> >> >> - To develop a smartphone application for XWiki. >> - The application should be able to navigate wiki spaces and pages. >> - The application should allow offline editing of wiki space and pages >> and synchronise results on connecting with the repository. >> - The application should also allow users an option to launch a browser >> window. > > That is for the UI part yes. > > The user need a way to view the result and there is a lot of ways > which are not requiring the same work: > - launch the browser to the page (which will be the minimum for this GSOC) > - integrate the browser into the application if you have more time > - something event more integrated in the application if you have lot > of time but i doubt it will be possible ;) > > Plus any commons sense you are thinking of since you are probably more > eperianced than me in mobile development ;) > > But there is also another side of the project which is to develop a > nice android library package that could be used by any other Android > app to comunicate with XWiki. > > More than the featuires what is important is to have a good > architecture (maven build, follow Andoird good practices) that will > make what you did easy to improve and add other features later by > someone else. That's the better way to make XWiki have a good android > client in the long run. > >> I have some knowledge of XML-RPC client/server communication. However, >> you >> mentioned you are interested in using REST API for such communication. >> Does >> XWiki already have REST API or this API needs to be created as part of >> this >> project. Would you please refer me some material to study in this regard? > > Yes there is already a very complete REST interface, a lot more > complete than the XML-RPC one which is why the project should be based > on it. > >> >> I look forward to your response. >> >> >> Regards > > Notes: I only did a bit of Android developement mostly to test it so I > will not be able to help much on very advanced Android stuff > >> >> Rauf >> >> University of Gloucestershire >> _______________________________________________ >> devs mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/devs >> > >
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Wed, Mar 23, 2011 at 2:16 PM, Thomas Mortagne <[email protected]> wrote:
On Wed, Mar 23, 2011 at 14:02, Jerome Velociter <[email protected]> wrote:
On Wed, Mar 23, 2011 at 1:36 PM, Thomas Mortagne <[email protected]> wrote:
On Wed, Mar 23, 2011 at 12:32, Jerome Velociter <[email protected]> wrote:
On Wed, Mar 23, 2011 at 12:10 PM, Thomas Mortagne <[email protected]> wrote:
On Wed, Mar 23, 2011 at 12:05, Jerome Velociter <[email protected]> wrote:
On Sun, Mar 20, 2011 at 6:17 PM, Ludovic Dubost <[email protected]> wrote: > > Hi, > > I wanted to rename this project to Android/iPhone instead of Android only. > > I tend to think that today FULL native client development on Android or iOS > is outdated. > There are now libraries like Appcelerator Titanium > (http://www.appcelerator.com/) or PhoneGap (http://www.phonegap.com/) > that allow to do cross platform development with "native UI" look and feel > in Javascript and with very nice web integration.
I support this approach too, and agree that a pure Android client does not bring much to the table.
HTML/CSS/JS is becoming the logical run-time for mobile web-oriented apps.
In addition to the integration library like titanium or PhoneGap we might want to look into a mobile dev UI framework like jquery mobile or JoApp (http://joapp.com/)
Again that's form an UI point of view only which is not the main concern of my proposal, feel free to add another GSOC project.
No this has nothing to do with UI. It's about how one sees the development model for the mobile Web.
Now I agree it can be viewed as a different project. I'm personally not going to add it because I believe the mobile skin project proposed by Caty is a good enough objective in the scope of the GSoC and that anything else in the mobile area would dilute the effort. And as Ludo stated, the mobile skin is sort of a pre-requisite for any good mobile app. That's just my opinion, if anyone thinks differently he can propose this project of course.
The mobile skin is obviously needed and this project is not here to be an alternative. And I agree with you that if it's only to provide a mobile version of the XWiki UI, mobile skin is better and enough as well as a lot more maintained.
I think again you don't understand what this project is really about. As I said in another thread page editing is just a useful demo application of the use of the android xwiki client library which is supposed to be used by any android application which wants to deal with XWiki data to synchronize etc...
Don't get me wrong, I understand the project and it scope, which can be wider than "just a mobile app" with a generic lib for android. I just don't think it's so interesting for XWiki right now - no offense. To disclose fully my reasoning, I think it's not a good idea to do 2 SoC projects in the mobile area (because even if the projects are not alternatives one to another, they still are both in the mobile area) ; and if I were to chose just one, it would obviously be the mobile skin one which if achieved brings great (and immediate) value. Again that's just my 2cts, others might not think like this. Right now we are in the project ideas phase so I really don't want to discourage anyone to get interested in it, share ideas, etc ; quite the opposite actually, the more insights the better. I just gave my take on the story.
As you said we are in the proposal stage and the point is that there will not be just one project to choose anyway so that's a discussion for later.
Of course all proposals does not bring the same value to XWiki itself if I had to vote for only between theses two that it would be the skin but that has nothing to do here. I don't see the point in trying to determine which proposal is the best when it's two very different stuff...
Just wanted to explain why I support Ludovic's vision but why I also would not add another project proposal. Nothing else ; and indeed that's not the place to debate what is best to do, that's why I took care of saying this was my personal opinion and nothing more. Sorry if this led to any kind of confusion. Jerome
Jerome
Jerome
Jerome
> > I've done a prototype with Appcelerator and calling REST/JSON apis from it > is a breeze and the result is a very nice native looking application. > The great advantage is to develope mostly once for both platforms. > > Also the application is tightly connected to a good mobile skin. Indeed > given XWiki's web capabilities, you cannot have of an application developped > on top of XWiki working on a mobile without actually calling the application > itself in web mode (good example is a livetable). So you can't only interact > with the content engine of XWiki. Therefore a good native mobile XWiki > application is a front end with nice "mobile" oriented widgets for the home > page, the activity stream, the search and maybe others which then link to > the native XWiki pages embedded in a mobile skin. > > Althouth native mobile application + mobile skin are connected they can > still be viewed as different projects as the mobile skin can be used on it's > own. > > Ludovic > > Le 20/03/11 18:00, Thomas Mortagne a écrit : >> >> Hi Rauf, >> >> Great you are interested in this project ! >> >> On Sun, Mar 20, 2011 at 17:32, Abdul Rauf<[email protected]> wrote: >>> >>> Dear Thomas Mortagne >>> >>> >>> I am very excited to contribute in open source community through the >>> platform of Google Summer of Code 2011. I have visited the ideas page >>> of “XWiki” at http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/ for >>> GSoC 2011. I am interested in working on “Google Android client” for >>> XWiki. >>> The reason being is my interest in smartphone development. I have >>> previously >>> worked in Windows Phone 7 and to some extent in Blackberry. I want to >>> experience development in other platforms such as Android. I've worked in >>> Java, CSS, HTML and Javascript. >>> >>> >>> I am writing to let you know my understanding of the project and would >>> like >>> your feedback on it. My understanding of the requirements is as follows: >>> >>> >>> - To develop a smartphone application for XWiki. >>> - The application should be able to navigate wiki spaces and pages. >>> - The application should allow offline editing of wiki space and pages >>> and synchronise results on connecting with the repository. >>> - The application should also allow users an option to launch a browser >>> window. >> >> That is for the UI part yes. >> >> The user need a way to view the result and there is a lot of ways >> which are not requiring the same work: >> - launch the browser to the page (which will be the minimum for this GSOC) >> - integrate the browser into the application if you have more time >> - something event more integrated in the application if you have lot >> of time but i doubt it will be possible ;) >> >> Plus any commons sense you are thinking of since you are probably more >> eperianced than me in mobile development ;) >> >> But there is also another side of the project which is to develop a >> nice android library package that could be used by any other Android >> app to comunicate with XWiki. >> >> More than the featuires what is important is to have a good >> architecture (maven build, follow Andoird good practices) that will >> make what you did easy to improve and add other features later by >> someone else. That's the better way to make XWiki have a good android >> client in the long run. >> >>> I have some knowledge of XML-RPC client/server communication. However, >>> you >>> mentioned you are interested in using REST API for such communication. >>> Does >>> XWiki already have REST API or this API needs to be created as part of >>> this >>> project. Would you please refer me some material to study in this regard? >> >> Yes there is already a very complete REST interface, a lot more >> complete than the XML-RPC one which is why the project should be based >> on it. >> >>> >>> I look forward to your response. >>> >>> >>> Regards >> >> Notes: I only did a bit of Android developement mostly to test it so I >> will not be able to help much on very advanced Android stuff >> >>> >>> Rauf >>> >>> University of Gloucestershire >>> _______________________________________________ >>> devs mailing list >>> [email protected] >>> http://lists.xwiki.org/mailman/listinfo/devs >>> >> >> > > > -- > Ludovic Dubost > Blog: http://blog.ludovic.org/ > XWiki: http://www.xwiki.com > Skype: ldubost GTalk: ldubost > > > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (6)
-
Abdul Rauf -
Jerome Velociter -
Ludovic Dubost -
Paul Libbrecht -
Sergiu Dumitriu -
Thomas Mortagne