<table><tr><td style="">ngraham added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D15011">View Revision</a></tr></table><br /><div><div><p>Thanks for the kind words. I don't think the objections have been ignored, though:</p>
<p>Objection:</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>but my question is: is it possible to somehow make a toggle to keep the status quo ie. have no search box? [...] I urge you again to please consider leaving an option to have it the same as it is.</p></blockquote>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>I'm -1 for this, it's not needed to click in just start typing witch is more intuitive. Adding this optional by config?</p></blockquote>
<p>Response:</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>Sorry, it almost never makes sense to have user-facing options for this kind of very specific thing. I know that change can be a bit scary at times, but design evolves, and we have a theming system for people who don't like the defaults.</p></blockquote>
<p>Objection:</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>Also please note that the clear button functionality is working wrong with RTL layouts.</p></blockquote>
<p>[Irrelevant to this patch; it's an issue with the TextField itself that should be fixed there.]</p>
<p>Objection:</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>Heh, flip-flopped back to <a href="https://userbase.kde.org/images.userbase/thumb/f/fe/Kickoff_Menu_Style.png/300px-Kickoff_Menu_Style.png" class="remarkup-link" target="_blank" rel="noreferrer">https://userbase.kde.org/images.userbase/thumb/f/fe/Kickoff_Menu_Style.png/300px-Kickoff_Menu_Style.png</a> till we get the next bug report about how it should be hidden.</p></blockquote>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>The original issue (in Neon/Kubuntu task, not sure) was that Kickoff is not clear if one can search or not, because of text changing. Why not just keeping the current “Type to search” label as is, and move the user@host text up as in the patch?</p></blockquote>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>There is nothing cold, stark or undifferentiated about Kickoff and its search bar now. [...] And slapping on a white opaque box with bright blue outer glow just like it was in KDE 4 doesn't seem like preserving minimalism either.</p></blockquote>
<p>Response:</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>[...] I see this as the natural next step in refining what "minimalism" means to KDE, which is a microcosm of a larger trend throughout the design world vis-a-vis minimalism:</p></blockquote>
<p>More generally, one of the reasons why we have a <a href="http://hig.kde.org/" class="remarkup-link" target="_blank" rel="noreferrer">HIG</a> is so that we can all agree to abide by a series of common rules rather than having to re-argue the same subjective aesthetic matters over and over again. And on this subject, <a href="https://hig.kde.org/style/theme.html#application-specific-theme" class="remarkup-link" target="_blank" rel="noreferrer">the HIG says</a>:</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>Application specific theme</p>
<div class="remarkup-code-block" style="margin: 12px 0;" data-code-lang="text" data-sigil="remarkup-code-block"><pre class="remarkup-code" style="font: 11px/15px "Menlo", "Consolas", "Monaco", monospace; padding: 12px; margin: 0; background: rgba(71, 87, 120, 0.08);">Only set a custom color scheme, never set a custom widget theme.</pre></div></blockquote>
<p>Kickoff isn't an application, but the message is clear: abide by the appearance specified by the global widget theme, and don't apply custom styles to common controls. But that's exactly what Kickoff is doing, in violation of this recommendation.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R119 Plasma Desktop</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D15011">https://phabricator.kde.org/D15011</a></div></div><br /><div><strong>To: </strong>ngraham, Plasma, VDG, davidedmundson, abetts<br /><strong>Cc: </strong>broulik, safaalfulaij, oysteins, anthonyfieroni, filipf, abetts, davidedmundson, michaeltunnell, plasma-devel, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, sebas, apol, mart<br /></div>