[Sugar-devel] [Server-devel] [IAEP] copy files to/from server
martin.abente.lahaye at gmail.com
Mon May 23 17:28:15 EDT 2011
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.
In the non-technical front, I believe we should stick to the Journal
integration idea, displaying this resource exactly how we display
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.
On Mon, May 23, 2011 at 4:16 PM, Christoph Derndorfer
<christoph.derndorfer at gmail.com> wrote:
> On Mon, May 23, 2011 at 2:24 PM, Martin Langhoff <martin.langhoff at gmail.com>
>> On Mon, May 23, 2011 at 1:41 AM, Sridhar Dhanapalan
>> <sridhar at laptop.org.au> 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).
> Christoph Derndorfer
> co-editor, olpcnews
> url: www.olpcnews.com
> e-mail: christoph at olpcnews.com
More information about the Sugar-devel