New Concepts to be applied for the assignment (because there likely won't be time to cover GUIs and graphics in lecture it is even more important that you attend tutorial and understand the examples covered).
- Writing a program that reacts to button events using the tkinter module (to keep things consistent do not use another module).
- Drawing basic shapes and setting graphical properties using the tkinter module (to keep things consistent do not use another module).
Only new concepts that need to be applied in the assignment are listed, concepts previously applied in other assignments may need to used in the implementation of your solution. Since the program you write will likely be fairly short it can be all included in a single file/module. Defining a new class is not needed but you will have to implement a new function (to react to the button event).
Functional requirements
Modify the existing code in the program [starting program] to draw the graphic of a rectangle that appears in a new Window when the button is pressed. (For this assignment it's acceptable that the button and window are both globals). The rectangle (which is added to the popup window) with have the following properties.
- Dimensions of the new window (width=1024,height=768) (worth 1.0 GPA)
- Properties of the rectangle (which appears in the
window):
- Coordinates of top left hand corner (50,100) (worth 1.0 GPA)
- Coordinates of bottom right hand corner (250,200) (worth 1.0 GPA)
- The rectangle is draw in bold colors: filled in 'pink', outlined in 'orange' (worth 1.0 GPA)
It's important that you set the values precisely as specified so the marker can tell you know exactly how/when to set the graphical properties when getting your program to react to the button press event. The figure below shows a screen capture of the popup window as the bottom was pressed in my solution. If you need to see the entire chain of events from execution to button press here is a [video capture].
How to do determine 'how you did' on an assignment? (Short answer: you can thoroughly test your program and become familiar with non-functional requirements)
Program functionality (implementing working program features)
Test your program: Because the assignment description (along with required features) is posted ahead of time if you test your program thoroughly before submitting the final version then you should get a pretty clear idea of "how you will do". This should be easy verify especially if you pay attention to the details of assignment requirements and you can verify the results visually as well.
Style and documentation (non-functional assignment requirements)
- To keep the marker's workload reasonable and to reduce marking time unless otherwise specified in the description these things will not factor into the grading of mini-assignments.
Non -functional assignment requirements (style and documentation)
Although it won't affect your grade for mini-assignments you should still practice applying good style in your solution as well as writing documentation. It will keep your skills for the full assignments (when you will be graded on these things) and get you used to having good habits.
- Naming conventions: You should employ
good naming conventions for identifiers (variables and constants) as covered
in the "Introduction to programming" section of the course.
- Your file must be specifically named as specified under the specific point [Naming the file] under the "Marking and grading" heading.
- Named constants should be used as appropriate.
- Python documentation: This should be
specified in the header of the program (very top of your program in the form
of Python documentation). The basics of documentation were covered in the
"Intro to programming" section of the course. Later sections may include
additional details.
- Identifying information: All assignments should include contact information (full name, student ID number and tutorial section [Here's a Link if you don't know how to find this information]) at the very top of your program.
- Program version.
(version date or version number).
- Under the version you should specify which assignment features were implemented in that version. An example covering the use of program versioning and documentation was covered in the "Introduction to programming" lectures.
- Any program limitations or weaknesses.
- In general: The program output and the program code itself (python program) must be properly aligned and formatted including whitespace as needed to group related parts and separate sections (which again was covered in the "Intro to programming" lectures of the course. Additional requirements in the formatting of output may be included in the ["Functional requirements"] section of the assignment.
Marking and grading
-
What to submit:
If your submission won't run using Python 3.x on any computer then it won't
be awarded credit. It's up to you if you wish use the graphical
program builder other than IDLE (or another development environment rather
than a simple text editor) to write/run your programs but if you do you
submit your program in the form of text ".py"
file or files.
- All computer users: Be careful that you actually submit the file containing your program and not a related file, here's one example of a problem: operating systems sometimes create a "lock file" when a file is being edited to prevent multiple users or programs from trying to edit that file. (Names of lock files typically include the file being edited but begin with a tilde character e.g. the file being edited is 'a1.py' so the lock file is named '~a1.py'. Because the lock files do not contain the actual data take care that you don't accidentally submit the lock file instead of the file (some students have actually done this).
- Windows users: take care that you don't accidentally submit a shortcut to a file instead of the actual file. (Check the file name and compare the file size to your original file. Simply downloading the shortcut file as a test won't work because that shortcut will work on your computer but not on anyone else's machine and this may mean your work won't be graded.
-
Naming the file containing your program: You must save your program in a file called "gui.py". Failing to use this exact name will affect your grade (-0.2 GPA).
- Before the due date, late assignments or components of assignments/assignment extensions: Due dates are strict and extensions require acceptable documentation in order to get permission from the [course instructor]. If/when permission is awarded for a late submission then I will let the marker know that the regular penalty will not be applied (so when ask for an extension I need to know the name of that person). Alternate submission mechanisms to D2L (non exhaustive list of examples: email, uploads to cloud-based systems such as Google drive, time-stamps, TA memories) cannot be used as alternatives if you have forgotten to submit work or otherwise have not properly submitted into D2L. Only files submitted into D2L by the due date is what will be marked, everything else will be awarded no credit. The final cut off date after which full assignments will not be accepted is after the [maximum progressive penalty (listed below)] can be applied.