> Sure you don't need? I have 4 pcs at home called (without fantasy) > "server", "mediacenter" , "blackbox" (my notebook) and "wifebox" :). And a > router called "router". > Typing one of these names rekonq searched google for them as first result, > while now it rightly loads them.
just type http://server the first time the second time it will be in the history, and inserted as first item of the list. we can't interogate a dns each time the user press a key, the best we can do is interogate when he stops typing. > And I think the same is valid for words like "localhost" and so on. > Basically this is why the isHttp() check is unuseful. > > Try to guess user ideas is unsane. unsane ? if we don't do that, all the concept of one bar (instead of two bar: history and search) is unsane. > And someone will always find one case > where he prefers one solution over the others proposed. > I strongly suggest to just show engines results as they are implemented: I disagree with that. > > The only interesting thing of KUriFilter is protocol detection: for > > instance gg: kde: http: etc. > Again, no. Please, read again my previous mail. Without it more than one > half of the url typed will fail to load. I agree it is useful after the user press enter, but only the protocol detection is interesting when he is typing. _______________________________________________ rekonq mailing list [email protected] https://mail.kde.org/mailman/listinfo/rekonq
