Mimi Yin wrote:
Some users may want or need to disable SSL when accessing the Hub.

Good point, so we should keep the SSL and Port fields around so people can futz with them.

As Morgen pointed out, this isn't necessary as alternate MC configurations can use an alternate Chandler Server configuration. If we drop port+SSL, the page goes back to being even cleaner.

I'm also thinking through issues of default-ness, interaction with settings files, etc. There were a surprising number of caveats and related issues when we futzed with accounts recently.

What does this mean in concrete terms? How can we be strategic about changes to the accounts dialog?

QA the implementation and review the workflows well during migration testing. Aparna probably has the best example so far: re: "default-ness". Anyone not using Hub can't set up a working default sharing account.

+ We wouldn't be changing which account was the default account. Chandler Hub sharing would still be the default sharing account.

Yes, but before the "Chandler Hub" account could be used with servers other than our Hub by changing the settings.

+ We are changing:
- Sign up text
- What the Sign up text links to
- Removing the server and path fields
- Adding a new account type: Chandler Server sharing

Which of these changes do you feel might cause complications with settings files, default-ness, etc?

Primarily the adding of a new account type, especially only one of which can be the default where the user can't change the default or delete it. The implementation may also have a lurking bug or two that we should check carefully. It needs to be restored from settings properly, from dump/reload, etc. Needs to do the right thing with settings and reload when both Hub and Server are set, etc. All very manageable.

I think the design will work out fine, and we'll just accept some of these interactions before Preview. It optimizes for our tightly-coupled ecosystem, at the expense of a making it a bit harder to work with a modular ecosystem. Post-preview, we'll (probably) add features to allow changing the default and that disadvantage will go away.

-- Jared
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

Reply via email to