Hi Kevin We have a set of people working on the new manual. However the majority of contributors were not happy working with Tex, so we have moved to sections in Google Docs. The plan though, is just to edit the text there, we will likely move the content generated there to another medium to generate the proper page numbers, sections etc.
If you would like to help, just send me your google ID and I can add you. Scott On 17/02/2011, at 1:38 PM, Kevin Ford wrote: > > OK, this works. The manual needs to say this without too much hunting > around (searching for the word "zoom" wasn't useful). Specifically, in > Sec 2.8 it's written U: Equal to pressing the hardware button ”Up”, which > is not informative. Quite bit a searching to find in Sec. 2.1 what > hardware buttom "up" does. This needs to be added to Sec. 2.8. BTW, I'm > fluent in TeX; I could help with the manual. Who's in charge? > > Kevin Ford > > > On Wed, February 16, 2011 9:38 am, Max Kellermann wrote: >> On 2011/02/16 15:09, Kevin Ford <[email protected]> wrote: >>> I'd really like to have dedicated buttoms on the screen for this (that >>> can >>> be turned on/off according to pilot's taste). Something small but >>> visible, say lower right portion of the screen. >> >> Enable gestures, and swipe up/down for zooming. >> > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Xcsoar-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xcsoar-user ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Xcsoar-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcsoar-user
