[Sugar-devel] friendview.py

Tomeu Vizoso tomeu at sugarlabs.org
Mon Oct 19 06:51:45 EDT 2009


On Sat, Oct 17, 2009 at 14:45, Eben Eliason <eben at laptop.org> wrote:
> On Sat, Oct 17, 2009 at 9:40 AM, Wade Brainerd <wadetb at gmail.com> wrote:
>> Yeah, P2P activity sharing would be awesome.
>>
>> http://wiki.sugarlabs.org/go/Development_Team/Almanac/Activity_Bundles
>> says "Activities are meant to be shared between children. If a child
>> doesn't have the activity, it is automatically transfered to the child
>> when he or she joins the shared activity." but I don't believe this
>> was ever implemented...?
>
> Right.
>
> To me, it sounds like the first step in building either of these
> systems (automatic p2p transfer, download from browse) is figuring out
> a way to publish the activity icon so that we DON'T have to show a
> question mark. I would much rather show the icon for the activity that
> the child doesn't have, and perhaps badge it in some way to indicate
> that they don't yet have it.
>
> This seems desirable regardless of which solution we choose to
> download the activity.

Tim, would you like at doing that with telepathy, or would you prefer
to first display a "missing" icon?

Thanks,

Tomeu

>
>
>> -Wade
>>
>> On Sat, Oct 17, 2009 at 9:35 AM, Benjamin M. Schwartz
>> <bmschwar at fas.harvard.edu> wrote:
>>> Tim McNamara wrote:
>>>> Naturally, people will probably want to click on that question mark. Would
>>>> we be able to have a dialogue like "Search for activity %s?" % name, which
>>>> if accepted opens up Browse and searches http://activities.sugarlabs.org to
>>>> download it?
>>>
>>> That would be about ten times better than the current behavior.
>>>
>>>> This would be easiest if you can p2p file share activities...
>>>> I've played around a bit, but it doesn't look especially obvious.
>>>
>>> Yes, that would be, by far, even better.  It shouldn't be incredibly
>>> difficult, since Telepathy provides us with a high-level file transfer
>>> operation, but there's still some code required to (1) request the
>>> transfer, (2) create a bundle if necessary, (3) transfer the bundle, (4)
>>> install the bundle, and then (5) launch it.
>>>
>>>
>>> _______________________________________________
>>> Sugar-devel mailing list
>>> Sugar-devel at lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>>
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>



-- 
«Sugar Labs is anyone who participates in improving and using Sugar.
What Sugar Labs does is determined by the participants.» - David
Farning


More information about the Sugar-devel mailing list