<div class="gmail_quote">2010/4/13 Lionel Chauvin <span dir="ltr"><<a href="mailto:megabigbug@yahoo.fr">megabigbug@yahoo.fr</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">> The "problem" is that I had to change some behavior, in example the first<br>
> item selection on popup. This to let rekonq use KUriFilter to resolve a<br>
> typed url WITHOUT suggestions. That is the problem here.<br>
<br>
</div>I am not sure I understand what you want to do.<br>
<br>
If the first item is not selected, rekonq can't explain to the user what is<br>
done when he press enter. </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
For instance, he can't understand why "<a href="http://www.kde-apps.org" target="_blank">http://www.kde-apps.org</a>" is launched<br>
when he types "kde-apps" and why it processes a google search if he types<br>
"kde".<br></blockquote><div><br></div><div>That's the way firefox works, for instance. I don't say this is the best way to do. Indeed I said the opposite.</div><div>I'm saying that this is the way things work well. And to reenable the other way, we need to no more fail </div>
<div>on UTF-8 resolutions.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
It should always propose at least one suggestion. KUriFilter can help to build<br>
this suggestion or perhaps not, I didn't study this point. If it is too slow<br>
for process that, why we should keep it ?<br></blockquote><div><br></div><div>We have to keep KUriFilter, otherwise we cannot ensure things will work.</div><div>In a Qt-only environment you do something like:</div><div><br>
</div><div>QString (typed by user) --> GuessUrlFromUserInput --> QUrl --> load</div><div><br></div><div>This chain works with real urls because GuessUrlFromUserInput is good and fast to "guess" QUrls, but it will fail on "puzzle urls"</div>
<div>eg: "<a href="http://google.com/search?q=">google.com/search?q=</a>" + something user typed, because of the encodings after the resolution.</div><div><br></div><div>In a KDE environment you need something like: </div>
<div> </div></div>QString (typed by user) --> KUriFIlter --> KUrl --> load<div><br></div><div>This will work in the same way than the Qt chain and better, because:</div><div>- it supports kde web shortcuts (eg: "gg:string" urls)</div>
<div>- it really resolv and/or ping urls instead of "trying to guess" them.</div><div><br></div><div>so, typing "ciao", GuessUrlFromString loads non extant "<a href="http://ciao">http://ciao</a>", while KUriFilter try to understand if the host "ciao" exists. If it exists it loads "<a href="http://ciao">http://ciao</a>", otherwise it searches the default search engine for it.</div>
<div>Anyway this costs time, that is hardcoded exactly to 5 seconds waiting for DNS and/or ping response.</div><div><br></div><div><br></div><div>All this to explain why KUriFilter is a must for every KDE network application. Hope this helps.</div>
<div><br></div><div>Regards,</div>