In this dialog, can we change the description to say that the first path below "Standard Library" is the default save location. Can we also explain that the Standard Library is the location from where packages will be loaded first followed by the rest of the paths.

In this dialog, can we change the description to say that the first path below "Standard Library" is the default save location. Can we also explain that the Standard Library is the location from where packages will be loaded first followed by the rest of the paths.

Good point. I totally missed that text. I will try to come up with some wording that covers the new behavior.

In this dialog, can we change the description to say that the first path below "Standard Library" is the default save location. Can we also explain that the Standard Library is the location from where packages will be loaded first followed by the rest of the paths.

Good point. I totally missed that text. I will try to come up with some wording that covers the new behavior.

this is actually covered in:
https://jira.autodesk.com/browse/DYN-3571

but fixing it now is even better.

I think it may ultimately change, but it's good to make it as correct as possible IMO.

@sm6srw - theres one AC that was included in the task that I don't see in your description:
if std.lib is disabled, the entry in the ui should appear disabled - what do you think of this one? We could also leave this for later depending on if we expose those options to the UI as well.

This looks pretty solid to me - one thought that occurs to me is that depending on our final strategy for dealing with conflicts during package install (as opposed to Dynamo startup) - that we may reevaluate std.lib's location (first or last), additionally feedback from UX may lead us to rethink this anyway.

Given that, do you think the position is difficult to change after this PR or it will be pretty straightforward? - I was wondering if the logic could be abstracted into a position field somewhere we could set.

@sm6srw - theres one AC that was included in the task that I don't see in your description:
if std.lib is disabled, the entry in the ui should appear disabled - what do you think of this one? We could also leave this for later depending on if we expose those options to the UI as well.

Thanks, I missed this one. I will take a look.

This looks pretty solid to me - one thought that occurs to me is that depending on our final strategy for dealing with conflicts during package install (as opposed to Dynamo startup) - that we may reevaluate std.lib's location (first or last), additionally feedback from UX may lead us to rethink this anyway.

Given that, do you think the position is difficult to change after this PR or it will be pretty straightforward? - I was wondering if the logic could be abstracted into a position field somewhere we could set.

It is a small change. It happens in two places right now. But I have been thinking that it might be possible to remove that logic all together now from the PackageLoader with these changes. I think I will take a look at that.