<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="12" style="border: 1px #c9c399 solid; border-radius: 6px; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="https://git.reviewboard.kde.org/r/121165/">https://git.reviewboard.kde.org/r/121165/</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;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">So the whole things seems quite OK to me, (Just some coding style issues which you can check with KDE Coding style and fix them)</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">But for the problem that posts are adding on top:
Until now, we were only adding new posts on top of older ones, but to show older posts we need to add them at the bottom, so there's a solution, In TimelineWidget.cpp line 267 you see this code:
d->mainLayout->insertWidget(d->order, widget);
Which is were posts are actually adding to UI. You need to change the value of "order" there to -1 (Which currently is using in reverse ordering mode of Choqok)
Well, you can do this by adding a protected function to TimelineWidget class which will be available from drived class such as TwitterApiSearchTimelineWidget to TEMPORARILY change the order before adding these posts, and revert it to it's previous state afterwards. (Just make sure that Choqok is working fine in reverse mode also, Config -> Appearance dialog has the option to enable reverse mode)</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">But after doing so, you'll have another problem, which you have to reverse order the list of new posts before sending them into TwitterApiSearchTimelineWidget::addNewPosts() function or inside that function. There's already a loadingAnotherPage flag there which is no longer valid with your new code, you can use that flag to know whether this is the first page of search (No need for changing orders) or older posts which needs to change both above mentioned orders.</p></pre>
<br />
<p>- Mehrdad Momeny</p>
<br />
<p>On November 17th, 2014, 11:46 p.m. UTC, Ian Schwarz wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="12" style="border: 1px #888a85 solid; border-radius: 6px; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tr>
<td>
<div>Review request for Choqok.</div>
<div>By Ian Schwarz.</div>
<p style="color: grey;"><i>Updated Nov. 17, 2014, 11:46 p.m.</i></p>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt;">Repository: </b>
choqok
</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;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">This patch does 3 things:</p>
<ol style="padding: 0;text-rendering: inherit;margin: 0 0 0 2em;line-height: inherit;white-space: normal;">
<li style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: normal;">
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">It removes the old, stale "page browsing" that has not worked for the longest time. Instead, it introduces a button to "load more tweets" which actually works and loads older tweets. However as of now, you have to click it TWICE for the first time to work. After that, every addidtional click will retrieve more old tweets. They are shown on top of the newer ones which is quite unfortunate, I don't know how to change that. (see also https://bugs.kde.org/show_bug.cgi?id=340795)</p>
</li>
<li style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: normal;">
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">It introduces a "follower list", similar to the "friends list" for Twitter, which contains only followers' screen names. The reason for that is that on Twitter, you can only send DM's to your FOLLOWERS instead of your "friends" (i.e. people you have followed). The git version "allows" you to send them to the people you have followed which results in mute failure and no error message. We do still need the old friends list though so we can know whom we have followed (and thus whether to display the "follow" or the "unfollow" option).</p>
</li>
<li style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: normal;">
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">"Show all posts by $NAME" should not use the Twitter search/tweets API, as this API will only return tweets that are less than 7 days old. Instead, use statuses/user_timeline which returns up to 3,200 tweets of any age.</p>
</li>
</ol>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Let me state that I do not expect this patch to be accepted as is or even with minor changes. What I hope instead is that people who know more about C++/Qt/Choqok look at this and go "I see what you're trying to do, but there is a better way." and then actually propose a better way. I feel I have done as much as I could to enable Choqok to make progress towards a mostly working Twitter client for Linux.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Oh, and bumping the version to 1.4.0.1 or somesuch would be good sometime in the future. Maybe this way we can get distribution/packagers to ship a more functional version of Choqok in the future. The old 1.4.0 release is horribly broken by comparison.</p></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>choqok/microblogs/twitter/twittersearch.cpp <span style="color: grey">(da85565)</span></li>
<li>choqok/microblogs/twitter/twitterpostwidget.cpp <span style="color: grey">(f8bf945)</span></li>
<li>choqok/microblogs/twitter/twittersearch.h <span style="color: grey">(662e8d7)</span></li>
<li>choqok/helperlibs/twitterapihelper/twitterapisearch.cpp <span style="color: grey">(b3078c4)</span></li>
<li>choqok/helperlibs/twitterapihelper/twitterapisearchtimelinewidget.h <span style="color: grey">(ec40605)</span></li>
<li>choqok/helperlibs/twitterapihelper/twitterapisearchtimelinewidget.cpp <span style="color: grey">(82dc1b1)</span></li>
<li>choqok/microblogs/laconica/laconicamicroblog.cpp <span style="color: grey">(dd86db2)</span></li>
<li>choqok/microblogs/laconica/laconicasearch.h <span style="color: grey">(4bfac2d)</span></li>
<li>choqok/microblogs/laconica/laconicasearch.cpp <span style="color: grey">(4b1c9c9)</span></li>
<li>choqok/helperlibs/twitterapihelper/twitterapidmessagedialog.cpp <span style="color: grey">(70092db)</span></li>
<li>choqok/helperlibs/twitterapihelper/twitterapimicroblog.h <span style="color: grey">(b9dd97a)</span></li>
<li>choqok/helperlibs/twitterapihelper/twitterapimicroblog.cpp <span style="color: grey">(cb666cb)</span></li>
<li>choqok/helperlibs/twitterapihelper/twitterapisearch.h <span style="color: grey">(b421585)</span></li>
<li>choqok/helperlibs/twitterapihelper/twitterapiaccount.h <span style="color: grey">(d880f14)</span></li>
<li>choqok/helperlibs/twitterapihelper/twitterapiaccount.cpp <span style="color: grey">(e2efe97)</span></li>
<li>choqok/helperlibs/twitterapihelper/twitterapidmessagedialog.h <span style="color: grey">(ed36a1d)</span></li>
</ul>
<p><a href="https://git.reviewboard.kde.org/r/121165/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>