Sounds good,

Now you should look at finding an issue in the client, fix it and propose a
pull request, as it's part of the candidacy process.

Ludovic


2013/5/2 Buddhiprabha Erabadda <[email protected]>

> Hi,
>
>
> I created a proposal for this project idea including the information as you
> instructed and submitted to mélange. From my current understanding about
> the mobile client, I proposed some features and ways I hope to follow to
> implement them. Please review them and let me know if they need to be
> altered or more features are needed to be added.
>
>
> I would like to know your comments regarding the project proposal and if
> there will be a slot for this project idea.
>
>
> Thank you in advance.
>
> On Thu, May 2, 2013 at 2:05 AM, Ludovic Dubost <[email protected]> wrote:
>
> > Hi,
> >
> > I just pushed an updated configuration screen which has an "automatic"
> mode
> > to detect the configuration of the URLs.
> > This should simplify setup.
> >
> > As I told you, running the UI in a (supported) browser is much more
> > efficient than in the emulator and the features are currently exactly the
> > same (there is almost no native code at this point)
> >
> > Ludovic
> >
> >
> > 2013/5/1 Ludovic Dubost <[email protected]>
> >
> > >
> > >
> > > Le mercredi 1 mai 2013, Buddhiprabha Erabadda a écrit :
> > >
> > > Hi Ludovic,
> > >>
> > >> I got the new code and I could build that successfully. The problem
> with
> > >> installation had been a compatibility issue with my android device.
> The
> > >> application's build target is 4.2.2 and my device has an older
> version.
> > >
> > >
> > > I need to check this. I thought I had put an old minimum target  but
> > maybe
> > > I've done that wrong
> > >
> > >>
> > >> I built the project from source and installed it on an emulator. Now I
> > am
> > >> trying to connect to a local server according to your previous
> message.
> > >> (using the emulator is slower than using the actual device as usual
> :) )
> > >>
> > >> I could see that "Settings" page of a wiki has options to add the
> > required
> > >> information. (I guess the user interface of that page can be improved
> to
> > >> look nicer)  I will go through the prototype and let you know what
> > changes
> > >
> > >
> > > I'm working right now to add some code to detect most settings from the
> > > host name.
> > > This will simplify setup
> > >
> > >
> > >
> > >> are required in my point of view and what I think are most important
> as
> > >> you
> > >> instructed in a previous mail.
> > >
> > >
> > > Yes  that's the most important.
> > > Take some time also to detail your experience with relevant
> technologies
> > >
> > > Ludovic
> > >
> > >>
> > >> Thank you.
> > >>
> > >> On Wed, May 1, 2013 at 5:59 PM, Ludovic Dubost <[email protected]>
> > wrote:
> > >>
> > >> > I push some new code on the v2:
> > >> >
> > >> > - an android source tree (which depends on Cordoba 2.7rc1 as other
> > >> cordovas
> > >> > don't work with Android 4.2)
> > >> > - some changes in the javascript code
> > >> >
> > >> > Note to make android work you need to :
> > >> >
> > >> > - add a link to src/main/www in assets/www (cd android/assets, ln -s
> > >> > ../../src/main/www www)
> > >> > - change cordova-2.6.0 to cordova-2.7.0 in index.html
> > >> >
> > >> > Ludovic
> > >> >
> > >> >
> > >> >
> > >> > 2013/5/1 Ludovic Dubost <[email protected]>
> > >> >
> > >> > > Hi,
> > >> > >
> > >> > > I'm not sure why the apk does not work. I ran it fine on the
> > >> simulator.
> > >> > It
> > >> > > could be a compatibility issue with your device (which is it ?)
> > >> > > If the screens stays on wikis and tools it means initialization
> has
> > >> > > failed, but it could be many things (failed to load translations,
> > >> failed
> > >> > to
> > >> > > load cordova, etc..)
> > >> > >
> > >> > > The easiest way to run the application is to run it on a local
> > >> browser.
> > >> > IE
> > >> > > and Safari I think can run it fine.
> > >> > > Firefox and Chrome will block on ajax requests because of security
> > >> > issues.
> > >> > >
> > >> > > To fix this you can use:
> > >> > >
> > >> > > 1/ put the code behind a web server
> > >> > > 2/ Use the Firefox CORS extension to force CORS headers which will
> > >> allow
> > >> > > cross domain requests
> > >> > >
> > >> > > I usually develop on Safari (on Mac) as it can run the code as is.
> > >> > >
> > >> > > Ludovic
> > >> > >
> > >> > >
> > >> > >
> > >> > > 2013/4/30 Buddhiprabha Erabadda <[email protected]>
> > >> > >
> > >> > >> Hi Ludovic,
> > >> > >>
> > >> > >> Thank you for your instructions regarding configurations. I had
> > >> > previously
> > >> > >> taken the older JQuery Mobile version which does not have a
> > >> > configuration
> > >> > >> function.
> > >> > >>
> > >> > >> I downloaded the alpha release of the mobile client from the link
> > you
> > >> > >> sent.[1]  I installed it on my Android device and run it. But for
> > >> some
> > >> > >> reason it only gives me a list view with two items "wikis" and
> > >> "tools"
> > >> > and
> > >> > >> it is not possible to process further. What can be the reason for
> > >> this?
> > >> > >>
> > >> > >> Since the apk did not work I tried to build it from the
> source.[2]
> > >> Since
> > >> > >> it
> > >> > >> had a build.xml inside the Android folder I built with ant and it
> > was
> > >> > >> successfully built. But I was not able to run the project. Can
> you
> > >> > please
> > >> > >> advice me regarding building the project from source so that I
> can
> > >> test
> > >> > >> the
> > >> > >> current version of the mobile client? Thank you in advance.
> > >> > >>
> > >> > >> [1]
> > >> http://dev.xwiki.org/xwiki/bin/view/Design/MobileClientAlphaRelease
> > >> > >> [2]
> > >> > >>
> > >> > >>
> > >> >
> > >>
> >
> https://github.com/xwiki-contrib/mobile-standardxwikiclient/tree/v2/android
> > >> > >>
> > >> > >> On Tue, Apr 30, 2013 at 2:08 AM, Ludovic Dubost <
> [email protected]
> > >
> > >> > >> wrote:
> > >> > >>
> > >> > >> > Hi Buddhiprabha,
> > >> > >> >
> > >> > >> > You are very welcome to make a good proposal in the mobile area
> > >> that
> > >> > >> would
> > >> > >> > build on the current mobile client.
> > >> > >> > You need to show us that you know what it means to do Mobile
> Web
> > >> > >> > Development, that you understand the current architecture of
> the
> > >> code
> > >> > >> and
> > >> > >> > can work on the technologies needed (Cordova, Notifications,
> > >> etc..).
> > >> > >> > The next set of features will probably require slightly more
> > native
> > >> > >> > development.
> > >> > >> >
> > >> > >> > You can try to convince us that you are a good candidate by
> > >> analyzing
> > >> > >> the
> > >> > >> > current prototype and tell us what you think should be improved
> > and
> > >> > what
> > >
> > >
> > >
> > > --
> > > Sent from Mobile
> > >
> >
> >
> >
> > --
> > Ludovic Dubost
> > Founder and CEO
> > 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
> >
>
>
>
> --
> *Buddhiprabha Erabadda*
> *Department of Computer Science and Engineering*
> *University of Moratuwa*
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
>



-- 
Ludovic Dubost
Founder and CEO
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

Reply via email to