Now: Visual Rhetorics

The visual rhetorics course I’m teaching this semester is by now well enough plotted to pass along a link, finally. I haven’t taught the class before, which only means that its materials this time are spun provisionally from many influences–an independent study and qualifying exam at SU, Michael Salvo’s syllabus, Dànielle DeVoss’s syllabus, and good conversations with CGB just after the new year. Its large arc follows from photography to document design to infographics and data visualization. I remain cautiously optimistic that these three sub-arcs will fit together okay within the fourteen meetings we have. No surprise, but I’m supplementing heavily with PDFs and assigning as required texts only Barthes’ Camera Lucida, Handa’s edited collection, and Cairo’s The Functional Art. One project involves writing (and designing) Ch. 10 for the Cairo book–a “missing” chapter focused on visual rhetoric. There’s an ignite presentation set up to articulate in short-form one’s emerging visual-rhetorical priorities and interests in relation to one of the people interviewed at the end of The Functional Art. And then there is a loose-fitting, build-your-own-collection portfolio whose creation and assembly is spread as evenly as possible throughout.

I’m still trying to figure out the role of in-class workshop blocks devoted to self-paced attempts with Photoshop and Illustrator. And I can’t quite decide how formally and explicitly to dwell on technical matters and rationale related to different image file types. Against these uncertainties (or yet-unmade decisions), I count as one advantage that I have had all but three of the fourteen students in class before, and it’s a terrific bunch who will assert their preferences whenever I’m slow to decide.

PHPinally

We’re experimenting in the WC this semester with consultation by
discontinuous email
. Students can upload up to five pages of whatever they
are working on, the draft then zigs and zags (taking two lefts and then a
right?) through the internet to a listserv account where five always-on
consultants take turns commenting and returning drafts, usually within 24 hours
after the draft is sent. The system seemed to be working fine until recently
when we realized a flaw in the design of the upload form. Basically, the
form allows students to 1.) upload a file or 2.) copy and paste a chunk of text
into the form. ‘Submit’ The form then calls up a PHP script, which, when
there is an uploaded file, puts the file in a temporary directory, builds the
email message to the listserv, attaches the file, sends the email to the
listserv, and finally clears the file from the temporary directory. That much
seemed to be working fine for, oh, ten weeks, and we have 45 such consultations
to show for it. But:

Continue reading →