As we are still early in our journey, despite not yet having learned much, let us see how our observational and pattern-matching and problem solving skills can still yield productive changes toward the solution of a task.

You are to modify provided code, once functionality and operations of it are understood, to produce, as image output, a scene containing the following characteristics:

• confined within a square resolution of at least 1000×1000 pixels
• contain at least:
  • 1 filled rectangle, no shorter than 32 pixels on any side
  • 1 unfilled rectangle, no shorter than 64 pixels on any side
  • 1 circle, diameter no smaller than 128 pixels
  • 1 ellipse
  • utilize at least 8 uniquely mixed colors
  • NOTE: background not a substitute for required filled rectangle above
• annotate your image with your initials, ideally in some corner

You will want to go here to edit and fill in the various sections of the document:

• https://lab46.g7n.org/notes/unix/spring2024/projects/gtf0

To be successful in this project, the following criteria (or their equivalent) must be met:

• Project must be submit on time, by the deadline.
  • Late submissions will lose 33% credit per day, with the submission window closing on the 3rd day following the deadline.
• All code must run cleanly (no warnings or errors)
  • all requested functionality must conform to stated requirements (either on this document or in a comment banner in source code files themselves).
• Executed programs must display in a manner similar to provided output
  • output formatted, where applicable, must match that of project requirements
• Processing must be correct based on input given and output requested
• Output, if applicable, must be correct based on values input
• Code must be nicely and consistently indented
• Code must be consistently written, to strive for readability from having a consistent style throughout
• Code must be commented
  • Any “to be implemented” comments MUST be removed
    • these “to be implemented” comments, if still present at evaluation time, will result in points being deducted.
    • Sufficient comments explaining the point of provided logic MUST be present
• Track/version the source code in your lab46 semester repository
• Submit a copy of your source code to me using the submit tool

Let's say you have completed work on the project, and are ready to submit, you would do the following:

lab46:~/src/SEMESTER/DESIG/PROJECT$ submit DESIG PROJECT file1 file2 file3 ... fileN

You should get some sort of confirmation indicating successful submission if all went according to plan. If not, check for typos and or locational mismatches.

I'll be evaluating the project based on the following criteria:

26:gtf0:final tally of results (26/26)
*:gtf0:modified code appropriately to accomplish task [16/16]
*:gtf0:commented code adequately to describe process [8/8]
*:gtf0:removed unused code [2/2]

• each class member is to participate in the contribution of relevant information and formatting of the documentation
  • minimal member contributions consist of:
    • near the class average edits (a value of at least four productive edits)
    • near the average class content change average (a value of at least 1024 bytes (absolute value of data content change))
    • no zero-sum commits (adding in one commit then later removing in its entirety for the sake of satisfying edit requirements)
  • adding and formatting data in an organized fashion, aiming to create an informative and readable document that anyone in the class can reference
  • content contributions will be factored into a documentation coefficient, a value multiplied against your actual project submission to influence the end result:
    • no contributions, co-efficient is 0.50
    • less than minimum contributions is 0.75
    • met minimum contribution threshold is 1.00

• Solutions not abiding by spirit of project will be subject to a 50% overall deduction
• Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction
• Solutions not utilizing indentation to promote scope and clarity or otherwise maintaining consistency in code style and presentation will be subject to a 25% overall deduction
• Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction