Opened 15 years ago

Closed 14 years ago

Last modified 11 years ago

#491 closed defect (fixed)

TurtleArt sharing needs new logic

Reported by: walter Owned by: walter
Priority: Normal Milestone:
Component: Turtleart Version: Git as of bugdate
Severity: Major Keywords:
Cc: Distribution/OS: Unspecified
Bug Status: Assigned


As in the case of Write, if the sharer leaves, there is no way for new joiners to get synchronized.

Attachments (1)

turtle_art_blocks_not_in_sync.png (410.5 KB) - added by garycmartin 15 years ago.

Download all attachments as: .zip

Change History (6)

comment:1 Changed 15 years ago by walter

  • Milestone changed from 0.86 to 0.88

Lots of ideas, but not a definite plan of action in time for 0.86

comment:2 Changed 15 years ago by garycmartin

Yep, have just started some general collaboration testing here, resuming a TA activity previously shared is fine as long as no one involved has made additional 'off air' edits. If changes have been made, you have no idea what you might be driving for the other collaborators (attached a quick screenshot). If you stick to working together, collaboration works well.

Changed 15 years ago by garycmartin

comment:3 Changed 14 years ago by walter

  • Milestone changed from 0.88 to 0.90

The current plan is to share turtles, not code. (Code can be shared through the Journal or clipboard). The underlying mechanism (support for multiple turtles) is in place. The new sharing model will not be finished in time for 0.88. Pushing out to 0.90

comment:4 Changed 14 years ago by walter

  • Resolution set to fixed
  • Status changed from new to closed

Actually squeezed this into 0.88... Turtles are shared and it is assumed code will be shared through the send-to mechanism in the Journal.

comment:5 Changed 11 years ago by dnarvaez

  • Milestone 0.90 deleted

Milestone 0.90 deleted

Note: See TracTickets for help on using tickets.