From owner-freebsd-doc@FreeBSD.ORG Sat Jan 25 03:54:24 2014 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 323F1523; Sat, 25 Jan 2014 03:54:24 +0000 (UTC) Received: from relay.mailchannels.net (si-004-i103.relay.mailchannels.net [198.20.121.20]) by mx1.freebsd.org (Postfix) with ESMTP id 1235A18B3; Sat, 25 Jan 2014 03:54:21 +0000 (UTC) X-Sender-Id: _forwarded-from|111.125.78.19 Received: from mail-24.name-services.com (ip-10-244-196-74.us-west-2.compute.internal [10.244.196.74]) by relay.mailchannels.net (Postfix) with ESMTPA id 7734460C25; Sat, 25 Jan 2014 03:54:11 +0000 (UTC) X-Sender-Id: _forwarded-from|111.125.78.19 Received: from mail-24.name-services.com (mail-24.name-services.com [10.246.16.22]) (using TLSv1 with cipher AES128-SHA) by 0.0.0.0:2500 (trex/5.0.19); Sat, 25 Jan 2014 03:54:12 GMT X-MC-Relay: Forwarding X-MailChannels-SenderId: _forwarded-from%7C111.125.78.19 X-MailChannels-Auth-Id: demandmedia Received: from [192.168.111.121] (UnknownHost [111.125.78.19]) by mail-24.name-services.com with SMTP; Fri, 24 Jan 2014 19:54:05 -0800 Message-ID: <52E3354A.1000904@a1poweruser.com> Date: Sat, 25 Jan 2014 11:53:46 +0800 From: Fbsd8 User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Thomas Hoffmann Subject: Re: docs/144515: [handbook] Expand handbook Table of contents References: <201401221442.s0MEgd2o082802@freefall.freebsd.org> <52E075F7.7020105@a1poweruser.com> <20140123020029.GE52955@glenbarber.us> <52E1053A.8000608@a1poweruser.com> <834FD10A-0519-42F1-B804-DCE7428A863F@FreeBSD.org> <52E13ACC.2020005@FreeBSD.org> <52E140D1.5090809@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-doc@FreeBSD.org, Gabor Kovesdan X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 03:54:24 -0000 Thomas Hoffmann wrote: > On Thu, Jan 23, 2014 at 11:18 AM, Gabor Kovesdan > wrote: > > On 2014.01.23. 16 :59, Thomas Hoffmann wrote: > > I agree, the TOC is already too long vertically. Adding > subsections would exacerbate the problem. > > By "horizontal page" I mean taking advantage of the full screen > width, for example, by using multi-columns or similar technique. > That would get more info on each screen page. Compare the TOC > with the x-config.html page ( > http://www.freebsd.org/doc/en___US.ISO8859-1/books/handbook/x-__config.html > ), > which uses the full page width. > > The problem with this is that TOC is a multiple level enumeration by > nature, which is conventionally listed vertically in order. Using > two columns may be confusing for people since it is not > conventional. And if we use 2 columns, what order would it follow? > Like this: > > 1 2 > 1.1 2.1 > 1.2 2.2 > 1.3 2.3 > > Or this: > > 1 > 1.1 1.2 > 1.3 1.4 > > And what to do on smaller screens if the two columns do not fit? > > I believe that a collapsible tree list would be the best option but > that requires JavaScript, which we prefer to avoid... > > Gabor > > > Top to bottom, left to right would be the normal "western" approach, no? > > Personally, I would have no problem with a TOC that only listed the > major chapters. If you want the details sections/subsections) you would > drill (click) down as required: > 1. 6. > 2. 7. > 3 8. > 4. 9. > 5. 10. > > or even > > 1. > 2. > 3. > 4. > 5. > 6. > etc. > > It would require less scrolling, but this might be objectionable to many. > > I understand completely your desire to avoid JS. > > This may simply be an intractable problem. > > -Tom Since the handbook is published using a new tool set, just how does this new tool set auto build the TOC? If I remember correctly there was some posts a while back about forcing the publish tool to not build a complete TOC, ie: dropping the subsections. Maybe the simple solution is to allow the new tool set to build a complete TOC automatically.