Re: [Sugar-devel] External devices @ development environment
I spent some time looking at it but I have not been able to get it to work. Part of the problem is that gvfs is not installed, which I've now fixed. You can get that with an "./osbuild pull". I suspect it will also be necessary to bind mount /run/media. I edited build/out/sandbox-host/install/lib/python2.7/site-packages/broot/root.py Adding /run/media to system_source_paths. I think I also had to create the /var/lib/broot/sugar-build-V5jn9/run/media directory. udiskctl seems happy but gio still doesn't see any device. We probably need to look at the gvfs daemons logs to see what is going on. Maybe more deps are missing or more bind mounts are necessary. On 4 December 2013 12:50, Emil Dudev wrote: > Hello, > > I have a problem with external devices (such as a USB). The development > environment (setup on Fedora, as described here > http://developer.sugarlabs.org/dev-environment.md.html) seems to not > recognize when a USB device is connected. > > I have tracked the problem to Gio.VolumeMonitor (at least I think that's > where the problem is). > All calls to Gio.VolumeMonitor.get().get_mounts() return an empty list. > Also, no signals seem to be emitted from Gio.VolumeMonitor.get(). > This is where I'm stuck. > > Does anyone have a similar problem? > > Emil Dudev > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup/Restore Sugar implementation
On Fri, 2013-12-06 at 10:26 +1100, James Cameron wrote: > On Thu, Dec 05, 2013 at 06:02:40PM -0500, Walter Bender wrote: > > Maybe: > > > > Make a copy of the contents of your Journal. For safety, make a copy of your journal > > > > Restore the contents of your Journal. Restore your journal, from your safe copy > > While we programmers perceive the Journal as a thing that has separate > contents, a learner is more likely to perceive the Journal as the > contents, and this perception does not need to be corrected. > > So I agree with the suggestion, but without the words "the contents > of". > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup/Restore Sugar implementation
On Thu, Dec 05, 2013 at 06:02:40PM -0500, Walter Bender wrote: > Maybe: > > Make a copy of the contents of your Journal. > > Restore the contents of your Journal. While we programmers perceive the Journal as a thing that has separate contents, a learner is more likely to perceive the Journal as the contents, and this perception does not need to be corrected. So I agree with the suggestion, but without the words "the contents of". -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup/Restore Sugar implementation
On Thu, 2013-12-05 at 21:04 -0200, Gonzalo Odiard wrote: > Yes. Can be a more extended explanation, > there are space. Is better ... Please can you give: Make a safe copy of the content of your journal and Restore a security copy into your journal in your own language? Iain > > Gonzalo > > > On Thu, Dec 5, 2013 at 8:02 PM, Walter Bender > wrote: > Maybe: > > Make a copy of the contents of your Journal. > > Restore the contents of your Journal. > > -walter > > > On Thu, Dec 5, 2013 at 5:52 PM, Gonzalo Odiard > wrote: > > The wording is all tentative, I would like get help in that > area. > > > > The left side means " backup" the right is "restore". > > > > Gonzalo > > > > > > > > > > On Thu, Dec 5, 2013 at 5:49 PM, Walter Bender > > > wrote: > >> > >> great to see this come together. > >> > >> question about the wording on the screenshots (haven't > looked at the code > >> yet) > >> > >> not sure what 'safe copy' means on the left side of [1] > >> not sure what 'security copy' means on the right side of > [1] > >> > >> [1] > http://wiki.sugarlabs.org/go/File:Backup_initial_window.png > >> > >> regards. > >> > >> -walter > >> > >> On Thu, Dec 5, 2013 at 3:43 PM, Gonzalo Odiard > wrote: > >> > I have sent for review a implementation of the feature: > >> > > >> > sugar: https://github.com/sugarlabs/sugar/pull/176 > >> > sugar-artwork: > https://github.com/sugarlabs/sugar-artwork/pull/24 > >> > sugar-toolkit-gtk3: > >> > https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/60 > >> > > >> > Thanks to Martin Abente, who worked on this and in > previous > >> > implementations > >> > of the backup/restore, and provided feedback and code. > >> > > >> > This implementation have a frontend and backends > separated, > >> > to make easier to add new implementations adding only a > single module. > >> > > >> > Right now, only a backend to work with local devices is > implemented, > >> > the remote backend do nothing, is only to show how the > selection of > >> > backends > >> > is done by the user, but will be deleted before push to > master. > >> > > >> > The access to the backup/restore feature is through the > palette in the > >> > journal icon, > >> > in the frame or in the bottom toolbar in the journal > window. > >> > > >> > Screenshot were updated in the feature page > >> > > > http://wiki.sugarlabs.org/go/Features/Backup_and_Restore#User_Experience > >> > most of the page need update yet. > >> > > >> > Comments are welcomed. > >> > > >> > Gonzalo > >> > > >> > ___ > >> > Sugar-devel mailing list > >> > Sugar-devel@lists.sugarlabs.org > >> > http://lists.sugarlabs.org/listinfo/sugar-devel > >> > > >> > >> > >> > >> -- > >> Walter Bender > >> Sugar Labs > >> http://www.sugarlabs.org > > > > > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > > > > ___ > 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] Backup/Restore Sugar implementation
Yes. Can be a more extended explanation, there are space. Gonzalo On Thu, Dec 5, 2013 at 8:02 PM, Walter Bender wrote: > Maybe: > > Make a copy of the contents of your Journal. > > Restore the contents of your Journal. > > -walter > > > On Thu, Dec 5, 2013 at 5:52 PM, Gonzalo Odiard wrote: > > The wording is all tentative, I would like get help in that area. > > > > The left side means " backup" the right is "restore". > > > > Gonzalo > > > > > > > > > > On Thu, Dec 5, 2013 at 5:49 PM, Walter Bender > > wrote: > >> > >> great to see this come together. > >> > >> question about the wording on the screenshots (haven't looked at the > code > >> yet) > >> > >> not sure what 'safe copy' means on the left side of [1] > >> not sure what 'security copy' means on the right side of [1] > >> > >> [1] http://wiki.sugarlabs.org/go/File:Backup_initial_window.png > >> > >> regards. > >> > >> -walter > >> > >> On Thu, Dec 5, 2013 at 3:43 PM, Gonzalo Odiard > wrote: > >> > I have sent for review a implementation of the feature: > >> > > >> > sugar: https://github.com/sugarlabs/sugar/pull/176 > >> > sugar-artwork: https://github.com/sugarlabs/sugar-artwork/pull/24 > >> > sugar-toolkit-gtk3: > >> > https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/60 > >> > > >> > Thanks to Martin Abente, who worked on this and in previous > >> > implementations > >> > of the backup/restore, and provided feedback and code. > >> > > >> > This implementation have a frontend and backends separated, > >> > to make easier to add new implementations adding only a single module. > >> > > >> > Right now, only a backend to work with local devices is implemented, > >> > the remote backend do nothing, is only to show how the selection of > >> > backends > >> > is done by the user, but will be deleted before push to master. > >> > > >> > The access to the backup/restore feature is through the palette in the > >> > journal icon, > >> > in the frame or in the bottom toolbar in the journal window. > >> > > >> > Screenshot were updated in the feature page > >> > > http://wiki.sugarlabs.org/go/Features/Backup_and_Restore#User_Experience > >> > most of the page need update yet. > >> > > >> > Comments are welcomed. > >> > > >> > Gonzalo > >> > > >> > ___ > >> > Sugar-devel mailing list > >> > Sugar-devel@lists.sugarlabs.org > >> > http://lists.sugarlabs.org/listinfo/sugar-devel > >> > > >> > >> > >> > >> -- > >> Walter Bender > >> Sugar Labs > >> http://www.sugarlabs.org > > > > > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup/Restore Sugar implementation
Maybe: Make a copy of the contents of your Journal. Restore the contents of your Journal. -walter On Thu, Dec 5, 2013 at 5:52 PM, Gonzalo Odiard wrote: > The wording is all tentative, I would like get help in that area. > > The left side means " backup" the right is "restore". > > Gonzalo > > > > > On Thu, Dec 5, 2013 at 5:49 PM, Walter Bender > wrote: >> >> great to see this come together. >> >> question about the wording on the screenshots (haven't looked at the code >> yet) >> >> not sure what 'safe copy' means on the left side of [1] >> not sure what 'security copy' means on the right side of [1] >> >> [1] http://wiki.sugarlabs.org/go/File:Backup_initial_window.png >> >> regards. >> >> -walter >> >> On Thu, Dec 5, 2013 at 3:43 PM, Gonzalo Odiard wrote: >> > I have sent for review a implementation of the feature: >> > >> > sugar: https://github.com/sugarlabs/sugar/pull/176 >> > sugar-artwork: https://github.com/sugarlabs/sugar-artwork/pull/24 >> > sugar-toolkit-gtk3: >> > https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/60 >> > >> > Thanks to Martin Abente, who worked on this and in previous >> > implementations >> > of the backup/restore, and provided feedback and code. >> > >> > This implementation have a frontend and backends separated, >> > to make easier to add new implementations adding only a single module. >> > >> > Right now, only a backend to work with local devices is implemented, >> > the remote backend do nothing, is only to show how the selection of >> > backends >> > is done by the user, but will be deleted before push to master. >> > >> > The access to the backup/restore feature is through the palette in the >> > journal icon, >> > in the frame or in the bottom toolbar in the journal window. >> > >> > Screenshot were updated in the feature page >> > http://wiki.sugarlabs.org/go/Features/Backup_and_Restore#User_Experience >> > most of the page need update yet. >> > >> > Comments are welcomed. >> > >> > Gonzalo >> > >> > ___ >> > Sugar-devel mailing list >> > Sugar-devel@lists.sugarlabs.org >> > http://lists.sugarlabs.org/listinfo/sugar-devel >> > >> >> >> >> -- >> Walter Bender >> Sugar Labs >> http://www.sugarlabs.org > > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup/Restore Sugar implementation
The wording is all tentative, I would like get help in that area. The left side means " backup" the right is "restore". Gonzalo On Thu, Dec 5, 2013 at 5:49 PM, Walter Bender wrote: > great to see this come together. > > question about the wording on the screenshots (haven't looked at the code > yet) > > not sure what 'safe copy' means on the left side of [1] > not sure what 'security copy' means on the right side of [1] > > [1] http://wiki.sugarlabs.org/go/File:Backup_initial_window.png > > regards. > > -walter > > On Thu, Dec 5, 2013 at 3:43 PM, Gonzalo Odiard wrote: > > I have sent for review a implementation of the feature: > > > > sugar: https://github.com/sugarlabs/sugar/pull/176 > > sugar-artwork: https://github.com/sugarlabs/sugar-artwork/pull/24 > > sugar-toolkit-gtk3: > https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/60 > > > > Thanks to Martin Abente, who worked on this and in previous > implementations > > of the backup/restore, and provided feedback and code. > > > > This implementation have a frontend and backends separated, > > to make easier to add new implementations adding only a single module. > > > > Right now, only a backend to work with local devices is implemented, > > the remote backend do nothing, is only to show how the selection of > backends > > is done by the user, but will be deleted before push to master. > > > > The access to the backup/restore feature is through the palette in the > > journal icon, > > in the frame or in the bottom toolbar in the journal window. > > > > Screenshot were updated in the feature page > > http://wiki.sugarlabs.org/go/Features/Backup_and_Restore#User_Experience > > most of the page need update yet. > > > > Comments are welcomed. > > > > Gonzalo > > > > ___ > > Sugar-devel mailing list > > Sugar-devel@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar 0.101.0 (unstable)
Hello, this is the first development release of the cycle that will bring us to 0 .102. Highlights: * Allow to limit the number of open activities. * More informations about hardware and software in control panel. * Allow to hide the Register menu. * Add support for 5 GHz frequency channels. * A lot of bugfixes. Sources: http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.101.0.tar.xz http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.101.0.tar.xz http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.101.0.tar.xz http://download.sugarlabs.org/sources/sucrose/glucose/sugar-runner/sugar-runner-0.101.1.tar.xz A lot of people contributed to this release. Thanks to everyone! -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Transfer all file metadata
Hello, I believe I have solved the 'bug' of this ticket: http://bugs.sugarlabs.org/ticket/2473 The problem is that when sending files, only the title, description and mime type are preserved. This is due to telepathy (Channel.Type.FileTransfer), as it does not support other properties. There is a fix for telepathy (Channel.Interface.FileTransfer.Metadata), but it's implemented in a different version of telepathy. I have solved this bug by packing all the metadata and sending it as the description. When the file is saved on the receiving machine, the metadata is unpacked. This works without a problem. But a problem arises with backward compatibility. If a user with this 'bug fix' sends a file to a user without it, the receiving user will have JSON formatted data as the description of the file. I'm not sure if this will be accepted, due to the last part. Yet I have not found way to fix it. Here are the code edits: https://github.com/edudev/sugar/compare/sugarlabs:master...edudev:ticket2473 Emil Dudev ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup/Restore Sugar implementation
great to see this come together. question about the wording on the screenshots (haven't looked at the code yet) not sure what 'safe copy' means on the left side of [1] not sure what 'security copy' means on the right side of [1] [1] http://wiki.sugarlabs.org/go/File:Backup_initial_window.png regards. -walter On Thu, Dec 5, 2013 at 3:43 PM, Gonzalo Odiard wrote: > I have sent for review a implementation of the feature: > > sugar: https://github.com/sugarlabs/sugar/pull/176 > sugar-artwork: https://github.com/sugarlabs/sugar-artwork/pull/24 > sugar-toolkit-gtk3: https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/60 > > Thanks to Martin Abente, who worked on this and in previous implementations > of the backup/restore, and provided feedback and code. > > This implementation have a frontend and backends separated, > to make easier to add new implementations adding only a single module. > > Right now, only a backend to work with local devices is implemented, > the remote backend do nothing, is only to show how the selection of backends > is done by the user, but will be deleted before push to master. > > The access to the backup/restore feature is through the palette in the > journal icon, > in the frame or in the bottom toolbar in the journal window. > > Screenshot were updated in the feature page > http://wiki.sugarlabs.org/go/Features/Backup_and_Restore#User_Experience > most of the page need update yet. > > Comments are welcomed. > > Gonzalo > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Backup/Restore Sugar implementation
I have sent for review a implementation of the feature: sugar: https://github.com/sugarlabs/sugar/pull/176 sugar-artwork: https://github.com/sugarlabs/sugar-artwork/pull/24 sugar-toolkit-gtk3: https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/60 Thanks to Martin Abente, who worked on this and in previous implementations of the backup/restore, and provided feedback and code. This implementation have a frontend and backends separated, to make easier to add new implementations adding only a single module. Right now, only a backend to work with local devices is implemented, the remote backend do nothing, is only to show how the selection of backends is done by the user, but will be deleted before push to master. The access to the backup/restore feature is through the palette in the journal icon, in the frame or in the bottom toolbar in the journal window. Screenshot were updated in the feature page http://wiki.sugarlabs.org/go/Features/Backup_and_Restore#User_Experience most of the page need update yet. Comments are welcomed. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
