<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Removal of the Master Pages sidebar deck"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=110436#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Removal of the Master Pages sidebar deck"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=110436">bug 110436</a>
from <span class="vcard"><a class="email" href="mailto:philipz85@hotmail.com" title="Yousuf Philips (jay) <philipz85@hotmail.com>"> <span class="fn">Yousuf Philips (jay)</span></a>
</span></b>
<pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=110436#c4">comment #4</a>)
<span class="quote">> No, the use case remains common that the template you choose to create a new
> presentation with does not have the Slide master you want to use predefined.
>
> What then? </span >
You choose another template or you create the slide masters you want.
<span class="quote">> The Master Page deck allows you to assign the slide a master from another
> template--still quite functional and there is nothing in UI to replace that.</span >
If it cant import all the slide masters from a template, it isnt that
functional.
<span class="quote">> At the least, work flow for layout of a presentation to then use as a
> template requires the deck's content pannels. Otherwise every slide master
> for a new template starts from default.</span >
Didnt follow.
(In reply to Heiko Tietze from <a href="show_bug.cgi?id=110436#c8">comment #8</a>)
<span class="quote">> While I'd always vote for cleaning up the UI, and in particular the rarely
> used sidebar decks, the master slide deck is useful. Removing it forces the
> user into the template manager (at least me don't like this workflow) and
> hinders the later modification when users start with content and apply
> formatting/style to the final document.</span >
If you dont go through the template manager, you cant import all master slides
in a template, so the template manager is the only workflow that provides this
functionality. Didnt follow what you meant by the "hinders the later
modification...".</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>