Re: [Sugar-devel] Bundlebuilder dev command
Sorry for the late answer, 2013/9/15 Daniel Narvaez dwnarv...@gmail.com: Hello, as discussed in another thread, the sugar-toolkit bundlebuilder dev command is not respecting the SUGAR_ACTIVITIES_PATH (a fix for that landed in sugar-toolkit-gtk3 recently). Thanks for the fix. I wonder if we should just drop the dev command, and suggest to develop directly in sugar-build/activities (or ~/Activities when outside sugar-build). All that the command does is to create a symlink anyway, if someone really wants they can do that themselves easily... As it is, the dev command feels like unnecessary magic to me. I'm so so with the idea of deprecating the dev command, Daniel. From one side you are right, all it does is create a symlink. On the other hand, is a symlink added in the exact place, in order for Sugar to install your activity. As a user, I never had to worry about it, it just works. As a comparison, the 'volo create' command we have in sugar-web does simple operations as well (as we use it) but is very nice to have that automated. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Bundlebuilder dev command
-1 Please don't remove the dev command. It works. If you don't use does not means other don't find it useful. Gonzalo On Wed, Sep 18, 2013 at 8:23 AM, Manuel Quiñones ma...@laptop.org wrote: Sorry for the late answer, 2013/9/15 Daniel Narvaez dwnarv...@gmail.com: Hello, as discussed in another thread, the sugar-toolkit bundlebuilder dev command is not respecting the SUGAR_ACTIVITIES_PATH (a fix for that landed in sugar-toolkit-gtk3 recently). Thanks for the fix. I wonder if we should just drop the dev command, and suggest to develop directly in sugar-build/activities (or ~/Activities when outside sugar-build). All that the command does is to create a symlink anyway, if someone really wants they can do that themselves easily... As it is, the dev command feels like unnecessary magic to me. I'm so so with the idea of deprecating the dev command, Daniel. From one side you are right, all it does is create a symlink. On the other hand, is a symlink added in the exact place, in order for Sugar to install your activity. As a user, I never had to worry about it, it just works. As a comparison, the 'volo create' command we have in sugar-web does simple operations as well (as we use it) but is very nice to have that automated. -- .. manuq .. ___ 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] Bundlebuilder dev command
On Wednesday, 18 September 2013, Manuel Quiñones wrote: I wonder if we should just drop the dev command, and suggest to develop directly in sugar-build/activities (or ~/Activities when outside sugar-build). All that the command does is to create a symlink anyway, if someone really wants they can do that themselves easily... As it is, the dev command feels like unnecessary magic to me. I'm so so with the idea of deprecating the dev command, Daniel. From one side you are right, all it does is create a symlink. On the other hand, is a symlink added in the exact place, in order for Sugar to install your activity. As a user, I never had to worry about it, it just works. As a comparison, the 'volo create' command we have in sugar-web does simple operations as well (as we use it) but is very nice to have that automated. Hi, note that I'm not suggesting people should create a symlink, rather they should develop directly in the activities directory. All that they need to know is where that directory is, which is something that doesn't really seem avoidable to hack on sugar. The fact that activities doesn't need a build system, that you can just create a directory somewhere and start writing code, is one of the best aspects of the sugar design IMO and the dev command is hiding it behind a not very useful abstraction. -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Bundlebuilder dev command
Fair enough, I'll let people which cares about gtk2 toolkit and the dev
command fix that bug :)
On Wednesday, 18 September 2013, Gonzalo Odiard wrote:
-1
Please don't remove the dev command.
It works. If you don't use does not means other don't find it useful.
Gonzalo
On Wed, Sep 18, 2013 at 8:23 AM, Manuel Quiñones
ma...@laptop.orgjavascript:_e({}, 'cvml', 'ma...@laptop.org');
wrote:
Sorry for the late answer,
2013/9/15 Daniel Narvaez dwnarv...@gmail.com javascript:_e({}, 'cvml',
'dwnarv...@gmail.com');:
Hello,
as discussed in another thread, the sugar-toolkit bundlebuilder dev
command
is not respecting the SUGAR_ACTIVITIES_PATH (a fix for that landed in
sugar-toolkit-gtk3 recently).
Thanks for the fix.
I wonder if we should just drop the dev command, and suggest to develop
directly in sugar-build/activities (or ~/Activities when outside
sugar-build). All that the command does is to create a symlink anyway,
if
someone really wants they can do that themselves easily... As it is,
the dev
command feels like unnecessary magic to me.
I'm so so with the idea of deprecating the dev command, Daniel.
From one side you are right, all it does is create a symlink. On the
other hand, is a symlink added in the exact place, in order for Sugar
to install your activity. As a user, I never had to worry about it,
it just works. As a comparison, the 'volo create' command we have in
sugar-web does simple operations as well (as we use it) but is very
nice to have that automated.
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org javascript:_e({}, 'cvml',
'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
[Sugar-devel] Fwd: C. Scott Ananian (Re: Sugar Labs permission request to dual license under LGPL and Apache License)
We now need to make the license changes in the sugar-artwork git. And to finish up the ones in the sugar-web modules (if I remember correctly we have not added headers yet). -- Forwarded message -- From: *Tony Sebro* Date: Monday, 16 September 2013 Subject: C. Scott Ananian (Re: Sugar Labs permission request to dual license under LGPL and Apache License) To: Walter Bender walter.ben...@gmail.com Cc: Daniel Narvaez dwnarv...@gmail.com On 09/13/2013 05:05 PM, Walter Bender wrote: I just wrote to him at his cscott.net address... Asked him to contact you. regards. -walter Thanks for reaching out to him. Scott just gave his written consent. With that, every copyright holder you identified in /sugar-artwork repository has consented to re-license his/her copyrights under the Apache License 2.0. Best, -Tony -- Tony Sebro, General Counsel, Software Freedom Conservancy +1-212-461-3245 x11 t...@sfconservancy.org www.sfconservancy.org -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] 0.100 schedule
I wish I could do that but I'm not really able to commit to meeting schedules these days. It's a lot easier for me to work async. It's not like you can't do this without me though :) I can read the logs and comment. On Monday, 16 September 2013, Gonzalo Odiard wrote: What you (and other in the community) think about organize weekly chat meetings form now, and until 0.100 release, to help coordinate triage, and solve the more important issues pending? Gonzalo On Thu, Sep 5, 2013 at 12:15 PM, Daniel Narvaez dwnarv...@gmail.comjavascript:; wrote: As discussed in the code freeze thread, we are not going to freeze but instead do another unstable release, 0.99.4, in four weeks. I think it make sense to reevaluate and hopefully come up with a date for 0.100 after that one. I'm going to keep the schedule on trac from now on: http://bugs.sugarlabs.org/roadmap -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org javascript:; 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
[Sugar-devel] Web activities on XO-4
I finally got web activities working on XO-4, in the AU build published yesterday [1] . I did it by modifying webactivities.py to use WebKitGTK1 instead of v2. The changes are: https://github.com/manuq/sugar-toolkit-gtk3-1/compare/webacts-webkit1 I tried it with Gears Activity v3, and is working. It stores the data and the metadata. So it is communicating with the shell just fine. The touchscreen is not responding very well, at least in this activity. I can tap buttons, but I can barely drag to move a gear or to draw one. The dragging seems to be cancelled in the middle of the action. Mouse input works fine. Also as expected, the icons look small in the XO screen because I need to adapt the theme. But that is an easy one, just changing the CEL_SIZE variable in the LESS file to create another CSS for the XO screen DPI, and adding a CSS media query selector to the HTML. I'll provide a patch to sugar-web-template and will update my web activities. The inspector is not working, it does not display. It shoud display by Ctrl+Shift+I or by right-click - Inspect element. There is no error in the logs and the API is there [2], but nothing is happening. Surprisingly, JavaScript console logs go to the activity log. We are missing that in master. I managed to keep the activity:// scheme that we need for the same-origin policy, but I still had to add the setting 'enable-file-access-from-file-uris' to workaround the cross-site requests. I can't find a way to register the URI scheme in WK1, so I added a big FIXME. [1] http://build.laptop.org.au/xo/os/sugar-100/build-21/ [2] http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebInspector.html -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Web activities on XO-4
This is great news. -walter On Wed, Sep 18, 2013 at 1:01 PM, Manuel Quiñones ma...@laptop.org wrote: I finally got web activities working on XO-4, in the AU build published yesterday [1] . I did it by modifying webactivities.py to use WebKitGTK1 instead of v2. The changes are: https://github.com/manuq/sugar-toolkit-gtk3-1/compare/webacts-webkit1 I tried it with Gears Activity v3, and is working. It stores the data and the metadata. So it is communicating with the shell just fine. The touchscreen is not responding very well, at least in this activity. I can tap buttons, but I can barely drag to move a gear or to draw one. The dragging seems to be cancelled in the middle of the action. Mouse input works fine. Also as expected, the icons look small in the XO screen because I need to adapt the theme. But that is an easy one, just changing the CEL_SIZE variable in the LESS file to create another CSS for the XO screen DPI, and adding a CSS media query selector to the HTML. I'll provide a patch to sugar-web-template and will update my web activities. The inspector is not working, it does not display. It shoud display by Ctrl+Shift+I or by right-click - Inspect element. There is no error in the logs and the API is there [2], but nothing is happening. Surprisingly, JavaScript console logs go to the activity log. We are missing that in master. I managed to keep the activity:// scheme that we need for the same-origin policy, but I still had to add the setting 'enable-file-access-from-file-uris' to workaround the cross-site requests. I can't find a way to register the URI scheme in WK1, so I added a big FIXME. [1] http://build.laptop.org.au/xo/os/sugar-100/build-21/ [2] http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebInspector.html -- .. manuq .. ___ 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
Re: [Sugar-devel] Bundlebuilder dev command
It is only an issue for sugar-build, not Sugar installed by non-developers. And it is documented [1]. And ls -s sugar-build/activities Activities works. -walter [1] http://developer.sugarlabs.org/dev-environment.md.html#activities On Wed, Sep 18, 2013 at 2:32 PM, Gonzalo Odiard gonz...@laptop.org wrote: I people continue using ~/Activities directory is not a problem, right? What is the point of move the directory where the activities are installed? Changing these directories without a good motive _is_ a problem. Nobody will update the documentation, wiki pages, tutorials, and development book, then people will be confused. Gonzalo On Wed, Sep 18, 2013 at 1:29 PM, Daniel Narvaez dwnarv...@gmail.com wrote: Fair enough, I'll let people which cares about gtk2 toolkit and the dev command fix that bug :) On Wednesday, 18 September 2013, Gonzalo Odiard wrote: -1 Please don't remove the dev command. It works. If you don't use does not means other don't find it useful. Gonzalo On Wed, Sep 18, 2013 at 8:23 AM, Manuel Quiñones ma...@laptop.org wrote: Sorry for the late answer, 2013/9/15 Daniel Narvaez dwnarv...@gmail.com: Hello, as discussed in another thread, the sugar-toolkit bundlebuilder dev command is not respecting the SUGAR_ACTIVITIES_PATH (a fix for that landed in sugar-toolkit-gtk3 recently). Thanks for the fix. I wonder if we should just drop the dev command, and suggest to develop directly in sugar-build/activities (or ~/Activities when outside sugar-build). All that the command does is to create a symlink anyway, if someone really wants they can do that themselves easily... As it is, the dev command feels like unnecessary magic to me. I'm so so with the idea of deprecating the dev command, Daniel. From one side you are right, all it does is create a symlink. On the other hand, is a symlink added in the exact place, in order for Sugar to install your activity. As a user, I never had to worry about it, it just works. As a comparison, the 'volo create' command we have in sugar-web does simple operations as well (as we use it) but is very nice to have that automated. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Daniel Narvaez -- 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] Web activities on XO-4
Fantastic. Good work! Gonzalo On Wed, Sep 18, 2013 at 2:01 PM, Manuel Quiñones ma...@laptop.org wrote: I finally got web activities working on XO-4, in the AU build published yesterday [1] . I did it by modifying webactivities.py to use WebKitGTK1 instead of v2. The changes are: https://github.com/manuq/sugar-toolkit-gtk3-1/compare/webacts-webkit1 I tried it with Gears Activity v3, and is working. It stores the data and the metadata. So it is communicating with the shell just fine. The touchscreen is not responding very well, at least in this activity. I can tap buttons, but I can barely drag to move a gear or to draw one. The dragging seems to be cancelled in the middle of the action. Mouse input works fine. Also as expected, the icons look small in the XO screen because I need to adapt the theme. But that is an easy one, just changing the CEL_SIZE variable in the LESS file to create another CSS for the XO screen DPI, and adding a CSS media query selector to the HTML. I'll provide a patch to sugar-web-template and will update my web activities. The inspector is not working, it does not display. It shoud display by Ctrl+Shift+I or by right-click - Inspect element. There is no error in the logs and the API is there [2], but nothing is happening. Surprisingly, JavaScript console logs go to the activity log. We are missing that in master. I managed to keep the activity:// scheme that we need for the same-origin policy, but I still had to add the setting 'enable-file-access-from-file-uris' to workaround the cross-site requests. I can't find a way to register the URI scheme in WK1, so I added a big FIXME. [1] http://build.laptop.org.au/xo/os/sugar-100/build-21/ [2] http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebInspector.html -- .. manuq .. ___ 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] Bundlebuilder dev command
I people continue using ~/Activities directory is not a problem, right? What is the point of move the directory where the activities are installed? Changing these directories without a good motive _is_ a problem. Nobody will update the documentation, wiki pages, tutorials, and development book, then people will be confused. Gonzalo On Wed, Sep 18, 2013 at 1:29 PM, Daniel Narvaez dwnarv...@gmail.com wrote: Fair enough, I'll let people which cares about gtk2 toolkit and the dev command fix that bug :) On Wednesday, 18 September 2013, Gonzalo Odiard wrote: -1 Please don't remove the dev command. It works. If you don't use does not means other don't find it useful. Gonzalo On Wed, Sep 18, 2013 at 8:23 AM, Manuel Quiñones ma...@laptop.orgwrote: Sorry for the late answer, 2013/9/15 Daniel Narvaez dwnarv...@gmail.com: Hello, as discussed in another thread, the sugar-toolkit bundlebuilder dev command is not respecting the SUGAR_ACTIVITIES_PATH (a fix for that landed in sugar-toolkit-gtk3 recently). Thanks for the fix. I wonder if we should just drop the dev command, and suggest to develop directly in sugar-build/activities (or ~/Activities when outside sugar-build). All that the command does is to create a symlink anyway, if someone really wants they can do that themselves easily... As it is, the dev command feels like unnecessary magic to me. I'm so so with the idea of deprecating the dev command, Daniel. From one side you are right, all it does is create a symlink. On the other hand, is a symlink added in the exact place, in order for Sugar to install your activity. As a user, I never had to worry about it, it just works. As a comparison, the 'volo create' command we have in sugar-web does simple operations as well (as we use it) but is very nice to have that automated. -- .. manuq .. ___ 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] Bundlebuilder dev command
Nothing changed in sugar itself, I just fixed obvious bugs, like
environment variables not being consistently respected, nonsense code
duplication etc.
About sugar-build, the change is necessary because you want everything to
be contained in the mounted directory (sugar-build), so that it's available
both inside and outside the chroot. That way you can easily hack on it
outside and run it inside. This is correctly documented on
developer.sugarlabs.org and, as far as I know, nowhere else.
On Wednesday, 18 September 2013, Gonzalo Odiard wrote:
I people continue using ~/Activities directory is not a problem, right?
What is the point of move the directory where the activities are installed?
Changing these directories without a good motive _is_ a problem.
Nobody will update the documentation, wiki pages,
tutorials, and development book, then people will be confused.
Gonzalo
On Wed, Sep 18, 2013 at 1:29 PM, Daniel Narvaez
dwnarv...@gmail.comjavascript:_e({}, 'cvml', 'dwnarv...@gmail.com');
wrote:
Fair enough, I'll let people which cares about gtk2 toolkit and the dev
command fix that bug :)
On Wednesday, 18 September 2013, Gonzalo Odiard wrote:
-1
Please don't remove the dev command.
It works. If you don't use does not means other don't find it useful.
Gonzalo
On Wed, Sep 18, 2013 at 8:23 AM, Manuel Quiñones ma...@laptop.orgwrote:
Sorry for the late answer,
2013/9/15 Daniel Narvaez dwnarv...@gmail.com:
Hello,
as discussed in another thread, the sugar-toolkit bundlebuilder dev
command
is not respecting the SUGAR_ACTIVITIES_PATH (a fix for that landed in
sugar-toolkit-gtk3 recently).
Thanks for the fix.
I wonder if we should just drop the dev command, and suggest to
develop
directly in sugar-build/activities (or ~/Activities when outside
sugar-build). All that the command does is to create a symlink
anyway, if
someone really wants they can do that themselves easily... As it is,
the dev
command feels like unnecessary magic to me.
I'm so so with the idea of deprecating the dev command, Daniel.
From one side you are right, all it does is create a symlink. On the
other hand, is a symlink added in the exact place, in order for Sugar
to install your activity. As a user, I never had to worry about it,
it just works. As a comparison, the 'volo create' command we have in
sugar-web does simple operations as well (as we use it) but is very
nice to have that automated.
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
Daniel Narvaez
--
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Web activities on XO-4
Nice work. Did you check that you are actually getting a different origin in each activity using the new approach to activity://? On Wednesday, 18 September 2013, Manuel Quiñones wrote: I finally got web activities working on XO-4, in the AU build published yesterday [1] . I did it by modifying webactivities.py to use WebKitGTK1 instead of v2. The changes are: https://github.com/manuq/sugar-toolkit-gtk3-1/compare/webacts-webkit1 I tried it with Gears Activity v3, and is working. It stores the data and the metadata. So it is communicating with the shell just fine. The touchscreen is not responding very well, at least in this activity. I can tap buttons, but I can barely drag to move a gear or to draw one. The dragging seems to be cancelled in the middle of the action. Mouse input works fine. Also as expected, the icons look small in the XO screen because I need to adapt the theme. But that is an easy one, just changing the CEL_SIZE variable in the LESS file to create another CSS for the XO screen DPI, and adding a CSS media query selector to the HTML. I'll provide a patch to sugar-web-template and will update my web activities. The inspector is not working, it does not display. It shoud display by Ctrl+Shift+I or by right-click - Inspect element. There is no error in the logs and the API is there [2], but nothing is happening. Surprisingly, JavaScript console logs go to the activity log. We are missing that in master. I managed to keep the activity:// scheme that we need for the same-origin policy, but I still had to add the setting 'enable-file-access-from-file-uris' to workaround the cross-site requests. I can't find a way to register the URI scheme in WK1, so I added a big FIXME. [1] http://build.laptop.org.au/xo/os/sugar-100/build-21/ [2] http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebInspector.html -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org javascript:; 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] Web activities on XO-4
2013/9/18 Daniel Narvaez dwnarv...@gmail.com: Nice work. Did you check that you are actually getting a different origin in each activity using the new approach to activity://? Logged document.location.origin, it gives file://, that's why I had to add the 'enable-file-access-from-file-uris' setting. What the new approach does is substitute activity://.. for file://.. when a resource is requested. On the other hand, touch works *sometimes*. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Web activities on XO-4
You could put an http server in the activity... Sucks but I'm not sure there is a better way :/ On Wednesday, 18 September 2013, Manuel Quiñones wrote: I finally got web activities working on XO-4, in the AU build published yesterday [1] . I did it by modifying webactivities.py to use WebKitGTK1 instead of v2. The changes are: https://github.com/manuq/sugar-toolkit-gtk3-1/compare/webacts-webkit1 I tried it with Gears Activity v3, and is working. It stores the data and the metadata. So it is communicating with the shell just fine. The touchscreen is not responding very well, at least in this activity. I can tap buttons, but I can barely drag to move a gear or to draw one. The dragging seems to be cancelled in the middle of the action. Mouse input works fine. Also as expected, the icons look small in the XO screen because I need to adapt the theme. But that is an easy one, just changing the CEL_SIZE variable in the LESS file to create another CSS for the XO screen DPI, and adding a CSS media query selector to the HTML. I'll provide a patch to sugar-web-template and will update my web activities. The inspector is not working, it does not display. It shoud display by Ctrl+Shift+I or by right-click - Inspect element. There is no error in the logs and the API is there [2], but nothing is happening. Surprisingly, JavaScript console logs go to the activity log. We are missing that in master. I managed to keep the activity:// scheme that we need for the same-origin policy, but I still had to add the setting 'enable-file-access-from-file-uris' to workaround the cross-site requests. I can't find a way to register the URI scheme in WK1, so I added a big FIXME. [1] http://build.laptop.org.au/xo/os/sugar-100/build-21/ [2] http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebInspector.html -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org javascript:; 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] Web activities on XO-4
This is for the potential security risk of opening files outside of the activity directory, or because can be a problem with different activities running at the same time or multiple instances of the same activity? Gonzalo On Wed, Sep 18, 2013 at 5:46 PM, Daniel Narvaez dwnarv...@gmail.com wrote: You could put an http server in the activity... Sucks but I'm not sure there is a better way :/ On Wednesday, 18 September 2013, Manuel Quiñones wrote: I finally got web activities working on XO-4, in the AU build published yesterday [1] . I did it by modifying webactivities.py to use WebKitGTK1 instead of v2. The changes are: https://github.com/manuq/sugar-toolkit-gtk3-1/compare/webacts-webkit1 I tried it with Gears Activity v3, and is working. It stores the data and the metadata. So it is communicating with the shell just fine. The touchscreen is not responding very well, at least in this activity. I can tap buttons, but I can barely drag to move a gear or to draw one. The dragging seems to be cancelled in the middle of the action. Mouse input works fine. Also as expected, the icons look small in the XO screen because I need to adapt the theme. But that is an easy one, just changing the CEL_SIZE variable in the LESS file to create another CSS for the XO screen DPI, and adding a CSS media query selector to the HTML. I'll provide a patch to sugar-web-template and will update my web activities. The inspector is not working, it does not display. It shoud display by Ctrl+Shift+I or by right-click - Inspect element. There is no error in the logs and the API is there [2], but nothing is happening. Surprisingly, JavaScript console logs go to the activity log. We are missing that in master. I managed to keep the activity:// scheme that we need for the same-origin policy, but I still had to add the setting 'enable-file-access-from-file-uris' to workaround the cross-site requests. I can't find a way to register the URI scheme in WK1, so I added a big FIXME. [1] http://build.laptop.org.au/xo/os/sugar-100/build-21/ [2] http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebInspector.html -- .. manuq .. ___ 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 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Web activities on XO-4
You mean why the http server would be a problem?
On Wednesday, 18 September 2013, Gonzalo Odiard wrote:
This is for the potential security risk of opening files outside of the
activity directory,
or because can be a problem with different activities running at the same
time
or multiple instances of the same activity?
Gonzalo
On Wed, Sep 18, 2013 at 5:46 PM, Daniel Narvaez
dwnarv...@gmail.comjavascript:_e({}, 'cvml', 'dwnarv...@gmail.com');
wrote:
You could put an http server in the activity... Sucks but I'm not sure
there is a better way :/
On Wednesday, 18 September 2013, Manuel Quiñones wrote:
I finally got web activities working on XO-4, in the AU build
published yesterday [1] . I did it by modifying webactivities.py to
use WebKitGTK1 instead of v2. The changes are:
https://github.com/manuq/sugar-toolkit-gtk3-1/compare/webacts-webkit1
I tried it with Gears Activity v3, and is working. It stores the data
and the metadata. So it is communicating with the shell just fine.
The touchscreen is not responding very well, at least in this
activity. I can tap buttons, but I can barely drag to move a gear or
to draw one. The dragging seems to be cancelled in the middle of the
action. Mouse input works fine.
Also as expected, the icons look small in the XO screen because I need
to adapt the theme. But that is an easy one, just changing the
CEL_SIZE variable in the LESS file to create another CSS for the XO
screen DPI, and adding a CSS media query selector to the HTML. I'll
provide a patch to sugar-web-template and will update my web
activities.
The inspector is not working, it does not display. It shoud display
by Ctrl+Shift+I or by right-click - Inspect element. There is no
error in the logs and the API is there [2], but nothing is happening.
Surprisingly, JavaScript console logs go to the activity log. We are
missing that in master.
I managed to keep the activity:// scheme that we need for the
same-origin policy, but I still had to add the setting
'enable-file-access-from-file-uris' to workaround the cross-site
requests. I can't find a way to register the URI scheme in WK1, so I
added a big FIXME.
[1] http://build.laptop.org.au/xo/os/sugar-100/build-21/
[2]
http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebInspector.html
--
.. manuq ..
___
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 javascript:_e({}, 'cvml',
'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] Web activities on XO-4
No, why is needed use a local web server instead of the use of the proposed solution (use 'enable-file-access-from-file-uris' ) Gonzalo On Wed, Sep 18, 2013 at 6:06 PM, Daniel Narvaez dwnarv...@gmail.com wrote: You mean why the http server would be a problem? On Wednesday, 18 September 2013, Gonzalo Odiard wrote: This is for the potential security risk of opening files outside of the activity directory, or because can be a problem with different activities running at the same time or multiple instances of the same activity? Gonzalo On Wed, Sep 18, 2013 at 5:46 PM, Daniel Narvaez dwnarv...@gmail.comwrote: You could put an http server in the activity... Sucks but I'm not sure there is a better way :/ On Wednesday, 18 September 2013, Manuel Quiñones wrote: I finally got web activities working on XO-4, in the AU build published yesterday [1] . I did it by modifying webactivities.py to use WebKitGTK1 instead of v2. The changes are: https://github.com/manuq/sugar-toolkit-gtk3-1/compare/webacts-webkit1 I tried it with Gears Activity v3, and is working. It stores the data and the metadata. So it is communicating with the shell just fine. The touchscreen is not responding very well, at least in this activity. I can tap buttons, but I can barely drag to move a gear or to draw one. The dragging seems to be cancelled in the middle of the action. Mouse input works fine. Also as expected, the icons look small in the XO screen because I need to adapt the theme. But that is an easy one, just changing the CEL_SIZE variable in the LESS file to create another CSS for the XO screen DPI, and adding a CSS media query selector to the HTML. I'll provide a patch to sugar-web-template and will update my web activities. The inspector is not working, it does not display. It shoud display by Ctrl+Shift+I or by right-click - Inspect element. There is no error in the logs and the API is there [2], but nothing is happening. Surprisingly, JavaScript console logs go to the activity log. We are missing that in master. I managed to keep the activity:// scheme that we need for the same-origin policy, but I still had to add the setting 'enable-file-access-from-file-uris' to workaround the cross-site requests. I can't find a way to register the URI scheme in WK1, so I added a big FIXME. [1] http://build.laptop.org.au/xo/os/sugar-100/build-21/ [2] http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebInspector.html -- .. manuq .. ___ 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 -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Web activities on XO-4
Well, there are several html features which depend on each activity having
their own origin, for example local storage.
On Wednesday, 18 September 2013, Gonzalo Odiard wrote:
No, why is needed use a local web server instead of
the use of the proposed solution (use 'enable-file-access-from-file-
uris' )
Gonzalo
On Wed, Sep 18, 2013 at 6:06 PM, Daniel Narvaez
dwnarv...@gmail.comjavascript:_e({}, 'cvml', 'dwnarv...@gmail.com');
wrote:
You mean why the http server would be a problem?
On Wednesday, 18 September 2013, Gonzalo Odiard wrote:
This is for the potential security risk of opening files outside of the
activity directory,
or because can be a problem with different activities running at the
same time
or multiple instances of the same activity?
Gonzalo
On Wed, Sep 18, 2013 at 5:46 PM, Daniel Narvaez dwnarv...@gmail.comwrote:
You could put an http server in the activity... Sucks but I'm not sure
there is a better way :/
On Wednesday, 18 September 2013, Manuel Quiñones wrote:
I finally got web activities working on XO-4, in the AU build
published yesterday [1] . I did it by modifying webactivities.py to
use WebKitGTK1 instead of v2. The changes are:
https://github.com/manuq/sugar-toolkit-gtk3-1/compare/webacts-webkit1
I tried it with Gears Activity v3, and is working. It stores the data
and the metadata. So it is communicating with the shell just fine.
The touchscreen is not responding very well, at least in this
activity. I can tap buttons, but I can barely drag to move a gear or
to draw one. The dragging seems to be cancelled in the middle of the
action. Mouse input works fine.
Also as expected, the icons look small in the XO screen because I need
to adapt the theme. But that is an easy one, just changing the
CEL_SIZE variable in the LESS file to create another CSS for the XO
screen DPI, and adding a CSS media query selector to the HTML. I'll
provide a patch to sugar-web-template and will update my web
activities.
The inspector is not working, it does not display. It shoud display
by Ctrl+Shift+I or by right-click - Inspect element. There is no
error in the logs and the API is there [2], but nothing is happening.
Surprisingly, JavaScript console logs go to the activity log. We are
missing that in master.
I managed to keep the activity:// scheme that we need for the
same-origin policy, but I still had to add the setting
'enable-file-access-from-file-uris' to workaround the cross-site
requests. I can't find a way to register the URI scheme in WK1, so I
added a big FIXME.
[1] http://build.laptop.org.au/xo/os/sugar-100/build-21/
[2]
http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebInspector.html
--
.. manuq ..
___
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
--
Daniel Narvaez
--
Daniel Narvaez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Web activities on XO-4
Ok. Thanks. The web server need have something special or just serve a directory is enough? Gonzalo On Wed, Sep 18, 2013 at 6:22 PM, Daniel Narvaez dwnarv...@gmail.com wrote: Well, there are several html features which depend on each activity having their own origin, for example local storage. On Wednesday, 18 September 2013, Gonzalo Odiard wrote: No, why is needed use a local web server instead of the use of the proposed solution (use 'enable-file-access-from-file- uris' ) Gonzalo On Wed, Sep 18, 2013 at 6:06 PM, Daniel Narvaez dwnarv...@gmail.comwrote: You mean why the http server would be a problem? On Wednesday, 18 September 2013, Gonzalo Odiard wrote: This is for the potential security risk of opening files outside of the activity directory, or because can be a problem with different activities running at the same time or multiple instances of the same activity? Gonzalo On Wed, Sep 18, 2013 at 5:46 PM, Daniel Narvaez dwnarv...@gmail.comwrote: You could put an http server in the activity... Sucks but I'm not sure there is a better way :/ On Wednesday, 18 September 2013, Manuel Quiñones wrote: I finally got web activities working on XO-4, in the AU build published yesterday [1] . I did it by modifying webactivities.py to use WebKitGTK1 instead of v2. The changes are: https://github.com/manuq/sugar-toolkit-gtk3-1/compare/webacts-webkit1 I tried it with Gears Activity v3, and is working. It stores the data and the metadata. So it is communicating with the shell just fine. The touchscreen is not responding very well, at least in this activity. I can tap buttons, but I can barely drag to move a gear or to draw one. The dragging seems to be cancelled in the middle of the action. Mouse input works fine. Also as expected, the icons look small in the XO screen because I need to adapt the theme. But that is an easy one, just changing the CEL_SIZE variable in the LESS file to create another CSS for the XO screen DPI, and adding a CSS media query selector to the HTML. I'll provide a patch to sugar-web-template and will update my web activities. The inspector is not working, it does not display. It shoud display by Ctrl+Shift+I or by right-click - Inspect element. There is no error in the logs and the API is there [2], but nothing is happening. Surprisingly, JavaScript console logs go to the activity log. We are missing that in master. I managed to keep the activity:// scheme that we need for the same-origin policy, but I still had to add the setting 'enable-file-access-from-file-uris' to workaround the cross-site requests. I can't find a way to register the URI scheme in WK1, so I added a big FIXME. [1] http://build.laptop.org.au/xo/os/sugar-100/build-21/ [2] http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebInspector.html -- .. manuq .. ___ 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 -- Daniel Narvaez -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Web activities on XO-4
Yeah, a web server is how this issue is usually overcome. I was expecting a proper way but seems that only webkit2 has one, the register_uri_scheme . 2013/9/18 Gonzalo Odiard gonz...@laptop.org: Ok. Thanks. The web server need have something special or just serve a directory is enough? Gonzalo On Wed, Sep 18, 2013 at 6:22 PM, Daniel Narvaez dwnarv...@gmail.com wrote: Well, there are several html features which depend on each activity having their own origin, for example local storage. On Wednesday, 18 September 2013, Gonzalo Odiard wrote: No, why is needed use a local web server instead of the use of the proposed solution (use 'enable-file-access-from-file-uris' ) Gonzalo On Wed, Sep 18, 2013 at 6:06 PM, Daniel Narvaez dwnarv...@gmail.com wrote: You mean why the http server would be a problem? On Wednesday, 18 September 2013, Gonzalo Odiard wrote: This is for the potential security risk of opening files outside of the activity directory, or because can be a problem with different activities running at the same time or multiple instances of the same activity? Gonzalo On Wed, Sep 18, 2013 at 5:46 PM, Daniel Narvaez dwnarv...@gmail.com wrote: You could put an http server in the activity... Sucks but I'm not sure there is a better way :/ On Wednesday, 18 September 2013, Manuel Quiñones wrote: I finally got web activities working on XO-4, in the AU build published yesterday [1] . I did it by modifying webactivities.py to use WebKitGTK1 instead of v2. The changes are: https://github.com/manuq/sugar-toolkit-gtk3-1/compare/webacts-webkit1 I tried it with Gears Activity v3, and is working. It stores the data and the metadata. So it is communicating with the shell just fine. The touchscreen is not responding very well, at least in this activity. I can tap buttons, but I can barely drag to move a gear or to draw one. The dragging seems to be cancelled in the middle of the action. Mouse input works fine. Also as expected, the icons look small in the XO screen because I need to adapt the theme. But that is an easy one, just changing the CEL_SIZE variable in the LESS file to create another CSS for the XO screen DPI, and adding a CSS media query selector to the HTML. I'll provide a patch to sugar-web-template and will update my web activities. The inspector is not working, it does not display. It shoud display by Ctrl+Shift+I or by right-click - Inspect element. There is no error in the logs and the API is there [2], but nothing is happening. Surprisingly, JavaScript console logs go to the activity log. We are missing that in master. I managed to keep the activity:// scheme that we need for the same-origin policy, but I still had to add the setting 'enable-file-access-from-file-uris' to workaround the cross-site requests. I can't find a way to register the URI scheme in WK1, so I added a big FIXME. [1] http://build.laptop.org.au/xo/os/sugar-100/build-21/ [2] http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebInspector.html -- .. manuq .. ___ 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 -- Daniel Narvaez -- Daniel Narvaez -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Web activities on XO-4
Just a directory. It needs to be one server per activity though, so that the different port gives us a different origin. On 18 September 2013 23:32, Gonzalo Odiard gonz...@laptop.org wrote: Ok. Thanks. The web server need have something special or just serve a directory is enough? Gonzalo On Wed, Sep 18, 2013 at 6:22 PM, Daniel Narvaez dwnarv...@gmail.comwrote: Well, there are several html features which depend on each activity having their own origin, for example local storage. On Wednesday, 18 September 2013, Gonzalo Odiard wrote: No, why is needed use a local web server instead of the use of the proposed solution (use 'enable-file-access-from-file- uris' ) Gonzalo On Wed, Sep 18, 2013 at 6:06 PM, Daniel Narvaez dwnarv...@gmail.comwrote: You mean why the http server would be a problem? On Wednesday, 18 September 2013, Gonzalo Odiard wrote: This is for the potential security risk of opening files outside of the activity directory, or because can be a problem with different activities running at the same time or multiple instances of the same activity? Gonzalo On Wed, Sep 18, 2013 at 5:46 PM, Daniel Narvaez dwnarv...@gmail.comwrote: You could put an http server in the activity... Sucks but I'm not sure there is a better way :/ On Wednesday, 18 September 2013, Manuel Quiñones wrote: I finally got web activities working on XO-4, in the AU build published yesterday [1] . I did it by modifying webactivities.py to use WebKitGTK1 instead of v2. The changes are: https://github.com/manuq/sugar-toolkit-gtk3-1/compare/webacts-webkit1 I tried it with Gears Activity v3, and is working. It stores the data and the metadata. So it is communicating with the shell just fine. The touchscreen is not responding very well, at least in this activity. I can tap buttons, but I can barely drag to move a gear or to draw one. The dragging seems to be cancelled in the middle of the action. Mouse input works fine. Also as expected, the icons look small in the XO screen because I need to adapt the theme. But that is an easy one, just changing the CEL_SIZE variable in the LESS file to create another CSS for the XO screen DPI, and adding a CSS media query selector to the HTML. I'll provide a patch to sugar-web-template and will update my web activities. The inspector is not working, it does not display. It shoud display by Ctrl+Shift+I or by right-click - Inspect element. There is no error in the logs and the API is there [2], but nothing is happening. Surprisingly, JavaScript console logs go to the activity log. We are missing that in master. I managed to keep the activity:// scheme that we need for the same-origin policy, but I still had to add the setting 'enable-file-access-from-file-uris' to workaround the cross-site requests. I can't find a way to register the URI scheme in WK1, so I added a big FIXME. [1] http://build.laptop.org.au/xo/os/sugar-100/build-21/ [2] http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebInspector.html -- .. manuq .. ___ 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 -- Daniel Narvaez -- Daniel Narvaez -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Web activities on XO-4
Map-2.xo (or thereabouts) had a web server built in. I don't remember the specifics, but if someone can dig up the code there might be some ideas in there. I recall Dan Williams was helpful in drafting a script for finding the best available port per activity instance. On Wed, Sep 18, 2013 at 8:12 PM, Manuel Quiñones ma...@laptop.org wrote: Yeah, a web server is how this issue is usually overcome. I was expecting a proper way but seems that only webkit2 has one, the register_uri_scheme . 2013/9/18 Gonzalo Odiard gonz...@laptop.org: Ok. Thanks. The web server need have something special or just serve a directory is enough? Gonzalo On Wed, Sep 18, 2013 at 6:22 PM, Daniel Narvaez dwnarv...@gmail.com wrote: Well, there are several html features which depend on each activity having their own origin, for example local storage. On Wednesday, 18 September 2013, Gonzalo Odiard wrote: No, why is needed use a local web server instead of the use of the proposed solution (use 'enable-file-access-from-file-uris' ) Gonzalo On Wed, Sep 18, 2013 at 6:06 PM, Daniel Narvaez dwnarv...@gmail.com wrote: You mean why the http server would be a problem? On Wednesday, 18 September 2013, Gonzalo Odiard wrote: This is for the potential security risk of opening files outside of the activity directory, or because can be a problem with different activities running at the same time or multiple instances of the same activity? Gonzalo On Wed, Sep 18, 2013 at 5:46 PM, Daniel Narvaez dwnarv...@gmail.com wrote: You could put an http server in the activity... Sucks but I'm not sure there is a better way :/ On Wednesday, 18 September 2013, Manuel Quiñones wrote: I finally got web activities working on XO-4, in the AU build published yesterday [1] . I did it by modifying webactivities.py to use WebKitGTK1 instead of v2. The changes are: https://github.com/manuq/sugar-toolkit-gtk3-1/compare/webacts-webkit1 I tried it with Gears Activity v3, and is working. It stores the data and the metadata. So it is communicating with the shell just fine. The touchscreen is not responding very well, at least in this activity. I can tap buttons, but I can barely drag to move a gear or to draw one. The dragging seems to be cancelled in the middle of the action. Mouse input works fine. Also as expected, the icons look small in the XO screen because I need to adapt the theme. But that is an easy one, just changing the CEL_SIZE variable in the LESS file to create another CSS for the XO screen DPI, and adding a CSS media query selector to the HTML. I'll provide a patch to sugar-web-template and will update my web activities. The inspector is not working, it does not display. It shoud display by Ctrl+Shift+I or by right-click - Inspect element. There is no error in the logs and the API is there [2], but nothing is happening. Surprisingly, JavaScript console logs go to the activity log. We are missing that in master. I managed to keep the activity:// scheme that we need for the same-origin policy, but I still had to add the setting 'enable-file-access-from-file-uris' to workaround the cross-site requests. I can't find a way to register the URI scheme in WK1, so I added a big FIXME. [1] http://build.laptop.org.au/xo/os/sugar-100/build-21/ [2] http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebInspector.html -- .. manuq .. ___ 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 -- Daniel Narvaez -- Daniel Narvaez -- .. manuq .. ___ 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
