Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 06A90C6F0 for ; Sat, 12 May 2012 20:50:44 +0000 (UTC) Received: (qmail 50240 invoked by uid 500); 12 May 2012 20:50:43 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 50147 invoked by uid 500); 12 May 2012 20:50:43 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 50139 invoked by uid 99); 12 May 2012 20:50:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 May 2012 20:50:43 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rgb.mldc@gmail.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-ob0-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 May 2012 20:50:37 +0000 Received: by obhx4 with SMTP id x4so5651476obh.6 for ; Sat, 12 May 2012 13:50:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=liQwEqEXTN9kUDEATrIsRsHLyOhNLnQzG7nLPJyDRWM=; b=QNaMV7X6J2Mwp9jgkE6DdOj3+x/wqr3mAXpPep0Nyf6RzZ0iP5DTPRX+XR601dTBeH KQgKSBCOMAvZXWYqWlpmmkcRoLaNDUjFZ9hzTxrJwIVpBK18CiVcUckayUCsvqsaJORu vRTo9b8653WTSxbrwZqXf2GXUiTYqUb2VaqHRKEM8W3vtaXiQQEqBesPpNeeQ5RHnxWW I51A8N79xmXHmn5LySmRR7tUkidEsJ0WJ7OAzP4kaDkR+mV7tkW+/vHHWymtiubI/NBn 8Y8+L3d+jr2hirpuQrOk4GD602GqMZmQYxBZcvC1ah8Xcf7INyZScb2EHvlTCAEkKbCJ Xcbg== MIME-Version: 1.0 Received: by 10.50.140.99 with SMTP id rf3mr1395563igb.25.1336855816177; Sat, 12 May 2012 13:50:16 -0700 (PDT) Received: by 10.50.209.106 with HTTP; Sat, 12 May 2012 13:50:16 -0700 (PDT) In-Reply-To: <4FAEB656.2050705@laposte.net> References: <4FAEB656.2050705@laposte.net> Date: Sat, 12 May 2012 22:50:16 +0200 Message-ID: Subject: Re: [4.0 brainstorming] Making Page Breaks more visible From: RGB ES To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 2012/5/12 Hagar Delest : > +1. > Seems very logical indeed. > The "Page break" label should be visible somewhere in line with the PB > location. Do you mean it should be in the margin? Not necessarily: I put it to the left mainly to avoid clash with notes (they are always to the right), but moving the label near to the text area for a more compact design is a good idea. > A hot spot that opens the attributes by double-click would improve th use= r > experience to change page numbers, page styles, ... Indeed!! Ricardo > Hagar > > Le sam. 12 mai 2012 16:40:27 CEST, RGB ES a =E9crit = : > > >> I would like to ask you for feedback on this idea, to know if you >> think it is good or bad and why, and finally if you think it is >> feasible. >> >> Writer shows page breaks (PB) with a line on top of next page's text >> area. LyX shows PB with a line crossing the page on the insertion >> point with the text "Page break" on the middle of it. These different >> approaches can be more or less useful, but both are conceptually >> wrong: >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0PB are not about breaking pages, but about br= eaking *text >> flow* and sending content to the next page. >> >> So PB should be an attribute of the object (a paragraph, a table) that >> actually breaks content flow. Writer already work that way: on the >> paragraph format (both direct and style) or table properties we have a >> "text flow" tab that allows us to define breaks, either before or >> after the object, either with or without page style change. >> >> Considering all this, I believe PB should be shown on the same object >> that creates the break, and on the object side where break occurs: >> this way, PB display will be consistent with the way PB works on >> Writer. >> >> See here for a lousy mock-up: >> >> http://people.apache.org/~rgb-es/PageBreaks3.png >> >> What do you think? >> >> Regards >> Ricardo >> >