KindlesDream LAFKONWorkshop

From XPUB & Lens-Based wiki
Revision as of 20:32, 23 September 2010 by Migratebot (talk | contribs) (Created page with "= LAFKON Workshop = == organisation == please choose a username and a password and send me (christoph at lafkon dot net) the output of: <source lang="text"> htpasswd -nm...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

LAFKON Workshop

organisation

please choose a username and a password and send me (christoph at lafkon dot net) the output of:

htpasswd -nm yourusername


or use http://www.htaccesstools.com/htpasswd-generator/

so i can create you an account for the subversion repository. yourusername will also be used for your directory for the workshop.


technical

sudo gedit /etc/texmf/texmf.cnf


TEXMFFORKABLE = /path/to/your/forkable/folder/utils/latex/TEXMF


TEXMF = $TEXMFCONFIG,$TEXMFVAR,$TEXMFHOME,$TEXMFFORKABLE,$TEXMFSYSCONFIG ...


sudo texhash


workshop schedule

PROLOGUE

ALREADY MADES

  • Linux Audio Conference 2008
  • Linux Audio Conference 2009
  • make art 2009
  • chmod+x art 2010

Examples to give an idea.


FUNDAMENTAL TOOLS AND PRINCIPLES

Explanation of fundamental principles and ideas behind the forkable repository. This will include some of the fundamentals of the Unix Philosophy and its consequences in practise for the forkable repository as well as a basic introduction to LaTeX.

EXAMPLES IN ACTION

These are examples because they are not fundamental to the approach but could be easily replaced by anything that works for e.g. text manipulation (BASH) or more visual oriented tasks like e.g. graphics manipulation (Processing). E.g. Python, Shoebot, ...

Everything that is shown is available in code and the starting point for participants to hack, rethink, modify, question.

TECHNICAL

At this point all participants should have a running copy of the forkable repository. This requires a linux distro(ubuntu,debian,puredyne), a basic texlive installation, a svn checkout of forkable.

Every participant will have a working directory inside the forkable document tree that can be commited and used by other participants.

ACT

By now every participant has the document tree with scripts and LaTeX code she can execute, compile and hack.

IMAGINABLE SCENARIOS


PARTICIPANT WANTS TO INVESTIGATE THE POSSIBILITIES OF LATEX

WHAT CAN HE DO?

  • Write LaTeX Code/Macros
  • Work on formatting possibilities
  • Find out what's difficult in LaTeX, find workarounds
  • Find out about automated generation of LaTeX Code

WHAT SHOULD HE DO?

  • Document his work with compilable LaTeX Code

PARTICIPANT WANTS TO WORK LUA/PYTHON/BRAINFUCK/PROCESSING

WHAT CAN SHE DO?

  • Generate anything with language X
  • Manipulate LaTeX Code/Macros with language X
  • Do something completely different

WHAT SHOULD SHE DO?

  • Document her work with compilable LaTeX Code

PARTICIPANT WANTS TO INVESTIGATE IN TEXT BASED FORMATS

WHAT CAN SHE DO?

  • Find text based formats
  • Learn about text manipulation (e.g. Unix Power Tools)

WHAT SHOULD SHE DO?

  • Document her work with compilable LaTeX Code

PARTICIPANT WANTS TO DRAW AN IMAGE AND SING A SONG

WHAT CAN HE DO?

  • Sing a song and dance along

WHAT SHOULD HE DO?

  • Document his work with compilable LaTeX Code

PARTICIPANT WANTS TO WORK ON A EXISTING PROJECT

WHAT CAN HE DO?

  • continue his work and research

WHAT SHOULD HE DO?

  • Document his work with compilable LaTeX Code

PARTICIPANT WANTS TO DO SOMETHING WE COULD NEVER HAVE IMAGINED

WHAT CAN SHE DO?

  • Still trying to imagine

WHAT SHOULD SHE DO?

  • Document her work with compilable LaTeX Code

By now participants work alone or collaboratively on a theme while trying to stick to a modular practise that continously releases grains of code and work which can be appropriated and reused by other participants of the workshop. The goal is to produce "interstates" that CAN be adapted, means, participants will have to think their work not as one monolithic oeuvre but the combination modules that stick together. This can be lines of code, images, texts, ideas, everything that is eligible for reuse.

For the documentation we try to establish a common set of LaTeX macros to keep LaTeX Code interoperable.

UNUSED BY NOW (may be lucky findings): Timeline Plots with GNUPlot MetaPost Tutorial Vector data processing in GRASS GIS Vector network analysis - GRASS-Wiki Welcome to Epigrass’s documentation! GML (Graffiti Markup Language) Graphviz The sng home page rita OBJ Files - A 3D Object Format Shoebot Country Dance Animation Eliza javalatex - wikibooks2latex LaTeX-Kompendium: Notensatz GNU R: Automation und dynamische Dokumenterstellung Programmieren in TeX / LaTeX SourceForge.net: simon / speech2text LaTeX: Serienbrief mit externen Daten Evolutionary Computing with Push, PushGP, and Pushpop Importing Inkscape in Fontforge Therion: new approach to cave surveying


EPILOGUE

Participants pack their workshop result into a LaTeX project. This includes the development of LaTeX formatting, font preparation, ...

From all separate projects we will select parts for one formatting and pack all contents collaboratively into one "publication".

The "end publication" can be printed in its current state (depending on its size) or used through its modules (formatting, content, developed scripts) as starting point for further publications/projects.