8/16/24 – Rich Text Protocol

Summary: Today we started by finishing our review of our plaintext protocols (Yesterday’s Activity). We then discussed our next project Rich Text Protocol.

The Rich Text Protocol is very similar to our Plaintext Protocol but must include support for the following features…

  • Size: small, medium large
  • Color: black, red, green, blue
  • Style: none, boldunderline, italic
  • Script: noscript,  subscript, superscript

The default text is medium size, black, no styles, no script.

Your protocol will be evaluated on the same following aspects…

  • Functionality – The protocol accomplishes the task at hand. It always works.
  • Clarity – The protocol is written clearly and is easy to understand
  • Formatting – The document looks polished and professional.
  • Efficiency – The protocol uses as few bits as possible.
  • Ease of Use – It is fast and easy to use.
  • Examples – The protocol includes at least one example.

Homework: Rich Text Protocols are due Tuesday at 8:00am (submit via Google Classroom)(CA-05)

8/14/24 – Plaintext Protocol Workday

Summary: Today we worked to finish our Plain Text Protocol in Google Classroom (due Tomorrow before class)(CA-03).

Write a protocol (set of instructions) on how to turn plaintext into binary and vice versa. You protocol should include the ability to write the following

  • a-z
  • A-Z
  • Punctuation . , ? ! “
  • Numbers 0-9
  • Basic Math Operations + – * /
  • And of course a “blank space” to separate words.

Be sure to include at least one example in your protocol to help illustrate how it works.

Rubric: Your work must meet the following requirements…

  • Functionality – The protocol accomplishes the task at hand. It always works.
  • Clarity – The protocol is written clearly and is easy to understand
  • Formatting – The document looks polished and professional.
  • Efficiency – The protocol uses as few bits as possible.
  • Ease of Use – It is fast and easy to use.
  • Examples – The protocol includes at least one example.

Homework: Complete your Plaintext Protocol in Google Classroom

8/13/24 – Introduction to Plaintext Protocol

Summary: Today we started by doing some bellwork in Today’s Activity and then went back to review yesterday’s test questions (we did not do the candy protocol). We then made sure that everybody created the following accounts below…

Finally we introduced the Plaintext Protocol (due Thursday)(see Google Classroom for details).

Homework: Plaintext Protocol (due Thursday)

8/8/24 – Shortcuts with Hexadecimal

Summary: Today we learned about why hexadecimal is useful and shortcuts to convert between binary and hexadecimal.

  • Byte – Typically 8 bits
  • Data – Any type of information. Could be represented using words, numbers, bits or other forms.
  • Overflow Error – An error that occurs when you don’t have enough room to store your data.

At the end of class we drew isometric terominos and tried to rotated them around the x, y, and z axis.

Homework: none