<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Sans Serif'; font-size:7pt; font-weight:400; font-style:normal;">On Friday 31 July 2009 22:41:12 Lionel Chauvin wrote:<br>
> I found this discussion:<br>
> http://www.archivum.info/kfm-devel@kde.org/2005-10/00016/PATCH:_webshortcut<br>
>s<br>
><br>
> I understand now why the delimiter was not replaced by a space by default.<br>
> One reason is because webshortcuts are also usable in krunner and they are<br>
> in conflict with commands.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I don't understand it, instead. I think these webshortcuts could be considered like real protocols, following the standard url = scheme colon path.<br>
Bah.. perhaps it's just me..<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> Ok, for 0.2 we can let webshortcuts broken when the delimiter is space.<br>
><br>
> One reason why space was not choosen for default is for queries like: "kde<br>
> xcomposite". We don't want launch the kde api website.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Space separator is definitely a non-sense for me<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> I think our futur awsome bar must re-think webshortcuts and use opensearch<br>
> to remove ambiguities.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I'm not sure about this. In my <span style=" text-decoration: line-through;">idea</span> vision we have to provide two different runners here. One for google search and another (existant) for webshortcuts.<br>
That's all! Ordering query results, I'm sure Ivan can help us to "magically" remove the "gg ciao" searches.. ;)<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>-- <br>
Andrea Diamantini,<br>
rekonq project<br>
WEB: http://rekonq.sourceforge.net<br>
IRC: adjam_AT_freenode<br>
GPG Fingerprint: 57DE 8E32 7D1A 0E16 AA52 59D8 84F9 3ECD DBF9 730F<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p></body></html>