Relearn 2017


▀ ▁ ▂ ▃ ▄ ▅ ▆ ▇ █ ▉▊▋▌▍▎▏▐ ░ ▒ ▓ ▔ ▕ ▖▗ ▘▙ ▚ ▛ ▜▝ ▞ ▟ ▤ ▥ ▦ ▧ ▨ ▩ ◰ ◱ ◲ ◳

140 cross-browser supported color names
1 - Falling within an accepted range of size, amount, power, quality, etc.
1 - In the manner of Piet program, setting a grid of colors that can be translated into an image
2- Pick an image (Lenna)
3 - Having recognized excellence or authority. 
3- Using the standards of the css colors designation to re-create this image with words
4 - Caculate the occurence of words to resume the image
Aaaarhg graphviz trouble here
Abstracting away design concepts and reusing elements done by other people-
- A circle in bash
Analyzing the instruction models? cooking recipes? Code is a manifesto of your design
And also re reading,_Alessandro_-_Post-Digital_Print._The_Mutation_of_Publishing_Since_1894.pdf and finding some nice ideas for the elaboration of this comparison
And at the same time trying to make a comparison between the logics of wisiwig and inline/coded design from the designer's point of view
And Move from Language to Graphics
A number of maxims that have gained currency among the builders and users of UNIX
- assembly
Atom supported languages
Big difference between GUI, and html generated projects.
    - (both ?)
Brother hl-1430 driver (sort of)
Can the concept of "piping" be translated?
Can these maxims be applied as a sort of design style book?
Catholic: icons, images, (iconisation of abstract notions) to push this parallel -> the Mac
        Codeability of designs.
Code and GUI are just two representations of the same abstact structure.
command line to clone git repo from server
- Converting the NYT front page text to 91 different programming languages and combining them into one pdf.
    convert lena.jpg txt_lena.txt
CSS color names:
Decomposing the design process
Designing Dictionaries
- Designing heraldic equivalents for every single css color name (all 140 of them) 
Designing without icons. What does that mean? Does it change your practise?
    Design more and more starting from/fricting with software & technological background. Ie. going from Photoshop to HTML.
Eg. Can we descibe an HTML generated design into language. And translate that back into a visual image.
- etc
examples :
- expect the output of a program to become the input of the next
Exploding pad: replace gnu with gnu is not unix
export & import | quine |
        expressing designs, friction between the showing and the doing
Find a different way to design the design-languages
For example: css has lots of hierarchies
'Formalise' maxims for headless design. "Can one pipe one design into another?"
from etymology (standard): 
Get a text from a pad in the terminal:
git clone relearn@
Google quick draw
grammar of the design process
graphviz (dot (basic, oriented graph !) or neato ? (+command line -> unoriented graph))
- Grepping the terms input, output and design in the UNIX Time-Sharing journal from 1978
GUI generates code
Hacker = Command line = Fear
Headless art
Headless Design:
Heraldic representation of colors
here is a text file giving the color references of the image pixel by pixel :
How does the structure i write, connect to what happens on the screen. And see how you then can use that to change your design from a linguistic approach.
How does this shift connect to the tradition of graphic design.
How do tools affect the way we design?
how to find the nearest name of a color value :
Hybrid representations
Image as language
Image code to produce image/image as a code :
inkscape (xml editor - also, there is spiro)
"Instead of counting quantities (1,2,3,4...), the Pirahã only estimate quantities (relatively small, relatively large)"
interesting design just by using commandline
Is there any affective relationship with the shell?
---> Is there a way to use code without visual appearance ?
Language of Design:
Largely underdevelopped, not so understood, could be helpful for experimentations in non direct timelines
Linguistic relativity
Linking back to a tradition of using instructions to create designs
List of unicode characters
Literaldraw by OSP :
- low level programming languages
- make each program do one thing well
Mapping as structures
Mapping different ways of representing a layout
Mapping into (natural language) language
Mapping the mornig session with graphviz (tree) and then representing it in another way to display the translateral links between elements.
Marcel proposed this side of the track originally.
Markdown = Code?
Markdown editor works in reverse
metafont (curves are pre-defined)
Move from Graphics to Language
"Natural color system" (primary colors) palette:
(Notations for dance movements) >>  ///
- object oriented programming languages, libraries
obtained with Imagemagick : 
    - of intentions ?
    - of usage ?
