Prev: daemon.DaemonContext and logging
Next: New user documentation for ‘python-daemon’ (was: daemon.DaemonContext and logging)
From: Donn on 17 Dec 2009 13:43
On Thursday 17 December 2009 19:46:41 Terry Reedy wrote:
> His idea was for a document rather than
> app centric plain.
These days I find the notion of monolithic apps to be a pita.
The concept of many small black boxes (but open source) that each do a single
job and pipe in/out is so much more powerful. I don't see why everything in a
gui and down can't be such a box. Then we get to wire them together as needed.
We'd still have 'big apps' but they would be constructed more loosely and we
could adapt them to fit real life needs.

I dunno. I think big apps are dinosaurs. As much as I love Inkscape and
Blender and others, they are all islands with vast gulfs between them.

And let's have Python glue them all together!

> Not clear how one would pipe data from app to app in
> his model, though.
The picture I have of it is illustrated by Blender's material node system.
have a look at this pic:
http://upload.wikimedia.org/wikipedia/commons/2/26/Working_with_Nodes_Blender.PNG
Just a mental jump-off point. Think bash meets zui with a Python driving. :D

\d

--
\/\/ave: donn.ingle(a)googlewave.com
home: http://otherwise.relics.co.za/
2D vector animation : https://savannah.nongnu.org/projects/things/
Font manager : https://savannah.nongnu.org/projects/fontypython/
First  |  Prev  | 
Pages: 1 2 3 4 5 6
Prev: daemon.DaemonContext and logging
Next: New user documentation for ‘python-daemon’ (was: daemon.DaemonContext and logging)