Hi, Following the publication of the v1 prototype code on github, I've started working on the v2 prototype. I've finished creating a basic new version: - using object oriented jS - using jqMobi instead of JQuery Mobile - using a JS based network layer This version has currently much less features (no offline, etc..) than the previous one but the performance is already much better and it is possible to relogin or reload a page. I've created the following page to track the development http://dev.xwiki.org/xwiki/bin/view/Design/MobileClient The code of v2 is in a branch on github: https://github.com/xwiki-contrib/mobile-standardxwikiclient/tree/v2 There is still a lot of work like: - editing the configuration - adding the XEM and other queries that were present in the v1 version - implement Cati's design - add some network recovery features (for instance when you are not authentified anymore) Ludovic 2013/2/2 Ludovic Dubost <ludovic(a)xwiki.com> and -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi Caty, Changes are great. I'll continue to work on the application soon to re-add the features of the previous version. There are some things that don't match the current application: 1/ The search button at the bottom is actually not doing search. It's a "resize" button to resize the web screen manually if it failed automatically. This is currently needed because I could not be really sure to catch when the page (loaded in an iframe) is fully loaded (images for instance) and therefore I needed the button in case the width is not set automatically. This might not be needed in the future if I can make it work well without it and if we can resize the iframe with the fingers which I could not yet make work. However let's keep the search button as having search in this toolbar is good. So you should make a button that means "fit to screen". We could put that button somewhere else (in the top bar when the page is an HTML page) 2/ The status icon had two states to show if there is activity on the network. It's important to have this. I could not find a better thing then having status + loading activity in the same place. If you have a better proposal shoot. In the mean time we need the 2 icons because knowing if there is still loading activity is important. Note that loading activity is fully transversal and not linked to the current page. We could also have information about wether the status of loading of the current page but it might be too much (there are four states: in the queue - plus place in the queue / which queue it is in, low or high priority - , loading, finished with success, finished with error). The page won't get out of the queue if you leave the page to go to another screen (however long term this could move your request in the low priority queue) Next I will work on: - xem support - managing the settings - search - app within minutes content If there are volunteers to participate, you are welcome. Now that the code is public, we could have multi-developer collaboration. Ludovic 2013/4/4 Ecaterina Moraru (Valica) <valicac(a)gmail.com> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/MobileAppV2Improve… wrote: to XWiki -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs