Browse Source

minor edits

Kr Younger 6 years ago
parent
commit
d4dadcd278
2 changed files with 13 additions and 9 deletions
  1. 7
    4
      README.TXT
  2. 6
    5
      README.md

+ 7
- 4
README.TXT View File

@@ -22,7 +22,7 @@ You should run the app, learn how to use it, so you understand what it does. It
22 22
 shall we say, user-friendly. So you may find what you have to do to make it work somewhat
23 23
 awkward. 
24 24
 
25
-Then, you should read thru the code seeing how the code actually implements the things you 
25
+Then, you should read thru the code repository seeing how the code actually implements the things you 
26 26
 see when you run the code. Find the "main" routine, which is where the app starts up. Trace from there
27 27
 to see what code gets called where and when. Trace how the operations of the code work.
28 28
 
@@ -47,16 +47,17 @@ Read them all, trying to get an idea of how it all goes together.
47 47
 
48 48
 Notice when reading the code...
49 49
 
50
-- Each account has: id, name, email, balance
50
+- Each account has: id, name, email, balance; find that in a class.
51 51
 - What does Premium account do that Basic does not?
52 52
 - What are the two starter account already built into the project?
53
-- Trace how the Cash machine sets the account
53
+- Trace how the Cash machine sets the current account
54
+-- enter account id and "login to account"
54 55
 - Trace how a deposit happens
55 56
 -- enter a number then click deposit
56 57
 - Trace how a withdrawal happens
57 58
 -- enter a number then click withdraw
58 59
 - How does "exit" log out of the account?
60
+- What might be a better name for "exit"?
59 61
 
60 62
 
61 63
 Things to Change for the Lab
@@ -67,6 +68,7 @@ FIRST, fork this repo into your own account.
67 68
 
68 69
      After getting each of these items completed, 
69 70
      be sure to do a 'git commit' to save you work. 
71
+     Learn your git.
70 72
      Never Lose Code. 
71 73
      NEVER LOSE CODE. EVER. :-)
72 74
 
@@ -93,7 +95,7 @@ make sure the project runs. (Else the Board... well, disappointment lies that di
93 95
   * Make the login stuff more clear
94 96
   * Disable the three buttons that operate on an account until a login happens 
95 97
   * and then enable them. add another TextField for the amount entries. 
96
-  * Make it different from the fieldwhere you set the account ID.
98
+  * Make it different from the TextField where you set the account ID.
97 99
 
98 100
 * Enable the amount entries to be floating point numbers instead of 
99 101
   just integers when doing deposits and withdrawals.

+ 6
- 5
README.md View File

@@ -17,14 +17,15 @@ The point of this lab is to read thru some existing code, in this case, a progra
17 17
 launches a window on your computer and lets you play with a couple of "banking accounts".
18 18
 You should run the app, learn how to use it, so you understand what it does. It is not,
19 19
 shall we say, user-friendly. So you may find what you have to do to make it work somewhat
20
-awkward. 
20
+awkward.
21 21
 
22
-Then, you should read thru the code seeing how the code actually implements the things you 
23
-see when you run the code. Find the "main" routine, which is where the app starts up. Trace from there
24
-to see what code gets called where and when. Trace how the operations of the code work.
22
+Then, you should read thru the code repository seeing how the code actually implements the 
23
+things you see when you run the code. Find the "main" routine, which is where the app 
24
+starts up. Trace from there to see what code gets called where and when. Trace how the 
25
+operations of the code work.
25 26
 
26 27
 Finally, you are to add some new functionality to the app, to make it "more useful, powerful &
27
-more rewarding for the user". 
28
+more rewarding for the user".  
28 29
 Your effort will be met with promotions, parades, and stock options. (no, just kidding).
29 30
 
30 31
 ## Lab Brief