[Sugar-devel] Turtle Art on Activities.sugarlabs.org

[Behavior Vehikel]

Hi,

For exchanging and publishing data created by Kandid I have a vague
idea. Don't know if it makes sense. I want to avoid a client / server
centric architecture. It should work more peer to peer.

1) Every computer having Kandid installed could run a small Database.
Only a few data records + meta – information.
2) And there should be a daemon (service) running on this computers
independent whether the Kandid activity is started or not.
3) If there are some buddies in my neighborhood having the same daemon
running new data records can be send or received in the background.

* There should be life time concept to forget old stuff.
* A explicit user interaction should be necessary to mark and comment
things for publishing. Avoid to flood the world with garbage.

best regards
Thomas
-- 
http://digital-defect.org


2010/2/25, David Farning <dfarning at gmail.com>:
> The other day during an infrastructure meeting, Walter brought up some
> thought on how to enable kids to exchange Turtle Art projects....
>
> Alsroot has been thinking about how to do this through a.sl.o since he
> became the activities.sugarlabs.org code maintainer.
>
> The high level view is that someone can easily upload Turtle Art creations
> to somewhere and then they, or others, can go to a portal to download other
> Turtle Art creations.
>
> Client side, this would require:
> 1. Adding a widget to either the journal or the TA activity to upload the TA
> Bundle.
> 2. Adding a TA bundle installer to handler TA Bundle downloads.
>
> Server side, this would require:
> 1. A place to accept TA bundle uploads.
> 2. A search-able place from which to download TA bundles
>
> We have some similar systems we can look to as examples.
> 1. Scratch -- Scratch has an upload button and users can download scratch
> projects from --  http://scratch.mit.edu/galleries/browse/newest
> 2. ASLO --  Users upload XO bundles via a web interface and download via a
> web interface.
>
> My initial instinct is to see if ASLO can be adopted to fit this need.
> Primarily because we have it, it works, and it is scalable.  On the other
> hand, if the only tool in one's toolbox is a hammer, everything looks like a
> nail. (How is that for over using clichés and buzzword?)
>
> Considerations:
> ASLO rocks:)
> ASLO can be adapted to handle various file types.  For example:
> https://addons.mozilla.org/en-US/firefox/browse/type:3
> https://addons.mozilla.org/en-US/firefox/browse/type:2
>
> Each file type can have a separate look and feel.
>
> Is the activity creation and upload process too complicated for young users?
>
> Moving forward:
> Would it be possible to journal or TA widget which:
> 1.  Walks the student though a upload wizard.
> 2.  Combines the TA project into a into a bundle with the metadata generated
> in the wizard.
> 3.  Sends the bundle to activites.sl.o/uploads
>
> Would it be possible to setup/adapt ASLO to:
> 1. Handle TA files types.
> 2. Accepts TA bundles+metadata uploads and inserts them into the review
> queue.
>
> david
>