Open structures
Or if that fails:
password: entrepot
Paul Cox's book made of visual patterns refering to colors
Pointing and refering
Prepend the content on a pad with ' . '
Producing a manifesto :
Protestant: interpretation of the bible is left to the reader, the believer.  -> the CLI
Recipe to display the contents of this pad in less:
related to the Sapir–Whorf Hypothesis ? (could be a starting point as well)
Relationships, Fields, Grids, Naming systems, Hierarchies, Areas, Scales, Colors
Researching the resistance of tools which are not usually used by designers
Saphir Whorf hypothesis: once you start thinking in a certain language, it limits the thoughts you have.
Separation of concerns
So graphviz is probably not the proper language to use
Sol Lewitt
Sort the html:
Sort the html, get and print to pdf
Sort the sentences:
Sort the text, get and print to pdf
source: unix timesharing system maxims IBM (HAL)
Stubborn pad: replace more with less
Synesthesy interpretation of colours (numbers, days of the week, months)
Syntax highlighter
take in account the possible interpretations that people can have from a language (oral language = accent…)
Text based interfaces, text based parameters
The accent is the language?
the Bible was written in Latin, making it less accessible to a general audience, who then had to rely on the images present in the book, whereas protestantism is more focused on the individual interpretation of text
The borders are blurry. 
The command line as a central tool in a design practice.
the other side of the interface, the command line being the accessibility of this alternate side 
There is also a sense of 'purity' when writing code yourself. But then there are many more steps to take.
There is a paradox in the code editors; code is supposed to lead to interfaces but the code is already an interface in itself because of its highlighting syntax system
The result is 'delayed' instead of instant gratification in the process of designing. One has to wait for the script to run, which is a text based process, rather than a visual.
There was a generation that started to work with GUI's. Now there is a group of designers that work from a coding background.
The word shell comes from the fact that it brings multiple programs together.
This metaphor does still apply now with the GUI & command line. 
This way of working is relatively new for the graphic design field.
Thomas had originally proposed this track
Tim Ingold, in "A brief history of lines" describes the evolution of writing text and points out the fact that written text was first written without any spaces and then litlte by little became "composed", with indentations, paragraphs breaks etc for readability reasons
Tree representation or not ?
Trying to find a logic to make layout design with using block unicode characters,
Try to examine how coding influences design?
Umberto Eco
Umberto Eco: the Macintosh was introducing a 'catholic' approach, rather than the protestant of the previous cli -like interfaces.
UNIX as it's own religion?
Unix Time-Sharing System Forward, Doug McIlroy, Bell Laboratories, 1978, p. 1902 
Using "Unix Time-sharing system forward" text as a model to start form some ideas ?
wget -qO-[[padname]]/export/txt
wget -qO- | less
wget -qO- | sort | curl -F "file=@-;type=text/plain"
wget -qO- | sort | less
wget -qO- http://complex.local:9001/p/Ransom-Headlessnesss-in-the-Design/export/html | sort | curl -F "file=@-;type=text/plain"
wget -qO- http://complex.local:9001/p/Ransom-Headlessnesss-in-the-Design/export/html | sort | curl -F "file=@-;type=text/plain" && wget -qO- http://complex.local:9001/p/Ransom-Headlessnesss-in-the-Design-sorted-html/export/html | node stdin.js sorted-html.pdf
wget -qO- http://complex.local:9001/p/Ransom-Headlessnesss-in-the-Design/export/txt | sort | curl -F "file=@-;type=text/plain" && wget -qO- http://complex.local:9001/p/Ransom-Headlessnesss-in-the-Design-sorted-txt/export/html | node stdin.js sorted-txt.pdf
-> what could be an "interface" to the Bible narrative is the stained glass of the churches with the representations of the biblic scenes, that made the story accessible to a even bigger amount of people includig the non readers ones
What do we mean with the shell?
What’s my color? rose pale
what would be the litteracy of coding?
while true; do wget -qO- | sed 's/gnu/gnu is not unix/' | curl -F "file=@-;type=text/plain"; sleep 1; done;
while true; do wget -qO- | (printf " . " && cat) | curl -F "file=@-;type=text/plain"; sleep 0.5; done;
while true; do wget -qO- | sed 's/more/less/' | curl -F "file=@-;type=text/plain"; sleep 1; done;
Who get's to decide what is the standard
Who get to write the web ?
Will this juxtaposition 'end in' a Beeldenstorm? (what are the implications)
Without icons pr metaphors.
Working in a gui sometimes feels like working as a blind man, not knowing what happens, and being focused on the outcomes.
Working in the shell is much more language based. It needs consious thinking and combining logical steps to create the outcome.
You need to speak the language of the text interface. Design & typography is very closely related, and now, with the command line as a central tool, even more.