Hi again.<div><br></div><div>So, based on this list, I made a 12 week plan for the project based on the 12 week scheme used in GSoC:</div><div><br></div><div><div>Week 1/2: Tweak Nepomuk runner</div><div>Week 2/3: Tweak File search runner</div>
<div>Week 3: Tweak Google runner</div><div>Weeks 4 to 5 (or 6?): Put result querying in a different thread</div><div>Week 6: Polish what has been done so far</div><div><br></div><div>Week 7: Get user feedback better (Tell when searching and when nothing was found, some helping message at start)</div>
<div>Week 8: Separate results in groups, allow user to define the priority of each runner (or allow developer to define the priority each one of their runner's commands can set it)</div><div>Week 9: Make results fit on only one krunner screen, shrink less relevant results, hide lesser relevant results on main krunner screen</div>
<div>Week 10: Expanding/unexpanding search groups</div><div>Week 11: Extra actions for each item of the results, depending on its type</div><div>Week 12: Polish and get everything ready to go</div><div><br></div><div>What do you think?</div>
<br><div class="gmail_quote">Em 1 de maio de 2011 04:06, Luiz Romário Santana Rios <span dir="ltr"><<a href="mailto:luizromario@gmail.com">luizromario@gmail.com</a>></span> escreveu:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Ah, this is not a definitive list. We can add/remove stuff from it.<br><br><div class="gmail_quote">Em 1 de maio de 2011 04:04, Luiz Romário Santana Rios <span dir="ltr"><<a href="mailto:luizromario@gmail.com" target="_blank">luizromario@gmail.com</a>></span> escreveu:<div>
<div></div><div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Take a look at this and see if it's OK:<div><br></div><div><div>Improve krunner result displaying brainstorm:</div>
<div>+ Tweak runners result rating</div><div> * Nepomuk runner</div><div> ~ Remove over and over repeated results</div>
<div> * File search runner</div><div> Priority criteria</div><div> ~ Exact match: for "photos", priorize "Photos" over "Photos - september", for example</div><div> ~ Priorize folders over files</div>
<div> ~ Folders that contain several folders or files that match the query, probably showing them as "subresults"</div><div> * Google runner</div><div> ~ Show a list of actual results from the search (Is this possible?)</div>
<div>+ Change krunner result displaying</div><div> * Group each runner results into its own category</div><div> * Allow user to change the categories' priorities (For example: first, commands, then, files, then, nepomuk, etc....).</div>
<div> * Show as many results as it fits in krunner, shrinking the less relevant ones. (configurable)</div><div> * If there are results from more than a runner, give the user an option to expand one category and show only its results.</div>
<div> ~ Show further results in the associated application</div><div> * Show extra actions for each item</div><div> * Give the option of using a compact layout</div><div> * Mockup: <a href="https://picasaweb.google.com/luizromario/Mockups#5601639496208873426" target="_blank">https://picasaweb.google.com/luizromario/Mockups#5601639496208873426</a></div>
<div>+ Fine-tune krunner</div><div> * Popup some helping text if user waits too long</div><div> * Tell the user when krunner is searching and when it found nothing</div>
<div> * Put query in a different thread so krunner doesn't freeze while the user is typing something (if it still isn't).</div><div><br></div><div>And I think the KSysGuard part it uses needs some care too.</div>
<div><br></div><div>Anyway, sorry for taking so long, I got stuck sometimes when doing this. </div><div><br><div class="gmail_quote">
2011/4/30 Aaron J. Seigo <span dir="ltr"><<a href="mailto:aseigo@kde.org" target="_blank">aseigo@kde.org</a>></span><div><div></div><div><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>
</div><div>On Friday, April 29, 2011 23:57:57 Luiz Romário Santana Rios wrote:<br>
> 2011/4/29 Aaron J. Seigo <<a href="mailto:aseigo@kde.org" target="_blank">aseigo@kde.org</a>><br>
><br>
> > On Friday, April 29, 2011 00:21:11 Luiz Romário Santana Rios wrote:<br>
> > > 2011/4/28 Aaron J. Seigo <<a href="mailto:aseigo@kde.org" target="_blank">aseigo@kde.org</a>><br>
> > ><br>
> > > > On Thursday, April 28, 2011 09:15:08 Luiz Romário Santana Rios wrote:<br>
> > > > > Currently, when we type something in, krunner displays the<br>
> > > > > results<br>
> > > > > as it finds it, without giving a feedback of whether it is<br>
> > > > > searching or just didn't find anything.<br>
> > > ><br>
> > > > that would be a nice addition.<br>
> > > ><br>
> > > > > It also does not separate the results into its different<br>
> > > > > categories<br>
> > > ><br>
> > > > that's because they are organized by relevance. if they are<br>
> > > > sorted into categories, and if there are 4 categories that<br>
> > > > match and 5 items in<br>
> ><br>
> > each<br>
> ><br>
> > > > category then the best match from the 4th category will be the<br>
> > > > 16th<br>
> ><br>
> > item<br>
> ><br>
> > > > in the list(!) even though it is more likely to be what the user<br>
> > > > wants than most<br>
> > > > of the items above it.<br>
> > > ><br>
> > > > i have yet to see a solution for this problem, but am open to<br>
> > > > such a<br>
> > > > solution<br>
> > > > being offered.<br>
> > ><br>
> > > Well, I thought about showing only the most relevant results for<br>
> > > each<br>
> > > category and priorizing the category with the most relevant results.<br>
> > > If a<br>
> ><br>
> > which is almost always going to be the nepomuk search ;)<br>
> ><br>
> > > user want to see more results for that category, they would just<br>
> > > need to expand it. I'll do some mockups for that and will post<br>
> > > here.<br>
> ><br>
> > sounds good; mockups always help.<br>
><br>
> Here's one:<br>
> <a href="http://lh5.googleusercontent.com/_V8ZPvFyTxNc/Tbty2kU7CII/AAAAAAAAARs/v_Ut1J" target="_blank">http://lh5.googleusercontent.com/_V8ZPvFyTxNc/Tbty2kU7CII/AAAAAAAAARs/v_Ut1J</a><br>
> 8P4DQ/01%20-%20Expand%20and%20Shrink%20less%20relevant%20results.png<br>
><br>
> It's bad, I know, I suck at making mockups, but it gives part of the idea of<br>
> what I mean.<br>
<br>
</div></div>wire frame mockups like that one are just fine. they let one concentrate on<br>
the structure rather than get distracted by shiny things ;)<br>
<div><br>
> Notice that I show two different ways of expanding the results<br>
> in it. I think the button is better, but it takes too much space, so I'm<br>
<br>
</div>and what would be the workflow to expand / collapse / run?</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
an important part of krunner is being able to very quickly type and execute.<br>
the UI is not fancy, but it is designed for speed.<br></blockquote><div><br></div></div></div><div>See mockup in the beginning of the message. But, basically, running anything by just typing and hitting enter wouldn't change much.</div>
<div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
> > then the Nepomuk runner needs tweaking in how it rates results.<br>
><br>
> So this is the first thing we should do, I guess.<br>
<br>
</div>it's definitely a good starting point. :)<br>
<div><br>
> What I meant was that I think it's better to wait one or two seconds after<br>
> the user stops typing so that krunner doesn't start querying with an<br>
> incomplete string.<br>
<br>
</div>that would probably ruin one of the main features of krunner: match as you<br>
type.<br></blockquote><div><br></div></div><div>Yeah, you're right.</div><div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
> I also think it would give focus to the main result, if<br>
> there's one, but I may be wrong.<br>
<br>
</div>it already does.<br>
<div><br>
> Weird. Should it work if I just type in something and then press the down<br>
> arrow?<br>
<br>
</div>yes...<br>
<div><br>
> Well, I will stop and think over this project and get back with better<br>
> summarized idead and more mockups tomorrow.<br>
<br>
</div>:)<br></blockquote><div><br></div></div><div>See above. :)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
--<div><br>
<div><div></div><div>Aaron J. Seigo<br>
humru othro a kohnu se<br>
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43<br>
<br>
KDE core developer sponsored by Qt Development Frameworks<br>
</div></div><br></div><div>_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org" target="_blank">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br><br></div></blockquote></div>-- <br>Luiz Romário Santana Rios<br>
</div></div>
</blockquote></div></div></div><br><br clear="all"><br>-- <br><font color="#888888">Luiz Romário Santana Rios</font></blockquote></div><br>-- <br>Luiz Romário Santana Rios<br>
</div>