On 2012.04.18 13:10, Ludovic Rousseau wrote: > Le 18 avril 2012 12:40, Pete Batard<p...@akeo.ie> a écrit : >> On 2012.04.18 08:37, Ludovic Rousseau wrote: >>> I want something that adapt to the browser (not the screen) the USER >>> wants to use. >> >> No. You want something that looks better on small sized browser windows >> (which I agree needs to be improved), but, if we go with your proposal, >> that will also make it less readable on large sized browser windows. > > You know better than me what I want.
I can apply the same. You seem to know better than me than what I wanted when I designed the page, the sole motivation of which was to make a good first impression, and that, contrary to what I went some length to do (by setting an explicit width in the CSS), I actually didn't really want text that extended roughly the same width as the menu or have nicely formatted paragraphs in a way similar to what you would find in a book, even as I see it as both more aesthetically pleasing and more readable, but instead text that extended the whole width of the browser. Well, to restate my one and only goal here: I created the content with the following specific intent: make the best possible first impression. This includes, but is not limited to making it load fast. We did hear your view with regards to considering that a fast wiki would be good enough to achieve that goal, which is also consistent with your proposal, as it makes the portal page resemble a wiki, but I do disagree with speed being the only matter, and that was the reason why spent some time trying to come with something better. To me, beside speed, making a good first impression very much includes making the content look appealing to as many users as possible, including, but not limited to, mobile ones. Now, you did point out that the content doesn't look good on small browsers, which I agree is an issue that needs to be addressed, but your proposal to do just that is to make it look worse on large browsers, which would result in small browsers only being able to meet the original goal of making a good first impression. Also, you may want to consider that the menu will never resize (unless we want to make text smaller or something), so, as long a menu is in use, mobile user who want to access the Development items will always have to scroll to use it. In that case, if we want to focus on mobile users, I guess we should redesign the whole page. But basically, you are arguing that everybody should go with your sense of aesthetics, when it comes to text display, and that anybody who dares disagree is wrong, regardless of whether they were the ones who specifically created the "artistic" content, with an explicit intent of going with a different sense of aesthetics from what is pleasing to you (of what you deem acceptable). > I can't win. When it comes to aesthetics, indeed you can't. You can't go around expect people who have a different artistic sense to rally to your preferred style, unless you try to argue why you think your preference (text that goes the full width always) is expected to be more appealing to users at large. My belief (which is the reason I bother) is that the majority of our users is expected to disagree with your views when it comes to text spread and readability and thus I can only respectfully disagree that we should go with your proposal if it isn't amended to address the issue of continuing trying to make the best first impression possible for non-mobile users. Regards /Pete ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
