User Tools

Site Tools


Sidebar

projects

wcp1 (due 20240828)
wcp2 (due 20240904)
pct0 (bonus; due 20240905)
pct1 (bonus; due 20240905)
pct2 (due 20240905)
abc0 (due 20240906)
dac0 (due 20240911)
pct3 (bonus; due 20240911)
wcp3 (due 20240911)
gtf0 (due 20240918)
pct4 (due 20240918)
wcp4 (due 20240918)
pct5 (bonus; due 20240926)
tpb0 (due 20240926)
wcp5 (due 20240926)
gfo0 (due 20241002)
pct6 (due 20241002)
tpb1 (due 20241002)
wcp6 (due 20241002)
pct7 (bonus; due 20241009)
usr0 (due 20241009)
wcp7 (due 20241009)
bwp1 (bonus; due 20241016)
pct8 (due 20241016)
tpb2 (due 20241016)
wcp8 (due 20241016)
pct9 (bonus; due 20241023)
wcp9 (due 20241023)
wpa0 (due 20241023)
fwg0 (due 20241030)
gfo1 (due 20241030)
pctA (due 20241030)
wcpA (due 20241030)
pctB (bonus; due 20241106)
upf0 (due 20241106)
wcpB (due 20241106)
ldg0 (due 20241113)
pctC (due 20241113)
wcpC (due 20241113)
pctD (bonus; due 20241120)
wcpD (bonus; due 20241120)
bwp2 (bonus; due 20241204)
gfo2 (due 20241204)
pctE (bonus; due 20241204)
wcpE (bonus; due 20241204)
EoCE (due 20241216)
haas:fall2024:unix:projects:gtf0

Corning Community College

CSCS1730 UNIX/Linux Fundamentals

PROJECT: Graphics To Figure-out (GTF0)

OBJECTIVE

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.

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

Grabit is a tool used to grab projects needed to work on. This will assist you in grabbing most projects we work on throughout the course. Just type in Grabit then place project name in the proper directory for the project.

For example: In your gtf0 directory you would type 'grabit UNIX gtf0'

REPOSITORY STEPS

A public directory is need to be able to view your images from a browser

  • Create a public html directory with the following command
mkdir -p ~/public_html
  • Allow public permissions on the directory with the following
chmod 0711 ~/public_html

BUILD THE CODE

  • While in your gtf0 directory use the make command to build the code
make gtf0

It is also possible to compile manually

gcc -Wall --std=gnu18 -o gtf0 gtf0.c -lgd

However, it is not necessary to compile GTF0 for Unix due to the shebang added in the first line:

#!/usr/bin/env -S tcc -run -lgd

As such, you are able to run the file as a C script instead of having to compile the program. Simply run with the command:

./gtf0.c

If you were to remove this however, you would need to compile the program before running. An easy way to make sure this shebang is at the top of your file is with the following:

head -n 1 gtf0.c

This is to be runned in the directory that your gtf0.c is in.

RUN THE PROGRAM

Simply enter the command ./gtf0.c inside the gtf0 directory and the program will produce one gtf0.png

VIEW THE IMAGE

  • Using the mv command, move the resulting image from your gtf0 dir to your public html dir
mv gtf0.png ~/public_html
  • To allow public viewing of the image use the chmod command
chmod 0644 ~/public_html/gtf0.png

LIBGD FUNCTIONALITY

LibGD is a open source code library that allows images to be created with intuitive functionality

To learn more about LibGD you can visit the LibGD homepage and the LibGD documentation.

Below you will find an assortment of function prototypes that will be useful for completing project GTF0. All of these prototypes have been taken from the LibGD documentation as linked above. These specify function names, parameters and their types, and return values.

MIXING A COLOR

Before anything can be drawn there needs to be a color to draw it in

Colors can be mixed with gdImageColorAllocate

int color = gdImageColorAllocate (gdImagePtr im, int r, int g, int b);

gdImagePtr im is the image the function edits

int r, int g, and int b are the red, green, and blue components of the color. Typically represented as hex values between 0x00 and 0xFF

There are many ways to find a colors hex value, including googles

Official gdImageColorAllocate wiki page

DRAWING A LINE
gdImageLine (gdImagePtr im, int x1, int y1, int x2, int y2, int color);

gdImagePtr im is the image the function edits

int x1 is the starting x position of the line

int y1 is the starting y position of the line

int x2 is the ending x position of the line

int y2 is the ending y position of the line

int color is the color the line is drawn as

Official gdImageLine wiki page

DRAWING A RECTANGLE
gdImageRectangle (gdImagePtr im, int x1, int y1, int x2, int y2, int color);

gdImagePtr im is the image the function edits

int x1 is the left bound

int y1 is the upper bound

int x2 is the right bound

int y2 is the lower bound

int color is the color the rectangle is drawn as

Official gdImageRectangle wiki page

FILLING AN ENCLOSED SPACE
gdImageFill (gdImagePtr im, int x, int y, int color);

gdImagePtr im is the image the function edits

int x and int y are the coordinates the fill propagates from

int color is the color that is drawn as

Official gdImageFill wiki page

DRAWING A FILLED RECTANGLE
gdImageFilledRectangle (gdImagePtr im, int x1, int y1, int x2, int y2, int color);

gdImagePtr im is the image the function edits

int x1 is the left bound; i.e., the x coordinate for the top left point of the rectangle to be drawn.

int y1 is the upper bound; similarly, this is the corresponding y coordinate for the top left point of the rectangle.

int x2 is the right bound; this will be the x coordinate of the bottom right point of the rectangle, which incidentally will determine height and width of the rectangle.

int y2 is the lower bound

int color is the color the rectangle is drawn as

Official gdImageFilledRectangle wiki page

DRAWING A CIRCLE
gdImageEllipse (gdImagePtr im, int mx, int my, int w, int h, int color);

gdImagePtr im is the image the function edits

int mx and int my is the coordinates of the circle center

int w is the horizontal diameter of the circle

int h is the vertical diameter of the circle

w and h must be the same to create a circle

int color is the color the circle is drawn as

Official gdImageEllipse wiki page

DRAWING AN ELLIPSE
gdImageEllipse (gdImagePtr im, int mx, int my, int w, int h, int color);

gdImagePtr im is the image the function edits

int mx and int my are the coordinates of the ellipse center

int w is the horizontal diameter of the ellipse

int h is the vertical diameter of the ellipse

int color is the color the ellipse is drawn as

Official gdImageEllipse wiki page

 

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 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

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:

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

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 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

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
haas/fall2024/unix/projects/gtf0.txt · Last modified: 2024/08/26 14:27 by 127.0.0.1