On Mar 19, 2007, at 3:01 PM, Isaiah Beerbower wrote:
Hello,
Hello :D
After looking at Quartz Composer and thinking/researching the matter I think making Workflow.app take an object oriented 'dataflow' approach may be better than my previous diagrams.
That's nice, I've been thinking about doing something like this for some time now and I think there are some very nice benefits to it if done well.
Wikipedia has an article about this to: http://en.wikipedia.org/wiki/Dataflow_language
Didn't know it had so much potential tho.
I've also been thinking that it would be better in the long run if Workflow.app became a language in it's own right. The code generation sounded like a good idea at first, but I'm not so sure about it now...
It should be possible, but perhaps it isn't necessary if a way to extend the available objects is present (I really like the idea of grouping smaller objects together to construct bigger entities). Another thing is that drawing a line (if it can be done) between a full blown language and something with a smaller scope is difficult I think. My idea is that you can give users as much as you can, and they will use only what is needed to complete their task.
Ricardo Correa _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
