A few days ago I wrote down some (very preliminary) ideas relating to liquid

1) Blog format doesn't work so well as a collaborative research tool (if this is the intention). In some way "bootstrapping" could occur to transition (as in any software development project) from description and ideas into the in some way finished project/software.

2) Exposed code as interface should be key. It doesn't make sense to tunnel down from an always already conditioned (static) interface into always dynamic code. The reverse process needs to take place.

3) Widgets, desktop - again operating in a one way street relation to code - (and mention of open source below). The desktop provides for an illusion of transparency - it is an horizon on which the real (the con trick of software which proposes its own license-wrapped existence) appears. That code defines and can redefine (cynical non-transparency) is the important part. The desktop is a limited field of action - action restraint (Mallarme). Examples of potential workflow include GNU Emacs and Planner mode - content and code are rewritten simultaneously with publication as a funneling markup (restriction) to HTML. Again the format/rendering of data is less important IN THIS RELATION - it could equally well be graphed pixels, a pie chart. What matters is that there is a reduction - we potentially leave code space but as in a conversation can re-enter at will - that is the active part.