On Thu, Jul 16, 2009 at 08:03:15PM -0500, David Farning wrote: > On Thu, Jul 16, 2009 at 7:41 PM, Aleksey Lim<alsr...@member.fsf.org> wrote: > > On Fri, Jul 17, 2009 at 12:17:13AM +0000, Aleksey Lim wrote: > >> Hi all, > >> > >> One of lacks that sugar environment has is simple way to share sugar > >> objects for broad audience i.e. like scratch community has[1] > >> (thanks to davidmorris form #sugar). > >> > >> So, I've created [2]. Original idea was having highly integrated sharing > >> features into sugar shell but looks like we can do simple things first > >> and even utilize only Browse for browsing/download/upload sugar objects. > >> > >> The problem is - what web engine we should use. > >> > >> * Utilize AMO[3] engine which is used in activities.sugarlabs.org > >> in that case we can create something like library.sugarlabs.org to not > > > > Pro: > > * we do not split users behaviour, they need the same experience > > that ASLO requires > > * one common branding for activities and objects sites > > * AMO has sufficient(imo) functionality - reviews, ranking, collections > > and thumbs mode > > https://addons.mozilla.org/en-US/firefox/browse/type:2/cat:all?sort=popular > > * we hack AMO code anyway - its not a problem in adding new AMO environment > > > > Contra: > * Locality - In may instances the stuff created by students will only > be of interest to their friends, teachers, and parent. Serving via > ASLO publishes the content globally.
"publishes the content globally" is the original purpose for this feature in contrast with http://wiki.sugarlabs.org/go/Features/Peer_to_Peer_Objects_Sharing Or you mean possibility to share objects on local servers? -- Aleksey _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel