On 2012.04.17 14:55, Ludovic Rousseau wrote: > I also do not like to have web pages with the source code.
What's your proposal then? Be mindful that the web page is likely to require an update when a new release is produced, so that the download links are update, and is uploaded to the same place as doxygen, which we already automate the update and upload on a new release. Keeping 2 files (index.html + style.css) in a separate git repo, and having to somehow link it with our current repo for release automation doesn't seem like the best option to me, and I think having an offline index.html that duplicates the content of our main page in the doc may be helpful. But I'd like to hear alternative proposals from people who don't see it that way (and preferably something that can easily be automated for maintenance) > The patch is simple. Just remove the "width:700px;" in the CSS file. I'd like to have an upper limit (ie 700px or 800px max, resize for less) as paragraphs that extend the whole width don't look that good on a widescreen (not as easy to read => not so good first impression). If the choice is between widescreen and mobile users, then, with the majority of our users expected to browse the page on WXGA+, WSXGA+ or higher (high res and widescreen are popular with developers AFAIK), I'd try to make it better looking for those users before the mobile ones. But hopefully we can figure out a way to set a max while having a resize for lower res. 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
