(Created page with '= Developing an awesome bar for rekonq<br> = As we are having some problems to organize our work on this stuff, I thought to write here the things I was thinking abou...') |
(→Developing an awesome bar for rekonq: Adeed tab to serch) |
||
| Line 9: | Line 9: | ||
#'''Add a notification area'''. On the right of the urlbar. With a simple API and able to show clickable icons about feeds, ssl infos, kget urls and "whatever you want". We have some examples of this in the plasma desktop. And a "libnotification". We need to study and document a bit about<br> | #'''Add a notification area'''. On the right of the urlbar. With a simple API and able to show clickable icons about feeds, ssl infos, kget urls and "whatever you want". We have some examples of this in the plasma desktop. And a "libnotification". We need to study and document a bit about<br> | ||
#'''implement show results animation'''. The best thing here is probably jonas implementation. It was [http://gitorious.org/~jondeandres/rekonq/jondeandres-clone/commits/runners here].'''<br>''' | #'''implement show results animation'''. The best thing here is probably jonas implementation. It was [http://gitorious.org/~jondeandres/rekonq/jondeandres-clone/commits/runners here].'''<br>''' | ||
| − | #'''Implement detect results engine'''. We can use some runners here or reuse the UrlResolver class in the [http://gitorious.org/rekonq/mainline/commits/LastBar LastBar] branch. (Remember: republish it). | + | #'''Implement detect results engine'''. We can use some runners here or reuse the UrlResolver class in the [http://gitorious.org/rekonq/mainline/commits/LastBar LastBar] branch. (Remember: republish it). <br> |
| − | + | #'''Implement tab-to-search'''. User presses tab to search the first domain in the awesomebar. similar to what chromium does. | |
As we are having some problems to organize our work on this stuff, I thought to write here the things I was thinking about for the rocking new rekonq bar.
I'd like to rewrite all code from scratch here, adding features in an incremental way. These are my points, comments and suggestions are welcome:
About #3 and #4 points, I think it will be better to maintain the "showing animation" & the "results engine" code separated. Again, comments and suggestions are welcome :)
KDE TechBase 