Talk:Activities/Turtle Art-0.86

discussion thread about collaboration

 * bemasc: have a minute to talk about collaboration?
 * walterbender: sure.
 * I was a bit disappointed to get exactly zero response on my e-mail.
 * bemasc: the one about terminal?
 * bemasc: sounds very cool, but I haven't had a chance to try it yet
 * bemasc: I am wondering about how to support multiple styles of collaboration within one activity
 * bemasc: maybe tomeu knows: are there plans to be able to share clipboard entries?
 * or do we save them to the Jpournal and them share them from there?
 * so we definitely have the ability to do the second thing
 * I ask because probably the most useful share in TA is to share a stack of code.
 * but to go through all those steps is tediuos.
 * I haven't heard a proposal recently to push clipboard entries around, but technically it shouldn't be hard
 * My immediate question is: where does it go, on the recipient's side?
 * my default share is "joined at the hip" sharing... which I find cumbersome
 * bemasc: on to their clipboard...
 * walterbender: that's fine, but then it should be indicated differently from a Journal->Journal transfer in the UI
 * so that the user knows what to expect when they accept the transfer
 * If clipboard sharing were easy, I could use it instead of add it to my activity explciitly
 * I'm a strong proponent of "universal collaboration" tech of this sort.
 * bemasc: +1
 * I put this in the same category with overlay chat and push-to-talk
 * bemasc: maybe if two people are collaborating, then to share a clipboard entry doesn't need confirmation, it just happens
 * bemasc: sort of what the bulletin board was supposed to be...
 * walterbender: that's a good point
 * the problem is: the clipboard is system-wide
 * tomeu: might be #330 - the description is a bit too vague to be sure
 * It should not go on top, in the way of your clipboard entry
 * I don't think allowing other users to push things to your clipboard arbitrarily is a wise design.
 * the good thing is that the colors already make a perfect visual cue that it's not yours, but that's only if you pull up the frame for drag&drop
 * bemasc: even if it went somewhere besides the top of your clipboard stack?
 * walterbender: what if we reuse the "incoming file transfer" system, but have that notification appear on the left side
 * homunq: resource exhaustion attacks galore.
 * homunq: but this is someone you are already sharing with...
 * bemasc: but only from your friends with whom you're currently sharing
 * heh
 * this line of thought helps, but I still have a problem in that I want to support multiple types of sharing
 * I am of the right age to remember the "punting" attacks that were common on AOL
 * well, it's adding complication, but you could put some limits.
 * walterbender: I'm not sure what you mean by that. Could you elaborate?
 * I already support the kind of sharing bemasc uses in Terminal... everyone sees everything everyone else does.
 * bemasc: but I also want to support a different kid of sharing, where we each do our own thing and only share the output of our individual turtles
 * sdziallas: thx! won't be able to review it today, but maybe i can get a look at it tomorrow in the bus
 * silbe: sure ;)
 * bemasc: and the sharing blocks function is a third type, but we have a potential system-wide solution for that.
 * sdziallas: (bluntly assuming you're interested in a review :) )
 * walterbender: Are the second and third not handled sufficiently by passing around Journal objects?
 * bemasc: the third, yes. But I wasn't clear about the second one.
 * I want one canvas but independent turtles
 * that is different from everyone sharing one turtle
 * walterbender: do the turtles each need to be owned by one user?
 * actually, sharing one turtle but not sharing the code is a fourth possibility...
 * maybe you could support multiple-turtle operation, independent of whether there are multiple users
 * bemasc: the idea would be for each of us to program our own solution to a problem but see the display of all of our efforts in one place
 * bemasc: then we could share the code (through the journal) if necessary
 * well, one way to do this is is to enforce "program our own solution" socially rather than technically
 * bemasc: I could/should support multiple turtles, but my problem is more general.
 * bemasc: let's take terminal for example.
 * so N users join, each creates a turtle, and each edits their own turtle's code.
 * what if I want to share only most of what I type?
 * bemasc: I can do that, but how to have some mode where we share one turtle?
 * Well, Terminal is a particularly weird example, since it's not a from-scratch creation. Its behavior is limited by the underlying technologies, which are bash, ssh, screen, xterm, etc.
 * in that case, N users join, but only one of them creates a turtle
 * and they all agree to edit that turtle's code
 * bemasc: I guess I need to think about the UI flow a bit more
 * or N users join, 3 of them make turtles, and then they divide into three teams, plus two "helpers"
 * each team works on their own turtle, but the helpers look at all the code and offer advice to all of them
 * (and maybe ensure that they stay in sync, if all 3 are supposed to be doing something choreographed)
 * The possible complexity of use cases is unlimited
 * and at some point, one inevitably decides that some complex use case is simply too much work to get right.


 * homunq	remembers when he was a kid, there was a great book named "turtle geometry" (actually my uncle did the typesetting) and it had multiple turtles illustrating cool interactions - they could detect each other. I never figured out how to make that happen on my apple II, though (I'm sure I could work it out now).
 * bemasc: I'll have to think about how the invitation process would work
 * that book is how I learned special relativity at about age 10-15. (I never read it cover-to-cover but just browsing the illustrations and reading a bit I "got it" over those 5 years)
 * bemasc: I suppose you join to a particular turtle and see everything associated with that turtle
 * homunq: gosh
 * and only the output of the other turtles...
 * walterbender: you are working awfully hard to prevent people from seeing each other's code.
 * bemasc: it is a matter of clutter...
 * walterbender: there's already a system to show/hide the code
 * honestly, it is more impressive about the book than about me. I have never seen another explanation of special relativity that even came close to being that comprehensible.
 * bemasc: yes, so maybe I need to invoke it only for the turtles you aren't controlling
 * walterbender: I think it might be easier to extend that mechanism to multiple turtles
 * so many turtles, so little time :)
 * One obvious thing to do would be to spawn a new workspace for each turtle
 * so each turtle draws on a separate canvas
 * bemasc: I could just run multiple instances of TA
 * and then additionally have an "All turtles" canvas that shows them all, composited together.
 * bemasc: but I want to share the canvas
 * bemasc: that is an idea...
 * The "All turtles
 * argh


 * homunq	wants them in same canvas. Still remembers the illustrations of predator-prey strategies between two turtles.
 * For simplicity, maybe the "All turtles" canvas never shows any code; it's view-only.
 * "All turtles" could be a daemon user that joins all the activities
 * it'd launch separately
 * I don't think that's how I would implement it, but I don't know much about TurtleArt's internals.
 * bemasc: I am thinking it might be easy to just let the current sharing scheme do what it does and just use All Turtles to aggregate the results of the various actvities being shared
 * I mean, being able to get a bearing/distance for other turtles and put them in variables would be a great block.


 * homunq	goes back to own bikeshed.
 * walterbender: that depends on whether the turtles can interact
 * which, I imagine, is what you want.
 * In that case, it's not merely an aggregation problem.
 * bemasc: right now they cannot, but "All Turtles" could be the medium for their interaction.
 * Yes, but communication between different shared instances is somewhere between impossible and inadvisable.


 * homunq	has one more comment about your bikeshed: on the apple II, the default canvas was toroidal, and I liked that better.
 * homunq: in most Logos, that is a switch
 * yes
 * homunq: it would be easy enough to add to TA
 * homunq: right now, I explicitly turn it off when I export to Logo
 * but kids will not find the switch until they're bigger. I think toroidal is the best default.
 * homunq: let me play with it. It was a design decision I inherited from Brian
 * (though my daughter went through a phase at 3 when the invisible canvas was hilarious, now at 4 it annoys her. So it's actually a tough choice.)
 * anyway, lots to think about. thanks everyone.
 * I mean, getting the turtle lost. When she went in straight lines all the time she thought it was cool.


 * homunq	supposes that an infinite cylinder would have the best of both worlds. You never get totally lost, but you are pushed to think of abstract space....

debugging code from roberto
0, u'show', 0, 309, [None, 1, None, [1, [u'string', u'text'], 74, 319, [0, None]], [2, u'forward', 55, 526, [None, 12, 3]], [3, u'left', 55, 565, [2, 4, 5]], [4, [u'number', u'90'], 129, 574, [3, None]], [5, u'show', 55, 604, [3, 6, None]], [6, [u'string', u'text'], 129, 614, [5, None]], [7, u'start', 229, 151, [None, 8]], [8, u'forever', 241, 201, [7, 9, None]], [9, u'kbinput', 322, 215, [8, 10]], [10, u'print', 322, 269, [9, 11, None]], [11, u'keyboard', 396, 278, [10, None]], [12, [u'number', u'100'], 129, 535, [2, None]], [-1, u'turtle', 1.4210854715202004e-14, 199.99999999999997, 270.0, 0, 50, 5]]