week eleven – thursday 10th october
font and type
The next step was to set a font and align the type to create a design for the pages.
For now I have set it to fit in the bottom left of the page as a ‘title’ of the artwork with the contributors name underneath as an ‘artist’.
I also played with caps versus no caps, looking at the artist models explored in week eight. Bold statement caps are loud and obvious, the lowercase has a more fed-up, pissed off vibe.
I felt that when stating the issues themselves (e.g ‘animal abusers’) there needed to be more emphasis on the significance these issues have on us. I think that I will use lowercase on the cover page to entice people in, to not make a super ‘punk/angry’ booklet that people will only pick up if they want to hear or are in the mood.
The simple ‘We’re Pissed’ on the front cover of my mockup seemed to do well as people wanted to know what ‘we’ were pissed about and why it was written/designed in such a way that was more matter-of-fact than forcing this anger down their throats.
I duplicated the PFont and text String elements of my code, swapping out the ‘angry text’ for the names of the contributors so that their names could sit with their submission. However the two arrays didn’t run at the same time, despite there being the same number of values in each array. I then sort of guessed that I needed to seperate counters for each of the seperate texts, to enable them to run through the array in the same order I simply set the value of counterTwo as that of counterOne.
So now the idea is to take a range of screenshots per statement relevant to the persons finger length and to then compile this on photoshop!
Coding for Creative Practice 