Hi Alan, On Jul 12, 2013, at 6:36 , Alan Robertson <al...@unix.sh> wrote:
> On 07/11/2013 09:56 PM, Stefan Pendl wrote: >> Am 12.07.2013 03:50, schrieb Alan Robertson: >>> I didn't get any reply to this. This is a serious problem. >>> >>> Doxygen is generating HTML which is unusable by a significant percentage >>> of mobile devices. I only have access to one mobile device (the iPad 3) where it also makes sense to browse doxygen's output (even when the tree view is enabled). If you want support for other mobile devices, please include a fix (or send me a device) For mobile devices with low resolution/capabilities it is best to configure doxygen with these (default) settings: DISABLE_INDEX = NO GENERATE_TREEVIEW = NO HTML_DYNAMIC_SECTIONS = NO You could put the results with these settings on a separate location used for mobile devices only. >>> >>> Do I need to send this email somewhere else? >>> >> If you report it at the bugzilla site of doxygen, it is more likely to >> not get lost. > OK. What's the URL for it? https://bugzilla.gnome.org/enter_bug.cgi?product=doxygen >> >> The bug reports are published on this list too, so if someone has a >> workaround for your problem, he can answer here. >> >> Keep in mind that documentation is not created with mobiles in mind, so >> this would be a new recommendation. >> >> Because it is HTML and mobiles have a browser installed, doesn't mean it >> will work on mobiles, else there wouldn't be the need for so many sites >> to have a mobile compatibility mode. >> >> I think that PDF is suitable for mobiles, since a user of the >> application I am participating in development requested PDF for his >> mobile device. > By design, PDF is terrible for mobiles. It is absolutely awful to > navigate on any screen, and was created for a printing to paper for a > fixed page size (usually very large) in mind and is paginated for > rendering on dead trees - so it has wasted space for margins that relate > to aspects of paper that just don't exist in viewers. Browsing PDFs on an iPad works fine. It can zoom in just enough to get rid of the margins just by double tapping. Not sure how it works with Android. > > HTML is a better alternative - it is designed from the beginning to > scale to the screen size. And the HTML navigation in recent versions of > doxygen output is quite reasonable. > > My web site is quite readable on my phone - if I use the right browser > and zoom in. I suspect this of being a browser bug, but I don't know > that for sure. If it's a browser bug, it exists on the two most common > browsers for Android - which sort of argues against that... One typically needs to give some hints to the browser when using touch instead of a mouse. For iOS I added the following to the navtree.css: -webkit-overflow-scrolling : touch; Regards, Dimitri ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Doxygen-users mailing list Doxygen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/doxygen-users
