Table of Contents


1.1 0) research - event-frame-process KR

1.2 1] Infrastructure - windows, media, vc, diagram

1.3 2] Relation//display and processes

and base visible manipulation of these

fork jonni

1.4 3] Emacs CL/Common Lisp guide to note: cl-guide.el


1.5 4] resource POOL    media

image pool

links main files - org-mode - C-c C-o [[]] format - RESOURCES - iimage/wdired ref also

auto-indexing - again linked to RCS

1.6 5] Lisp/SLIME buffer connection (by way of pipes?)

or more simply C-u prefix to C-x C-e prints results into current buffer

from here we could parse matters

text/code <-> (unix/any) process

also swank [whole thread at]


1.7 6] version control. spider diagrams/networked and snapshots



2 resources:    media

file:lifecode/platform.lisp // potential port to Emacs Lisp for KR - using (require 'cl)


3 eev itself

Commands to generate pages with lists of hyperlinks: M-h f -- hyperlinks to the current file M-h M-i -- hyperlinks to the current Info node M-h M-f -- hyperlinks to an Emacs function M-h M-k -- hyperlinks to a key sequence and to the function associated to it M-h M-v -- hyperlinks to an Emacs variable M-h M-m -- hyperlinks to a manpage (ask for name) M-h m -- hyperlinks to a manpage (being viewed) M-h M-d -- hyperlinks about a Debian package

4 org-mode/eev

we have:

cycling of headings, links, links also support search facilities, database (tags), and properties

properties API:


elisp:(find-file-other-frame "Elisp.org") An elisp form to evaluate (this is in org-mode and eev)

<elisp:(find-node "(elisp)Processes")>

<elisp:(find-node "(emacs-w3m)")>

we can also add new hyperlink types

// how do we jump across headings

links main files - org-mode - C-c C-o [[]] format - RESOURCES - iimage/wdired ref also


4.1 some way of cycling through links in buffer - see linkd or org-mode

eg. pages as in goby - narrowing to link or code regions

[org-mode headings with ** format C-u TAB global cycle. S-tab and tab]

also see file:lifecode/org-toc.el

org - table of contents mode [ cycle through once we toggle with f character after:


5 linkd ???

what does linkd add? - copy cycling fetaures or find these in org-mode


process block


it works with org-mode - SAVING bug

also look at howm:


two way linking:

all based on grep

and also cell-mode and eon:


6 subtitling in file:/root/experiment/gneve

7 support for framing/annotations: see also: file://root/experiment/lifecode/annotate110907.el

(flite also perhaps)

8 pointers:: Processes

processes in the buffer - active, contributing (as actor's dialogue, as agents (tied into OS) to buffer

9 event software - roll call of techniques (PD, audio in Emacs - nyquist, rec, play, shell):

sliced rec and play ??

commandline splitting with for example: play xad -f u -s b -t raw -r 8000

(using raw split -b 1024 par example)

nyquist from emacs as inferior lisp

rec -w wav file.wav and play (play also in nyquist)

gneve - video

iimage - images

emacs - comint and pd console output

pd -stderr -- send printout to standard error instead of GUI

// added to .pdrc and then comint-run pd -- this gives us output

--- look again at pd, plenum, five software acts:

pd: -qlist.... but to specify exactly what we want

10 Strategies/acts here:

  1. curtains drawn - remote operation

pre-compilation (macros) //assemblage

  1. Protocol and domain terms

protocol performance. frames

system events and process manipulation

  1. Coded rabbit holes - script and speech
  2. sampling/data slicing/slow scan

slicing audio -> pd - round table of microphones

slice video -> automated gneve?

--- also this si to some extent scheduling

  1. simulation/catastrophe

audience simulation (processes again). script and actions

  1. pink light

11 shifts

Piksel - from hardware to execution by way of interface.

  1. jessica - chaos
  2. Ludics RFID
  3. volcanic
  4. otto bruno - dovetailer
  5. porn coding - virus
  6. execution - apparatus rendered active
  7. but on some kind of process/KR base

what? how?

12 comments/diagram

//buffer as resource

on which we have - view action (processes)

and link system - KR again



time slicing - split a recorded file/jekyll/other potential shell scripts

time lapse - and (VC) - record text or code file chnages (only for some kind of spider-branch rendition)

version control (VC) // version control as branching text audio on splitting timeline - potential web-based wiki-like feature-set for text

audio and video version control



code and markup

code generation - simple examples

this organisation - outline (mode) itself - // as macros/language to be marked up automatically from this page


event summary



**view/action/resources. collation/collection of resources (files/actions/views?)

//- some kind of diagram mode for this kind of thing

Author: m <m@1010.co.uk>

Date: 2007/10/04 19:43:43