You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2012/05/15 11:23:51 UTC
[Bug 119355] New: Making Page Breaks more visible and easy to modify
https://issues.apache.org/ooo/show_bug.cgi?id=119355
Priority: P3
Bug ID: 119355
Assignee: ooo-issues@incubator.apache.org
Summary: Making Page Breaks more visible and easy to modify
Severity: enhancement
Issue Type: DEFECT
Classification: Application
OS: All
Reporter: rgb-es@apache.org
Hardware: PC
Status: CONFIRMED
Version: AOO340
Component: ui
Product: word processor
Created attachment 77545
--> https://issues.apache.org/ooo/attachment.cgi?id=77545&action=edit
Displaying page break more clearly and making them "interactive"
Writer shows page breaks (PB) with a line on top of next page's text area. LyX
shows manual 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:
PB are not about breaking pages, PB are about breaking *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. But the problem is only on the way on which PB are
*displayed* because "on the background" 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 how PB work on Writer.
Changing the way on which PB are displayed gives also the opportunity to make
them more "interactive" by giving to the user simple and "in place" tools to
modify them.
See attachment for a simply mock-up and detailed explanation.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 119355] Making Page Breaks more visible and easy to modify
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=119355
--- Comment #3 from rgb <rg...@apache.org> ---
> So on odt files paragraph breaks are always managed by paragraph styles.
Typo: on odt files *page* breaks are always managed by paragraph styles.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 119355] Making Page Breaks more visible and easy to modify
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=119355
bjdujing@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bjdujing@gmail.com
--- Comment #4 from bjdujing@gmail.com ---
No defect.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 119355] Making Page Breaks more visible and easy to modify
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=119355
rgb <rg...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Issue Type|DEFECT |ENHANCEMENT
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 119355] Making Page Breaks more visible and easy to modify
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=119355
--- Comment #2 from rgb <rg...@apache.org> ---
(In reply to comment #1)
> Idea is nice, but we would need to:
>
> - Avoid using "PB" or any other text in the labels, we don't do it anywhere
> in the interface. A small handle will be enough.
Agree. Maybe an icon?
> - Have a look at the ODF specification and understand if a Page Break is a
> standalone element or an attribute of paragraphs and text objects, and in
> that case handle it properly.
Lurking on "content.xml" file inside an odt file, I found that manual page
breaks are defined through automatically generated paragraph styles. For
example, if you insert a manual page break with Ctrl-Enter, at the document
"preamble" you'll have
<office:automatic-styles><style:style style:name="P1" style:family="paragraph"
style:parent-style-name="Text_20_body"><style:paragraph-properties
fo:break-before="page"/>
i.e., a declaration for a style automatically generated, not visible on the
Stylist and based on the text body style. This automatically generated style is
used to insert the page break: the first paragraph on the new page after the
manual break will be labelled as
<text:p text:style-name="P1">Paragraph text</text:p>
On paragraph styles with automatic page breaks (for example, headings that
always starts on a new page), these are declared on the style definition inside
styles.xml file, with something like this
<style:style style:name="Heading_20_1" style:display-name="Heading 1"
style:family="paragraph" style:parent-style-name="Heading"
style:next-style-name="Text_20_body" style:default-outline-level="1"
style:class="text" style:master-page-name=""><style:paragraph-properties
style:page-number="auto" fo:break-before="page"/><style:text-properties
fo:font-size="115%" fo:font-weight="bold" style:font-size-asian="115%"
style:font-weight-asian="
bold" style:font-size-complex="115%"
style:font-weight-complex="bold"/></style:style>
So on odt files paragraph breaks are always managed by paragraph styles.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 119355] Making Page Breaks more visible and easy to modify
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=119355
Oliver-Rainer Wittmann (orw at apache dot org) <or...@googlemail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|enhancement |normal
--- Comment #6 from Oliver-Rainer Wittmann (orw at apache dot org) <or...@googlemail.com> ---
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 119355] Making Page Breaks more visible and easy to modify
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=119355
Andrea Pescetti <pe...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pescetti@apache.org
--- Comment #1 from Andrea Pescetti <pe...@apache.org> ---
Idea is nice, but we would need to:
- Avoid using "PB" or any other text in the labels, we don't do it anywhere in
the interface. A small handle will be enough.
- Have a look at the ODF specification and understand if a Page Break is a
standalone element or an attribute of paragraphs and text objects, and in that
case handle it properly.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 119355] Making Page Breaks more visible and easy to modify
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=119355
--- Comment #5 from Marcus <ma...@apache.org> ---
@bjdujing:
Maybe you haven't seen it. This issue is not flagged as bug but as enhancement.
Of course there is nothing to reproduce.
--
You are receiving this mail because:
You are the assignee for the bug.