Table of Contents
Corning Community College
CSCS1320 C/C++ Programming
PROJECT: Graphics To Figure-out (GTF0)
OBJECTIVE
As we start our journey into programming, 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.
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
EDIT
You will want to go here to edit and fill in the various sections of the document:
GTF0
GRABIT
The first step towards completing the project is to get the skeleton code and Makefile Lab46 has a command you can run called grabit, it can be used by typing the command, followed by the course designation, followed by the project in this case it would be
grabit cprog gtf0
REPOSITORY STEPS
BUILD THE CODE
Edit the provided skeletal code from the grabit using a txt editor like nano. edit this code to fit the criteria for the project
RUN THE PROGRAM
To be able to run the gtf0.c file use the following command in the grabit file:
make debug
Issue the command ls -l and if there is a green “gft0” file, everything worked :) {for now}
If you execute this command it should produce a .png image
VIEW THE IMAGE
The image can either be viewed, if on a Pi, from the GUI file explorer
Or if in lab46: 1. Copy the file to ~/public_html/
username@lab46:~/src/spring2024/gtf0$ cp ./gft0.png ~/public_html
2. Change current directory to ~/public_html
cd ~/public_html
3. Change permissions to be able to be read by all
chmod +r gtf0.png
4.view image from web browser
https://lab46.g7n.org/~username/gtf0.png
LIBGD FUNCTIONALITY
MIXING A COLOR
You can make custom colors in C with commands from the libgd library so do this specify the integer variable that will have the color assigned to it
int black = 0;
then using the gdImageColorAllocate command, specify the intensity of each color, red green and blue, and reassign the output to the color
image red green blue black = gdColorAllocate (image, 0x00, 0x00, 0x00);
red green blue sections are in hexcode so the most intense value is 0xFF and the least being 0x00
so if red and blue = 0xFF
and green = 0x00
you will get purple
DRAWING A LINE
Syntax for drawing a graphics line
gdImageFill (image, x1, y1, x2, y2, color);
DRAWING A RECTANGLE
Syntax for drawing a graphics line
gdImageRectangle (image, topleftX, topleftY, bottomrightX, bottomrightY, colorofRectlines)
FILLING AN ENCLOSED SPACE
Basically the Fill bucket from any drawing software. You specify where the coordinates of the fill is (another way of thinking is that the coordinates is specifying where the “click” of the paint bucket tool would be on the screen) and all space within enclosed lines around the coord's get flooded with the specified color
gdImageFill (image, x1, y1, color);
DRAWING A FILLED RECTANGLE
Syntax for drawing a graphics line
gdImageFilledRectangle (image, topleftX, topleftY, bottomrightX, bottomrightY, color)
This will draw a solid rectangle of color
DRAWING A CIRCLE
Syntax for a circle uses an arc command but the start angle is 0° and the end is 360° (also the diameters are equal)
Arc syntax:
gdImageArc (image, centerX, centerY, diameterWidth, diameterHeight, start°, end°, colorofLine);
Circle Ex:
gdImageArc (image 150, 300, 100, 100, 0, 360, black);
DRAWING AN ELLIPSE
Syntax for an Ellipse
gdImageEllipse ( X1, Y2, width, height, colorofLine);
(could also be used for a circle)
Syntax for an Filled Ellipse
gdImageFilledEllipse ( X1, Y2, width, height, colorofFill);
SUBMISSION
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 compile cleanly (no warnings or errors)
- Compile with the -Wall and --std=gnu18 compiler flags
- 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
- No global variables (without instructor approval), no goto statements, no explicit calling of main()!
- Track/version the source code in your lab46 semester repository
- Submit a copy of your source code to me using the submit tool (make submit on lab46 will do this) by the deadline.
Submit Tool Usage
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.
RUBRIC
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]
Pertaining to the collaborative authoring of project documentation
- 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 256 bytes (absolute value of data content change))
- near the class total content contribution average (a value of at least 1kiB)
- 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
Additionally
- 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