On 10/15/2009 11:22 AM, Marius Dumitru Florea wrote: > Ecaterina Valica wrote: >> I think the usages of a such menu entry are to low. They maybe just >> agglomerate the menu. >> >> An autodetect based on the user agent would be IMO more practical and would >> serve its purpose.
User agent is never reliable. If we do it on the serverside, it can be turned off, manually set to a different value, and cache frontends will send the same content regardless of the user agent, unless properly configured. If we do it on the client, then there's no way to force a different layout. >> I think it's bad If I'm in "mobile" mode and I have to search 5 minute for >> the menu with "mobile" entry just to swithc my view. It should be >> autodetect. Yes, it is (will be) autodetect, this is what the media attribute does. >> And if it's autodetect ... then why have a "unpractical" menu entry? Because there are other uses for this. The layout is different, so maybe someone would prefer a desktop layout even on his PDA, or someone has a phone with a large screen which can properly display panels. Or maybe I want to see the print mode without pressing the browser's print preview button. > > I share the same opinion. I see this display mode more like a preference > in the user profile or a URL parameter (auto detect + a way to force it > if needed). > User preferences are common between different devices, so I'd have to switch the view mode anytime I switch from my Android to my workstation and back. Still, this is an open discussion, if more users/devs think that this menu is not needed, and autodetect is enough, then that's good enough for me. > >> >> On Wed, Oct 14, 2009 at 21:16, Thomas >> Mortagne<[email protected]>wrote: >> >>> On Wed, Oct 14, 2009 at 17:38, Sergiu Dumitriu<[email protected]> wrote: >>>> On Wed, Oct 14, 2009 at 17:24, Guillaume Lerouge<[email protected]> >>> wrote: >>>>> Hi Sergiu, >>>>> >>>>> On Wed, Oct 14, 2009 at 5:15 PM, Sergiu Dumitriu<[email protected]> >>> wrote: >>>>>> Hi Devs, >>>>>> >>>>>> Inspired by the newly launched W3C website, I'd like to introduce the >>>>>> possibility to choose the display mode: desktop (the current UI), >>>>>> print (the current print preview UI) and mobile (a 1-column, >>>>>> margin-free layout). I'd like to group these options in a new action >>>>>> menu entry, named DISPLAY (or VIEW) and placed between EDIT and EXPORT >>>>>> (I can't find a good position, suggestions welcome). In the same menu >>>>>> we can reintroduce the View Wiki Source feature ( >>>>>> http://jira.xwiki.org/jira/browse/XSCOLIBRI-122 ). >>>>>> >>>>>> So basically, the menu changes are: >>>>>> - new DISPLAY menu, with the options: Desktop, Mobile, Print, Wiki >>> Source >>>>>> - the chosen display mode (except wiki source) is sticky, meaning that >>>>>> it will continue to be used for the following page views >>>>>> - Print Preview disappears from ACTIONS >>>>>> >>>>> To me, view code is not a display action: "view code" should look >>> different >>>>> in desktop, mobile and print view. I'd rather have "view code" in the >>>>> "Actions" menu. >>>> On one hand, this behaves differently than the other 3 entries in the >>>> Display menu. >>>> >>>> On the other hand, this is not something you DO with the document >>>> (like rename or delete), but a different way of displaying it, thus I >>>> strongly think it doesn't belong to the Actions menu, and I moderately >>>> believe that it belongs in the Display menu. >>> +1, it has nothing to do in Actions menu, it's not an action. >>> >>>>> About the Display option, I think that would be great. Do you also plan >>> on >>>>> adding an autodetect based on the user agent? >>>> Kind of, stylesheets already have a "media" attribute that specifies >>>> for which type of device it should be used. The display menu will just >>>> "force" one of the stylesheets to be used, regardless of the current >>>> media, something like: >>>> >>>> <link rel="stylesheet" media="all or print" >>>> >>>>> Another question: should it be called "Display" or "View" ? "View" >>> sounds >>>>> maybe a bit more intuitive than "Display" but I don't have a strong pow >>> on >>>>> this. >>>> I don't know either, but I'm slightly inclined towards "Display". >>> I prefer "Display" too it sound maybe too technical for basic user. >>> >>>>> I'm +1 about a "Display" or "View" menu entry with Desktop, Mobile and >>>>> Print. >>>>> >>>>> Only potential issue is that it might make the top menu look a bit >>> crowded. >>>>> >>>>>> Any objections/comments? >>>>>> >>>>> See my remarks above. Great idea overall. >>>>> >>>>> Guillaume -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
