24 May
2011
24 May
'11
2:55 p.m.
On Tue, May 24, 2011 at 14:51, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
--
Thomas Mortagne
--
Thomas Mortagne
On Tue, May 24, 2011 at 09:45, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
Actually I just added https://github.com/chamika, that's it right ?
Hi Chamika,
On Mon, May 23, 2011 at 20:50, Chamika Weerasinghe <chamikaw(a)gmail.com> wrote:
Note that I think the first thing you should do before the first line
of java code (or maybe at least the hello world of the application ;))
is to have the skeleton of all that with nice maven based build
configuration that anyone can build anytime just by executing "mvn
clean install" and test it.
I just created a https://github.com/xwiki-contrib/android-client
repository which is where you will put your code during this GSOC.
If you don't already have one you should create a github account and
indicate it to me so that you I can give you the right to push on this
repository. Hi devs,
Since GSOC students have to start coding from today (23rd May) onwards I
like to gather requirements and decide scope of the mentioned project. A
short description of the project is included
here<http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Androidclien…
(http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Androidclient)
Simply I will try to access XWiki dataset using REST API and implement
Android Library. Then by using that Android Library a sample application
will be developed.
Before starting I would like to know all of your ideas related to this such
as what should be implemented, what will you expect from an Android Library
etc. So that I can get a better understand about the XWiki Android.
He is how I see it: first of all as much code as possible should be
shared with the "desktop" client and all that should be cut in as much
peaces as possible. The first desktop client I have in mind here is
XEclipse which is also a GSOC project this year so for shared parts
would be great that you work with Jun.
* model module: contains only the model (maybe it's already OK with
https://github.com/xwiki/xwiki-platform/tree/master/xwiki-platform-core/xwi…)
* REST helper: list/generate/execute all the supported REST requests.
Probably possible to share this with the desktop client.
* high level tools based on REST request: document caching et
synchronization, basically anything which is more that a direct REST
request and not a widget. Maybe cut this module in two if we can find
parts that can be shared with desktop client, will be impossible for
caching and synchronization I guess or at least not entirely
* widget module: contains android widgets that can be reused in other
android applications (XWiki navigator, editors...)
* the application: I proposed an android application which help
editing and navigating an XWiki instance in
http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Androidclient
because that's what demonstrate most of the REST API but if you have
other ideas to demonstrate on Android side no problem. Most of the
widgets used in this application should be in the "widget module" if
they are generic enough. We don't have yet the notion of
friends/connexion that will comes with wiki3.0 project otherwise that
would have been a good candidate for android contact synchronization.
Thank you all,
Best Regards,
Chamika Weerasinghe
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne