Re: [Sugar-devel] Browse.xo -- preserving a downloaded filename?
On Wed, Jul 1, 2009 at 12:02, Martin Langhoff wrote: > On Tue, Jun 30, 2009 at 7:46 PM, Martin > Langhoff wrote: >> We need a file manager IMHO. > > Michael asks about this specific statement, as it is fairly broad. > Let's keep it in the context of "it is worth fixing bugs that mangle > filenames" so the Journal can indeed double up as a passable (if > limited) file manager :-) > > "We need to do some file management sanely". > > Not an easy line to walk, but doable. As I just said in another thread, please check for the current plan in the archives and let's move from there so we don't have to repeat everything again. We'll also need people who want to carry the plan forward instead of just shouting "OMG! Sugar developers stole my filesystem!" Michael's suggestion is quite practical, and we also have Browse and control panel extensions where to place code to deal with the download and the installation of lease files. Regards, Tomeu > cheers, > > > m > -- > martin.langh...@gmail.com > mar...@laptop.org -- School Server Architect > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse.xo -- preserving a downloaded filename?
On Tue, Jun 30, 2009 at 7:46 PM, Martin Langhoff wrote: > We need a file manager IMHO. Michael asks about this specific statement, as it is fairly broad. Let's keep it in the context of "it is worth fixing bugs that mangle filenames" so the Journal can indeed double up as a passable (if limited) file manager :-) "We need to do some file management sanely". Not an easy line to walk, but doable. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse.xo -- preserving a downloaded filename?
Martin Langhoff wrote: > > On Tue, Jun 30, 2009 at 7:25 PM, Bert Freudenberg > > wrote: > > What's your use case? > > In the normal course of operation, the XOs will work with the XS over > wireless, getting their individual leases. This is a fallback "rescue" > leases.sig . Here's a gentle suggestion on how to more quickly (but narrowly) implement this use case: why not use Pippy to write a minimal activity that downloads the leases.sig file [e.g. with urllib2, wget, or curl], tests for mounted USB sticks, prompts the user if they're missing, and that copies the leases.sig file to the USB stick? I think this might be a good way to go because * it'll be faster than figuring out how to solve file management, * it doesn't depend on anyone else making changes, and * it may be of some educational value to people who want to understand how the system actually works and how they might automate it for themselves. Regards, Michael ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse.xo -- preserving a downloaded filename?
On Tue, Jun 30, 2009 at 1:48 PM, Gary C Martin wrote: > On 30 Jun 2009, at 18:20, Simon Schampijer wrote: > >> On 06/30/2009 07:17 PM, Martin Langhoff wrote: >>> Using Browse.xo v101 on 8.2.x I cannot get Browse.xo to save a file >>> with the name that I am requesting. >>> >>> Browse.xo seems to take the name I hint from the server (from the URL >>> and using an 'content-disposition: attachment, filename="leases.sig"' >>> header). But it renames it as >>> >>> "File leases.sig downloaded from http://.. " >>> >>> Filenames are often important. Even minor changes to a filename can >>> cause a lot of user grief. >>> >>> In general, OSs (from the kernel to the UI) try to keep the sanctity >>> of the filename as they do with the data. When they don't, all sorts >>> of trouble ensues. We wouldn't mangle the user's data. We shouldn't >>> mangle the filenames. >>> >>> Decorating the filenames with additional metadata is _cool_ otoh... >>> >>> cheers, >>> >>> >>> >>> m >> >> Actually I came along this myself the other day. I would propose to >> have >> the file name as the entry title and the 'downloaded from' description >> in the journal entry description field. > > +0.8, it would also help keep titles a reasonable length when > downloading something from a site with a deeply nested or script > generated location. +1 from me. This is a good example where "actions" would come in handy. The action would indicate that the object was downloaded. The object itself would retain its own identity, and have its basic title/filename. I think adding the download location to the description field is a nice idea. In the future, I'd like to improve support for metadata that can expose it within the details page of an entry, so that this could actually be represented as "downloaded from: location", instead of eating up the description field. Eben > Regards, > --Gary > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse.xo -- preserving a downloaded filename?
On Tue, Jun 30, 2009 at 2:18 PM, Martin Langhoff wrote: > On Tue, Jun 30, 2009 at 7:20 PM, Simon Schampijer wrote: >> Actually I came along this myself the other day. I would propose to have the >> file name as the entry title and the 'downloaded from' description in the >> journal entry description field. > > +1! +1 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse.xo -- preserving a downloaded filename?
On Tue, Jun 30, 2009 at 7:20 PM, Simon Schampijer wrote: > Actually I came along this myself the other day. I would propose to have the > file name as the entry title and the 'downloaded from' description in the > journal entry description field. +1! cheers, martin -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse.xo -- preserving a downloaded filename?
On Tue, Jun 30, 2009 at 7:52 PM, Dave Bauer wrote: > What would the file manager be for? Who is downloading this file, A teacher. Probably less technical than the kids. > how often > and what do they need to do with it? It is easy enough to download it from > the Terminal for a technical user. The technical users are on this list. Not in the field. What could you do with a file browser? - Put files on a USB stick to share them with others? - Browse a complex or large USB stick with files from my friends? cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse.xo -- preserving a downloaded filename?
On Tue, Jun 30, 2009 at 1:46 PM, Martin Langhoff wrote: > On Tue, Jun 30, 2009 at 7:25 PM, Bert Freudenberg > wrote: > > What's your use case? > > Does "leases.sig" give you a hint? :-) > > The XS can now handle antitheft services. One of the things I added is > the ability to generate a leases.sig with short-lived leases for all > the (non-stolen) machines in the school. > > In the normal course of operation, the XOs will work with the XS over > wireless, getting their individual leases. This is a fallback "rescue" > leases.sig . > > As you can see in my other email, the problem is compounded with the > Journal messing up rename :-/ > > We need a file manager IMHO. > What would the file manager be for? Who is downloading this file, how often and what do they need to do with it? It is easy enough to download it from the Terminal for a technical user. Dave > > > > > martin > -- > martin.langh...@gmail.com > mar...@laptop.org -- School Server Architect > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Dave Bauer d...@solutiongrove.com http://www.solutiongrove.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse.xo -- preserving a downloaded filename?
On 30 Jun 2009, at 18:20, Simon Schampijer wrote: > On 06/30/2009 07:17 PM, Martin Langhoff wrote: >> Using Browse.xo v101 on 8.2.x I cannot get Browse.xo to save a file >> with the name that I am requesting. >> >> Browse.xo seems to take the name I hint from the server (from the URL >> and using an 'content-disposition: attachment, filename="leases.sig"' >> header). But it renames it as >> >> "File leases.sig downloaded from http://.. " >> >> Filenames are often important. Even minor changes to a filename can >> cause a lot of user grief. >> >> In general, OSs (from the kernel to the UI) try to keep the sanctity >> of the filename as they do with the data. When they don't, all sorts >> of trouble ensues. We wouldn't mangle the user's data. We shouldn't >> mangle the filenames. >> >> Decorating the filenames with additional metadata is _cool_ otoh... >> >> cheers, >> >> >> >> m > > Actually I came along this myself the other day. I would propose to > have > the file name as the entry title and the 'downloaded from' description > in the journal entry description field. +0.8, it would also help keep titles a reasonable length when downloading something from a site with a deeply nested or script generated location. Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse.xo -- preserving a downloaded filename?
On Tue, Jun 30, 2009 at 7:25 PM, Bert Freudenberg wrote: > What's your use case? Does "leases.sig" give you a hint? :-) The XS can now handle antitheft services. One of the things I added is the ability to generate a leases.sig with short-lived leases for all the (non-stolen) machines in the school. In the normal course of operation, the XOs will work with the XS over wireless, getting their individual leases. This is a fallback "rescue" leases.sig . As you can see in my other email, the problem is compounded with the Journal messing up rename :-/ We need a file manager IMHO. martin -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse.xo -- preserving a downloaded filename?
On 30.06.2009, at 19:20, Simon Schampijer wrote: > On 06/30/2009 07:17 PM, Martin Langhoff wrote: >> Using Browse.xo v101 on 8.2.x I cannot get Browse.xo to save a file >> with the name that I am requesting. >> >> Browse.xo seems to take the name I hint from the server (from the URL >> and using an 'content-disposition: attachment, filename="leases.sig"' >> header). But it renames it as >> >> "File leases.sig downloaded from http://.. " >> >> Filenames are often important. Even minor changes to a filename can >> cause a lot of user grief. >> >> In general, OSs (from the kernel to the UI) try to keep the sanctity >> of the filename as they do with the data. When they don't, all sorts >> of trouble ensues. We wouldn't mangle the user's data. We shouldn't >> mangle the filenames. >> >> Decorating the filenames with additional metadata is _cool_ otoh... >> >> cheers, >> >> >> >> m > > Actually I came along this myself the other day. I would propose to > have > the file name as the entry title and the 'downloaded from' description > in the journal entry description field. While I would like this change it might make the Journal look more like a file manager which it isn't. - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse.xo -- preserving a downloaded filename?
On 30.06.2009, at 19:17, Martin Langhoff wrote: > Using Browse.xo v101 on 8.2.x I cannot get Browse.xo to save a file > with the name that I am requesting. > > Browse.xo seems to take the name I hint from the server (from the URL > and using an 'content-disposition: attachment, filename="leases.sig"' > header). But it renames it as > > "File leases.sig downloaded from http://.. " This is not the filename but the journal entry title. The actual filename is just a uuid. That said, yes, the original filename should be preserved at least in the metadata (if the DS isn't actually rewritten to store files under their original name). What's your use case? - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse.xo -- preserving a downloaded filename?
On 06/30/2009 07:17 PM, Martin Langhoff wrote: > Using Browse.xo v101 on 8.2.x I cannot get Browse.xo to save a file > with the name that I am requesting. > > Browse.xo seems to take the name I hint from the server (from the URL > and using an 'content-disposition: attachment, filename="leases.sig"' > header). But it renames it as > >"File leases.sig downloaded from http://.. " > > Filenames are often important. Even minor changes to a filename can > cause a lot of user grief. > > In general, OSs (from the kernel to the UI) try to keep the sanctity > of the filename as they do with the data. When they don't, all sorts > of trouble ensues. We wouldn't mangle the user's data. We shouldn't > mangle the filenames. > > Decorating the filenames with additional metadata is _cool_ otoh... > > cheers, > > > > m Actually I came along this myself the other day. I would propose to have the file name as the entry title and the 'downloaded from' description in the journal entry description field. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
