Re: [Sugar-devel] Sugar web activity wait 1 minute at startup
Got it!
It come from the SVG files referenced by the toolbar and used for FR and EN
flag.
#main-toolbar #en-button {
margin-left: 100px;
background-image: url(images/en.svg);
}
#main-toolbar #fr-button {
margin-left: 5px;
background-image: url(images/fr.svg);
}
It seems that these files [1] had reference on an external RDF resource.
This resource exist, don't know why I've got a timeout both when connected
and not connected.
image/svg+xml
http://purl.org/dc/dcmitype/StillImage"; />
I've switch these files with others and it works now.
Thanks for your help to all.
@Ignacio, I've took theses files from your WhatIs activity...
Lionel.
[1] https://github.com/llaske/FoodChain/blob/master/images/en.svg
2014-02-03 Lionel Laské :
> Nice !
> Great Gonzalo, I'm going to inspect that.
>
> Lionel.
>
>
> 2014-02-03 James Cameron :
>
> On Mon, Feb 03, 2014 at 05:11:30PM -0200, Gonzalo Odiard wrote:
>> > The lines with doctype and body are not related with the problem,
>> > just commenting the reerence to styles.css solves the problem.
>> >
>> > I have been looking at styles.css, but didn't find what could be the
>> > problem. I hope this is of some help!
>>
>> It probably is. Try an empty styles.css, and if the problem is still
>> missing gradually add back lines of styles.css until the problem
>> returns.
>>
>> A very interesting discovery.
>>
>> --
>> James Cameron
>> http://quozl.linux.org.au/
>>
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Call to Maintainers: GCI 2013 work
Hello Maintainers, Google Code In 2013 has finished, and was probably one of the most productive ever. We have a page with links to all the tasks [1]. I have added information about the module (activity or sugar) for every task, to make easier to maintainers, get all the code related to their activities. Please, if you already merged the code related to a task, add "Merged" in the "State" column. There are a "Info" colum where you can put the activity version where is available or git id. The table is sort-able, to make easier locate by module. GCI participants can help to keep the page updated too, adding the information of already merged items. The intention of this page is help Sugar to take advantage all this great work. We need agree in a State for the tasks where after review, we decided not include the code. We need close the related tickets too, to avoid making volunteers work on that issues again. Regards, -- Gonzalo Odiard SugarLabs - Learning Software for children [1] http://wiki.sugarlabs.org/go/Google_Code_In_2013/Final_Work ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar web activity wait 1 minute at startup
Nice ! Great Gonzalo, I'm going to inspect that. Lionel. 2014-02-03 James Cameron : > On Mon, Feb 03, 2014 at 05:11:30PM -0200, Gonzalo Odiard wrote: > > The lines with doctype and body are not related with the problem, > > just commenting the reerence to styles.css solves the problem. > > > > I have been looking at styles.css, but didn't find what could be the > > problem. I hope this is of some help! > > It probably is. Try an empty styles.css, and if the problem is still > missing gradually add back lines of styles.css until the problem > returns. > > A very interesting discovery. > > -- > 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] Sugar web activity wait 1 minute at startup
On Mon, Feb 03, 2014 at 05:11:30PM -0200, Gonzalo Odiard wrote: > The lines with doctype and body are not related with the problem, > just commenting the reerence to styles.css solves the problem. > > I have been looking at styles.css, but didn't find what could be the > problem. I hope this is of some help! It probably is. Try an empty styles.css, and if the problem is still missing gradually add back lines of styles.css until the problem returns. A very interesting discovery. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Physics-17
Activity Homepage: http://activities.sugarlabs.org/addon/4193 Sugar Platform: 0.96 - 0.100 Download Now: http://activities.sugarlabs.org/downloads/file/28893/physics-17.xo Release notes: 17 ENHANCEMENT: Chain tool behaves like Magic Pen: you can draw arbitrary shapes and closed loops Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar web activity wait 1 minute at startup
Hi Lionel, I have found something. Attached is a modified index.html, who makes the activity start fast. The only changes are: - Food Chain @@ -8,9 +7,10 @@ - + + After start, the images are not well positioned, but that is another problem. The lines with doctype and body are not related with the problem, just commenting the reerence to styles.css solves the problem. I have been looking at styles.css, but didn't find what could be the problem. I hope this is of some help! Gonzalo On Sun, Jan 26, 2014 at 5:38 AM, Lionel Laské wrote: > > Hi all, > > I'm currently porting my FoodChain activity [1] as a full Sugar Web > activity. It's mainly a packaging work because FoodChain is already written > in HTML5/JavaScript but with a Python package around it. > > The new Sugar Web activity works well but when I'm testing it on Sugar > 0.100 on the XO, the loading process is very long (more than 1 minute) - > tested on the XO 1.75 and XO 4 on the old and the recent package. > > I've isolated the lost time using the sugar-launch command (see log > below). It takes more than 1 minute to load "favicon.ico" (see log between > 15:04:23 and 15:05:34). I don't see any reason for that because it's a very > tiny file. > More, when I delete this file, the lost time is still here and when I see > the trace for another Sugar Web activity, I don't have this loading time, > including when "favicon.ico" is not here. > Launching the activity on sugar-build don't show this issue neither. > I suspect that the problem is not on "favicon.ico" but on something like a > "timeout" somewhere (on a socket ?). > Source code of the activity is here [2], the packaged activity with this > issue could be downloaded here [3]. > > Any suggestion is welcome to help me to debug this issue. > > Best regards from France. > > Lionel. > > > [1] http://activities.sugarlabs.org/en/sugar/addon/4612 > [2] https://github.com/llaske/FoodChain > [3] http://laske.fr/tmp/foodchain-4.xo > > > > > [olpc@schoolserver FoodChain.activity]$ sugar-launch > org.olpcfrance.FoodChain > org.olpcfrance.FoodChain > 1390662262.276506 ERROR root: Using port 50662 > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:22] "GET /index.html > HTTP/1.1" 200 - > > (sugar-activity:4018): Gdk-CRITICAL **: gdk_device_get_source: assertion > `GDK_IS_DEVICE (device)' failed > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET > /lib/sugar-web/graphics/css/sugar.css HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /enyo/enyo.css > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /enyo/enyo.js > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /lib/require.js > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /depends.js > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /styles.css > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET > /lib/canvas/package.js HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET > /lib/canvas/Canvas.js HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET > /lib/canvas/CanvasControl.js HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET > /lib/canvas/Shape.js HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET > /lib/canvas/Circle.js HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET > /lib/canvas/Rectangle.js HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET > /lib/canvas/Text.js HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET > /lib/canvas/Image.js HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /l10n.js HTTP/1.1" > 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /util.js HTTP/1.1" > 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /audio.js > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /timer.js > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /card.js HTTP/1.1" > 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /chain.js > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /shadowbutton.js > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /sprite.js > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /learngame.js > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /buildgame.js > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /playgame.js > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /credits.js > HTTP/1.1" 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET /app.js HTTP/1.1" > 200 - > xo-d2-7d-0b.localdomain - - [25/Jan/2014 15:04:23] "GET > /activity/activity-icon.svg HTTP/1.1" 200 - > xo-d2-7d-0b.l
Re: [Sugar-devel] Notifications
On Mon, Feb 3, 2014 at 9:40 AM, Manuel Quiñones wrote: > 2014-01-29 Sam Parkinson : > > > > Hi, > > > > Here is a video: https://vidd.me/oJD > > Great start! > > We've been discussing this on IRC, and Sam pointed me to the design > proposal. Is the first one on this page: > http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications > > (Sam, please point to the design you are basing your work next time :-) > > I think the [!] badge is better than the pulsing icon. Pulsing is > used to indicate that the activity is starting. > > About "system" notifications, the proposal doesn't make a distinction. > Disk usage notifications can belong to the Journal, and messages > coming from the school server can live in their own icon. The same > can be used for any other notification. > > -- > .. manuq .. Some other prior work: http://wiki.sugarlabs.org/go/Features/Messages_Notification http://wiki.sugarlabs.org/go/Features/Simple_Messages_Notification ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Start an activity from inside another, take 2
Good work! Gonzalo On Fri, Jan 31, 2014 at 2:23 PM, Manuel Quiñones wrote: > I made a feature page: > http://wiki.sugarlabs.org/go/Features/Start_activity_from_another_activity > > And here is a demo screencast: > https://dl.dropboxusercontent.com/u/588753/start.webm > > Code: > > http://wiki.sugarlabs.org/go/Features/Start_activity_from_another_activity#How_To_Test > > I still need to: > > - make the Journal a user of this > - handle exceptions > - tests > > > -- > .. manuq .. > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Notifications
2014-01-29 Sam Parkinson : > > Hi, > > Here is a video: https://vidd.me/oJD Great start! We've been discussing this on IRC, and Sam pointed me to the design proposal. Is the first one on this page: http://wiki.sugarlabs.org/go/Design_Team/Proposals/Notifications (Sam, please point to the design you are basing your work next time :-) I think the [!] badge is better than the pulsing icon. Pulsing is used to indicate that the activity is starting. About "system" notifications, the proposal doesn't make a distinction. Disk usage notifications can belong to the Journal, and messages coming from the school server can live in their own icon. The same can be used for any other notification. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] JOURNAL+
+1 to all the points from manuq. I love have this view integrated, may be not as a replacement, but as a optional view for the journal, but we need care about all the details. > > There is the action text (Logged, Did a, Wrote) which is set like this: > (In activity.info) > > > > action_text = Watched > > - good idea! Apart from the action text in activities, there can be > Journal entries not tied to activities. This happens for example if > you copy a file from a USB stick, or if you download a file from > Browse. We should consider those cases. Maybe a general text like > "Got a.. [image icon] 2 days ago". > > I (with my activity maintainer hat) want remember to the sugar maintainers you need be careful about making changes needing changes in all the activities. right now we have almost 500 activities, with different grade of maintainer response, and usually take a time to make these changes. Also remember we need these words translated to the languages of our users, and in these particular case, we will need modify the toolkit to allow the translation of this new translatable string in the activity.info file. I still remember the work we did for the summary field, and I confess am a little frustrated to not be able to show it in the sugar ui yet. Maybe now we can work to include it in 0.102 Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] JOURNAL+
2014-02-02 Sam Parkinson : > > Hi > > This changes the journal completely! Now objects are displayed like > sentences, like a real journal. I love it! There are a lot of considerations to make here, so please understand that it can be a long journey implementing without getting regressions. The 90% is easy to implement, the difficulty is in the details (Gonzalo's mantra). Also, it would be great if you can finish the other great stuff you were implementing before trying to eat this big elephant. The replacement of the list view in the home is much appreciated, and the notifications too. Of course is up to you if you want to carry things in parallel, but it will be easier for us all. My time as maintainer is limited, and I have my own tasks. Let me clarify that you are doing a great job and your contributions are much appreciated. Welcome to the design team :) So, for this one: - It seems you are basing your work on the design 01 here: http://wiki.sugarlabs.org/go/Design_Team/Designs/Journal is good to make that explicit, I was aware of the page but others may not know. - The latest changes in the Journal added multiple selection of items, so they can be easy to copy and delete. I think that feature should not be left aside. - In current Journal and in the design 01 there is a list of the friends that have collaborated with you, in case the activity was shared. I like how design 01 display them adding the "with.." to the phrase. - If you start a download in Browse or other activity, or if a file is transferred, the Journal shows a progress bar. This should be considered in the new design. > There is the action text (Logged, Did a, Wrote) which is set like this: (In > activity.info) > > action_text = Watched - good idea! Apart from the action text in activities, there can be Journal entries not tied to activities. This happens for example if you copy a file from a USB stick, or if you download a file from Browse. We should consider those cases. Maybe a general text like "Got a.. [image icon] 2 days ago". > > Then there is the expander thing: > > (Record GTK3 is buggy!) > > This is as simple as: > > mediaObject.metadata['is_child'] = True > > datastore.write(mediaObject) > > activity.add_child(recd.datastoreId) > > Pull request: https://github.com/sugarlabs/sugar/pull/240 > > Thanks, > > Sam -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] SLOB meeting postposed 48 hours
Due to some problems with irc.freenode.net we were not able to meet today. We have rescheduled the meeting for Wednesday, February 5 at 9 EST. Thank you for your understanding. Debido a algunos problemas con irc.freenode.net no fuimos capaces de cumplir hoy. Hemos reprogramado el encuentro de Miércoles, 05 de febrero a las 9 EST. regards. -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
Re: [Sugar-devel] [Sugar-Devel] Toolkit version in the activity info
in the "exec" property in the activity.info file, we have the information about the class to start. Is not good enough check in that file? Another easy alternative is check in the file setup.py Honestly, I don't think we should add a new field in the activity.info file. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Sugar-Devel] Toolkit version in the activity info
2014-01-31 Daniel Narvaez : > On 1 February 2014 03:00, Sam Parkinson wrote: >> >> >> Hi, >> >> Dnarvaez and I were discussing this on the irc; we really need to do >> distinction between the tool kit version in activity.info. >> >> This would be needed to for: >> >> view source >> because now changes to sugar-toolkit-gtk3 can break the gtk2 toolkit (!) >> >> Basically we were thinking to make a new thing: sugar-activity3 to launch >> gtk3 activities. > > It should probably just be a symlink. >> >> It would probably be the same at first, but in the future could be used to >> stop breakage to gtk2 activities. > > I think it was a mistake to not make a sugar-activity3 when we ported. > Though I'm not sure we can undo that now. It would be an API breakage (gtk3 > activities would stop to work unless they changed to sugar-activity3). > > If ever make another parallel installable gtk toolkit it should definately > be sugar-toolkit4 though :) >> >> So yeah, is this going to break everything? Could you think of a better >> way? > > It should not break much actually. Activities that have not switched to > sugar-activity3 will just not get the right sugar toolkit in view source. > > The main issue is probably that activities that change to sugar-activity3 > won't run on old sugar versions. Sigh... wish we had done this when porting > really :/ Yeah, is a shame we didn't thought about this. Maybe because we supposed that the move from gtk2 to gtk3 was transitory. > The alternative, as we discussed, is a new "toolkit" property in the info. > That should not break stuff, it's one more thing to remember for activity > authors though. Maybe we can have bundlebuilder warn about it. > > > More ideas welcome! For the View Source issue, the activities py files can be inspected. If they contain gtk3 code, then show toolkit3. Else, show the old toolkit. For example: grep -r --include="*py" "from gi.repository". Not the cleanest option, but works if this is the only issue identifying the proper toolkit for an activity. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
