[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-frameworks-devel
Subject:    D23384: [WIP] Adding support for mounting KIOFuse URLs for applications that don't use KIO
From:       Nathaniel Graham <noreply () phabricator ! kde ! org>
Date:       2019-12-01 18:35:42
Message-ID: c0320b177d575543edd0c25230d20eb7 () localhost ! localdomain
[Download RAW message or body]

[Attachment #2 (text/plain)]

ngraham added a comment.


  In D23384#570125 <https://phabricator.kde.org/D23384#570125>, @dfaure wrote:
  
  > @ngraham AFAIK gnome has a trick where a fuse mount is created, its path is \
passed to the application being started, and the application, if it supports gvfs, \
re-translates that into a URL and uses that instead if it makes more sense. This way \
"dumb" apps get a local file (with all the limitations of doing synchronous I/O over \
the network) and network-transparent applications use URLs.  >  On the other hand, \
the KDE logic is "if the app takes %f and not %u in the Exec line, it doesn't support \
remote URLs, so we need to download the file first" (that's done by kioexec). If you \
see a "download first" check if kioexec is running. But if it's the app doing it, \
then I have no idea.  
  
  `kioexec` is not running during any of these lengthy downloads. Totem, VLC, and \
SMplayer all have %U in their desktop files, FWIW.  
  We may want to rethink this logic anyway. Any app that doesn't integrate with \
ioslaves should get the FUSE path rather than a locally-downloaded file, irrespective \
of whether or not its desktop file has %f or %u IMO. There are just too many \
disadvantages to the locally downloaded file approach, which is why we're doing this \
FUSE thing in the first place.  
  Perhaps the "lengthy local download first" issue is caused by not having \
https://invent.kde.org/kde/kio-fuse/merge_requests/2 yet.

REPOSITORY
  R241 KIO

REVISION DETAIL
  https://phabricator.kde.org/D23384

To: feverfew, fvogt, davidedmundson, dfaure, ngraham
Cc: sitter, davidedmundson, kde-frameworks-devel, ngraham, LeGast00n, GB_2, michaelh, \
bruns


[Attachment #3 (text/html)]

<table><tr><td style="">ngraham added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: \
right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: \
#F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: \
inline-block; border: 1px solid rgba(71,87,120,.2);" \
href="https://phabricator.kde.org/D23384">View Revision</a></tr></table><br \
/><div><div><blockquote style="border-left: 3px solid #8C98B8;  color: #6B748C;
          font-style: italic;
          margin: 4px 0 12px 0;
          padding: 8px 12px;
          background-color: #F8F9FC;">
<div style="font-style: normal;
          padding-bottom: 4px;">In <a \
href="https://phabricator.kde.org/D23384#570125" style="background-color: #e7e7e7;  \
border-color: #e7e7e7;  border-radius: 3px;
          padding: 0 4px;
          font-weight: bold;
          color: black;text-decoration: none;">D23384#570125</a>, <a \
href="https://phabricator.kde.org/p/dfaure/" style="  border-color: #f1f7ff;
              color: #19558d;
              background-color: #f1f7ff;
                border: 1px solid transparent;
                border-radius: 3px;
                font-weight: bold;
                padding: 0 4px;">@dfaure</a> wrote:</div>
<div style="margin: 0;
          padding: 0;
          border: 0;
          color: rgb(107, 116, 140);"><p><a \
href="https://phabricator.kde.org/p/ngraham/" style="  border-color: #f1f7ff;
              color: #19558d;
              background-color: #f1f7ff;
                border: 1px solid transparent;
                border-radius: 3px;
                font-weight: bold;
                padding: 0 4px;">@ngraham</a> AFAIK gnome has a trick where a fuse \
mount is created, its path is passed to the application being started, and the \
application, if it supports gvfs, re-translates that into a URL and uses that instead \
if it makes more sense. This way &quot;dumb&quot; apps get a local file (with all the \
limitations of doing synchronous I/O over the network) and network-transparent \
applications use URLs.<br />  On the other hand, the KDE logic is &quot;if the app \
takes %f and not %u in the Exec line, it doesn&#039;t support remote URLs, so we need \
to download the file first&quot; (that&#039;s done by kioexec). If you see a \
&quot;download first&quot; check if kioexec is running. But if it&#039;s the app \
doing it, then I have no idea.</p></div> </blockquote>

<p><tt style="background: #ebebeb; font-size: 13px;">kioexec</tt> is not running \
during any of these lengthy downloads. Totem, VLC, and SMplayer all have %U in their \
desktop files, FWIW.</p>

<p>We may want to rethink this logic anyway. Any app that doesn&#039;t integrate with \
ioslaves should get the FUSE path rather than a locally-downloaded file, irrespective \
of whether or not its desktop file has %f or %u IMO. There are just too many \
disadvantages to the locally downloaded file approach, which is why we&#039;re doing \
this FUSE thing in the first place.</p>

<p>Perhaps the &quot;lengthy local download first&quot; issue is caused by not having \
<a href="https://invent.kde.org/kde/kio-fuse/merge_requests/2" class="remarkup-link" \
target="_blank" rel="noreferrer">https://invent.kde.org/kde/kio-fuse/merge_requests/2</a> \
yet.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R241 \
KIO</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a \
href="https://phabricator.kde.org/D23384">https://phabricator.kde.org/D23384</a></div></div><br \
/><div><strong>To: </strong>feverfew, fvogt, davidedmundson, dfaure, ngraham<br \
/><strong>Cc: </strong>sitter, davidedmundson, kde-frameworks-devel, ngraham, \
LeGast00n, GB_2, michaelh, bruns<br /></div>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic