1. Study summary of the week 1.1 mind map: Java Graphical interface Summary
2. Written assignment 1. Event handling in the GUI 1.1 writes out some of the most important keywords in the event-handling model.
- Event sources, events, event listeners
1.2 Write event-handling related code (you need to have your number and name in the program) and prove that you understand the event-handling model.
2. Big job: Use the graphical interface to improve your shopping cart 2.1 give the Project Division form and GIT address
| Student |
responsible for the task |
Blog Address |
| Jiang Zholin |
ShoppingCart |
Git |
| Dong Mingshu |
Good |
Git |
2.2 Try to use the graphical interface to overwrite (your program, the graphical interface needs to appear in your name)
2.3 What is wrong with the process of overwriting a console-based program as a GUI-based program? Summary: What principles should be followed when writing methods in the future?
- The main problem is the command line interface to the graphical interface, the objects of the two are different, need to introduce new classes, new functions, so that people need to adapt.
- The principle of writing methods is to be able to expand the methods to adapt to different windows.
2.4 Gives a record of how several people commit to the same item on the code cloud. If a person does not submit a record, it is considered incomplete.
2.5 Add points: Record your program action videos via Licecap and put them in your blog job.
3. Other topics 1:netbeans basic use (GUI: Compute A+B) 1.1 Run interface
1.2 The key code that appears in NetBeans must not copy the code to another editor.
1.3 What happens to the program if you enter a non-numeric value in the text box? How to improve?
- When I enter a non-numeric value in the text box because of the design of my own function, the program will run with a malformed error.
- For this problem I think you can use the Try,catch statement to correctly handle the error.
Topic 2:swing user interface components and event handling 2.1 run screen, need to appear your school number and name.
2.2 The key code that appears in NetBeans must not copy the code to another editor.
2.3 What is the difference between the code of this login interface and the login interface code generated using NetBeans? (analysis from both the layout manager and the event-handling code)
- From the layout manager, the code for this sign-in meeting is generally less restrictive than adjustment rules, and NetBeans can achieve layout management by simply dragging and dropping.
- From event handling, the login interface is written in code to be more flexible with event handling, and NetBeans has formed its own framework.
Topic 3: Using NetBeans to design a complex user interface (menu) 3.1 Run the interface, you need to show your school number and name.
3.2 The key code that appears in NetBeans must not copy the code to another editor.
3. Count the amount of code completed this week
| Week Time |
Total code Amount |
New Code Volume |
total number of files |
number of new files |
| 1 |
0 |
0 |
0 |
0 |
| 2 |
0 |
0 |
0 |
0 |
| 3 |
0 |
0 |
0 |
0 |
| 4 |
437 |
437 |
7 |
7 |
| 5 |
905 |
468 |
13 |
6 |
| 6 |
1294 |
389 |
21st |
8 |
| 7 |
1678 |
384 |
30 |
9 |
201621123021 Java programming Seventh week of study summary
