<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">andrea diamantini</b> <span dir="ltr"><<a href="mailto:adjam7@gmail.com">adjam7@gmail.com</a>></span><br>Date: 2010/9/15<br>
Subject: Re: [rekonq] [ANNOUNCE] rekonq 0.6 stable release<br>To: <a href="mailto:benjamin.poulain@nokia.com">benjamin.poulain@nokia.com</a><br><br><br><br><br><div class="gmail_quote">2010/9/13 <span dir="ltr"><<a href="mailto:benjamin.poulain@nokia.com" target="_blank">benjamin.poulain@nokia.com</a>></span><div class="im">
<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<div><br>
> In this period, due to the "programming speed" we had to fight with a lot of regressions, most coming from my "no-one-else-checked" commits (sorry), some<br>
> others coming here and there from your patches.<br>
<br>
</div>Maybe it is time to introduce systematic code review? That could help to spread the knowledge about the code base, help to reduce the regressions, and two people are able to fix regressions instead of one.<br>
<br>
Rekonq is not really a toy project anymore, and I feel it could benefit from reviews.</blockquote><div><br></div><div><br></div></div><div>I think something has to be done, yes. Are you suggesting something you just use (eg: in Qt, QtWebKit)?</div>
<div>There are also a bunch of "orthogonal" problems (are they really?) about I'd like to consider:</div><div>1) the imminent move (November, 2010) to a new platform (<a href="http://git.kde.org" target="_blank">git.kde.org</a>).</div>
<div>2) Maintain the lowest possible entering barriers. It seems that git + gitorious merge requests system are the best tool for. IMHO it's not the same in the actual KDE reviewboard. But I hope it is so just because of SVN...</div>
<div>3) The necessity to maintain a sort of control on the introduction of new features.</div><div class="im">
<div> </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
> 2) Moving from WebView to GraphicsWebView.<br>
><br>
</div><div>> The second one is just a Benjamin Poulain's hint that needs more investigation before.<br>
<br>
</div>Actually, I am gonna backpedal a little on this one when it comes to OpenGL.<br>
<br>
Two reasons for that:<br>
1) a bug in the graphics system opengl preventing correct repaint of Canvas. It will be fixed in 4.7.1.<br>
2) some inconsistent behavior with hardware acceleration. Which will require (1) more benchmarking from me, (2) a backbuffer using raster for non-accelerated content. We are actually looking into that as well for MeeGo, so hopefully a solution will come from there.<br>
<br>
Appart from OpenGL support, it could still be interesting to move to GraphicsWebView without OpenGL at first. I can help prototyping that.<br>
<br>
cheers,<br>
Benjamin</blockquote></div></div>
</div><br>