<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 solid;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="http://git.reviewboard.kde.org/r/112909/">http://git.reviewboard.kde.org/r/112909/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On September 24th, 2013, 1:27 p.m. UTC, <b>John Layt</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Agree to merge this as is, it removes the stuff that would be duplicated in the Qt dialog. As for longer-term, I don't see any of those features being much used or of much use at all. If I'm wrong and people start complaining and can make a reasonable case, then I'll accept them being added into the Qt dialog. If any feature will be missed, it would be the Advanced option of directly entering CUPS options. I suspect there are some power users out there using that to get around some of Qt's short-comings, like advanced page ranges "3,7-9,15". However the usability is terrible and just shouldn't be done that way. If people make a case for it, then we can look at a better ui for it in Qt, e.g. one that has them choosing from a combo of valid values. That leaves the convenience api for server-side/client-side page selection, which for a one-line code saving is really not worth it. The only other reason I can think of for keeping the api is if we ever want to re-add a universal KDE tab to the dialog, for example for Color Management. I had a cunning plan for that about a year ago, I need to go dig it up and see what actually needs doing and if I can get away with putting it into Qt instead. If we don't need it for that, then I say get rid of it entirely: we don't know what any future needs might be, so we have no guarantee that the current api will work for that, so lets not lock outselves into something until we actually need to.
Oh, and I need to look at the rationale behind KPrintPreview to see if we really need it still.</pre>
</blockquote>
</blockquote>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Ok, let me know if I can help with anything around this.</pre>
<br />
<p>- Martin</p>
<br />
<p>On September 23rd, 2013, 6:47 p.m. UTC, Martin Klapetek wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('http://git.reviewboard.kde.org/static/rb/images/review_request_box_top_bg.ab6f3b1072c9.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for KDE Frameworks and John Layt.</div>
<div>By Martin Klapetek.</div>
<p style="color: grey;"><i>Updated Sept. 23, 2013, 6:47 p.m.</i></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Most of the printing features are now part of Qt 5.2 and basically only 4 features are left:
- Page Label
- Page Border
- Mirror Pages
- (Advanced) Job Options
- Server-side paging
I've dropped Job Options as it was quite terrible way to edit/pass CUPS options directly. Server-side paging is actually just a convenient feature as with QPrintDialog, apps that can't do paging themselves need 2 lines of code to set the printing dialog up, thanks to KDEPrintDialog only one line is needed. The rest I've put under Page Options tab in the print dialog. To be honest I don't think they are that useful (or used, even) but we have the code and CUPS support already. If these options were to be dropped however, I'd drop the whole KDE Print support then as it would become just a convenient wrapper around QPrintDialog.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Testing </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Tested with Konsole5.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>staging/kde4attic/src/CMakeLists.txt <span style="color: grey">(4acf1b6)</span></li>
<li>staging/kde4attic/src/kcupsoptionsjobwidget.ui <span style="color: grey">(182b23e)</span></li>
<li>staging/kde4attic/src/kcupsoptionsjobwidget_p.cpp <span style="color: grey">(3c7913d)</span></li>
<li>staging/kde4attic/src/kcupsoptionspageswidget.ui <span style="color: grey">(a68865d)</span></li>
<li>staging/kde4attic/src/kcupsoptionspageswidget_p.h <span style="color: grey">(ede67e6)</span></li>
<li>staging/kde4attic/src/kcupsoptionspageswidget_p.cpp <span style="color: grey">(79c6834)</span></li>
<li>staging/kde4attic/src/kcupsoptionssettingswidget_p.cpp <span style="color: grey">(7b58a37)</span></li>
<li>staging/kde4attic/src/kdeprintdialog.cpp <span style="color: grey">(4722f4c)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/112909/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>