Re: SoK idea: Improve krunner result displaying and navigation.
Hi again. So, based on this list, I made a 12 week plan for the project based on the 12 week scheme used in GSoC: Week 1/2: Tweak Nepomuk runner Week 2/3: Tweak File search runner Week 3: Tweak Google runner Weeks 4 to 5 (or 6?): Put result querying in a different thread Week 6: Polish what has been done so far Week 7: Get user feedback better (Tell when searching and when nothing was found, some helping message at start) 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) Week 9: Make results fit on only one krunner screen, shrink less relevant results, hide lesser relevant results on main krunner screen Week 10: Expanding/unexpanding search groups Week 11: Extra actions for each item of the results, depending on its type Week 12: Polish and get everything ready to go What do you think? Em 1 de maio de 2011 04:06, Luiz Romário Santana Rios escreveu: > Ah, this is not a definitive list. We can add/remove stuff from it. > > Em 1 de maio de 2011 04:04, Luiz Romário Santana Rios < > luizroma...@gmail.com> escreveu: > > Take a look at this and see if it's OK: >> >> Improve krunner result displaying brainstorm: >> + Tweak runners result rating >> * Nepomuk runner >>~ Remove over and over repeated results >> * File search runner >>Priority criteria >>~ Exact match: for "photos", priorize "Photos" over "Photos - >> september", for example >>~ Priorize folders over files >>~ Folders that contain several folders or files that match the query, >> probably showing them as "subresults" >> * Google runner >>~ Show a list of actual results from the search (Is this possible?) >> + Change krunner result displaying >> * Group each runner results into its own category >> * Allow user to change the categories' priorities (For example: first, >> commands, then, files, then, nepomuk, etc). >> * Show as many results as it fits in krunner, shrinking the less >> relevant ones. (configurable) >> * If there are results from more than a runner, give the user an option >> to expand one category and show only its results. >>~ Show further results in the associated application >> * Show extra actions for each item >> * Give the option of using a compact layout >> * Mockup: >> https://picasaweb.google.com/luizromario/Mockups#5601639496208873426 >> + Fine-tune krunner >> * Popup some helping text if user waits too long >> * Tell the user when krunner is searching and when it found nothing >> * Put query in a different thread so krunner doesn't freeze while the >> user is typing something (if it still isn't). >> >> And I think the KSysGuard part it uses needs some care too. >> >> Anyway, sorry for taking so long, I got stuck sometimes when doing this. >> >> 2011/4/30 Aaron J. Seigo >> >> On Friday, April 29, 2011 23:57:57 Luiz Romário Santana Rios wrote: >>> > 2011/4/29 Aaron J. Seigo >>> > >>> > > On Friday, April 29, 2011 00:21:11 Luiz Romário Santana Rios wrote: >>> > > > 2011/4/28 Aaron J. Seigo >>> > > > >>> > > > > On Thursday, April 28, 2011 09:15:08 Luiz Romário Santana Rios >>> wrote: >>> > > > > > Currently, when we type something in, krunner displays the >>> > > > > > results >>> > > > > > as it finds it, without giving a feedback of whether it is >>> > > > > > searching or just didn't find anything. >>> > > > > >>> > > > > that would be a nice addition. >>> > > > > >>> > > > > > It also does not separate the results into its different >>> > > > > > categories >>> > > > > >>> > > > > that's because they are organized by relevance. if they are >>> > > > > sorted into categories, and if there are 4 categories that >>> > > > > match and 5 items in >>> > > >>> > > each >>> > > >>> > > > > category then the best match from the 4th category will be the >>> > > > > 16th >>> > > >>> > > item >>> > > >>> > > > > in the list(!) even though it is more likely to be what the user >>> > > > > wants than most >>> > > > > of the items above it. >>> > > > > >>> > > > > i have yet to see a solution for this problem, but am open to >>> > > > > such a >>> > > > > solution >>> > > > > being offered. >>> > > > >>> > > > Well, I thought about showing only the most relevant results for >>> > > > each >>> > > > category and priorizing the category with the most relevant >>> results. >>> > > > If a >>> > > >>> > > which is almost always going to be the nepomuk search ;) >>> > > >>> > > > user want to see more results for that category, they would just >>> > > > need to expand it. I'll do some mockups for that and will post >>> > > > here. >>> > > >>> > > sounds good; mockups always help. >>> > >>> > Here's one: >>> > >>> http://lh5.googleusercontent.com/_V8ZPvFyTxNc/Tbty2kU7CII/ARs/v_Ut1J >>> > 8P4DQ/01%20-%20Expand%20and%20Shrink%20less%20relevant%20results.png >>> > >>> > It's bad, I know, I suck at making mockups, but it gives part of the >>> idea of >>
Re: SoK idea: Improve krunner result displaying and navigation.
Ah, this is not a definitive list. We can add/remove stuff from it. Em 1 de maio de 2011 04:04, Luiz Romário Santana Rios escreveu: > Take a look at this and see if it's OK: > > Improve krunner result displaying brainstorm: > + Tweak runners result rating > * Nepomuk runner >~ Remove over and over repeated results > * File search runner >Priority criteria >~ Exact match: for "photos", priorize "Photos" over "Photos - > september", for example >~ Priorize folders over files >~ Folders that contain several folders or files that match the query, > probably showing them as "subresults" > * Google runner >~ Show a list of actual results from the search (Is this possible?) > + Change krunner result displaying > * Group each runner results into its own category > * Allow user to change the categories' priorities (For example: first, > commands, then, files, then, nepomuk, etc). > * Show as many results as it fits in krunner, shrinking the less relevant > ones. (configurable) > * If there are results from more than a runner, give the user an option > to expand one category and show only its results. >~ Show further results in the associated application > * Show extra actions for each item > * Give the option of using a compact layout > * Mockup: > https://picasaweb.google.com/luizromario/Mockups#5601639496208873426 > + Fine-tune krunner > * Popup some helping text if user waits too long > * Tell the user when krunner is searching and when it found nothing > * Put query in a different thread so krunner doesn't freeze while the > user is typing something (if it still isn't). > > And I think the KSysGuard part it uses needs some care too. > > Anyway, sorry for taking so long, I got stuck sometimes when doing this. > > 2011/4/30 Aaron J. Seigo > > On Friday, April 29, 2011 23:57:57 Luiz Romário Santana Rios wrote: >> > 2011/4/29 Aaron J. Seigo >> > >> > > On Friday, April 29, 2011 00:21:11 Luiz Romário Santana Rios wrote: >> > > > 2011/4/28 Aaron J. Seigo >> > > > >> > > > > On Thursday, April 28, 2011 09:15:08 Luiz Romário Santana Rios >> wrote: >> > > > > > Currently, when we type something in, krunner displays the >> > > > > > results >> > > > > > as it finds it, without giving a feedback of whether it is >> > > > > > searching or just didn't find anything. >> > > > > >> > > > > that would be a nice addition. >> > > > > >> > > > > > It also does not separate the results into its different >> > > > > > categories >> > > > > >> > > > > that's because they are organized by relevance. if they are >> > > > > sorted into categories, and if there are 4 categories that >> > > > > match and 5 items in >> > > >> > > each >> > > >> > > > > category then the best match from the 4th category will be the >> > > > > 16th >> > > >> > > item >> > > >> > > > > in the list(!) even though it is more likely to be what the user >> > > > > wants than most >> > > > > of the items above it. >> > > > > >> > > > > i have yet to see a solution for this problem, but am open to >> > > > > such a >> > > > > solution >> > > > > being offered. >> > > > >> > > > Well, I thought about showing only the most relevant results for >> > > > each >> > > > category and priorizing the category with the most relevant results. >> > > > If a >> > > >> > > which is almost always going to be the nepomuk search ;) >> > > >> > > > user want to see more results for that category, they would just >> > > > need to expand it. I'll do some mockups for that and will post >> > > > here. >> > > >> > > sounds good; mockups always help. >> > >> > Here's one: >> > >> http://lh5.googleusercontent.com/_V8ZPvFyTxNc/Tbty2kU7CII/ARs/v_Ut1J >> > 8P4DQ/01%20-%20Expand%20and%20Shrink%20less%20relevant%20results.png >> > >> > It's bad, I know, I suck at making mockups, but it gives part of the >> idea of >> > what I mean. >> >> wire frame mockups like that one are just fine. they let one concentrate >> on >> the structure rather than get distracted by shiny things ;) >> >> > Notice that I show two different ways of expanding the results >> > in it. I think the button is better, but it takes too much space, so I'm >> >> and what would be the workflow to expand / collapse / run? > > >> an important part of krunner is being able to very quickly type and >> execute. >> the UI is not fancy, but it is designed for speed. >> > > See mockup in the beginning of the message. But, basically, running > anything by just typing and hitting enter wouldn't change much. > > >> >> > > then the Nepomuk runner needs tweaking in how it rates results. >> > >> > So this is the first thing we should do, I guess. >> >> it's definitely a good starting point. :) >> >> > What I meant was that I think it's better to wait one or two seconds >> after >> > the user stops typing so that krunner doesn't start querying with an >> > incomplete string. >> >> that would probably ruin one of the main features of krunner: match as you >> type. >> > >
Re: SoK idea: Improve krunner result displaying and navigation.
Take a look at this and see if it's OK: Improve krunner result displaying brainstorm: + Tweak runners result rating * Nepomuk runner ~ Remove over and over repeated results * File search runner Priority criteria ~ Exact match: for "photos", priorize "Photos" over "Photos - september", for example ~ Priorize folders over files ~ Folders that contain several folders or files that match the query, probably showing them as "subresults" * Google runner ~ Show a list of actual results from the search (Is this possible?) + Change krunner result displaying * Group each runner results into its own category * Allow user to change the categories' priorities (For example: first, commands, then, files, then, nepomuk, etc). * Show as many results as it fits in krunner, shrinking the less relevant ones. (configurable) * If there are results from more than a runner, give the user an option to expand one category and show only its results. ~ Show further results in the associated application * Show extra actions for each item * Give the option of using a compact layout * Mockup: https://picasaweb.google.com/luizromario/Mockups#5601639496208873426 + Fine-tune krunner * Popup some helping text if user waits too long * Tell the user when krunner is searching and when it found nothing * Put query in a different thread so krunner doesn't freeze while the user is typing something (if it still isn't). And I think the KSysGuard part it uses needs some care too. Anyway, sorry for taking so long, I got stuck sometimes when doing this. 2011/4/30 Aaron J. Seigo > On Friday, April 29, 2011 23:57:57 Luiz Romário Santana Rios wrote: > > 2011/4/29 Aaron J. Seigo > > > > > On Friday, April 29, 2011 00:21:11 Luiz Romário Santana Rios wrote: > > > > 2011/4/28 Aaron J. Seigo > > > > > > > > > On Thursday, April 28, 2011 09:15:08 Luiz Romário Santana Rios > wrote: > > > > > > Currently, when we type something in, krunner displays the > > > > > > results > > > > > > as it finds it, without giving a feedback of whether it is > > > > > > searching or just didn't find anything. > > > > > > > > > > that would be a nice addition. > > > > > > > > > > > It also does not separate the results into its different > > > > > > categories > > > > > > > > > > that's because they are organized by relevance. if they are > > > > > sorted into categories, and if there are 4 categories that > > > > > match and 5 items in > > > > > > each > > > > > > > > category then the best match from the 4th category will be the > > > > > 16th > > > > > > item > > > > > > > > in the list(!) even though it is more likely to be what the user > > > > > wants than most > > > > > of the items above it. > > > > > > > > > > i have yet to see a solution for this problem, but am open to > > > > > such a > > > > > solution > > > > > being offered. > > > > > > > > Well, I thought about showing only the most relevant results for > > > > each > > > > category and priorizing the category with the most relevant results. > > > > If a > > > > > > which is almost always going to be the nepomuk search ;) > > > > > > > user want to see more results for that category, they would just > > > > need to expand it. I'll do some mockups for that and will post > > > > here. > > > > > > sounds good; mockups always help. > > > > Here's one: > > > http://lh5.googleusercontent.com/_V8ZPvFyTxNc/Tbty2kU7CII/ARs/v_Ut1J > > 8P4DQ/01%20-%20Expand%20and%20Shrink%20less%20relevant%20results.png > > > > It's bad, I know, I suck at making mockups, but it gives part of the idea > of > > what I mean. > > wire frame mockups like that one are just fine. they let one concentrate on > the structure rather than get distracted by shiny things ;) > > > Notice that I show two different ways of expanding the results > > in it. I think the button is better, but it takes too much space, so I'm > > and what would be the workflow to expand / collapse / run? > an important part of krunner is being able to very quickly type and > execute. > the UI is not fancy, but it is designed for speed. > See mockup in the beginning of the message. But, basically, running anything by just typing and hitting enter wouldn't change much. > > > > then the Nepomuk runner needs tweaking in how it rates results. > > > > So this is the first thing we should do, I guess. > > it's definitely a good starting point. :) > > > What I meant was that I think it's better to wait one or two seconds > after > > the user stops typing so that krunner doesn't start querying with an > > incomplete string. > > that would probably ruin one of the main features of krunner: match as you > type. > Yeah, you're right. > > > I also think it would give focus to the main result, if > > there's one, but I may be wrong. > > it already does. > > > Weird. Should it work if I just type in something and then press the down > > arrow? > > yes... > > > Well, I will stop and think over this project and get back w
Re: SoK idea: Improve krunner result displaying and navigation.
On Friday, April 29, 2011 23:57:57 Luiz Romário Santana Rios wrote: > 2011/4/29 Aaron J. Seigo > > > On Friday, April 29, 2011 00:21:11 Luiz Romário Santana Rios wrote: > > > 2011/4/28 Aaron J. Seigo > > > > > > > On Thursday, April 28, 2011 09:15:08 Luiz Romário Santana Rios wrote: > > > > > Currently, when we type something in, krunner displays the > > > > > results > > > > > as it finds it, without giving a feedback of whether it is > > > > > searching or just didn't find anything. > > > > > > > > that would be a nice addition. > > > > > > > > > It also does not separate the results into its different > > > > > categories > > > > > > > > that's because they are organized by relevance. if they are > > > > sorted into categories, and if there are 4 categories that > > > > match and 5 items in > > > > each > > > > > > category then the best match from the 4th category will be the > > > > 16th > > > > item > > > > > > in the list(!) even though it is more likely to be what the user > > > > wants than most > > > > of the items above it. > > > > > > > > i have yet to see a solution for this problem, but am open to > > > > such a > > > > solution > > > > being offered. > > > > > > Well, I thought about showing only the most relevant results for > > > each > > > category and priorizing the category with the most relevant results. > > > If a > > > > which is almost always going to be the nepomuk search ;) > > > > > user want to see more results for that category, they would just > > > need to expand it. I'll do some mockups for that and will post > > > here. > > > > sounds good; mockups always help. > > Here's one: > http://lh5.googleusercontent.com/_V8ZPvFyTxNc/Tbty2kU7CII/ARs/v_Ut1J > 8P4DQ/01%20-%20Expand%20and%20Shrink%20less%20relevant%20results.png > > It's bad, I know, I suck at making mockups, but it gives part of the idea of > what I mean. wire frame mockups like that one are just fine. they let one concentrate on the structure rather than get distracted by shiny things ;) > Notice that I show two different ways of expanding the results > in it. I think the button is better, but it takes too much space, so I'm and what would be the workflow to expand / collapse / run? an important part of krunner is being able to very quickly type and execute. the UI is not fancy, but it is designed for speed. > > then the Nepomuk runner needs tweaking in how it rates results. > > So this is the first thing we should do, I guess. it's definitely a good starting point. :) > What I meant was that I think it's better to wait one or two seconds after > the user stops typing so that krunner doesn't start querying with an > incomplete string. that would probably ruin one of the main features of krunner: match as you type. > I also think it would give focus to the main result, if > there's one, but I may be wrong. it already does. > Weird. Should it work if I just type in something and then press the down > arrow? yes... > Well, I will stop and think over this project and get back with better > summarized idead and more mockups tomorrow. :) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: SoK idea: Improve krunner result displaying and navigation.
2011/4/29 Aaron J. Seigo > On Friday, April 29, 2011 00:21:11 Luiz Romário Santana Rios wrote: > > 2011/4/28 Aaron J. Seigo > > > > > On Thursday, April 28, 2011 09:15:08 Luiz Romário Santana Rios wrote: > > > > Currently, when we type something in, krunner displays the results > > > > as it finds it, without giving a feedback of whether it is > > > > searching or just didn't find anything. > > > > > > that would be a nice addition. > > > > > > > It also does not separate the results into its different categories > > > > > > that's because they are organized by relevance. if they are sorted into > > > categories, and if there are 4 categories that match and 5 items in > each > > > category then the best match from the 4th category will be the 16th > item > > > in the list(!) even though it is more likely to be what the user wants > > > than most > > > of the items above it. > > > > > > i have yet to see a solution for this problem, but am open to such a > > > solution > > > being offered. > > > > Well, I thought about showing only the most relevant results for each > > category and priorizing the category with the most relevant results. If a > > which is almost always going to be the nepomuk search ;) > > > user want to see more results for that category, they would just need to > > expand it. I'll do some mockups for that and will post here. > > sounds good; mockups always help. > Here's one: http://lh5.googleusercontent.com/_V8ZPvFyTxNc/Tbty2kU7CII/ARs/v_Ut1J8P4DQ/01%20-%20Expand%20and%20Shrink%20less%20relevant%20results.png It's bad, I know, I suck at making mockups, but it gives part of the idea of what I mean. Notice that I show two different ways of expanding the results in it. I think the button is better, but it takes too much space, so I'm not sure. Anyway, it will show more results for that category and hide the other ones. I'll be doing some more mockups, but do you know of some tool to make this easier? > > another thing that might work nicely is to show the favourite items > launched > by default so one doesn't even need to search to launch frequently used > items. > Yes, of course. > > > > > and shows some irrelevant results. > > > > > > by definition, that is not possible. the results are precisely what the > > > runners say match. if the results are not relevant, the runner at fault > > > should > > > be improved. > > > > Well, yes, but sometimes I'm looking for a file and a ton of Nepomuk > stuff > > get in the way, for example. That may a problem with the runner, though. > > > > But what I mean is that, sometimes, the exact match is not the most > relevant > > result. > > then the Nepomuk runner needs tweaking in how it rates results. > So this is the first thing we should do, I guess. > > > > > My idea is to give the user a better feedback of what's happening, > > > > > > telling > > > > > > > them that krunner is searching or that it didn't find anything about > > > > > > those > > > > > > > terms. > > > > > > would be nice, yes :) > > > > I think krunner should, first, just execute the command by default, just > > showing the textbox, and, then, if the user waits a few seconds, all the > > runner results would start to show up. > > what would be the benefit of that? > I didn't explain it quite well, my bad. What I meant was that I think it's better to wait one or two seconds after the user stops typing so that krunner doesn't start querying with an incomplete string. I also think it would give focus to the main result, if there's one, but I may be wrong. > > > > Also, if the user just stands in the > > front of krunner doing nothing, it would be nice to popup a "Type a > command > > or a keyword" text. > > that could be nice, yes. > > > > > which one of these will contain the default action. > > > > > > > > I also intend to make it possible for the user to navigate through > > > > the > > > > results using the arrow keys, instead of tabbing, > > > > > > you already can. :) as long as the user has not been using the arrow > > > keys > > > to > > > back into the history, then you can just hit the down arrow to start > > > going through the entries. > > > > Doesn't work for me. Is this in 4.6 or "trunk"? > > 4.6 and master, both. > Weird. Should it work if I just type in something and then press the down arrow? Well, I will stop and think over this project and get back with better summarized idead and more mockups tomorrow. Cheers. > > -- > Aaron J. Seigo > humru othro a kohnu se > GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 > > KDE core developer sponsored by Qt Development Frameworks > > ___ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > > -- Luiz Romário Santana Rios ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: SoK idea: Improve krunner result displaying and navigation.
On Friday, April 29, 2011 00:21:11 Luiz Romário Santana Rios wrote: > 2011/4/28 Aaron J. Seigo > > > On Thursday, April 28, 2011 09:15:08 Luiz Romário Santana Rios wrote: > > > Currently, when we type something in, krunner displays the results > > > as it finds it, without giving a feedback of whether it is > > > searching or just didn't find anything. > > > > that would be a nice addition. > > > > > It also does not separate the results into its different categories > > > > that's because they are organized by relevance. if they are sorted into > > categories, and if there are 4 categories that match and 5 items in each > > category then the best match from the 4th category will be the 16th item > > in the list(!) even though it is more likely to be what the user wants > > than most > > of the items above it. > > > > i have yet to see a solution for this problem, but am open to such a > > solution > > being offered. > > Well, I thought about showing only the most relevant results for each > category and priorizing the category with the most relevant results. If a which is almost always going to be the nepomuk search ;) > user want to see more results for that category, they would just need to > expand it. I'll do some mockups for that and will post here. sounds good; mockups always help. another thing that might work nicely is to show the favourite items launched by default so one doesn't even need to search to launch frequently used items. > > > and shows some irrelevant results. > > > > by definition, that is not possible. the results are precisely what the > > runners say match. if the results are not relevant, the runner at fault > > should > > be improved. > > Well, yes, but sometimes I'm looking for a file and a ton of Nepomuk stuff > get in the way, for example. That may a problem with the runner, though. > > But what I mean is that, sometimes, the exact match is not the most relevant > result. then the Nepomuk runner needs tweaking in how it rates results. > > > My idea is to give the user a better feedback of what's happening, > > > > telling > > > > > them that krunner is searching or that it didn't find anything about > > > > those > > > > > terms. > > > > would be nice, yes :) > > I think krunner should, first, just execute the command by default, just > showing the textbox, and, then, if the user waits a few seconds, all the > runner results would start to show up. what would be the benefit of that? > Also, if the user just stands in the > front of krunner doing nothing, it would be nice to popup a "Type a command > or a keyword" text. that could be nice, yes. > > > which one of these will contain the default action. > > > > > > I also intend to make it possible for the user to navigate through > > > the > > > results using the arrow keys, instead of tabbing, > > > > you already can. :) as long as the user has not been using the arrow > > keys > > to > > back into the history, then you can just hit the down arrow to start > > going through the entries. > > Doesn't work for me. Is this in 4.6 or "trunk"? 4.6 and master, both. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: SoK idea: Improve krunner result displaying and navigation.
2011/4/28 Aaron J. Seigo > On Thursday, April 28, 2011 09:15:08 Luiz Romário Santana Rios wrote: > > Currently, when we type something in, krunner displays the results as it > > finds it, without giving a feedback of whether it is searching or just > > didn't find anything. > > that would be a nice addition. > > > It also does not separate the results into its different categories > > that's because they are organized by relevance. if they are sorted into > categories, and if there are 4 categories that match and 5 items in each > category then the best match from the 4th category will be the 16th item in > the list(!) even though it is more likely to be what the user wants than > most > of the items above it. > > i have yet to see a solution for this problem, but am open to such a > solution > being offered. > Well, I thought about showing only the most relevant results for each category and priorizing the category with the most relevant results. If a user want to see more results for that category, they would just need to expand it. I'll do some mockups for that and will post here. > > > and shows some irrelevant results. > > by definition, that is not possible. the results are precisely what the > runners say match. if the results are not relevant, the runner at fault > should > be improved. > Well, yes, but sometimes I'm looking for a file and a ton of Nepomuk stuff get in the way, for example. That may a problem with the runner, though. But what I mean is that, sometimes, the exact match is not the most relevant result. > > > My idea is to give the user a better feedback of what's happening, > telling > > them that krunner is searching or that it didn't find anything about > those > > terms. > > would be nice, yes :) > I think krunner should, first, just execute the command by default, just showing the textbox, and, then, if the user waits a few seconds, all the runner results would start to show up. Also, if the user just stands in the front of krunner doing nothing, it would be nice to popup a "Type a command or a keyword" text. > > > Also, the results will be separated into different categories, say, > > programs, files and folders, Nepomuk tags, etc., giving the user the > ability > > of choosing which one of these categories they want to prefer or defer > and > > which one of these will contain the default action. > > > > I also intend to make it possible for the user to navigate through the > > results using the arrow keys, instead of tabbing, > > you already can. :) as long as the user has not been using the arrow keys > to > back into the history, then you can just hit the down arrow to start going > through the entries. > Doesn't work for me. Is this in 4.6 or "trunk"? > > > and to show a scrollbar > > instead of an arrow when there's a lot of results (or maybe a "More" > > button), > > i'd prefer a more button. a scroll bar will ruin the visuals. > > > also shrinking the less relevant results. > > shouldn't matter as they are already lower in the list? > Saving space for more results is one reason to do that. > > > Is this a good SoK idea? Is it too little? > > it might be too little, yes. but there is a ton of stuff that can be done > in > krunner, so a krunner focussed SoK that starts with the above would be just > fine imho. > Maybe I should already start looking krunner's code, so I can see what else should be done. > > > I also thought of a simpler K menu that can run runners in its search, > > letting you put the results in the favorites just by dragging. > > kickoff lets you do this, as does lancelot. > If kickoff does, it does not work here. But, yes, I just checked lancelot and it really does. > > -- > Aaron J. Seigo > humru othro a kohnu se > GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 > > KDE core developer sponsored by Qt Development Frameworks > > ___ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > > -- Luiz Romário Santana Rios ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: SoK idea: Improve krunner result displaying and navigation.
On Thursday, April 28, 2011 09:15:08 Luiz Romário Santana Rios wrote: > Currently, when we type something in, krunner displays the results as it > finds it, without giving a feedback of whether it is searching or just > didn't find anything. that would be a nice addition. > It also does not separate the results into its different categories that's because they are organized by relevance. if they are sorted into categories, and if there are 4 categories that match and 5 items in each category then the best match from the 4th category will be the 16th item in the list(!) even though it is more likely to be what the user wants than most of the items above it. i have yet to see a solution for this problem, but am open to such a solution being offered. > and shows some irrelevant results. by definition, that is not possible. the results are precisely what the runners say match. if the results are not relevant, the runner at fault should be improved. > My idea is to give the user a better feedback of what's happening, telling > them that krunner is searching or that it didn't find anything about those > terms. would be nice, yes :) > Also, the results will be separated into different categories, say, > programs, files and folders, Nepomuk tags, etc., giving the user the ability > of choosing which one of these categories they want to prefer or defer and > which one of these will contain the default action. > > I also intend to make it possible for the user to navigate through the > results using the arrow keys, instead of tabbing, you already can. :) as long as the user has not been using the arrow keys to back into the history, then you can just hit the down arrow to start going through the entries. > and to show a scrollbar > instead of an arrow when there's a lot of results (or maybe a "More" > button), i'd prefer a more button. a scroll bar will ruin the visuals. > also shrinking the less relevant results. shouldn't matter as they are already lower in the list? > Is this a good SoK idea? Is it too little? it might be too little, yes. but there is a ton of stuff that can be done in krunner, so a krunner focussed SoK that starts with the above would be just fine imho. > I also thought of a simpler K menu that can run runners in its search, > letting you put the results in the favorites just by dragging. kickoff lets you do this, as does lancelot. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
SoK idea: Improve krunner result displaying and navigation.
Currently, when we type something in, krunner displays the results as it finds it, without giving a feedback of whether it is searching or just didn't find anything. It also does not separate the results into its different categories and shows some irrelevant results. My idea is to give the user a better feedback of what's happening, telling them that krunner is searching or that it didn't find anything about those terms. Also, the results will be separated into different categories, say, programs, files and folders, Nepomuk tags, etc., giving the user the ability of choosing which one of these categories they want to prefer or defer and which one of these will contain the default action. I also intend to make it possible for the user to navigate through the results using the arrow keys, instead of tabbing, and to show a scrollbar instead of an arrow when there's a lot of results (or maybe a "More" button), also shrinking the less relevant results. Is this a good SoK idea? Is it too little? I also thought of a simpler K menu that can run runners in its search, letting you put the results in the favorites just by dragging. -- Luiz Romário Santana Rios ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
