maidsafe-archive / system_uri Goto Github PK

• OS: Ubuntu 16.10 64-bits
• rustc --version: rustc 1.16.0 (30cf806ef 2017-03-10)
• cargo --version: cargo-0.17.0-nightly (f9e5481 2017-03-03)
• Terminal:

$ cargo build
   Compiling ffi_utils v0.1.0 (https://github.com/maidsafe/safe_client_libs.git?branch=dev#3ba1cb67)
error: struct field shorthands are unstable (see issue #37340)
  --> /home/daniel/.cargo/git/checkouts/safe_client_libs-e3345e9360262bab/3ba1cb6/ffi_utils/src/catch_unwind.rs:54:21
   |
54 |                     error_code,
   |                     ^^^^^^^^^^

error: aborting due to previous error

error: Could not compile `ffi_utils`.

To learn more, run the command again with --verbose.

Having a / in the name provided breaks installation on Linux. Supposedly because it is being interpreted as a path that doesn't exist.

E.g. on docs.rs the open function is documented as:

Open a given URI on Linux systems

We should have more generic and extensive rustdoc for this function (and install too).

On macOS, specifically with the safe browser, registering a custom protocol works, but it's not guaranteed to open the registering app for that URI. It seems that with different app versions installed, or moved to different parts of the OS (through app translocation, eg), it's currently not guaranteed that a registered URI will open the registering app...

I'm not sure how OSX determines what to open (version... location... something else...). And I'm not sure if there's something on the app level that ought to/could be done to avoid this.

eg:

~/Applications/safe-browser.app opens, and registers itself to handle safe-auth://, BUT ~/downloads.safe-browser.app also exists so maybe OSX decides to open that for safe-auth:// urls, even though we just registered the former as the new handler. :(

I managed to get this to work on MacOS. (Would be helpful to add a line to the readme stating that you have to bundle the app for this to work on MacOS.)
The app does open but if I provide an argument to the link, e.g. "scheme://ARG", is there a way for me to use that argument inside my app?