Re: [Sugar-devel] [Server-devel] [IAEP] copy files to/from server
As I mentioned before, I am currently working on the multi-selection support for Journal (which is a prerequisite for the "cloud journal" and explains why I haven't been very active on this thread). Anyway, I am listening to other's technical and non-technical ideas, but _my_ approach is first to provide extra storage capacity on the XS in the most transparent way to the end users. Therefore, In the non-technical front, I believe we should stick to the Journal integration idea, displaying this resource exactly how we display removable devices. In the technical front, I haven't checked all the solutions mentioned but I would definitely go with something that _already_ provides support for regular file system interaction. With something like that (and please someone let me know if I am wrong), the integration part will be a lot easier, like i.e (as Walter commented) we could use his/mine/jasg "documents folder" patch. Saludos, tch On Mon, May 23, 2011 at 4:16 PM, Christoph Derndorfer wrote: > On Mon, May 23, 2011 at 2:24 PM, Martin Langhoff > wrote: >> >> On Mon, May 23, 2011 at 1:41 AM, Sridhar Dhanapalan >> wrote: >> > Interesting. Does WebDAV work as a normal mount, like CIFS or NFS? >> >> From the PoV of the user, yes, it looks like a mountpoint. >> Technically, you can mount it at the linux kernel level, at the gnome >> IO libraries level, or from Sugar, with a pure python implmentation. >> >> > What would be the best way to get this working on Sugar? >> >> You don't have a lot of time it seems. I'd implement it on top of >> gnome VFS of in pure Python. In both cases, I'd make it look like >> another disk from the Journal (as an initial implementation at least). >> >> I'd say talk with Martin Abente, he's looking into this problem space. > > Could we maybe split this thread and keep technical discussions focused on > XS-devel and Sugar-devel lists? I think this could also also help in getting > some non-technical and/or end-user feedback and suggestion from people on > IAEP who aren't into all the technical details (something which I think tch > was also interested in). > Thanks, > Christoph > > -- > Christoph Derndorfer > co-editor, olpcnews > url: www.olpcnews.com > e-mail: christ...@olpcnews.com > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Server-devel] [IAEP] copy files to/from server
On Mon, May 23, 2011 at 2:24 PM, Martin Langhoff wrote: > On Mon, May 23, 2011 at 1:41 AM, Sridhar Dhanapalan > wrote: > > Interesting. Does WebDAV work as a normal mount, like CIFS or NFS? > > From the PoV of the user, yes, it looks like a mountpoint. > Technically, you can mount it at the linux kernel level, at the gnome > IO libraries level, or from Sugar, with a pure python implmentation. > > > What would be the best way to get this working on Sugar? > > You don't have a lot of time it seems. I'd implement it on top of > gnome VFS of in pure Python. In both cases, I'd make it look like > another disk from the Journal (as an initial implementation at least). > > I'd say talk with Martin Abente, he's looking into this problem space. Could we maybe split this thread and keep technical discussions focused on XS-devel and Sugar-devel lists? I think this could also also help in getting some non-technical and/or end-user feedback and suggestion from people on IAEP who aren't into all the technical details (something which I think tch was also interested in). Thanks, Christoph -- Christoph Derndorfer co-editor, olpcnews url: www.olpcnews.com e-mail: christ...@olpcnews.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Server-devel] [IAEP] copy files to/from server
On Tue, May 17, 2011 at 6:01 PM, Anna wrote: > On Tue, May 17, 2011 at 4:15 PM, Martin Abente < > martin.abente.lah...@gmail.com> wrote: > >> Just to explain a little better this all fits into the "cloud journal" >> Idea which in the very first version should basically work as a cloud >> storage device (which should be placed in the XS IMHO). This will fix >> MANY problems we encountered in the field regarding the limited >> storage space, backups and virtual dogs eating homework. >> >> I still didn't make up my mind about which technical approach should I >> take in order to get this working, but I guess people already started >> sharing some ideas. And I would appreciate more ideas and discussion >> before I get to that point. >> >> The very basic requirement is: each children must have its private >> "cloud volume", where they can drop their files in the same way they >> interact with physical external storage devices. >> >> On top of that we can do a lot of things that might be very useful for >> teachers daily in the classrooms. >> >> Before I start working on this, ill add multi-selection capabilities >> to the journal so we can easily drop files from the local journal to >> the "cloud" one. The implementation of the multi-selection feature may >> or not follow the design we proposed on eduJAM's code sprint [1]. >> >> Questions? Ideas? Code? :) >> >> 1. http://wiki.sugarlabs.org/go/Journal_NewUI#Mockups >> >> > As an external service, Dropbox is not appropriate for a deployment, but I > messed around several months ago with integrating the Journal with Dropbox. > Since the setup is fairly complicated, I never suggested implementing it > here. > > Because of the way Sugar indexes files, I used a USB drive so that Dropbox > would show file names and extensions. From the user's perspective, all they > have to do is drop files onto a USB drive and everything else is automatic. > > Anyway, it's "proof of concept" of cloud storage with the Journal. And of > course, Dropbox is a bad idea unless you're talking about just a few users. > There are FOSS alternatives out there that can live on the XS. > > Here's my writeup: > http://www.olpcnews.com/forum/index.php?topic=4892.0 > > Anna Schoolfield > Birmingham > > ___ > Server-devel mailing list > server-de...@lists.laptop.org > http://lists.laptop.org/listinfo/server-devel > > FWIW, the $HOME/Docments patch could easily be modified to reference a shared network mount. http://lists.sugarlabs.org/archive/sugar-devel/2011-May/03.html -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
