https://bugs.documentfoundation.org/show_bug.cgi?id=143987
V Stuart Foote changed:
What|Removed |Added
See Also||https://bugs.documentfounda
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #19 from Mike Kaganski ---
(In reply to David from comment #18)
> if a pane would have the ability to be undocked from the sidebar then it
> wouldn't show as part of the sidebar until it was re-docked back into it?
Exactly;
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #18 from David ---
(In reply to Mike Kaganski from comment #16)
> (In reply to David from comment #15)
>
> > exception *for the transitional period*, until the proper undocking will be
> implemented for sidebar panels - see
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #17 from David ---
(In reply to Mike Kaganski from comment #16)
> (In reply to David from comment #15)
> "How the navigator pane already functions" is not something that we can try
> to reproduce in new UI elements, because
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #16 from Mike Kaganski ---
(In reply to David from comment #15)
IUUC, your comments then meant a vote for WONTFIX for the proposal here, based
on existing solution for the stated problem that the proposal intended to
solve.
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #15 from David ---
(In reply to Mike Kaganski from comment #14)
> (In reply to David from comment #13)
>
> Hmm, I'm sorry how comments 11-13 relate to the problem discussed here, and
> wonder why have they appeared here: I
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #14 from Mike Kaganski ---
(In reply to David from comment #13)
Hmm, I'm sorry how comments 11-13 relate to the problem discussed here, and
wonder why have they appeared here: I presume, they intend to help decide on
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #13 from David ---
(In reply to Mike Kaganski from comment #12)
> (In reply to David from comment #11)
> > That's what makes the Styles Formatting Toolbar such a powerful resource for
> > accessing core styles.
>
> What's
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #12 from Mike Kaganski ---
(In reply to David from comment #11)
> That's what makes the Styles Formatting Toolbar such a powerful resource for
> accessing core styles.
What's what makes the Styles Formatting Toolbar such a
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #11 from David ---
(In reply to Mike Kaganski from comment #10)
> Indeed. Note however, that this would be less than the original idea here -
> to have two style categories open at once.
That's what makes the Styles
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #10 from Mike Kaganski ---
(In reply to David from comment #9)
> Which also takes up additional space.
Indeed. Note however, that this would be less than the original idea here - to
have two style categories open at once.
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #9 from David ---
(In reply to Mike Kaganski from comment #8)
> If you have the expanded list auto-sized to fill the available height (minus
> the height of 4 other categories), then only a single click is needed.
Which also
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #8 from Mike Kaganski ---
If you have the expanded list auto-sized to fill the available height (minus
the height of 4 other categories), then only a single click is needed.
--
You are receiving this mail because:
You are
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #7 from David ---
(In reply to Mike Kaganski from comment #5)
> would make everything accessible, discoverable, and most useful information
> available on one dashboard.
If there is a long list of styles, this requires one
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #6 from Heiko Tietze ---
Don't forget the table style. I struggle with the implicit need to show page
and frame styles while editing text. That's why my take on it was to merge the
_text related_ styles into one view.
--
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #5 from Mike Kaganski ---
I think that a sidebar with *all* style families implemented as
default-collapsed panels with collapsed titles showing the current style name
(so sidebar looking like a stack of "comboboxes" giving
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
--- Comment #4 from David ---
A better solution IMO would be to use a customizable styles toolbar for the
most frequently used styles. Combining style families into one sidebar panel
would cause way too much scrolling for large numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
Dieter changed:
What|Removed |Added
CC||rferr...@sccoast.net
--- Comment #3
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
Heiko Tietze changed:
What|Removed |Added
Depends on||144079
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
Bug 143987 depends on bug 144079, which changed state.
Bug 144079 Summary: Stylist: New Text Styles view misses interactions for CS
https://bugs.documentfoundation.org/show_bug.cgi?id=144079
What|Removed
https://bugs.documentfoundation.org/show_bug.cgi?id=143987
Heiko Tietze changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
21 matches
Mail list logo
