<commit_before>---
title: Login/Unlock
layout: component
contributors:
    - name: <NAME>
      github: aherco
    - name: <NAME>
      github: jsannyjr
    - name: <NAME>
      github: evanhessler
    - name: <NAME>
      github: danielsjarif
    - name: <NAME>
      github: averdin2
---
<p class="lead">The gateway to knowledge at your fingertips, the Login/Unlock screen for Windows 7 and OS X is the gate to the wonders of computers.</p>

<h2>Typical Behavior</h2>

  <blockquote>A desktop or laptop computer’s log in screen is likely to be recognizable whether it is run on Windows, Linux, or OSX. While the aesthetics may change from platform to platform, the same idea and function is prevalent in all platforms. Each screen has a number of possible users that can be accessed. Each interface has the options of restarting or shutting down the system as well. One has the option of clicking on a list of users. If the account is unsecured, the user is logged in; however, all platforms have security features which may or may not behave differently. Please see <a href="#platform-specific-instances">platform-specific instances</a> for more.</blockquote>

<h4> Events </h4>
  <blockquote>To be written...</blockquote>

<h4> State Diagram </h4>
  <img src = "https://enricohomann.files.wordpress.com/2011/11/paper_2011_nov_09_statemachine_status_002.png" alt = "State Diagram">


<br/>
<br/>

<h4> Component in Action </h4>

<div class="row">
  <div class="col-sm-6"><commit_msg>Added events section<commit_after>---
title: Login/Unlock
layout: component
contributors:
    - name: <NAME>
      github: aherco
    - name: <NAME>
      github: jsannyjr
    - name: <NAME>
      github: evanhessler
    - name: <NAME>
      github: danielsjarif
    - name: <NAME>
      github: averdin2
---
<p class="lead">The gateway to knowledge at your fingertips, the Login/Unlock screen for Windows 7 and OS X is the gate to the wonders of computers.</p>

<h2>Typical Behavior</h2>

  <blockquote>A desktop or laptop computer’s log in screen is likely to be recognizable whether it is run on Windows, Linux, or OSX. While the aesthetics may change from platform to platform, the same idea and function is prevalent in all platforms. Each screen has a number of possible users that can be accessed. Each interface has the options of restarting or shutting down the system as well. One has the option of clicking on a list of users. If the account is unsecured, the user is logged in; however, all platforms have security features which may or may not behave differently. Please see <a href="#platform-specific-instances">platform-specific instances</a> for more.</blockquote>

<h4> Events </h4>
  <blockquote>The main purpose of login/unlock screens is to provide a security barrier against unwanted users. The primary way to accomplish this is to have a text entered password or passcode that is required for entry into the system. Hence, the most relevant events for the majority of login and unlock systems are for entering in text, clearing text, errors (for denying the password), and accepts (for accepting the passcode).</blockquote>

<h4> State Diagram </h4>
  <img src = "https://enricohomann.files.wordpress.com/2011/11/paper_2011_nov_09_statemachine_status_002.png" alt = "State Diagram">


<br/>
<br/>

<h4> Component in Action </h4>

<div class="row">
  <div class="col-sm-6">
{'fraction_non_alphanumeric': 0.0878438331854481, 'fraction_numerical': 0.015380065069506064, 'mean_word_length': 3.9156976744186047, 'pattern_counts': {'":': 0, '<': 55, '<?xml version=': 0, '>': 55, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4772708', 'n_tokens_mistral': 1015, 'n_tokens_neox': 945, 'n_words': 443}