<HTML><BODY><br><div><div id="style_13749497980000000371"><div id="style_13749497980000000371_BODY">On Saturday 27 July 2013, 14:07 +02:00 Milian Wolff <mail@milianw.de> wrote:<br>
<blockquote style="border-left:1px solid #0857A6;margin:10px;padding:0 0 0 10px;"><div id=""><div><div id="style_13749268450000000429"><div id="style_13749268450000000429_BODY">Hello Vlas,<br><br>
while I greatly appreciate your enthusiasm I have to take on my maintainer hat <br>
and ask you kindly to use ReviewBoard some more before pushing commits <br>
directly to KDevelop codebase.<br><br>
This commit for example needs to be revisited, I think:<br><br>
commit fe61dcf2259bcd97d2e5649070cb38f11c4ec963<br>
Author: Vlas Puhov <<a target="_blank">vlas.puhov@mail.ru</a>><br>
Date: Fri Jul 26 21:14:34 2013 +0400<br><br>
GrepViewPlugin: Search by default in previous location.<br><br>
BUG: 299751<br><br>
It should definitely use a combo box with a list of recent locations, similar <br>
to the pattern history and other fields already do.</div></div></div></div></blockquote><br><div id=""><div><div id="style_13749268450000000429"><div id="style_13749268450000000429_BODY">H'm...I didn't think about it. It's a good idea. Thanks.<br></div></div></div></div><blockquote style="border-left:1px solid #0857A6;margin:10px;padding:0 0 0 10px;"><div id=""><div><div id="style_13749268450000000429"><div id="style_13749268450000000429_BODY"><br>
Furthermore, please add more information to your commit messages. This one <br>
for example should state that the big hunk you removed is still "available" to <br>
the user from within the dialog by using the synchronize button (at least, I <br>
hope so)</div></div></div></div></blockquote><br><div id=""><div><div id="style_13749268450000000429"><div id="style_13749268450000000429_BODY">Nope, it's not avaliable, not anymore. This as you call it "the big hunk" was wrong from the start. If you take a close look you'll notice that this hunk didn't let you search in all opened projects, instead it opened just a first one. Futhermore there was the stupid check: first !m_directory.isEmpty() was checked and then if it's empty: !m_directory.startsWith(proj->folder().toLocalFile(). What a hell is that??? How can it start with something if it's empty?<br><br></div></div></div></div><blockquote style="border-left:1px solid #0857A6;margin:10px;padding:0 0 0 10px;"><div id=""><div><div id="style_13749268450000000429"><div id="style_13749268450000000429_BODY"><br>
This commit could also be cleaned up:<br>
commit 722457052892e3a79f40f82f3f2e005abcd3f91d<br>
Author: Vlas Puhov <<a target="_blank">vlas.puhov@mail.ru</a>><br>
Date: Sat Jul 20 16:15:00 2013 +0400<br><br>
BreakpointWidget: Show only file's name, the tooltip shows the full path.<br><br>
BreakpointDelegate::displayText's implementation should not use the ternary <br>
operator in my opinion and also needs a comment to clarify what it actually <br>
does. Furthermore, please put opening braces of function bodies on their own <br>
line, similar to how the other functions are doing it.</div></div></div></div></blockquote><br> I don't know if it really needs a comment. I mean, there is only only two lines of code. I've seen hunderds lines of code in kdevelop's code base without even a single word of explanation about what it does. So, I think it's ok.<br>And what is wrong with ternary operator? <br><blockquote style="border-left:1px solid #0857A6;margin:10px;padding:0 0 0 10px;"><div id=""><div><div id="style_13749268450000000429"><div id="style_13749268450000000429_BODY"><br>
Even better though would be to remove the whole code there and put that logic <br>
into the model, instead of inside the delegate. The code for that resides in <br>
BreakPoint::data, where you need to special-case the DisplayRole then to only <br>
return the filename. There it's also much simpler, as you have the url at hand <br>
and can just use m_url.fileName() instead of string parsing</div></div></div></div></blockquote><br><div id=""><div><div id="style_13749268450000000429"><div id="style_13749268450000000429_BODY">At first I thought about it too. But there is a little problem: BreakpointWidget is not the only one who retrieves data by DisplayRole. Actually it's the right thing for breakpoint model to return the full path instead of a file's name(it's more useful, for example breakpoint insertion uses the full path).</div></div></div></div><blockquote style="border-left:1px solid #0857A6;margin:10px;padding:0 0 0 10px;"><div id=""><div><div id="style_13749268450000000429"><div id="style_13749268450000000429_BODY"><br><br>
Some patches you committed also contain whitespace errors, please enable <br>
"remove trailing spaces on edited lines" in the editor settings. Also helpful <br>
is something like this in your git config:<br><br>
[core]<br>
whitespace = trailing-space,space-before-tab<br>
[apply]<br>
whitespace = fix</div></div></div></div></blockquote> <br><div id=""><div><div id="style_13749268450000000429"><div id="style_13749268450000000429_BODY">THANK YOU!!! Really. I didn't know about it.</div></div></div></div><blockquote style="border-left:1px solid #0857A6;margin:10px;padding:0 0 0 10px;"><div id=""><div><div id="style_13749268450000000429"><div id="style_13749268450000000429_BODY"><br><br>
Bye<br><br>
PS: I hope you see this as constructive criticism. I really don't want to <br>
annoy you or drive you away from the project - quite the contrary. I just hope <br>
to teach you some more tricks to improve the quality of your contributions <br>
even more. Using something like reviewboard is also how one learns a lot, by <br>
taking in the suggestions from others.<br><br>
Cheers! Rock on!<br>
-- <br>
Milian Wolff<br><a target="_blank">mail@milianw.de</a><br><a href="http://milianw.de" target="_blank">http://milianw.de</a><br data-mce-bogus="1"></div></div></div></div></blockquote><blockquote style="border-left:1px solid #0857A6;margin:10px;padding:0 0 0 10px;"><div id=""><div><div id="style_13749268450000000429"><div id="style_13749268450000000429_BODY"><br></div></div></div></div></blockquote>
PS: I'd love to use the reviewboard. But for me it looks like there is no one who is proficient enough in code base and at the same time interested in reviewing patches. For example, I posted a couple of patches : 1. Fix crash in disassembleWidged. It was on the reviewboard for 2 weeks - not a single comment. 2. Fix incorect debug session ending - 2 weeks too. Yeah Aleix wrote something, but he didn't tell(no one did!) that I was patching in a wrong place. 3. Fix debug/execute actions avaliable while none of projets are opened - was for review about 2 weeks too. Yes I know I was completely wrong about it, but afterwards I wasn't disabling those actions anymore, I just speeded a project's loading up, but still no comments. <br> So, the question is why? What is the meaning in posting patches on reviewboard if there is no one to review it?<br>
<br>-- <br>Vlas Puhov<br>
</div>
</div>
</div>
<br></BODY></HTML>