Brett Porter wrote:
Hi,
I'd like to schedule this one for beta-2, and can probably do the work
on it. I would probably run through the rest of the
admin/configuration screens and file other issues I find too.
It involves:
1) separate the forms/actions (or at least exclude the fields that are
not relevant when editing the remote repos)
2) treat the URL (remote) as a URL and the location (managed) as a
path. Don't munge anything.
3) I think we should consider separating them into different lists in
the configuration again.
It would fix:
- causing both subtle bugs (particularly in the URL handling), and
- a confusing user experience (settings appearing that are irrelevant
to remote repositories in the edit form).
I used to have this in the configuration as an abstract base class
containing the basic repository information (so much of the logic and
even pages can still be shared), but then extended differently for the
different types of repositories.
Does anyone have any thoughts on this?
+1 to this.. there have been some confusion to users about the remote
and managed repositories, I think most especially with the Scannable
field for the remote repositories.
Cheers,
Brett
Thanks,
Deng
