2) Encrypting/Deciphering would need to be dynamic. As would the sending and receiving of messages.
3) User input would be the primary cause of the dynamic events. The database will also cause events if there are new messages and management thereof.
4) I will be primarily using click events, key events, and on page load events.
5) I will structure events by adding listeners in the <head> section and directing them to the appropriate functions.
6) There will be plenty of forms to check. I’ll check if the user entered text into the fields, check if the input is valid, and alert the user of any possible errors and to which field the error arises from.
7) I will use asynchronous data to decipher data and possibly as a remembered user auto-login based on a cookie.
I wrote two versions of the exercise for this week. The first one just generated a set form. The second now generates a form based on user input by splitting the input line by line. I coded one function which controls the input while directing the flow to other functions which generate each input type. I used the large size for the grid view which looks a bit too large for the checkboxes.
If a field is empty, an alert is displayed:
After the alert, the border color of the field changes to red:
If any or all fields are empty, another alert dialog is displayed:
And, that is as far as I got.