Power to the people!
There is now 2 ways to set the theme: on the app config file (defaults
for all users) and in the user settings.
All CSS files present in the `client/themes` folder will be given as
choices to the users.
This is temporary (as in, temporary for a fairly long time) until we
have proper theme management.
- Move markup around to make the loading page a window of its own
instead of a sub-window of `#chat`
- Remove inline styling in loading page
- Use same styling than other non-messages windows for title and text
- Add a `z-index` to the loading page to hide the message input
- Vertically align the sign in page title with all other titles
- Make sure all `h1.title`s are bottom-margined consistently and remove
negative margin on the Settings page title to align with the Connect
page title (Reverting/Improving this should be done at the `h2` level
instead)
Also:
- Remove burger menu icon on mobile version of sign-in page
- Add the .signed-out class to the initial body instead of only when
sign-in has failed
- Remove hiding connect and logout button icons, which was buggy and is
now useless anyway
- Simplify `checked` attributes
- Use double quotes when possible
- Remove `class` duplicates
- Fix labels in password settings
- Remove `<small>` around version number
- refactor clientManager.js to allow configuration parsing as a serparate
function.
- refactor clientManager.js to add configuration writing function.
- add server.js changes to allow for new password-change functionality
- add password change ui to "settings" screen
- refactor client.js to use new clientManager functionality for saving
the configuration files
contains three small changes to use relative urls instead of absolute rooted at /
* favicons in index.html
* badge and pop sound in lounge.js
* the url for the socket.io endpoint
Typical use with nginx:
location /path/ {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_pass http://localhost:9000/;
}
those trailing / are important.
It appears LastPass looks for the use of the GET method in forms on the page to determine if it is secure or not. Since Shout never actually submits any of the forms, no method is set, which means the default of GET is used. Changes form methods to POST to quiet the warning. Should fix#648
