<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
> > 2.<br>
> > There are also kde 4.2 derived bugs. (e.g. tab text) I leaved unaltered<br>
> > code<br>
> > that works with KDE trunk, but not (well) with 4.2<br>
><br>
> I think it would be better to leave it as we (me and avaddon) coded it,<br>
> because otherwise you'll get a bug on 4.2 or 4.3.<br>
<br>
</div>On kde/trunk these bugs are not present. So it's just a 4.2 related problem.<br>
I cannot understand what code you are referring. I said I did no changes<br>
about.</blockquote><div> <br> connect(m_tabBar, SIGNAL(closeRequest(int)), this, SLOT(closeTab(int))); <br>
bool oneCloseButton = ReKonfig::showCloseTabButton(); <br>+#if KDE_IS_VERSION(4,2,60) <br>
+ setTabsClosable(oneCloseButton); // this causes #23 on KDE 4.2 <br>+#else <br>
setCloseButtonEnabled(oneCloseButton); // this is deprecated, remove for KDE >=4.3<br>+#endif <br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div><div></div><div class="h5"><br>
> > 3.<br>
> > new download system and modifications in the Application class to better<br>
> > support it. QPointer(s) are really a great idea :)<br>
> > I also modified a bit download class and removed QTimer notification.<br>
> > It's my<br>
> > fault. If someone is interested in, he can re-enable that.<br>
><br>
> Timer is in place to make download progress bar possible.<br>
> QPointers helped to track the deletion ofo objects when going to background<br>
> download mode and back.<br>
><br>
> > 4.<br>
> > Side Panel. As requested rekonq 0.1 will have it. We sure have to work<br>
> > about<br>
> > the bookmarks panel (before releasing 0.1) and put it on.<br>
> ><br>
> > 5.<br>
> > Bookmark classes improvements. All apart from one method I didn't<br>
> > understand<br>
> > and I never seen used.<br>
><br>
> Some stuff there is in place to make future features possible.<br>
><br>
> > 6.<br>
> > Contextual menu. Here I did the major changes (in the code). I removed<br>
> > the unuseful (for me) QMap actions and provided a KActionCollection for<br>
> > all webActions.<br>
><br>
> We don't really need action collection (and it's heavier than QMap) and it<br>
> makes code cleaner and easier to read. There is no point in changing<br>
> working code just to use KDE class instead of generic container.<br>
<br>
</div></div>Why you said it's heavier? I changed it just to let it be more readable. And<br>
having in mind (future) "Configure shortcuts" dialog insertion</blockquote><div><br>Let's see how much heavier:<br><br><span style="font-family: courier new,monospace;"> QObject dummy;</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> KActionCollection test1(&dummy);</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> QMap<QString, QAction> test2;</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> kDebug() << "KActionCollection :" << sizeof(test1);</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> kDebug() << "QMap :" << sizeof(test2);</span><br>
<br>this code output would be:<br><span style="font-family: courier new,monospace;">KActionCollection : 24</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;">QMap : 8</span><br>
<br>So as you can see this means 3x heavier (or 300%)<br><br>But the bigger issue is that in your implementation action collection isn't static, so every instance of WebView creates (in constructor) new collection. So if you have 30 tabs it's like 24 B x 30, but the worst thing is that it adds overhead for every web tab creation because you invoke KActionCollection each time you create a WebView object AND you create (every time) 8 KActions and initialize them and add to action (just to destruct them when user closes the tab...) I don't have time to test how much overhead it addes but I bet it's like 50~100%.<br>
<br>24 bytes per tab isn't that bad, but the additional overhead (longer creation time) is a real problem (especially if you have resource constrained systems like netbooks).<br><br>This collection should be static and lazy (init on demand).<br>
<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5"><br>
> 7.<br>
><br>
> > moveable tabs, that is gratis, via Qt 4.5 functions.<br>
> ><br>
> ><br>
> > I hope I'm remembering ALL changes I did. Please from now on, sync one<br>
> > your branch (master?) with mainline/master, test, code, suggest, do small<br>
> > themable<br>
> > commits and fill merge requests ;).<br>
> > I'd like to release 0.1alpha on next tuesday (28 apr) and from there on<br>
> > going<br>
> > in bugfixing and translation mode until 0.1 release (when? I don't know).<br>
> ><br>
> > From now on, if you don't have different ideas, we need to work on two<br>
> > essential aspects:<br>
> > - the bookmarks sidepanel<br>
> > - the focus problem<br>
> ><br>
> > About focus, I really cannot decide what is better to do, so I'm waiting<br>
> > for<br>
> > your suggestions (and your code ;) ).<br>
><br>
> What's with the focus?<br>
><br>
> > COPYRIGHT QUESTION<br>
> > I added a string on every rekonq file: the following<br>
> ><br>
> > * Copyright (C) 2009 rekonq team. Please, see AUTHORS file for details *<br>
> ><br>
> > This means we need to do also two things:<br>
> ><br>
> > 1. update Authors file (important)<br>
> > here I wrote 3 columns: name, mail, role<br>
> > You just need to add yours and perform a merge request.<br>
><br>
> I'm not sure about the role field, we don't have any roles, so it would be<br>
> a bit artifitial.<br>
<br>
</div></div>You can just indicate there if you are a developer, an artist, a translator,<br>
etc..</blockquote><div><br>OK, now I get it.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div class="im"><br>
> 2. update main file (VERY important)<br>
><br>
> > here you need to add... I'm pushing one example commented in<br>
> > main.cpp file.<br>
> ><br>
> > We can obviously remove the previous line and push all our names also on<br>
> > every<br>
> > file. I did this way just for convenience. Decide all together one way<br>
> > and just<br>
> > do it!!<br>
><br>
> IMO this is bad idea. It's not how things are done. We can have AUTHORS<br>
> file but leave the copyrights on per file basis.<br>
<br>
</div>About me it's ok, as said. I'll remove "rekonq team" string and search for<br>
copyrights... ;)<br>
<div class="im"><br>
> I'd like also rise a concern about backporting changes. It doesn't make<br>
> sense, because it's easier to port your changes to our fork than vice versa<br>
> and you shouldn't port (especially don't change) code that someone write<br>
> and tested because you don't know why it was written this way and not<br>
> another and the possibility of introducing new bug is big. I've run a diff<br>
> and I see there are awful lot of things you didn'd ported and most of this<br>
> is important stuff related to bugfixes and missing features. A lots pasts<br>
> of code were revritten or heavy refactored and there is no sense in doing<br>
> it again.<br>
<br>
</div>I really find difficult answering here.<br>
Why if I write something and you modify it, this is an improvement and if I<br>
change something backporting your code there are risks and possibility of<br>
introducing new bugs?</blockquote><div><br>It's just the fact that avaddon an I've spend couple of weeks tweaking the code and testing, peer-reviewing it, so this isn't something you want to change if you don't want to introduce new bugs. There are some subtle changes that have big impact on code quality. <br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Why your changes are critical or bugfix related and mine are "I didn't<br>
understand so I removed it"?</blockquote><div><br>And there is more code changed/added. It's numbers not egos that counts. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I asked with first email about features and changes I didn't port. I never<br>
received patches via mail or merge requests apart from avaddon's fixes to<br>
localization system (added) and your infamous "I did a lot of things but I<br>
cannot remember what".</blockquote><div><br>Here are your patches:<br></div><div><br><span style="font-family: courier new,monospace;">$ kompare avaddon-clone/</span><span style="font-family: courier new,monospace;"> mainline/</span><br>
<span style="font-family: courier new,monospace;">$ kompare pawelprazak-clone/</span><span style="font-family: courier new,monospace;"> mainline/</span><br><span style="font-family: courier new,monospace;"><br><span style="font-family: arial,helvetica,sans-serif;">Sorry but I don't have much time lately (there are things that need to be get sorted, some personal stuff), fixes are in our code. </span><br>
</span><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><br>
<br>
> Also IMO you can't make a release without unittesting (and unit tests I've<br>
> implemented are not even adopted in mainline yet), to make it right we need<br>
> quite a few new tests to make sure the code can be released to anyone (even<br>
> thou this is a preview).<br>
<br>
</div>I usually use (and see used) the shortcut "IMHO". but probably YOUR opinion is<br>
not humble..</blockquote><div><br>Don't be picky ;)<br><br>(hint: search Google for phrase: "imo acronym")<br><br>I guess there are lots of other things you've never seen...<br>Why to be afraid to have not-so-humble opinion anyway?<br>
<br>btw. it's one letter less to write ;P<br><br>Regards<br>Paweł<br></div></div><br><br>