When adding a project to SparkleShare, it's often nice to copy a full URI from somewhere and paste it into the box. Right now, you have to edit the URI to pieces to make it work.
SparkleShare should be able to tease out the relevant bits, even if it's redundant.
That is: Pasting a full URL in the remote path (or address if it is available) should split out the host & protocol from the path — probably even on the fly. At least it should check the URL and fix it after hitting add.
It should support both HTTPS and GIT URLs, like so:
git@github.com:hbons/SparkleShare.git
https://github.com/hbons/SparkleShare.git
In both cases, it's supposed to be hbons/SparkleShare.git for the path. Even if the resource needs to be the git@github.com ssh method instead of the https method, it should recognize the https URI and fix it.
Likewise, if one were to paste the URI into the address field for "own server", it should check the URI and split it apart into address and path — probably even on keypress or input field blur.
An alternate design would be to have one entry field which accepts a URI and could also assume a path fragment for recognized services, like if GitHub or GitLab is selected. It's probably simpler and easier for everyone.
When adding a project to SparkleShare, it's often nice to copy a full URI from somewhere and paste it into the box. Right now, you have to edit the URI to pieces to make it work.
SparkleShare should be able to tease out the relevant bits, even if it's redundant.
That is: Pasting a full URL in the remote path (or address if it is available) should split out the host & protocol from the path — probably even on the fly. At least it should check the URL and fix it after hitting add.
It should support both HTTPS and GIT URLs, like so:
git@github.com:hbons/SparkleShare.githttps://github.com/hbons/SparkleShare.gitIn both cases, it's supposed to be
hbons/SparkleShare.gitfor the path. Even if the resource needs to be thegit@github.comssh method instead of the https method, it should recognize the https URI and fix it.Likewise, if one were to paste the URI into the address field for "own server", it should check the URI and split it apart into address and path — probably even on keypress or input field blur.
An alternate design would be to have one entry field which accepts a URI and could also assume a path fragment for recognized services, like if GitHub or GitLab is selected. It's probably simpler and easier for everyone.