You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
206 lines
13 KiB
206 lines
13 KiB
<html>
|
|
<head>
|
|
<script src="/versions.js"></script>
|
|
<link href="../stylesheet.css" rel="stylesheet">
|
|
<link href="https://pad.vvvvvvaria.org/p/lgm2019" rel="alternate" title="Etherpad" type="text/html">
|
|
<link href="lgm2019.raw.txt" rel="alternate" title="Plain text" type="text/plain">
|
|
<link href="lgm2019.raw.html" rel="alternate" title="HTML" type="text/html">
|
|
<link href="lgm2019.meta.json" rel="alternate" title="Meta data" type="application/json">
|
|
<meta charset="utf-8">
|
|
<title>lgm2019</title>
|
|
</head>
|
|
<body>__PUBLISH__<br>
|
|
<br>
|
|
<strong># Ana & Ricardo - Why terminology matters</strong>
|
|
<br>
|
|
<br>* open design<br>
|
|
<br>"open"? <br>too many meanings<br>
|
|
<br>advocacy<br>
|
|
<br>Manufactura uses "free libre and open source software".<br>Most questionmarks in the description of this talk.<br>
|
|
<br>Open Source Design manifesto (on a napkin):<br>
|
|
<ul class="indent">
|
|
<li>I will find oppertunities to design in the open.</li>
|
|
<li>Share good and bad. </li>
|
|
<li>Share</li>
|
|
<li>Openly discuss </li>
|
|
<li>Improve my toolbox.</li>
|
|
</ul>written by open design foundation<br>started by a designer at Adobe<br>
|
|
<br>"free" was problematic, too close to "freedom"<br>then open source was introduced<br>
|
|
<br>too much about not paying for free tools/fonts<br>
|
|
<br>most importantly about doing things together<br>eg.: free to modify a font, adapting it to your own language<br>
|
|
<br>* open source design<br>
|
|
<br>more closely related to 4 free software freedoms<br>
|
|
<br>
|
|
<a href="https://discourse.opensourcedesign.net/" rel="noreferrer noopener">https://discourse.opensourcedesign.net/</a>
|
|
<br>collaborations between designers & developers<br>open source design > design for open source<br>
|
|
<br>sometimes happening through proprietary tools<br>Example of Ubuntu (Canonical)'s design department using Mac/Adobe<br>
|
|
<br>* tools<br>
|
|
<br>Can we use proprietary software and still call it open source design?<br>support/contribution vs. use<br>
|
|
<br>using is the biggest form of contribution<br>
|
|
<br>* manufactura<br>
|
|
<br>not open design<br>but not sure how to call it?<br>
|
|
<br>Libre Design?<br>F/LOSS Design?<br>
|
|
<br>Q&A:<br>
|
|
<br>Andreas (Scribus): not push people to use F/LOSS, but ... <br>Ricardo: Releasing end products under open licenses can be oke. But using FLOSS tools will make more of a difference.<br>
|
|
<br>Eyol: Are tools not good enough? Or not well known enough? Or is it a question of mindset / bigger questions?<br>Ana: If you're not changing your tools, you don't see what can be changed? Schools setting/following "industry standards" is not helping.<br>
|
|
<br>Q: Many problems between design & FLOSS. Aren't we dealing with bigger questions then tools?<br>Ricardo: Terminology is a very precise way of approaching these questions, indeed. <br>
|
|
<br>---<br>[<br>Free software tools ... as in Gimp/Inkscape/etc, but these days, a lot of web open source/free software tools, which rely on web standards, browsers, pdf engines, ...<br>"Freedom" resonating libertarian thinking, individual practice, design hero culture, ... <br>]<br>
|
|
<br>
|
|
<br>
|
|
<strong># Pascal Bies - Non-destructive procedural 2D-vector modelling</strong>
|
|
<br>
|
|
<br>
|
|
<a href="https://github.com/pasbi/ommpfritt" rel="noreferrer noopener">https://github.com/pasbi/ommpfritt</a>
|
|
<br>
|
|
<br>Doing vector Graphics differently.<br>In a non-inkscape-way.<br>
|
|
<br>duplicating shapes (in inkscape) vs. cloner objects <br>tool oriented vs. object oriented<br>
|
|
<br>cloner object<br>mirror object<br>instance object<br>
|
|
<br>following principles: DRY, KISS<br>trying not to use: spaghetti code, copy/paste<br>
|
|
<br>WYSIWYM - what you see is what you mean<br>
|
|
<br>Q: Another software: Synfig <a href="https://www.synfig.org/" rel="noreferrer noopener">https://www.synfig.org/</a>
|
|
<br>
|
|
<br>
|
|
<br>
|
|
<strong># FLOSS Educators BoF </strong>
|
|
<br>>>> <a href="https://pad.vvvvvvaria.org/lgm-floss-educator-bof" rel="noreferrer noopener">https://pad.vvvvvvaria.org/lgm-floss-educator-bof</a>
|
|
<br>
|
|
<br>
|
|
<br>
|
|
<strong># A new spline - Ralph Levien</strong>
|
|
<br>
|
|
<br>[> Relearn curve tools!]<br>
|
|
<br>Spiros demo <br>
|
|
<a href="https://levien.com/garden/js/spiro.html" rel="noreferrer noopener">https://levien.com/garden/js/spiro.html</a>
|
|
<br>
|
|
<br>
|
|
<a href="https://spline.technology/demo/" rel="noreferrer noopener">https://spline.technology/demo/</a>
|
|
<br>
|
|
<br>Research on splines, still developed. <br>Will be the main technique in Runebender ( <a href="https://github.com/linebender/runebender" rel="noreferrer noopener">https://github.com/linebender/runebender</a> ), the new type editor.<br>
|
|
<br>Sponsored by Google, allowed for full time development of this project.<br>
|
|
<br>
|
|
<br>
|
|
<strong># No design without research – Why and how to incorporate design research practices into our free software projects</strong>
|
|
<br>Belén Barros Pena<br>
|
|
<br>
|
|
<ul class="indent">
|
|
<li>Slides: <a href="https://belenbarrospena.github.io/no_design_without_research_lgm2019/#/" rel="noreferrer noopener">https://belenbarrospena.github.io/no_design_without_research_lgm2019/#/</a>
|
|
</li>
|
|
<li>Script: <a href="https://github.com/belenbarrospena/no_design_without_research_lgm2019/blob/master/README.md" rel="noreferrer noopener">https://github.com/belenbarrospena/no_design_without_research_lgm2019/blob/master/README.md</a>
|
|
</li>
|
|
<li></li>
|
|
</ul>Human computer interaction<br>Interaction design and social sciences<br>
|
|
<br>Design?<br>interaction design, software, how features behave, interfaces (not just the graphical ones)<br>
|
|
<br>Research? <br>activity involving user in the design process<br>
|
|
<br>Can interaction design exist without research?<br>Without involving users in the process.<br>
|
|
<br>In free software, this type of research is not always seen as necessary.<br>
|
|
<br>The naysayers - a classification:<br>
|
|
<br>1. itch scratchers<br>
|
|
<br>Software only developed for an individual problem.<br>Your itch is only your itch when you're the only one using the software.<br>
|
|
<ul class="indent">
|
|
<li></li>
|
|
<li>users your itch</li>
|
|
<li>1 100%</li>
|
|
<li>2 50%</li>
|
|
<li>3 33%</li>
|
|
</ul>
|
|
<br>When you release your code, you relase your itch.<br>
|
|
<br>2. the scornful<br>
|
|
<br>Ford-like<br>Designers have super power.<br>
|
|
<br>3. The dismissive<br>
|
|
<br>Design research as in asking people what they think.<br>
|
|
<br>But design research is not about asking opinions.<br>"Great designers are like great novelists: acute observers of human behaviour." - Don Norman, Workarounds<br>Design research is about uncovering the common patterns.<br>
|
|
<br>4. The defeatists<br>
|
|
<br>Research takes too much time, too much effort.<br>And therefore it is not suitable to free software.<br>
|
|
<br>Research for software making, involves<br>- time (6 interviews is enough, 5 interaction sessions of 45min is enough)<br>- money (travel costs but there is jitsi ....., OBS video recording?, compensation in other forms)<br>- effort (mainly about making sense of results, affinity diagrams in teams)<br>- some common sense advice (keep it small, take time, research is an attitude)<br>
|
|
<br>
|
|
<br>
|
|
<strong># USER PERSPECTIVE in the funding model</strong>
|
|
<br>Livio Fania<br>www.selenox.com<br>
|
|
<br>we need to think about financing free software<br>problem-solution thinking is not enough<br>free != bad quality (question of advocacy/promotion)<br>need of diversity, in users and developers<br>
|
|
<br>Questionnaire with 5 different FLOSS users/makers, nice<br>
|
|
<br>Livio proposes to divide tasks within a FLOSS project:<br>- developer<br>- project manager<br>- community manager<br>- user<br>
|
|
<br>Involved in building an online repository with FLOSS artists/designers<br>
|
|
<a href="https://docs.google.com/forms/d/e/1FAIpQLScHbKwa_YPwmhLSGZasThCZoientkZwdFCk3mqItA5_qwBFRA/viewform" rel="noreferrer noopener">https://docs.google.com/forms/d/e/1FAIpQLScHbKwa_YPwmhLSGZasThCZoientkZwdFCk3mqItA5_qwBFRA/viewform</a>
|
|
<br>
|
|
<br>"This form aims to build an online directory to connect artists from the free software community with other fellows and potential clients. One of the goals is also to showcase good quality work, in order to build credibility outside the community. So a selection will be made from a team of professionals of the graphic industry based on quality criteria [???]. The project is still a draft, so feel free to make comments or suggestions at the end of the form."<br>
|
|
<br>
|
|
<strong># Lightning talks</strong>
|
|
<br>
|
|
<br>
|
|
<a href="https://observablehq.com/" rel="noreferrer noopener">https://observablehq.com/</a>
|
|
<br>
|
|
<br>
|
|
<strong># PrePostPrint</strong>
|
|
<br>
|
|
<br>Different way to make graphic design.<br>research group<br>
|
|
<br>Before PrePostPrint > OLA: Outils Libres Alternatifs, series of 2 day sessions around a specific workflow or tool<br>
|
|
<br>pad2print<br>paged.js<br>
|
|
<br>experimental workflows<br>alternative/hacked/DIY tools<br>
|
|
<br>Q&A<br>- Interesting part of experimental publishing workflows, is the changing of collaboration mode (parallel, not first editing then design)<br>- Not often the case anymore that designers use one set of tools, often a tool is choosen in relation to a specific context or a specific way of collaborating<br>- Are you involved in css standards? Are you pushing the other way as well? Yes, W3C, <br>
|
|
<br># Freie Farbe<br>
|
|
<a href="https://www.freiefarbe.de/" rel="noreferrer noopener">https://www.freiefarbe.de/</a>
|
|
<br>
|
|
<a href="https://freecolour.org" rel="noreferrer noopener">https://freecolour.org</a>
|
|
<br>
|
|
<br>HLC code >>> spectral data >>> ink formulation (ink supplier mixes the ink, according to the spectral data)<br>
|
|
<br>
|
|
<strong># Paged.js workshop</strong>
|
|
<br>
|
|
<a href="https://www.pagedmedia.org/paged-js/" rel="noreferrer noopener">https://www.pagedmedia.org/paged-js/</a>
|
|
<br>
|
|
<br>
|
|
<ul class="indent">
|
|
<li>Repository for the workshop: <a href="https://gitlab.pagedmedia.org/JulieBlanc/printing-in-relation-to-graphic-art_workshop" rel="noreferrer noopener">https://gitlab.pagedmedia.org/JulieBlanc/printing-in-relation-to-graphic-art_workshop</a>
|
|
</li>
|
|
<li>Project repository: <a href="https://gitlab.pagedmedia.org/tools/pagedjs" rel="noreferrer noopener">https://gitlab.pagedmedia.org/tools/pagedjs</a>
|
|
</li>
|
|
</ul>
|
|
<br>Pagedjs want to be invisible, the in-between. <br>It's mostly based on web standards.<br>
|
|
<br>crucial to check if the browser supports @print statements<br>Firefox does not support it. You can preview in firefox, but not print. Also remember that firefox and chrome interpret lineheight differently.<br>Chrome does support it.<br>
|
|
<br>You can work in the margins with position: absolute;<br>But it doesn't flow yet, parallel flow is not supported yet.<br>
|
|
<br>Sidenote: PoDoFo <a href="http://podofo.sourceforge.net/" rel="noreferrer noopener">http://podofo.sourceforge.net/</a>
|
|
<br>RGB to CMYK pdf parser<br>Also replacing specific colors is possible.<br>
|
|
<br>Julie: pixel in css is more precise (no difference between screen and print)<br>W3C guy: they should be both precise<br>you could see differences between pixels and points, but you shouldn't. <br>This means that your screen is not set up correctly.<br>
|
|
<br>If you want to change font-size, you need to cmd out the * font-size: 1rem; in global/style.css<br>
|
|
<br>To have changing running headers, you can use pagedjs syntax:<br>By copying:<br>
|
|
<ul class="indent">
|
|
<li>h1{<ul class="indent">
|
|
<li>string-set: chapTitle content(text);</li>
|
|
</ul>
|
|
</li>
|
|
<li>}</li>
|
|
<li>@top-center{<ul class="indent">
|
|
<li>content: string(chapTitle);</li>
|
|
</ul>
|
|
</li>
|
|
<li>}</li>
|
|
<li></li>
|
|
</ul>By moving:<br>
|
|
<ul class="indent">
|
|
<li>h1 {<ul class="indent">
|
|
<li>position: running content(text);</li>
|
|
</ul>
|
|
</li>
|
|
<li>}</li>
|
|
<li>@top-center{<ul class="indent">
|
|
<li>content: element(chapTitle); </li>
|
|
</ul>
|
|
</li>
|
|
<li>}</li>
|
|
</ul>
|
|
<br>Don't use section/div by default, used a lot!<br>
|
|
<br>Use "target-counter" to make <br>- TOC page numbers<br>- refer to other pages, like "see page 6"<br>
|
|
<br>A full finished version of this book: <a href="https://gitlab.pagedmedia.org/samples/printing-in-relation-to-graphic-art" rel="noreferrer noopener">https://gitlab.pagedmedia.org/samples/printing-in-relation-to-graphic-art</a>
|
|
<br>Another important repo is: <a href="https://gitlab.pagedmedia.org/tools/experiments" rel="noreferrer noopener">https://gitlab.pagedmedia.org/tools/experiments</a>
|
|
<br>
|
|
<ul class="indent">
|
|
<li>Tools for bleed, cropmarks, generating an index</li>
|
|
<li>(but there is bleed in the center fold)</li>
|
|
</ul>
|
|
<br>
|
|
<a href="https://mattermost.pagedmedia.org" rel="noreferrer noopener">https://mattermost.pagedmedia.org</a>
|
|
<br>
|
|
<br>
|
|
<br>
|
|
</body>
|
|
</html>
|
|
|