[L2Ork-dev] tracecall

[Ivica Bukvic]

I like the second approach.

Best,

Ico

-- 
Ivica Ico Bukvic, D.M.A.
Director, Creativity + Innovation
Institute for Creativity, Arts, and Technology

Virginia Tech
Creative Technologies in Music
School of Performing Arts – 0141
Blacksburg, VA 24061
(540) 231-6139
ico at vt.edu

www.icat.vt.edu
www.performingarts.vt.edu
l2ork.icat.vt.edu
ico.bukvic.net

On Sat, Jul 18, 2020, 22:20 Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:

> Ok, I got a nice tracecall prototype going.
>
> Given this:
>
> [bang(
> |
> [int 42]
> |
> [tracecall]
> |
> [print]
>
> You get this to the console:
>
> print: list tracecall float 42
> print: list int bang
> print: list messresponder bang
> print: list canvas mouse 112 33 1 0
> print: list guiconnect mouse 112 33 1 0
>
> Now let's talk user-experience.
>
> IMO it's not very useful to have a series of messages output to an
> outlet. At the very least I'd like default behavior that sends
> something like this to the console:
>
> trace: tracecall float 42
> trace: int bang
> trace: messresponder bang
> trace: list canvas mouse 112 33 1 0
> trace: list guiconnect mouse 112 33 1 0
>
> Where trace is a link that selects the relevant object when mousing over
> it.
>
> Furthermore, the args should be links which, when clicked, send that
> data to the relevant object.
>
> I think that would be an extremely useful tool.
>
> Additionally, I'm wondering if tracing backwards really fits the
> dataflow paradigm. Wouldn't it be better like this?
>
> trace:
> guiconnect mouse 112 33 1 0
> canvas mouse 112 33 1 0
> messresponder bang
> int bang
> tracecall float 42
>
> And again with links in the obvious places.
>
> -Jonathan
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20200719/a5108732/attachment.html>