Thomas had originally proposed this track 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 other side of the interface, the command line being the accessibility of this alternate side Without icons pr metaphors. interesting design just by using commandline The command line as a central tool in a design practice. Largely underdevelopped, not so understood, could be helpful for experimentations in non direct timelines 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. Text based interfaces, text based parameters 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. Umberto Eco: the Macintosh was introducing a 'catholic' approach, rather than the protestant of the previous cli -like interfaces. Catholic: icons, images, (iconisation of abstract notions) to push this parallel -> the Mac Protestant: interpretation of the bible is left to the reader, the believer. -> the CLI This metaphor does still apply now with the GUI & command line. 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 -> 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
Will this juxtaposition 'end in' a Beeldenstorm? (what are the implications) Designing without icons. What does that mean? Does it change your practise? UNIX as it's own religion? A number of maxims that have gained currency among the builders and users of UNIX Can these maxims be applied as a sort of design style book?
- make each program do one thing well - expect the output of a program to become the input of the next - - source: unix timesharing system maxims IBM (HAL) Researching the resistance of tools which are not usually used by designers Can the concept of "piping" be translated?
Find a different way to design the design-languages Try to examine how coding influences design? For example: css has lots of hierarchies 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. Eg. Can we descibe an HTML generated design into language. And translate that back into a visual image.
Is there any affective relationship with the shell? What do we mean with the shell? The borders are blurry. The word shell comes from the fact that it brings multiple programs together.
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.
This way of working is relatively new for the graphic design field. How does this shift connect to the tradition of graphic design.
There is also a sense of 'purity' when writing code yourself. But then there are many more steps to take. - object oriented programming languages, libraries - low level programming languages - assembly - etc
Abstracting away design concepts and reusing elements done by other people-
Linking back to a tradition of using instructions to create designs
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 ---> Is there a way to use code without visual appearance ?
Mapping the mornig session with graphviz (tree) and then representing it in another way to display the translateral links between elements. Aaaarhg graphviz trouble here So graphviz is probably not the proper language to use
Piet program is a program executed by setting a grid of colors that can be translated into a text 1- Trying to reverse this process 2- Pick an image (Lenna) 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
--> synesthesy interpretation of colours (numbers, days of the week, months)
I. 1. Design or build operating systems 2. make each programm do one thing well 3. except the output of every program to become the input to another, as yet unknow program
II. 1. All first input shall come from the tracks pad [simply because we felt we had grasped enough idea to start experimenting] 2. Method to obtain an output should be chosen by the operator, using only headless methods (?) [thus, creating a new standard] 3. The result shall become the new input of another operator [applying is own standard to the previous one]
┌——> standard 0 ——> standard 1 ——> standard 2 ——> standard 3 ——> standard 4 ——> standard 5 ——┐ └——<————————<————————<———————<———————<———————<———————┘ [as we were originally 5 participants]
Conditional design manifesto : "Through the influence of the media and technology on our world, our lives are increasingly characterized by speed and constant change. We live in a dynamic,data-driven society that is continually sparking new forms of human interaction and social contexts. Instead of romanticizing the past, we want to adapt our way of working to coincide with these developments, and we want our work to reflect the here and now. We want to embrace the complexity of this landscape, deliver insight into it and show both its beauty and its shortcomings. Our work focuses on processes rather than products: things that adapt to their environment, emphasize change and show difference. Instead of operating under the terms of Graphic Design, Interaction Design, Media Art or Sound Design, we want to introduce Conditional Design as a term that refers to our approach rather than our chosen media. We conduct our activities using the methods of philosophers, engineers, inventors and mystics."
Headless design manifesto "Through the influence of the graphic user interface of our softwares on our daily usage, our lives are increasingly characterized by an incomprehension toward our softwares. We live in a usage-only-oriented society that is continually sparking new user-friendly interfaces. Instead of being mere users, we want to adapt our way of working to coincide with these developments, and we want our work to reflect our tools. We want to embrace the complexity , deliver insight into it and show both its beauty and its shortcomings. Our tracks focuses on intricated headless processes : understand a design process through command-line usage where the output of every program to become the input to another, as yet unknow program. Instead of operating under any GUI, we want to introduce Randsom Headlessness in the design as a term that refers to our approach rather than our finnality. We conduct our activities using the power of the command-line tool"
│ input - standard ▕————┐
└—————————┘ │ use to
│ A │ translate
interprete │ │ depend on │
│ │ dictionnary
v │ │
vision - interpretation
Unibash is an experiment with bash, unicode and etherpad. It's essentially a collection of bash scripts, with single-glyph names, using unicode icons as meaningful (?) names. Providing commands to download content from a pad (↓), upload content to a pad (↑) or execute as script from a pad (☁). Essentially allowing for the pads to be used as stdin & stdout.