Implement UI / UX for more usable IRC configurations

[bnvk]

The following are the proposed UI / UX tasks needed to make sense of the backend configurations of proposed in issue #412 to Shout application

Public Sign In

• User is asked for only Name and generates suggest nickname
• User can click "more options" for detailed IRC settings

User Sees (upon signing in)

• Automatically signed into one or multiple "fixed" Networks + Channels
• Interface hides the ability to leave these channels depending on specifications
• If only has one server (and cannot join others) hide the idea of "Server" altogether from UI
• If only has one channel (and cannot join others) hide the idea of "Channels" altogether from UI
• Auto hiding and showing and user controlled of sidebar as per above settings

[jdittrich]

What about saving the channels a user visited? I assume that most users visit certain channels frequently.

[bnvk]

@jdittrich that definitely makes for a good user experience. It will depend on the configuration of a Slick/Shout instance- using the "non-public" account there is already this feature for "user accounts"

[jdittrich]

Great. I don’t know how prominent it is in the non-public account, but I assume this is an important feature. As well, for the public account, one could probably use a cookie (or the like) to save the channel names.

[simonv3]

For bullet #1. I would argue that a user can submit a username. I think most people are familiar with the concept, and that it having something being auto generated would only confuse things.