On 9/27/07, Eben Eliason <[EMAIL PROTECTED]> wrote: > > > I think the point of confusion here is that some activities create > > > *multiple* entries. These entries, as output of a single activity, > > > are closely associated with the session which created them. In this > > > case, the session is the "roll of film" and the associated entries are > > > the individual photos. > > > > > Is there a way to associate these that maintains the security model? > > > > Certainly. Sugar just has to tell Rainbow "The user is resuming activity > > X. Please give it A, B, C." > > This sounds like what we're after, really. The question is how Sugar > can know what A, B, and C are. Either the activity has to start and > give Sugar the list of things it wants, or Sugar has to figure it out > on its own. If A, B, and C share some common identifier in their > metadata this could be used to determine what to give X (by passing a > query to the DS for anything having the same activity ID, for > instance). Does that fit your thinking? We'd have to adjust the > Sugar to provide this service in this case.
The journal when starting an activity can query the DS for all the objects with the same activity_id and tell rainbow to give access to all of them to the activity. Marco _______________________________________________ Sugar mailing list [email protected] http://lists.laptop.org/listinfo/sugar
