<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/114283/">http://git.reviewboard.kde.org/r/114283/</a>
</td>
</tr>
</table>
<br />
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I really like the idea. I think we should keep our Scroll* components in to ease porting, but move away from using it for our own stuff first, and then, before a first API promise, revisit if we can remove our own implementation (which I really hope we'll be able to).
I'd also like to read Marco's opinion on this.</pre>
<br />
<p>- Sebastian Kügler</p>
<br />
<p>On December 3rd, 2013, 7:09 p.m. UTC, David Edmundson 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 Plasma.</div>
<div>By David Edmundson.</div>
<p style="color: grey;"><i>Updated Dec. 3, 2013, 7:09 p.m.</i></p>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt;">Repository: </b>
plasma-framework
</div>
<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;">Use QtQuickControls ScrollView internally
Flickable has a very odd API in which contentHeight can't be trusted. we need to update our ScrollBars/ScrollArea to make use of the new
originX and originY in order to fix a lot of bugs that we currently see with scrollbars.
Instead of doing that, by porting to use QtQuick Controls we get all
these bug fixes as well as _significantly_ reducing our code.
Having a separate logic vs UI, makes things (IMHO) easier to read.
I don't expect to merge this as-is; I haven't included the plasma
feature that creates a SectionScroller if the content is a listview, but
that should be viable. As far as I know all other features (keyboard
controls / hiding buttons on touch screens) are still kept.
Files removed are as indication as to long term changes from making this
change, in order to do that we need to port all users from ScrollBars ->
ScrollArea. (which is worth doing anyway IMHO)
</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;">Widget Explorer in plasma-shell looks exactly as before.</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>src/declarativeimports/plasmacomponents/qml/ScrollBar.qml <span style="color: grey">(93d7baf)</span></li>
<li>src/declarativeimports/plasmacomponents/qml/private/ScrollBarDelegate.qml <span style="color: grey">(6b5edf0)</span></li>
<li>src/declarativeimports/plasmaextracomponents/qml/ScrollArea.qml <span style="color: grey">(20cd943)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/114283/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>