Hi, Also check out: http://platform.xwiki.org/xwiki/bin/view/Features/Skins http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Skins http://platform.xwiki.org/xwiki/bin/view/DevGuide/Skins Thanks, Caty On Mon, Mar 21, 2011 at 22:09, Ecaterina Moraru (Valica) < valicac(a)gmail.com&gt; wrote:

On Tue, Mar 22, 2011 at 20:19, Supreet Pal Singh &lt;supreetpal(a)gmail.com&gt;wrote;wrote: The nick is evalica. Good luck with your exams. Thanks, Caty

Hi Supreet, Great to see your interest in this project. On Wed, Mar 23, 2011 at 2:04 PM, Supreet Pal Singh &lt;supreetpal(a)gmail.com&gt; wrote: the the has functions of Couple of remarks : * It's maybe not obvious, but in my sketch the lower bar is static, so you don't have to scroll for it, it always remains at the bottom of the user screen

* As I tried to explain in my comment, I tend to think base use case of a mobile version is about searching + reading content and comment + annotations. I think edit is a marginal use case. Does not mean it should not be doable, but IMHO it should not be considered a primary action. OTOH a good and accessible search is a must have. That's why in my version the search bar is first class citizen, at the top of the page. * The search would be a dynamic one, a bit in the spirit of the search suggest available since XE 3.0 (best is to check the feature in the version in 3.0 RC1, due today) away your be Yes it's an approach that would work. Also I think the mobile skin is about dropping tons of stuff, so another approach would be to create a new skin from scratch and build it keeping only on what is essential (to have good performances).

in An idea could be you spend some time investigating how other wikis have designed there mobile version (wikimedia one is interesting, but I'm sure there are others) and refine on the design proposals Caty and I made with your own ones, what do you think ?

Jerome over with mobiles the supreetpal(a)gmail.com&gt;wroteote: mainly XWiki could _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi Supreet, Great to see your interest in this project. On Wed, Mar 23, 2011 at 2:04 PM, Supreet Pal Singh&lt;supreetpal(a)gmail.com&gt; wrote: Couple of remarks : * It's maybe not obvious, but in my sketch the lower bar is static, so you don't have to scroll for it, it always remains at the bottom of the user screen * As I tried to explain in my comment, I tend to think base use case of a mobile version is about searching + reading content and comment + annotations. I think edit is a marginal use case. Does not mean it should not be doable, but IMHO it should not be considered a primary action. OTOH a good and accessible search is a must have. That's why in my version the search bar is first class citizen, at the top of the page. * The search would be a dynamic one, a bit in the spirit of the search suggest available since XE 3.0 (best is to check the feature in the version in 3.0 RC1, due today) Yes it's an approach that would work. Also I think the mobile skin is about dropping tons of stuff, so another approach would be to create a new skin from scratch and build it keeping only on what is essential (to have good performances).

An idea could be you spend some time investigating how other wikis have designed there mobile version (wikimedia one is interesting, but I'm sure there are others) and refine on the design proposals Caty and I made with your own ones, what do you think ?

On Thu, Mar 24, 2011 at 8:35 AM, Sergiu Dumitriu &lt;sergiu(a)xwiki.com&gt; wrote: supreetpal(a)gmail.com&gt; lack menu Jerome's on are functions layer the done would the Hey, that was a very nice article :) Hopefully we ll also be able to optimise XWiki very effectively for mobile devices. Also, I need some help as to how I can about start writing the project code to develop the skin from scratch. more After giving it quite some thought here's my take on the Mobile Skin proposals: # I believe that keeping a static bar of functions/tabs on top would be more convenient than the one at bottom due to the fact that it would lead to a lot of clutter and presence of a lot of active buttons in a small amount of space. Here ( http://www.x.supreetpalsingh.com ) ,If we have a look at the image on the right where I have tried to demonstrate as to how the edit page would look on the skin suggested by Jerome with functions at the bottom of the page, we can clearly see that the bottom of the page is filled with a lot of active links/buttons making it less user friendly and inconvenient to use. ( Inconvenience may not be obvious but the clutter can easily be observed ) # Also two static bars (Search<top> and Functions<bottom>) will not be very useful as it would consume a lot of space and leave relatively less space for the main content of the page which can be displayed without scrolling. # The design proposal by Caty is according to me better but there can be a few changes to improve user experience. For Example , on the same link above if we observe the image on the left I have done away with big XWiki logo which was present earlier with the tabs instead inserted a thin horizontal title bar above them. This leads to two things: 1. Increased space per tab which is very useful since we are targeting a 'touchscreen' audience and the larger the tab the more user friendly it is . 2. If we decide to maintain the previous the size of the tabs we get room to accommodate one more tab/ function.

What do you think? '- -- Thanx, Supreet _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi Supreet Great to see you took the time to work on this. My remarks below On Fri, Mar 25, 2011 at 8:51 PM, Supreet Pal Singh &lt;supreetpal(a)gmail.com&gt; wrote: wrote: supreetpal(a)gmail.com&gt; lack menu Jerome's on are the version functions layer the done would the http://www.stevesouders.com/blog/2011/03/14/mobile-comparison-of-top-11/ help more more of image would of use. ( You are mixing stuff here. My proposal is about a "view page" mode. So the bottom bar is all you get, there is no such "save", "info" add pictures etc. in the proposal I make. I think it's important at this point to well differentiate the "view" and "edit" UIs. In my view, the edit UI should be modal, just as it is on the "desktop skin". This translate by no other button than "preview", "save" and "cancel". Yes, the rest disappear, no search bar, no lower toolbar with "delete" or "infos" buttons (those are actions related to the page and accessible when in "view" mode). Add picture could stay, but that's different, that's a component of the edit UI (same as we have "insert image" when editing a page with the WYSIWYG). So there is no such clutter at the bottom of the UI, since there is just the "toolbar" (even though I'm not a fan of this name, "action bar" is probably better) in view mode ; and the "buttons bar" ("save", "view", "cancel") in edit mode. Oh yes, I was mixing up because I thought the "action bar" was static

# Also two static bars (Search<top> and Functions<bottom>) will not be very scrolling. For me the search bar should not be static. It's at the top so that it's easily accessible when you first display a page, since it's something you often want to reach for immediately (scenario : I open my wiki, I search for a page, I read it, I comment it, etc.). But when you start reading the page, it's not so important to have it available on the screen.

a I tabs two is . to The action bar buttons don't have to be big. They need to be big enough so that you can touch them easily even with big fingers, but that's about it. In my opinion you can 8 without problem. Jerome _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hey, I was a little confused as to how we would go about developing the backend of the mobile skin as it seemed that everyone was interested in the development being done from scratch with only the required functions and code that would be loaded. Are there any pre existing modules to link the server and database with the newly developed skin or are we just going to develop a restricted UI/skin for mobile web-browsers with no changes on the backend? On Tue, Mar 29, 2011 at 2:06 AM, Supreet Pal Singh &lt;supreetpal(a)gmail.com > > > On Mon, Mar 28, 2011 at 7:57 PM, Jerome Velociter &lt;jerome(a)xwiki.com > >> Hi Supreet >> >> Great to see you took the time to work on this. >> >> My remarks below >> >> On Fri, Mar 25, 2011 at 8:51 PM, Supreet Pal Singh < supreetpal(a)gmail.com&gt; think: would separate less functions options for case comment primary why this build ipad http://www.stevesouders.com/blog/2011/03/14/mobile-comparison-of-top-11/ than results, skin myself but be to amount the observed there to you action left a it -- Thanx, Supreet _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs