-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ASPDM URI Protocol & Package Sources #10
Comments
I see, this seems to be a good idea. Im not sure I understand what 'domain' and 'name' is exactly. |
The domain name is just the host name of where the package repository is located, e.g. |
Oh ok I thought them as two separate things... Anyway... Commit : 307e163 Seems to be working well, in-GUI pack source switching will come with time... Working examples :
As for multiple repositories, that will be dealt with in time... |
Nice, this is what I was thinking about. |
In-GUI Packsource switching finally added 👍 Commit: 3c9e060 |
As a first iteration of this functionality, it's OK. In the future, we might want to present all the packages from all sources in the same list. |
Good idea, will do. 🍔 |
How should the different sources be displayed, if they were to be all in the same list? Should there be an extra Column marking the Package source? |
Yes. |
Don't know if I've missed something, but it seems to work fine. 👍 |
Update to this... Examples:
|
updated rHandler see #10, bugfix in Settings_Validate(), PackRemover was working incorrectly, PackCache installing and local repo managing still needs to be worked on.
The current URI format should include the host name from which the package is to be downloaded (this is mandatory for it to be a correctly formed URI). IMO it should read like this:
aspdm://domain.name/packageid
This also brings up another issue: I think it should be possible to add other additional package repositories in the ASPDM Client. It could be done in a similar way to what Eclipse does (look at the 'Work with' DDL):
The text was updated successfully, but these errors were encountered: