xpra icon
Bug tracker and wiki

Opened 6 years ago

Closed 4 years ago

Last modified 13 months ago

#407 closed task (fixed)

handle .xpra file associations on osx

Reported by: Antoine Martin Owned by: Antoine Martin
Priority: minor Milestone: 0.17
Component: platforms Version:
Keywords: osx Cc:

Description (last modified by Antoine Martin)

We already have this on win32 and Linux, so it makes sense to add it to osx.

Links:

Attachments (2)

Info.plist (2.0 KB) - added by Antoine Martin 6 years ago.
first attempt at making a new Info.plist with UTExportedTypeDeclarations
Info.2.plist (1.9 KB) - added by Antoine Martin 4 years ago.
file association works with this file - but OSX hides the actual filename somewhere else, of course

Download all attachments as: .zip

Change History (12)

comment:1 Changed 6 years ago by Antoine Martin

Description: modified (diff)

Changed 6 years ago by Antoine Martin

Attachment: Info.plist added

first attempt at making a new Info.plist with UTExportedTypeDeclarations

comment:2 Changed 4 years ago by Antoine Martin

Status: newassigned

I think this depends on #641.

comment:3 Changed 4 years ago by Antoine Martin

scheduling for 0.16

comment:4 Changed 4 years ago by Antoine Martin

Milestone: future0.16

comment:5 Changed 4 years ago by Antoine Martin

Milestone: 0.160.18

Blocked by #641.

As per http://stackoverflow.com/a/18988753/428751, lsregister can be useful:

alias lsregister='/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister'
lsregister -lint -f ./Xpra.app
lsregister -dump -f ./Xpra.app
Last edited 4 years ago by Antoine Martin (previous) (diff)

Changed 4 years ago by Antoine Martin

Attachment: Info.2.plist added

file association works with this file - but OSX hides the actual filename somewhere else, of course

comment:6 Changed 4 years ago by Antoine Martin

Owner: changed from Antoine Martin to alas
Status: assignednew

Done in r12380.
Can easily be tested by double-clicking on a session file like this one:

host=192.168.0.1
port=10000
mode=tcp
autoconnect=true

The OSX client should be launched and connect to the given server.
Will follow up in #1163 for handling xpra://username@HOST:PORT/ urls on osx.

@afarr: not sure you really care about this use case, though it might be useful for easily connecting to servers by pre-defining some commonly used session files and leaving them on the desktop.

comment:7 Changed 4 years ago by alas

Owner: changed from alas to Antoine Martin

Hmm... setting up a test.xpra file with the above content (with more appropriate numbers) in a clickable place... double clicking launches the launcher, but doesn't connect until I then click the launcher's connect button.

0.17.0 r12380 client against fedora 23 server.

Initial launch attempt prompted me with a “Xpra” can’t be opened because it is from an unidentified developer., not-unexpected, message... after going through rigamarole to allow Xpra to run, the initial attempt launched the launcher with empty fields.

Second double-click triggered the launcher firing with the fields filled, but still required a button click.

Third try, though (after having successfully connected on the previous try) worked as expected.

  • Just out of curiosity (for extra-credit?) I also added a password=password line in the .xpra file, between the mode & autoconnect lines, and tried once more and it worked as expected also!

Passing this back to you in case there're any details I missed... but looks ready to close.

comment:8 Changed 4 years ago by Antoine Martin

Resolution: fixed
Status: newclosed

FYI: the order of the options in session files does not matter. (and you can also specify encoding, etc..)

I did try to connect without a password and the launcher dialog did show up, with an error showing "connection timed out". I guess we should try to capture the real reason for the failure ("missing / wrong password"), but this will do for now.

comment:9 Changed 4 years ago by Antoine Martin

Milestone: 0.180.17

comment:10 Changed 13 months ago by Antoine Martin

Painful updates to this ugly code done in r20670 for #1762.

Note: See TracTickets for help on using tickets.