[+] Basic view of our GUI

[CharlotteChenyy]

New feature

• [x] Basic view of the GUI (static scene)
• [x] Some listeners and events

[Lei-Tin]

ʕ•̫͡•ʕ•̫͡•ʔ•̫͡•ʔ•̫͡•ʕ•̫͡•ʔ•̫͡•ʕ•̫͡•ʕ•̫͡•ʔ•̫͡•ʔ•̫͡•ʕ•̫͡•ʔ•̫͡•ʔ Charlotte姐姐也开始发力辣

[CharlotteChenyy]

ʕ•̫͡•ʕ•̫͡•ʔ•̫͡•ʔ•̫͡•ʕ•̫͡•ʔ•̫͡•ʕ•̫͡•ʕ•̫͡•ʔ•̫͡•ʔ•̫͡•ʕ•̫͡•ʔ•̫͡•ʔ Charlotte姐姐也开始发力辣

Lab要迟到啦QAQ

[ScottCTD]

Also, to simplify our work, I suggest we can combine login and register.

We only need a user name and a password to login and register.

If the user does not exist in our database, then we automatically register this user.

[ScottCTD]

In addition, this is a bill demo.

[Lei-Tin]

The GUI looks good but there are things to reconsider.

I believe we can make the GUI simpler.

Buttons like setting and import can be moved to the menu bar.

I guess this is a more appealing (and more importantly, simpler) choice:

Also, in order to adhere the rubric, the code should be cleaner.

In other words, the new GUI you are suggesting doesn't have another separate window to control the logging in and register? That would make the GUI much simpler to implement :3

Also, since we can right click to remove an entry, what is the purpose of the button on the left that does "remove entry"?

[ScottCTD]

The GUI looks good but there are things to reconsider. I believe we can make the GUI simpler. Buttons like setting and import can be moved to the menu bar. I guess this is a more appealing (and more importantly, simpler) choice: Also, in order to adhere the rubric, the code should be cleaner.

In other words, the new GUI you are suggesting doesn't have another separate window to control the logging in and register? That would make the GUI much simpler to implement :3

Also, since we can right click to remove an entry, what is the purpose of the button on the left that does "remove entry"?

• Even in the newly suggested GUI implementation, we still need a dialog to input the username and password. But it is possible to remove the dialog by adding some input fields in the main frame.
• The buttons like "remove" serve as alternative ways of interacting with entries in case someone doesn't know how to right-click.

[CharlotteChenyy]

Also, to simplify our work, I suggest we can combine login and register.

We only need a user name and a password to login and register.

If the user does not exist in our database, then we automatically register this user.

So, we don't need the user to confirm their password when he/she tries to register?