[IAEP] [Sugar-devel] Sharing Images in the neighborhood

[Aleksey Lim]

On Thu, Jul 16, 2009 at 10:46:43PM -0400, Caroline Meeks wrote:
> Today we wanted to take pictures the teacher had taken with a camera and
> share them with the class.
> 
> This turned out to be much harder then I expect.
> 
> It turns out you can't just share something from your journal into the
> neighborhood.
> 
> So we tried opening it in image viewer.
> Then share to neighborhood.
> Other person clicks on it.
> They get a popup from the journal asking what they want to open.
> Never shows what the first person opened.
> Is this an image viewer bug or was it designed to work this way?
> 
> We ended up uploading to picasa and Anurag sent me an invite. Another bug,
> (this one reported) is that you can't follow links easily in google mail, by
> just clicking on them.  However I remembered the workaround and used follow
> link.  I then shared the bookmark.
> 
> Then next bug (and this one is Google's not ours) the shared bookmark wanted
> people to log in, even though Anurag had made the album public.
> 
> Very painful for what should have been a simple task!
> 
> We need a way to get something from one journal to another without a lot of
> opening of other programs.  Even with this work around I now have to teach
> the kids, goto the neighborhood, open up the shared  browse, click the
> bookmark when it appears, download image, switch program, get image into
> TA.  Lots of steps. Infact what happened is 25% of the class opened browse
> from thier home rather then the shared browse then didn't know where to go.
> 
> Way simpler if we could just share a journal item with the neighborhood.
> Any ideas for both short term work arounds and longer term fixes?

(I see this week is a week of sharing:)

I propose to use page
http://wiki.sugarlabs.org/go/Features/Peer_to_Peer_Objects_Sharing
to collect all P2P sharing related features.
(in contrast with http://wiki.sugarlabs.org/go/Features/Server_Objects_Sharing)

In my mind there could be several schemas:

* Only one common collection of shared objects.

  User can mark any object in Journal as a "shared" object, so other users
  can choose "Browse shared objects" option from buddy context menu in
  neighborhood View and browse/download all shared objects(how, in what
  window?)

* A superset of first option - collections of objects

  In fact it relates to Library activity. User creates a collection of
  objects(they are "stored" in some way in Library object), later user
  shares this object, opening this object by other user means opening
  shared Library object(with list of shared objects).

  Having collections makes sense in "local" mode as well - user can have
  several collections for local purposes i.e. "My favorite books" etc.

-- 
Aleksey