Re: [Sugar-devel] [IAEP] collaboration testing session
On Thu, Jun 4, 2009 at 9:09 PM, David Van Assche wrote: > Hi folks, > We are having a collaborative sugar testing session next week Wednesday > 10th June at 20:00 UTC (That is 4 pm EDT, 3pm EST, 2 pm CST, 1 pm MST, and > 12 pm PST, most of Europe that will be 9 pm, 8 pm for the UK) > > So far we have 5 people signed up, but more are welcome as we really want to > see how collaboration works on many activities where it isn't quite obvious. > We will be taking notes and storing log files of the sessions, and will > suggest ways in which the activity in question might be more collaborative, > or may need less of it (who knows :-) Sounds good. I need the results of such tests for project planning. > We will be testing the activities that come preinstalled on the openSUSE > sugar images, but we'd like to test various distribution methods (virtual > appliance, cd, usb, hd) and various distros (at least Fedora SoaS, openSUSE > sugar, Mandriva or Caixa Magica) I dont believe 0.82 images are compatible > with 0.84 for collaboration, so am afraid this is for 0.84 only... I run Ubuntu, and I have virtual images for Fedora, Debian, and Caixa Magica. > Please > post your willingness to participate so we have an idea on who/how many will > be collaborating. We also need a volunteer to take notes, and a volunteer to > store logs files. There will of course be a transcript of the irc session > too (we will meet at #sugar-collaboration) We forsee this taking between 1 > and 2 hours... > > Here is the list of activities we will be testing, so make sure you have > them installed if you plan to take part (not all have collaborative > abilities, and for those that don't it can be a brainstorming session on > whether/how we can make them collaborative: > > sugar-finance > sugar-flipsticks-activity > sugar-freecell > sugar-imageviewer > sugar-implode > sugar-infoslicer > sugar-jigsaw-puzzle-activity > sugar-joke-machine-activity > sugar-jukebox > sugar-labyrinth > sugar-maze > sugar-memorize > sugar-moon > sugar-paint-activity > sugar-pippy > sugar-playgo > sugar-read > sugar-readetexts-activity > sugar-record > sugar-slider-puzzle-activity > sugar-speak > sugar-storybuilder > sugar-tamtam-common > sugar-tamtam-edit > sugar-tamtam-jam > sugar-tamtam-mini > sugar-tamtam-synthlab > sugar-analyze > sugar-turtleart > sugar-typing-turtle > sugar-viewslides > sugar-write > sugar-browse > sugar-irc > sugar-calculate > sugar-xomail (sugar-sweetmail) > sugar-cartoonbuilder > sugar-clock > sugar-colors > sugar-connect > sugar-drgeo-activity > xoEditor > sugar-evince > sugar-fiftytwo > sugar-chat > sugar-terminal > sugar-journal > sugar-physics > sugar-library > sugar-poll > sugar-tuxpaint > > kind Regards, > David (nubae) Van Assche > www.nubae.com > > > ___ > IAEP -- It's An Education Project (not a laptop project!) > i...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep > -- Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name And Children are my nation. The Cosmos is my dwelling place, The Truth my destination. http://earthtreasury.org/worknet (Edward Mokurai Cherlin) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Can't compile mozilla on sugar-jhbuild
Still failing to compile sugar-jhbuild: , | ../../staticlib/libxpcom_core.a: member ../../staticlib/libxpcom_core.a(nsDeque.o) in archive is not an object | collect2: ld returned 1 exit status | make[3]: *** [libxul.so] Erreur 1 ` I'm running GNU/Linux version 2.6.26-2-686 (Debian 2.6.26-15). Idea? -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [math4] Activity Awards, Activity Alerts, Frame Alerts
Hi Frederick,
On 6 Jun 2009, at 00:30, Frederick Grose wrote:
> On Fri, Jun 5, 2009 at 6:32 PM, Gary C Martin
> wrote:
> ...
>
> FWIW, David Van Assche raised some interesting Activity ideas at
> SugarCamp Paris and I'm interested/active in getting us to at lease
> 'demo' state in the Sugar 0.86 release timeframe. The idea is to focus
> on an 'awards' mechanism/style to encourage exploration and provide
> (sometimes) unexpected rewards. Idea is that Activity authors can
> define a range of badges/medals/icons for certain behaviours/
> accomplishment in an attempt to get students to dig deeper (mix of
> 'easter eggs' and specific goals). It's mainly Activity side work (a
> demo activity to start with) but perhaps could find a home in the
> Journal (through an ability of Activity to set some private entry tag
> and for Journal to display that in a user appealing graphical form).
>
> Even for something as hard to measure as the Write Activity, there
> could be 'awards' (hidden or hinted at) for things like "found 10 or
> more collaborators for one document", "gained at least 100 words each
> from 5 or more collaborators", "wrote more than 1,000 words", "you
> used the word entomology!". The idea is many would be hidden
> ("surprise, you did something cool!") and that some initial more
> obvious and visible 'awards' would hint that others were there for
> discovery.
>
> Regards,
> --Gary
>
> P.S. Mechanisms for 'awards' could hook into services like Moodle, the
> Journal, or via collaboration (so perhaps a shared Write session would
> show awards gained by the collaborators). Having a view to show all
> Activity Awards would also be a good driver (could be an activity, or
> ideally at some point part of Journal). The general idea for awards
> drifts in from the gaming environment, where awards are used to
> increase re-playability and tempt folks to try some other possible
> path.
> ...
>
> Nice concept.
>
> Some design and code integration with Activity Alerts,
> http://wiki.sugarlabs.org/go/Development_Team/Almanac/sugar.graphics.alert
> ,
> and Frame alerts, http://wiki.sugarlabs.org/go/Design_Team/Designs/Frame#12
> , http://wiki.sugarlabs.org/go/Design_Team/Designs/Frame#13, etc.
> may be appropriate.
Yep, I imagine it's being up to the activity how it reveals a new
'award' being reached, but it could be as simple as showing an
activity alert message (perhaps as a default design guideline for
awards, if it is accepted), or some fancy splash/animation if the
activity deems it appropriate.
> http://dev.sugarlabs.org/ticket/722 has some discussion. I would
> like to see more noticeable messages for chat invitation alerts, for
> example.
I think this is intended more for Activities (or Sugar shell) in the
background to get your attention, but I guess it could be appropriated
also for awards. I'll keep it in mind, thanks.
> Don't know where this is recorded for the Sugar 0.86 roadmap,
> http://wiki.sugarlabs.org/go/Development_Team/Release/Roadmap/0.86#Proposal_Goals
>
> ?
It's not there. Though it did get discussed at SugarCamp Paris (along
with a many other good ideas). I see awards as happening first as a
single Activity demonstrator, not initially needing any Sugar
integration work or time, but I (and David) would like to see it in
the same time frame as 0.86. If it works, and is of demonstrable
value, then we have fair grounds to lobby for the integration of
useful/generic code, already written, into Sugar 0.88 for other
Activities to easily reuse.
> The software infrastructure you propose could also be used for
> random or rule-based, single-point lesson reminders or reinforcers
> of learning.
Yep :-)
Regards,
--Gary
> --Fred
>
> ___
> FourthGradeMath mailing list
> fourthgradem...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/fourthgrademath
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] More information on font scaling problem
On 5 Jun 2009, at 21:42, James Simmons wrote: > Gary, > > Thanks for doing this. I wish I could say it cleared things up but > I feel more confused than before. You say these are both XO's with > different versions of Sugar. I thought that the font behavior on > the XO was consistent, no matter what version of Sugar you used, but > that you needed to use the SUGAR_SCALING environment variable in > other places to make the fonts look OK. That doesn't make sense > because the zoom factor should be 72, meaning that any font number > you put in would be multiplied by .72 and truncated to the next > lowest integer. Which is just the opposite of what you'd want to > do, because it's the XO that has the font too big, not my > development environment or SoaS. > > Even the .84 one doesn't look right to me. When I run sugar- > emulator on Fedora 10 the font looks *much* smaller than that. > > Maybe sugar-emulator *is* providing SUGAR_SCALING but instead of 100 > it is using 72? Not sure if this is valid, but if I open Terminal activity in 0.82 and "set | grep SUGAR", I see no SUGAR_SCALING environment variable provided. Only: SUGAR_ACTIVITY_ROOT=... SUGAR_BUNDLE_ID=... SUGAR_BUNDLE_NAME=... SUGAR_BUNDLE_PATH=... SUGAR_BUNDLE_VERSION=... SUGAR_LOCALEDIR=... SUGAR_THEME=... Interesting... trying the same under Sugar 0.84 (latest SoaS image) on an XO-1: SUGAR_THEME=... is no longer present SUGAR_SCALING=100 appears! Regards, --Gary > James Simmons > > > Gary C Martin wrote: >> Hi James, >> >> On 5 Jun 2009, at 10:16, Tomeu Vizoso wrote: >> >>> On Wed, Jun 3, 2009 at 16:40, James Simmons>> > wrote: I mentioned before that I'm having a font sizing problem on the XO running .82. When I set a font on a textviewer it looks OK running under sugar-devel or SoaS by is *much* larger on the XO. >>> >>> Sorry, in an earlier email i replied to you what would work in 0.84, >>> didn't realized you were talking about 0.82. >>> >>> In 0.84 Pango knows the resolution of the screen and scales all >>> fonts >>> accordingly. This means that by using, say 10, the font will always >>> look good in all hw. >>> >>> In 0.82 didn't knew about the screen, so we were scaling all fonts >>> by >>> using style.zoom(). >> >> Not sure if you have easy access to both Sugar 0.82 (larger text) >> and 0.84 (smaller text) on an XO-1 for testing, so I've just >> grabbed a screenshot from each showing ReadETexts-12 so at least >> you have examples of your current release behaviour. >> >> Regards, >> --Gary >> > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] collaboration testing session
On 5 Jun 2009, at 21:19, James Simmons wrote: > David, > > Four of the Activities you will be testing use pretty much the same > code > for collaboration: > > sugar-read > sugar-readetexts-activity > sugar-viewslides > sugar-imageviewer For what it's worth, ImageViewer is definitely not collaborating correctly (and has never) for me, it just defaults to the ObjectPicker code path if you try to join a shared session using either Gabble (jabber server) or Salute (local network). Tested 0.82 XO to XO, and 0.84 mixed environments (Soas, Sugar-jhbuild). Regards, --Gary > Read Etexts and View Slides use code copied from Read. Image Viewer > says in its comments that it uses code copied from Read Etexts. All > four basically just let you make a copy of the document that is being > shared. Read is different from the rest because (the last time I > looked) it did not save a copy of the shared document in the Journal. > The rest do. > > Another difference with Read is that it uses meta data in the PDF to > give a title to the Journal entry that is sharing the document. Read > Etexts and View Slides don't have any meta data in their documents, so > documents received from others are given the titles "Read Etexts" or > "View Slides". In the Neighborhood view the names of the documents > offered for sharing are clearly visible, so you'd think there would be > *some* way of getting that information from the sharing Activity so > you > could update the Title in the Journal but I haven't figured out how to > do it. > > View Slides displays a crude count "n of n bytes total" when it > downloads a file and this seems to work. When I put exactly the same > code in Read Etexts it only displayed the final count, not the count > in > progress. Read Etexts uses multi threading when TTS is installed, and > maybe that is related to the reason. > > Transfer of large files is *very* slow. > > Hope this information is of some use. > > James Simmons > > > ___ > 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] [IAEP] [Marketing] ASLO - rebranding
Excellent! After I saw the olpcnews post I spent an hour or so last night doing the same thing. I'm glad I don't have to finish / fine-tune ^__^ +1 On Fri, Jun 5, 2009 at 3:39 PM, Tomeu Vizoso wrote: > On Fri, Jun 5, 2009 at 21:29, Josh Williams wrote: > > Thanks everyone, > > > > Gary mentioned > > > >"Hey, fab, looking much cleaner/simpler/Sugar-like :-) One quick > >thought (will try to take a closer look later), would double > >thickness borders work better, make the colour theme pop a little > >more, feel more robust? > > > >Regards, > >--Gary " > > > > > > I agree that adding two or three pixels to the borders would help the > > design. However, if there aren't any major objections to the design, I > > think we should push it to the live ASLO, and make minor changes later. > > Any thoughts on this? > > +1 on this. And thanks a lot for your awesome work. Looking forward for > more! > > Regards, > > Tomeu > > > I can play around with adding thicker borders, but I'll have to adjust > > the widths of all the relevant divs and edit a few images. I can do > > this, but I'm a little pressed for time at the moment and would hate for > > this to stagnate any more than it has already. > > > > Cheers, > > > > Josh > > > > > > Sean DALY wrote: > >> Yes, much better integration with the rest of the site sections > >> > >> thanks Josh > >> > >> Sean > >> > >> > >> > >> On Fri, Jun 5, 2009 at 3:25 PM, David Farning > wrote: > >> > >>> Hey, > >>> > >>> That is awesome! > >>> > >>> david > >>> > >>> On Fri, Jun 5, 2009 at 12:23 AM, Josh Williams > wrote: > >>> > Hi everyone, > > I've been working on the css for ASLO, you can see where I'm at > http://activities-devel.sugarlabs.org/en-US/sugar/ . I've tried to > make > this fairly consistent with the design of sugarlabs.org. > > If any developers would be kind enough to upload some activities it > would help with checking for inconsistencies it would be greatly > appreciated. > > I'd like to push this to the live site in the near future, so please > let > me know what you think. > > Cheers, > > Josh > > > ___ > IAEP -- It's An Education Project (not a laptop project!) > i...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep > > > >>> ___ > >>> Marketing mailing list > >>> market...@lists.sugarlabs.org > >>> http://lists.sugarlabs.org/listinfo/marketing > >>> > >>> > > > > ___ > > IAEP -- It's An Education Project (not a laptop project!) > > i...@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/iaep > > > ___ > IAEP -- It's An Education Project (not a laptop project!) > i...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] cool animation w/ all-javascript space invaders
>create an Audio object that uses flash or >plugin media players in the background for backwards compatibility Yes, that's right. Since it exists "new Image()" new Audio() seems familiar. Thanks for your advise. 2009/6/4 Lucian Branescu > For sound, you'll either have to find a wrapper that can use both > and flash or use (or more precisely use it with > scripting, new Audio()) and create an Audio object that uses flash or > plugin media players in the background for backwards compatibility > (which can use soundmanager or whatever else you like). > > 2009/6/4 Felipe López Toledo : > > nice example > > > > it has a tween.js with easing equations - excellent > > > > about the sounds (here is the tricky part) > > it uses soundmanager2 http://www.schillmania.com/projects/soundmanager2/ > > really really usefulbut it depends on a swf file (soundmanager2.swf) > in > > the background.. so, if you don't have the flash plugin the sounds don't > > work :( > > > > here is more information about the flash based solution > > http://www.boutell.com/newfaq/creating/scriptsound.html > > > > there is also other flash audio wrappers > > like JS Sound Kit http://jssoundkit.sourceforge.net/ > > > > also, I found a (ugly) java applet solution :S > > > > and jQuery has its own sound plugin > http://plugins.jquery.com/project/sound > > that was useless > > > > so > > > > why not to use ? > > > > here it is :) http://karma.sugarlabs.org/can_cant/ > > btw It's simpler than the others > > > > > > 2009/6/3 Lucian Branescu > >> > >> Very interesting, especially because of its browser support. > >> > >> 2009/6/3 Bryan Berry : > >> > http://static.boundvariable.com/space-invaders/ > >> > > >> > does most of the animation that we need using raphaeljs, which uses > svg > >> > and not canvas http://www.raphaeljs.com > >> > > >> > -- > >> > Bryan W. Berry > >> > Technology Director > >> > OLE Nepal, http://www.olenepal.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] [math4] Activity Awards, Activity Alerts, Frame Alerts
On Fri, Jun 5, 2009 at 6:32 PM, Gary C Martin wrote:
...
FWIW, David Van Assche raised some interesting Activity ideas at
> SugarCamp Paris and I'm interested/active in getting us to at lease
> 'demo' state in the Sugar 0.86 release timeframe. The idea is to focus
> on an 'awards' mechanism/style to encourage exploration and provide
> (sometimes) unexpected rewards. Idea is that Activity authors can
> define a range of badges/medals/icons for certain behaviours/
> accomplishment in an attempt to get students to dig deeper (mix of
> 'easter eggs' and specific goals). It's mainly Activity side work (a
> demo activity to start with) but perhaps could find a home in the
> Journal (through an ability of Activity to set some private entry tag
> and for Journal to display that in a user appealing graphical form).
>
> Even for something as hard to measure as the Write Activity, there
> could be 'awards' (hidden or hinted at) for things like "found 10 or
> more collaborators for one document", "gained at least 100 words each
> from 5 or more collaborators", "wrote more than 1,000 words", "you
> used the word entomology!". The idea is many would be hidden
> ("surprise, you did something cool!") and that some initial more
> obvious and visible 'awards' would hint that others were there for
> discovery.
>
> Regards,
> --Gary
>
> P.S. Mechanisms for 'awards' could hook into services like Moodle, the
> Journal, or via collaboration (so perhaps a shared Write session would
> show awards gained by the collaborators). Having a view to show all
> Activity Awards would also be a good driver (could be an activity, or
> ideally at some point part of Journal). The general idea for awards
> drifts in from the gaming environment, where awards are used to
> increase re-playability and tempt folks to try some other possible path.
>
...
Nice concept.
Some design and code integration with Activity Alerts,
http://wiki.sugarlabs.org/go/Development_Team/Almanac/sugar.graphics.alert,
and Frame alerts,
http://wiki.sugarlabs.org/go/Design_Team/Designs/Frame#12
, http://wiki.sugarlabs.org/go/Design_Team/Designs/Frame#13, etc. may be
appropriate.
http://dev.sugarlabs.org/ticket/722 has some discussion. I would like to
see more noticeable messages for chat invitation alerts, for example. Don't
know where this is recorded for the Sugar 0.86 roadmap,
http://wiki.sugarlabs.org/go/Development_Team/Release/Roadmap/0.86#Proposal_Goals
?
The software infrastructure you propose could also be used for random or
rule-based, single-point lesson reminders or reinforcers of learning.
--Fred
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] More information on font scaling problem
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Fri, Jun 05, 2009 at 03:42:05PM -0500, James Simmons wrote: >Maybe sugar-emulator *is* providing SUGAR_SCALING but instead of 100 it >is using 72? I believe it does. You should be able to look for yourself with "cat /usr/bin/sugar-emulator" (or whereever sugar-emulator is located on your system). - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkopmoQACgkQn7DbMsAkQLgEqgCfU4M1BpTTObLS9oqK4KnOv2ST 8oQAnjG9r8q2hWS8h0AulAVH4SfYtI9c =HlVm -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal activity release 101 not tagged in Git
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Fri, Jun 05, 2009 at 04:37:32PM -0400, Frederick Grose wrote: >You are already on it by virtue of your work and contributions. Please >edit http://wiki.sugarlabs.org/go/Packaging_Team and its pending >links/subpages as appropriate. Ok. I'll look into that. Later - I am on my way to bed now (spent all of last night finalizing a major ghostscript packaging update). >Thank you for contributing so much already! --Fred Ah, well - my work is just silently absorbed by Ubuntu, and the core 0.84 packages that I finally got packaged last week does not work at all. Segmentation fault somewhere initially if using Xephyr, and if cheating and first running sugar non-emulated (just to create the initial account), activities won't start - no debug log messages, no nothing. Oh well. I should sleep now :-/ - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkopmf0ACgkQn7DbMsAkQLjW7wCeIwpGdpEagK0q7Z/9TJxYLFUd Xr0AoIG/iRZ565cKBPCW7MEzJl+IBMOT =r9Fi -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] More information on font scaling problem
Gary, Thanks for doing this. I wish I could say it cleared things up but I feel more confused than before. You say these are both XO's with different versions of Sugar. I thought that the font behavior on the XO was consistent, no matter what version of Sugar you used, but that you needed to use the SUGAR_SCALING environment variable in other places to make the fonts look OK. That doesn't make sense because the zoom factor should be 72, meaning that any font number you put in would be multiplied by .72 and truncated to the next lowest integer. Which is just the opposite of what you'd want to do, because it's the XO that has the font too big, not my development environment or SoaS. Even the .84 one doesn't look right to me. When I run sugar-emulator on Fedora 10 the font looks *much* smaller than that. Maybe sugar-emulator *is* providing SUGAR_SCALING but instead of 100 it is using 72? James Simmons Gary C Martin wrote: > Hi James, > > On 5 Jun 2009, at 10:16, Tomeu Vizoso wrote: > >> On Wed, Jun 3, 2009 at 16:40, James >> Simmons wrote: >>> I mentioned before that I'm having a font sizing problem on the XO >>> running .82. When I set a font on a textviewer it looks OK running >>> under sugar-devel or SoaS by is *much* larger on the XO. >> >> Sorry, in an earlier email i replied to you what would work in 0.84, >> didn't realized you were talking about 0.82. >> >> In 0.84 Pango knows the resolution of the screen and scales all fonts >> accordingly. This means that by using, say 10, the font will always >> look good in all hw. >> >> In 0.82 didn't knew about the screen, so we were scaling all fonts by >> using style.zoom(). > > Not sure if you have easy access to both Sugar 0.82 (larger text) and > 0.84 (smaller text) on an XO-1 for testing, so I've just grabbed a > screenshot from each showing ReadETexts-12 so at least you have > examples of your current release behaviour. > > Regards, > --Gary > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal activity release 101 not tagged in Git
You are already on it by virtue of your work and contributions. Please edit http://wiki.sugarlabs.org/go/Packaging_Team and its pending links/subpages as appropriate. Thank you for contributing so much already! --Fred On Fri, Jun 5, 2009 at 4:26 PM, Jonas Smedegaard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: RIPEMD160 > > On Fri, Jun 05, 2009 at 01:22:03PM -0500, David Farning wrote: > >The biggest value of a packaging team in my mind is to insure that > >packagers and distributions have a well defined voice in the > >ecosystem. > > >Our challenge over the next year will be to determine how to scale > >Sugar Labs _fairly_ build on the interests, contributions, and needs > >of the various stakeholders. > > Ok, convinced. > > Where do I sign up for that team? > > > - Jonas > > - -- > * Jonas Smedegaard - idealist og Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEAREDAAYFAkopf4wACgkQn7DbMsAkQLjVgQCcDM5p+x3jHw/Plqr2B5tJzz/a > TIQAnAw4UVSQwISQ7bPUjAhP4lXqNt3g > =RHt/ > -END PGP SIGNATURE- > ___ > 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] [IAEP] collaboration testing session
http://wiki.laptop.org/go/Collaboration_Central could be upgraded or migrated as a summary page or session report. --Fred On Fri, Jun 5, 2009 at 4:19 PM, James Simmons wrote: > David, > > Four of the Activities you will be testing use pretty much the same code > for collaboration: > > sugar-read > sugar-readetexts-activity > sugar-viewslides > sugar-imageviewer > > Read Etexts and View Slides use code copied from Read. Image Viewer > says in its comments that it uses code copied from Read Etexts. All > four basically just let you make a copy of the document that is being > shared. Read is different from the rest because (the last time I > looked) it did not save a copy of the shared document in the Journal. > The rest do. > > Another difference with Read is that it uses meta data in the PDF to > give a title to the Journal entry that is sharing the document. Read > Etexts and View Slides don't have any meta data in their documents, so > documents received from others are given the titles "Read Etexts" or > "View Slides". In the Neighborhood view the names of the documents > offered for sharing are clearly visible, so you'd think there would be > *some* way of getting that information from the sharing Activity so you > could update the Title in the Journal but I haven't figured out how to > do it. > > View Slides displays a crude count "n of n bytes total" when it > downloads a file and this seems to work. When I put exactly the same > code in Read Etexts it only displayed the final count, not the count in > progress. Read Etexts uses multi threading when TTS is installed, and > maybe that is related to the reason. > > Transfer of large files is *very* slow. > > Hope this information is of some use. > > James Simmons > > > ___ > 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] Journal activity release 101 not tagged in Git
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Fri, Jun 05, 2009 at 01:22:03PM -0500, David Farning wrote: >The biggest value of a packaging team in my mind is to insure that >packagers and distributions have a well defined voice in the >ecosystem. >Our challenge over the next year will be to determine how to scale >Sugar Labs _fairly_ build on the interests, contributions, and needs >of the various stakeholders. Ok, convinced. Where do I sign up for that team? - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkopf4wACgkQn7DbMsAkQLjVgQCcDM5p+x3jHw/Plqr2B5tJzz/a TIQAnAw4UVSQwISQ7bPUjAhP4lXqNt3g =RHt/ -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] collaboration testing session
David, Four of the Activities you will be testing use pretty much the same code for collaboration: sugar-read sugar-readetexts-activity sugar-viewslides sugar-imageviewer Read Etexts and View Slides use code copied from Read. Image Viewer says in its comments that it uses code copied from Read Etexts. All four basically just let you make a copy of the document that is being shared. Read is different from the rest because (the last time I looked) it did not save a copy of the shared document in the Journal. The rest do. Another difference with Read is that it uses meta data in the PDF to give a title to the Journal entry that is sharing the document. Read Etexts and View Slides don't have any meta data in their documents, so documents received from others are given the titles "Read Etexts" or "View Slides". In the Neighborhood view the names of the documents offered for sharing are clearly visible, so you'd think there would be *some* way of getting that information from the sharing Activity so you could update the Title in the Journal but I haven't figured out how to do it. View Slides displays a crude count "n of n bytes total" when it downloads a file and this seems to work. When I put exactly the same code in Read Etexts it only displayed the final count, not the count in progress. Read Etexts uses multi threading when TTS is installed, and maybe that is related to the reason. Transfer of large files is *very* slow. Hope this information is of some use. James Simmons ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [RELEASE] Library-1
I installed again on a more recent snapshot and its working fine! On Mon, Jun 1, 2009 at 11:57 PM, Aleksey Lim wrote: > On Mon, Jun 01, 2009 at 03:48:04PM -0400, Caroline Meeks wrote: > > Or to be more specific. I see the UI but none of the things that are in > my > > Journal, which is what I think I expect to see. > > could you post Library logs(with debug level enabled) > > > > > On Mon, Jun 1, 2009 at 3:47 PM, Caroline Meeks >wrote: > > > > > I have installed in to SoaS recent snapshot. Installs fine but I don't > see > > > anything when I open it. > > > > > > > > > On Mon, Jun 1, 2009 at 5:39 AM, Aleksey Lim >wrote: > > > > > >> Hi all, > > >> > > >> This is in initial release of Library activity. I decided to release > it > > >> before implementing collab features to get some feedback about UI and > > >> basic > > >> ideas of activity. So, it can browse only local objects. > > >> > > >> == Bundle == > > >> > > >> http://activities.sugarlabs.org/en-US/sugar/addon/4089 > > >> > > >> == NEWS == > > >> > > >> * Add filter to ObjectChooser invoking > > >> * Browse local objects > > >> > > >> == TODO fot v2 == > > >> > > >> * Run in 0.82 environment > > >> * Implement collab features > > >> > > >> -- > > >> Aleksey > > >> ___ > > >> Sugar-devel mailing list > > >> Sugar-devel@lists.sugarlabs.org > > >> http://lists.sugarlabs.org/listinfo/sugar-devel > > >> > > > > > > > > > > > > -- > > > Caroline Meeks > > > Solution Grove > > > carol...@solutiongrove.com > > > > > > 617-500-3488 - Office > > > 505-213-3268 - Fax > > > > > > > > > > > -- > > Caroline Meeks > > Solution Grove > > carol...@solutiongrove.com > > > > 617-500-3488 - Office > > 505-213-3268 - Fax > > -- > Aleksey > -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] [Marketing] ASLO - rebranding
On Fri, Jun 5, 2009 at 21:29, Josh Williams wrote: > Thanks everyone, > > Gary mentioned > > "Hey, fab, looking much cleaner/simpler/Sugar-like :-) One quick > thought (will try to take a closer look later), would double > thickness borders work better, make the colour theme pop a little > more, feel more robust? > > Regards, > --Gary " > > > I agree that adding two or three pixels to the borders would help the > design. However, if there aren't any major objections to the design, I > think we should push it to the live ASLO, and make minor changes later. > Any thoughts on this? +1 on this. And thanks a lot for your awesome work. Looking forward for more! Regards, Tomeu > I can play around with adding thicker borders, but I'll have to adjust > the widths of all the relevant divs and edit a few images. I can do > this, but I'm a little pressed for time at the moment and would hate for > this to stagnate any more than it has already. > > Cheers, > > Josh > > > Sean DALY wrote: >> Yes, much better integration with the rest of the site sections >> >> thanks Josh >> >> Sean >> >> >> >> On Fri, Jun 5, 2009 at 3:25 PM, David Farning wrote: >> >>> Hey, >>> >>> That is awesome! >>> >>> david >>> >>> On Fri, Jun 5, 2009 at 12:23 AM, Josh Williams wrote: >>> Hi everyone, I've been working on the css for ASLO, you can see where I'm at http://activities-devel.sugarlabs.org/en-US/sugar/ . I've tried to make this fairly consistent with the design of sugarlabs.org. If any developers would be kind enough to upload some activities it would help with checking for inconsistencies it would be greatly appreciated. I'd like to push this to the live site in the near future, so please let me know what you think. Cheers, Josh ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep >>> ___ >>> Marketing mailing list >>> market...@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/marketing >>> >>> > > ___ > IAEP -- It's An Education Project (not a laptop project!) > i...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Marketing] [IAEP] ASLO - rebranding
Thanks everyone, Gary mentioned "Hey, fab, looking much cleaner/simpler/Sugar-like :-) One quick thought (will try to take a closer look later), would double thickness borders work better, make the colour theme pop a little more, feel more robust? Regards, --Gary " I agree that adding two or three pixels to the borders would help the design. However, if there aren't any major objections to the design, I think we should push it to the live ASLO, and make minor changes later. Any thoughts on this? I can play around with adding thicker borders, but I'll have to adjust the widths of all the relevant divs and edit a few images. I can do this, but I'm a little pressed for time at the moment and would hate for this to stagnate any more than it has already. Cheers, Josh Sean DALY wrote: > Yes, much better integration with the rest of the site sections > > thanks Josh > > Sean > > > > On Fri, Jun 5, 2009 at 3:25 PM, David Farning wrote: > >> Hey, >> >> That is awesome! >> >> david >> >> On Fri, Jun 5, 2009 at 12:23 AM, Josh Williams wrote: >> >>> Hi everyone, >>> >>> I've been working on the css for ASLO, you can see where I'm at >>> http://activities-devel.sugarlabs.org/en-US/sugar/ . I've tried to make >>> this fairly consistent with the design of sugarlabs.org. >>> >>> If any developers would be kind enough to upload some activities it >>> would help with checking for inconsistencies it would be greatly >>> appreciated. >>> >>> I'd like to push this to the live site in the near future, so please let >>> me know what you think. >>> >>> Cheers, >>> >>> Josh >>> >>> >>> ___ >>> IAEP -- It's An Education Project (not a laptop project!) >>> i...@lists.sugarlabs.org >>> http://lists.sugarlabs.org/listinfo/iaep >>> >>> >> ___ >> Marketing mailing list >> market...@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/marketing >> >> ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Using Trac via email
On Fri, Jun 05, 2009 at 08:23:09PM +0200, Jonas Smedegaard wrote: Oh, and enabling SSL would be appreciated too. IIRC we've discussed this on IRC and it isn't possible because we're on a shared host (mod_gnutls too unstable, openssl has no SNI support, no CA issues a combined certificate for domains owned by different individuals). The only solution would be a separate IPv4 address and I guess there's none available. Bernie, do you know if there's a chance to get IPv6 on solarsail? That way we could at least offer https via IPv6. I sure would prefer an offline interface. But CLI-based online interface is better than (as only option) online web access. Of course. CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Using Trac via email
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Fri, Jun 05, 2009 at 05:14:08PM +0200, Sascha Silbe wrote: > On Fri, Jun 05, 2009 at 04:14:01PM +0200, Jonas Smedegaard wrote: > >> So if Trac generically had some client-server ABI that I could expect >> would be available at many other Trac installations, > There's an XML-RPC plugin [1] that seems to be complete enough (though > potentially buggy) for regular bug juggling. A very minimal XML-RPC > based client [2] provides interactive CLI access. Great! Could someone with admin access please enable XML-RPC access? Or is that somehow a concern to do? It seems the server plugin is stable, only the CLI client is in alpha state. Oh, and enabling SSL would be appreciated too. Yes, it _is_ possible to host multiple secure websites, despite the warnings emitted by Apache2! I'd be happy to provide the necessary info if someone is interested. > Note: I have not tried out any of these yet as I'm more interested in > an asynchronous (i.e. email based) interface. I sure would prefer an offline interface. But CLI-based online interface is better than (as only option) online web access. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkopYo0ACgkQn7DbMsAkQLgjjACgqLW/afK1n1LBDHtzc0XIPGo8 kagAni7qULgrf7CFsTwf948LOYI3mlvF =zm9m -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal activity release 101 not tagged in Git
On Fri, Jun 5, 2009 at 12:43 PM, Jonas Smedegaard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: RIPEMD160 > > On Fri, Jun 05, 2009 at 10:59:46AM -0400, Frederick Grose wrote: >>David Van Assche surfaced the idea here, >>http://www.mail-archive.com/i...@lists.sugarlabs.org/msg04259.html, >>with some recognition of the proposal. >> >>There seems to be a de-facto team at work already. Here is a wiki home >>to start furnishing, http://wiki.sugarlabs.org/go/Packaging_Team. > > Yep, I noticed that mail. And that was my reason for asking the scope > imagined for such a team. > > It seems to me that above referenced initiative is for Sugarlabs > offering prebuilt distro-compatible packages (why else the need for a > build service?). > > Please correct me if I am wrong. The biggest value of a packaging team in my mind is to insure that packagers and distributions have a well defined voice in the ecosystem. Sugar Labs is in a weird, and somewhat complicated place. Our end users are students and teachers. Our purchasers are school districts, government agencies and NGOs. But Sugar is only useful when well packaged by a distribution and delivered on a piece of hardware. This mean _lots_ of stake holders with sometime competitive, sometime collaborative, and sometimes conflicting interests. Our challenge over the next year will be to determine how to scale Sugar Labs _fairly_ build on the interests, contributions, and needs of the various stakeholders. david > - Jonas > > - -- > * Jonas Smedegaard - idealist og Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEUEAREDAAYFAkopWToACgkQn7DbMsAkQLh/TgCghp6jx59pFsR+TVdupV+921EZ > X6oAl34r2FWGsSVvq5tGTgX0ZOa2i0U= > =pIbZ > -END PGP SIGNATURE- > ___ > 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] Journal activity release 101 not tagged in Git
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Fri, Jun 05, 2009 at 10:59:46AM -0400, Frederick Grose wrote: >David Van Assche surfaced the idea here, >http://www.mail-archive.com/i...@lists.sugarlabs.org/msg04259.html, >with some recognition of the proposal. > >There seems to be a de-facto team at work already. Here is a wiki home >to start furnishing, http://wiki.sugarlabs.org/go/Packaging_Team. Yep, I noticed that mail. And that was my reason for asking the scope imagined for such a team. It seems to me that above referenced initiative is for Sugarlabs offering prebuilt distro-compatible packages (why else the need for a build service?). Please correct me if I am wrong. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEUEAREDAAYFAkopWToACgkQn7DbMsAkQLh/TgCghp6jx59pFsR+TVdupV+921EZ X6oAl34r2FWGsSVvq5tGTgX0ZOa2i0U= =pIbZ -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] More information on font scaling problem
On Fri, Jun 5, 2009 at 18:40, James Simmons wrote: > Tomeu, > > Isn't it just the opposite of what you wrote? My reading of the code > suggests that the SUGAR_SCALING environment variable was for everywhere BUT > the XO: > > http://api.sugarlabs.org/sugar.graphics.style-pysrc.html I think you are right, SUGAR_SCALING is set to 100 on machines with high resolution (such as the XO) and that's the default as well if it isn't set. We do this in Soas: http://git.sugarlabs.org/projects/soas/repos/mainline/blobs/master/soas-sugar.ks#line113 Anyway, the idea is that whatever value you find that looks good on the XO with 0.82, if you use style.zoom(), then it will look fine on other machines with Sugar 0.82 provided SUGAR_SCALING is correctly set. For the text to look fine in 0.84, you need to use a fixed, absolute value around 10. Regards, Tomeu > James Simmons > > > Tomeu Vizoso wrote: >> >> On Fri, Jun 5, 2009 at 17:32, James Simmons >> wrote: >> Oh, I understand now. Yeah, the SUGAR_SCALING env var was only used in >> the XO. On non-XOs it wasn't supposed to be needed, but may not be the >> case in some screens. > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] sugar-jhbuild - could not connect to server (http://svn.o-hand.com)
Sascha Silbe writes: > What distribution and what kernel version do you run? You might be > affected by Debian bug #531338 [1] / Fedora bug #491839 [2]. > > [1] http://bugs.debian.org/531338 That was it. Many thanks, -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ASLO - rebranding
Josh, I attempted to upload Read Etexts to your site. The upload seemed to go OK but there is no Activity found yet. Maybe it needs to be promoted from the sandbox? James Simmons Date: Thu, 04 Jun 2009 22:23:34 -0700 From: Josh Williams Subject: [Sugar-devel] ASLO - rebranding To: Sugar Devel Cc: iaep ,Sugar Labs Marketing Message-ID: <4a28abd6.2020...@tucson-labs.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi everyone, I've been working on the css for ASLO, you can see where I'm at http://activities-devel.sugarlabs.org/en-US/sugar/ . I've tried to make this fairly consistent with the design of sugarlabs.org. If any developers would be kind enough to upload some activities it would help with checking for inconsistencies it would be greatly appreciated. I'd like to push this to the live site in the near future, so please let me know what you think. Cheers, Josh ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] More information on font scaling problem
Tomeu, Isn't it just the opposite of what you wrote? My reading of the code suggests that the SUGAR_SCALING environment variable was for everywhere BUT the XO: http://api.sugarlabs.org/sugar.graphics.style-pysrc.html James Simmons Tomeu Vizoso wrote: > On Fri, Jun 5, 2009 at 17:32, James Simmons wrote: > > Oh, I understand now. Yeah, the SUGAR_SCALING env var was only used in > the XO. On non-XOs it wasn't supposed to be needed, but may not be the > case in some screens. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] sugar-jhbuild - could not connect to server (http://svn.o-hand.com)
On Fri, Jun 05, 2009 at 06:12:46PM +0200, Bastien wrote: | *** Checking out matchbox-window-manager *** [18/43] | svn checkout http://svn.o-hand.com/repos/matchbox/trunk/matchbox-window-manager matchbox-window-manager | svn: OPTIONS of 'http://svn.o-hand.com/repos/matchbox/trunk/matchbox-window-manager': could not connect to server (http://svn.o-hand.com) What distribution and what kernel version do you run? You might be affected by Debian bug #531338 [1] / Fedora bug #491839 [2]. [1] http://bugs.debian.org/531338 [2] https://bugzilla.redhat.com/show_bug.cgi?id=491839 CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] collaboration testing session
>Is there a wiki page to sign up and coordinate, or what's the procedure? >- Bert - http://wiki.sugarlabs.org/go/Collaboration_Testing is available for event references, documentation, etc. It is transcluded for now at http://wiki.sugarlabs.org/go/BugSquad/Meetings --Fred ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] sugar-jhbuild - could not connect to server (http://svn.o-hand.com)
On Fri, Jun 5, 2009 at 18:12, Bastien wrote: > Hi all, > > I can't check out sugar-jhbuild right now: > > , > | *** Checking out matchbox-window-manager *** [18/43] > | svn checkout > http://svn.o-hand.com/repos/matchbox/trunk/matchbox-window-manager > matchbox-window-manager > | svn: OPTIONS of > 'http://svn.o-hand.com/repos/matchbox/trunk/matchbox-window-manager': could > not connect to server (http://svn.o-hand.com) > | *** error during phase checkout of matchbox-window-manager: ## > Error running svn checkout > http://svn.o-hand.com/repos/matchbox/trunk/matchbox-window-manager > matchbox-window-manager *** [18/43] > ` > > is this just a temporary problem with http://svn.o-hand.com? > > Also, I got this error when building sugar-jhbuild on a fresh debian > testing machine: > > , > | FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; > fixing. > | sugar: ERROR: Gtk theme for scaling 72 not available in path > /home/guerry/sugar-jhbuild/install/share/sugar/data/sugar-72.gtkrc > ` > > Looks like the first error is not related to sugar and does not hurt. > The second error prevents the sugar emulation to run. > > Any idea? Maybe sugar-artwork didn't built completely? To check just run make install in sugar-artwork. Regards, Tomeu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] sugar-jhbuild - could not connect to server (http://svn.o-hand.com)
Hi all, I can't check out sugar-jhbuild right now: , | *** Checking out matchbox-window-manager *** [18/43] | svn checkout http://svn.o-hand.com/repos/matchbox/trunk/matchbox-window-manager matchbox-window-manager | svn: OPTIONS of 'http://svn.o-hand.com/repos/matchbox/trunk/matchbox-window-manager': could not connect to server (http://svn.o-hand.com) | *** error during phase checkout of matchbox-window-manager: ## Error running svn checkout http://svn.o-hand.com/repos/matchbox/trunk/matchbox-window-manager matchbox-window-manager *** [18/43] ` is this just a temporary problem with http://svn.o-hand.com? Also, I got this error when building sugar-jhbuild on a fresh debian testing machine: , | FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing. | sugar: ERROR: Gtk theme for scaling 72 not available in path /home/guerry/sugar-jhbuild/install/share/sugar/data/sugar-72.gtkrc ` Looks like the first error is not related to sugar and does not hurt. The second error prevents the sugar emulation to run. Any idea? -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] More information on font scaling problem
On Fri, Jun 5, 2009 at 17:32, James Simmons wrote: > Tomeu, > > I think I figured this out by looking at the code for sugar.graphics.style. > It looks like my Sugar test environment needs to have an environment > variable SUGAR_SCALING defined and it needs to be given a numeric value. If > I *don't* have such a variable then the measurements are suited for an XO. > If I *do* have one than the numeric value assigned to SUGAR_SCALING is > multiplied by my specified font size to get a larger font that looks good on > sugar-emulator. > > I'm guessing that Fedora 10 does not provide this environment variable. So > the question is, what value would I specify for this environment variable if > I specified it? Oh, I understand now. Yeah, the SUGAR_SCALING env var was only used in the XO. On non-XOs it wasn't supposed to be needed, but may not be the case in some screens. > Now on SoaS, which should be .84, I'm seeing the same font issue I had with > sugar-emulator in Fedora 10. Not only my app has a font which is much too > small, but Develop has a *really* small font for displaying code, whereas > the fonts in the rest of the app (where they likely used the default) look > fine. I'm not using the very latest SoaS but the one I have is only a few > weeks old. Can you try again with the last one? It contains a bugfix related to that. Thanks, Tomeu > James Simmons > > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] More information on font scaling problem
Tomeu, I think I figured this out by looking at the code for sugar.graphics.style. It looks like my Sugar test environment needs to have an environment variable SUGAR_SCALING defined and it needs to be given a numeric value. If I *don't* have such a variable then the measurements are suited for an XO. If I *do* have one than the numeric value assigned to SUGAR_SCALING is multiplied by my specified font size to get a larger font that looks good on sugar-emulator. I'm guessing that Fedora 10 does not provide this environment variable. So the question is, what value would I specify for this environment variable if I specified it? Now on SoaS, which should be .84, I'm seeing the same font issue I had with sugar-emulator in Fedora 10. Not only my app has a font which is much too small, but Develop has a *really* small font for displaying code, whereas the fonts in the rest of the app (where they likely used the default) look fine. I'm not using the very latest SoaS but the one I have is only a few weeks old. James Simmons ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] collaboration testing session
Yeah as stated, we will use the default jabber server which is the solutions grove one I guess... or are u talking about another one? David On Fri, Jun 5, 2009 at 4:38 PM, David Farning wrote: > David, > > Can you try to use the Solutions Groovy jabber server? Caroline and > Dave are putting some very helpful resources behind cleaning up the > server. > > david(The other one) > > On Fri, Jun 5, 2009 at 7:37 AM, Caroline Meeks > wrote: > > Hi David, > > > > Will you be using the server hosted by Solution Grove/Zill? We would be > > very happy if you did. > > > > We have seen mysterious spikes in resource usage that is not correlated > to > > the number of users connected. I am suspicious that some of the > activities > > use too many resources when they are shared. I'd like to set it up so > that > > someone on your team has access to what is going on on the server so you > can > > try to correlate any spikes to specific activities. > > > > Thanks, > > Caroline > > > > On Fri, Jun 5, 2009 at 12:09 AM, David Van Assche > > wrote: > >> > >> Hi folks, > >>We are having a collaborative sugar testing session next week > Wednesday > >> 10th June at 20:00 UTC (That is 4 pm EDT, 3pm EST, 2 pm CST, 1 pm MST, > and > >> 12 pm PST, most of Europe that will be 9 pm, 8 pm for the UK) > >> > >> So far we have 5 people signed up, but more are welcome as we really > want > >> to see how collaboration works on many activities where it isn't quite > >> obvious. We will be taking notes and storing log files of the sessions, > and > >> will suggest ways in which the activity in question might be more > >> collaborative, or may need less of it (who knows :-) > >> > >> We will be testing the activities that come preinstalled on the openSUSE > >> sugar images, but we'd like to test various distribution methods > (virtual > >> appliance, cd, usb, hd) and various distros (at least Fedora SoaS, > openSUSE > >> sugar, Mandriva or Caixa Magica) I dont believe 0.82 images are > compatible > >> with 0.84 for collaboration, so am afraid this is for 0.84 only... > Please > >> post your willingness to participate so we have an idea on who/how many > will > >> be collaborating. We also need a volunteer to take notes, and a > volunteer to > >> store logs files. There will of course be a transcript of the irc > session > >> too (we will meet at #sugar-collaboration) We forsee this taking between > 1 > >> and 2 hours... > >> > >> Here is the list of activities we will be testing, so make sure you have > >> them installed if you plan to take part (not all have collaborative > >> abilities, and for those that don't it can be a brainstorming session on > >> whether/how we can make them collaborative: > >> > >> sugar-finance > >> sugar-flipsticks-activity > >> sugar-freecell > >> sugar-imageviewer > >> sugar-implode > >> sugar-infoslicer > >> sugar-jigsaw-puzzle-activity > >> sugar-joke-machine-activity > >> sugar-jukebox > >> sugar-labyrinth > >> sugar-maze > >> sugar-memorize > >> sugar-moon > >> sugar-paint-activity > >> sugar-pippy > >> sugar-playgo > >> sugar-read > >> sugar-readetexts-activity > >> sugar-record > >> sugar-slider-puzzle-activity > >> sugar-speak > >> sugar-storybuilder > >> sugar-tamtam-common > >> sugar-tamtam-edit > >> sugar-tamtam-jam > >> sugar-tamtam-mini > >> sugar-tamtam-synthlab > >> sugar-analyze > >> sugar-turtleart > >> sugar-typing-turtle > >> sugar-viewslides > >> sugar-write > >> sugar-browse > >> sugar-irc > >> sugar-calculate > >> sugar-xomail (sugar-sweetmail) > >> sugar-cartoonbuilder > >> sugar-clock > >> sugar-colors > >> sugar-connect > >> sugar-drgeo-activity > >> xoEditor > >> sugar-evince > >> sugar-fiftytwo > >> sugar-chat > >> sugar-terminal > >> sugar-journal > >> sugar-physics > >> sugar-library > >> sugar-poll > >> sugar-tuxpaint > >> > >> kind Regards, > >> David (nubae) Van Assche > >> www.nubae.com > >> > >> > >> ___ > >> IAEP -- It's An Education Project (not a laptop project!) > >> i...@lists.sugarlabs.org > >> http://lists.sugarlabs.org/listinfo/iaep > > > > > > > > -- > > Caroline Meeks > > Solution Grove > > carol...@solutiongrove.com > > > > 617-500-3488 - Office > > 505-213-3268 - Fax > > > > ___ > > 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] More information on font scaling problem
On Fri, Jun 5, 2009 at 17:11, James Simmons wrote:
> Tomeu,
>
> The thing is, in the code below I *am* using style.zoom. It seems to have
> no effect at all.
What I would have supposed that would work is using in 0.84 a fixed
font size of 10 and on the XO style.zoom(X). I didn't wanted to imply
that X could be 10, I think we were using a smaller font size in the
Sugar UI.
Maybe Aleksey could add a zoom() function to sugar.port that on 0.82
would do some scaling based on the screen resolution and on 0.84 would
return the value unchanged?
Regards,
Tomeu
> My test environment on Fedora 10 is .82. My XO, running the latest (I
> believe) release candidate of Sugar is .82. Most of the XO's that might use
> Read Etexts will be running .82 or worse and will not be eager to upgrade.
> For that reason I'm trying to make my Activity work around the limitations
> of older versions of Sugar. As an example, .82 still has the bug that
> custom metadata is not saved across reboots. I was using a custom metadata
> field to store the page number that the user stopped reading on. In my
> latest this page number is saved at the end of the Title of the Journal
> entry, like this:
>
> Off on a Comet! by Jules Verne P64
>
> Aleksey and I also put in code that suppresses the Speech tab when neither
> speech-dispatcher nor the gstreamer plugin for espeak is installed.
>
> James Simmons
>
>
> Tomeu Vizoso wrote:
>
> On Wed, Jun 3, 2009 at 16:40, James Simmons
> wrote:
>
>
> I mentioned before that I'm having a font sizing problem on the XO
> running .82. When I set a font on a textviewer it looks OK running
> under sugar-devel or SoaS by is *much* larger on the XO.
>
>
> Sorry, in an earlier email i replied to you what would work in 0.84,
> didn't realized you were talking about 0.82.
>
> In 0.84 Pango knows the resolution of the screen and scales all fonts
> accordingly. This means that by using, say 10, the font will always
> look good in all hw.
>
> In 0.82 didn't knew about the screen, so we were scaling all fonts by
> using style.zoom().
>
> Aleksey, do you have an idea about what can do activity authors that
> wish to provide a single bundle that looks good both in 0.82 and 0.84?
>
> Thanks,
>
> Tomeu
>
>
>
> This is the
> code I'm currently using:
>
> self.scrolled = gtk.ScrolledWindow()
> self.scrolled.set_policy(gtk.POLICY_NEVER, gtk.POLICY_AUTOMATIC)
> self.scrolled.props.shadow_type = gtk.SHADOW_NONE
> self.textview = gtk.TextView()
> self.textview.set_editable(False)
> self.textview.set_cursor_visible(False)
> self.textview.set_left_margin(50)
> self.textview.connect("key_press_event", self.keypress_cb)
> buffer = self.textview.get_buffer()
> buffer.connect("mark-set", self.mark_set_cb)
> self.font_desc = pango.FontDescription("sans %d" % style.zoom(10))
> self.textview.modify_font(self.font_desc)
> self.scrolled.add(self.textview)
> self.textview.show()
> self.scrolled.show()
> v_adjustment = self.scrolled.get_vadjustment()
> self.clipboard = gtk.Clipboard(display=gtk.gdk.display_get_default(),
> selection="CLIPBOARD")
> self.page = 0
> self.textview.grab_focus()
>
> The "sans 10" font is really too small for SoaS but on the XO it makes
> 80 columns of text fill the width of the screen. Any ideas?
>
> James Simmons
>
>
>
>
> ___
> 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] Using Trac via email
On Fri, Jun 05, 2009 at 04:14:01PM +0200, Jonas Smedegaard wrote: So if Trac generically had some client-server ABI that I could expect would be available at many other Trac installations, There's an XML-RPC plugin [1] that seems to be complete enough (though potentially buggy) for regular bug juggling. A very minimal XML-RPC based client [2] provides interactive CLI access. Note: I have not tried out any of these yet as I'm more interested in an asynchronous (i.e. email based) interface. [1] http://trac-hacks.org/wiki/XmlRpcPlugin [2] http://code.google.com/p/tracshell/ CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] More information on font scaling problem
Tomeu,
The thing is, in the code below I *am* using style.zoom. It seems to
have no effect at all.
My test environment on Fedora 10 is .82. My XO, running the latest (I
believe) release candidate of Sugar is .82. Most of the XO's that might
use Read Etexts will be running .82 or worse and will not be eager to
upgrade. For that reason I'm trying to make my Activity work around the
limitations of older versions of Sugar. As an example, .82 still has
the bug that custom metadata is not saved across reboots. I was using a
custom metadata field to store the page number that the user stopped
reading on. In my latest this page number is saved at the end of the
Title of the Journal entry, like this:
Off on a Comet! by Jules Verne P64
Aleksey and I also put in code that suppresses the Speech tab when
neither speech-dispatcher nor the gstreamer plugin for espeak is installed.
James Simmons
Tomeu Vizoso wrote:
On Wed, Jun 3, 2009 at 16:40, James Simmons wrote:
I mentioned before that I'm having a font sizing problem on the XO
running .82. When I set a font on a textviewer it looks OK running
under sugar-devel or SoaS by is *much* larger on the XO.
Sorry, in an earlier email i replied to you what would work in 0.84,
didn't realized you were talking about 0.82.
In 0.84 Pango knows the resolution of the screen and scales all fonts
accordingly. This means that by using, say 10, the font will always
look good in all hw.
In 0.82 didn't knew about the screen, so we were scaling all fonts by
using style.zoom().
Aleksey, do you have an idea about what can do activity authors that
wish to provide a single bundle that looks good both in 0.82 and 0.84?
Thanks,
Tomeu
This is the
code I'm currently using:
self.scrolled = gtk.ScrolledWindow()
self.scrolled.set_policy(gtk.POLICY_NEVER, gtk.POLICY_AUTOMATIC)
self.scrolled.props.shadow_type = gtk.SHADOW_NONE
self.textview = gtk.TextView()
self.textview.set_editable(False)
self.textview.set_cursor_visible(False)
self.textview.set_left_margin(50)
self.textview.connect("key_press_event", self.keypress_cb)
buffer = self.textview.get_buffer()
buffer.connect("mark-set", self.mark_set_cb)
self.font_desc = pango.FontDescription("sans %d" % style.zoom(10))
self.textview.modify_font(self.font_desc)
self.scrolled.add(self.textview)
self.textview.show()
self.scrolled.show()
v_adjustment = self.scrolled.get_vadjustment()
self.clipboard = gtk.Clipboard(display=gtk.gdk.display_get_default(),
selection="CLIPBOARD")
self.page = 0
self.textview.grab_focus()
The "sans 10" font is really too small for SoaS but on the XO it makes
80 columns of text fill the width of the screen. Any ideas?
James Simmons
___
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] Journal activity release 101 not tagged in Git
David Van Assche surfaced the idea here, http://www.mail-archive.com/i...@lists.sugarlabs.org/msg04259.html, with some recognition of the proposal. There seems to be a de-facto team at work already. Here is a wiki home to start furnishing, http://wiki.sugarlabs.org/go/Packaging_Team. --Fred On Fri, Jun 5, 2009 at 8:19 AM, Tomeu Vizoso wrote: > > Well, I would like to see one day a Packaging Team in Sugar Labs with > its space in the wiki, meetings, etc but I'm not aware of any movement > yet in that direction. > > Regards, > > Tomeu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Success at the Gardner!
Some people report the trackpad not working just for their Fedora installer. Not sure what you mean by "When the boothelper matched". Perhaps catch me on #sugar to discuss (jzGreen). James. 2009/6/5 Dave Bauer > > > On Fri, Jun 5, 2009 at 10:30 AM, James Zaki wrote: > >> On the macbook front, I've started to chase the trackpad glitch upstream >> with fedora. Am now running F11 on macbook5,1, but with external mouse. Will >> update trac when I make progress. >> > James, i used the boothelper CD and if I used a boothelper on an older > soas, the trackpad did not work. When the boothelper matched it worked ok. > > Dave > > > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [GSoC] progress report
On Fri, Jun 5, 2009 at 16:26, Lucian Branescu wrote: > I gave up the pickling idea when I realised that XPCOM and GObject are > messy about that. > > > Activities have data and state, right? data is persistent throughout > different states and states are saved to the Journal. Oh, by data you are referring to whatever is written in files in the ~/.sugar/default/org.laptop.WebActivity/data directory? You can write whatever you want there, but as it isn't browseable by the user, I would recommend to use it only for configuration data, cache, etc. > Browse already saves the current page, the contents of the page and > some metadata about the page. It does not however do anything special > about extension data in the mozilla profile. They are carried along as > part of the activity's data, persistent, and are the same for all > states saved in the Journal. > > I was thinking whether it is correct to have the Gears entire profile > saved to the Journal, or for that matter the entire profile of any > other extension. Hmm, I'm not sure google gears' on-disk format is the best one to store into the journal, but maybe we can start with that and then see? Regards, Tomeu > 2009/6/5 Tomeu Vizoso : >> On Fri, Jun 5, 2009 at 16:01, Lucian Branescu >> wrote: >>> 2009/6/5 Tomeu Vizoso : On Thu, Jun 4, 2009 at 22:42, Lucian Branescu wrote: > 2009/6/4 Tomeu Vizoso : >> On Wed, Jun 3, 2009 at 22:00, Lucian Branescu >> wrote: >>> Since I missed the meeting, here goes. >>> >>> I've had a really hectic past few days, with 2 exams, just getting my >>> laptop back and constantly fighting my Uni network restrictions. But >>> it's better now, finished with exams and I figured out how to trick >>> the proxies. >>> >>> I played around with a template Site Specific Browser based on Browse, >>> almost identical up to now. I think I have SSB generation mostly >>> figured out, I need to start implementing it. I will probably have to >>> either change the existing bookmark mechanism or add a new one, >>> because bookmarks (specifically bookmarklets) should be part of data, >>> not state. >>> >>> I also tried Tomeu's technique for getting Gears to work, but that >>> xulrunner bug prevents any permissions being granted. My initial plan >>> was to test Gears with GMail, but it's not quite possible right now. >>> I'll look into it, but I'd rather not have to build xulrunner. >> >> I think we can workaround the dialog sizing issue in hulahop, ping me >> in IRC and we can see what we can do. > > Sizing isn't really an issue. The permission dialog appears and is the > size I would expect, but there's nothing in it. That sounds like a problem with the gears installation (cannot find the chrome). Once you solve that, you will find that the user cannot grant privileges to the site because the dialog is too small. >>> >>> Oh. >>> >>> Also, now I'm more inclined to do the dbus functionality through >>> pyxpcom, mostly because of security issues. >> >> In my experience with Flash activities using Gnash, rather than giving >> access to the full DataStore API it's much more practical to provide >> some very simple state-saving functionality at first. If the python >> side can tell the JS side to load a buffer of data, and can ask it to >> hand a buffer to save in the DS, we can make 90% of activities work >> with very little effort. We can always make available later the full >> API or even generic DBus access. > > Saving state is not really an issue. At least current web apps are > built so that they do not lose any data if they suddenly die and some > of them also resume from where the left off. For most, it would be > enough to save the URL. Well, I was talking about saving state to the journal. > Ideally, it would be better to serialise the webview, if possible. What do you mean by that? >>> >>> I had this wild idea that I should be able to pickle the WebView and store >>> that. >> >> I'm not sure if that would work, my guess is that debugging that would >> be quite hard. Keep also in mind that there are XPCOM and GObject >> instances as part of WebView's state, so pickling all that would be a >> problem. >> >>> However, since I decided to use Browse as much as possible, I realised >>> that Browse already does all the integration with the Journal, except >>> for extensions (like Gears). So Browse should probably be fixed to >>> store the extension profiles as part of state, not data, but I'm not >>> sure if that is correct behaviour. >> >> What do you mean by extension profiles? And about state vs. data? >> >> When I talk about the journal, I use to refer to all the stuff that >> the activity stores in the journal as the "activity state". "Metadata" >> would be the structured part of the state and "data" would
Re: [Sugar-devel] Random numbers and the Journal
> I'm using python's random.getrandbits() to generate unique identifiers in my program. However, I've discovered that when I start it from the Journal, I get errors, Perhaps its not the best practice to rely on a random number generator to give unique identifiers. Would you not store a number with your program, to guarantee uniqueness? Unless I have mistaken the issue. 2009/6/5 Benjamin M. Schwartz > I'm using python's random.getrandbits() to generate unique identifiers in > my program. However, I've discovered that when I start it from the > Journal, I get errors, which I can trace to the random number generator > producing the same sequence of random numbers that was generated when I > started it the first time. It is as if the random seed is being reset > every time I launch from the Journal. > > Does anyone know what's going on here? > > Thanks, > Ben > > > ___ > 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] [IAEP] collaboration testing session
David, Can you try to use the Solutions Groovy jabber server? Caroline and Dave are putting some very helpful resources behind cleaning up the server. david(The other one) On Fri, Jun 5, 2009 at 7:37 AM, Caroline Meeks wrote: > Hi David, > > Will you be using the server hosted by Solution Grove/Zill? We would be > very happy if you did. > > We have seen mysterious spikes in resource usage that is not correlated to > the number of users connected. I am suspicious that some of the activities > use too many resources when they are shared. I'd like to set it up so that > someone on your team has access to what is going on on the server so you can > try to correlate any spikes to specific activities. > > Thanks, > Caroline > > On Fri, Jun 5, 2009 at 12:09 AM, David Van Assche > wrote: >> >> Hi folks, >> We are having a collaborative sugar testing session next week Wednesday >> 10th June at 20:00 UTC (That is 4 pm EDT, 3pm EST, 2 pm CST, 1 pm MST, and >> 12 pm PST, most of Europe that will be 9 pm, 8 pm for the UK) >> >> So far we have 5 people signed up, but more are welcome as we really want >> to see how collaboration works on many activities where it isn't quite >> obvious. We will be taking notes and storing log files of the sessions, and >> will suggest ways in which the activity in question might be more >> collaborative, or may need less of it (who knows :-) >> >> We will be testing the activities that come preinstalled on the openSUSE >> sugar images, but we'd like to test various distribution methods (virtual >> appliance, cd, usb, hd) and various distros (at least Fedora SoaS, openSUSE >> sugar, Mandriva or Caixa Magica) I dont believe 0.82 images are compatible >> with 0.84 for collaboration, so am afraid this is for 0.84 only... Please >> post your willingness to participate so we have an idea on who/how many will >> be collaborating. We also need a volunteer to take notes, and a volunteer to >> store logs files. There will of course be a transcript of the irc session >> too (we will meet at #sugar-collaboration) We forsee this taking between 1 >> and 2 hours... >> >> Here is the list of activities we will be testing, so make sure you have >> them installed if you plan to take part (not all have collaborative >> abilities, and for those that don't it can be a brainstorming session on >> whether/how we can make them collaborative: >> >> sugar-finance >> sugar-flipsticks-activity >> sugar-freecell >> sugar-imageviewer >> sugar-implode >> sugar-infoslicer >> sugar-jigsaw-puzzle-activity >> sugar-joke-machine-activity >> sugar-jukebox >> sugar-labyrinth >> sugar-maze >> sugar-memorize >> sugar-moon >> sugar-paint-activity >> sugar-pippy >> sugar-playgo >> sugar-read >> sugar-readetexts-activity >> sugar-record >> sugar-slider-puzzle-activity >> sugar-speak >> sugar-storybuilder >> sugar-tamtam-common >> sugar-tamtam-edit >> sugar-tamtam-jam >> sugar-tamtam-mini >> sugar-tamtam-synthlab >> sugar-analyze >> sugar-turtleart >> sugar-typing-turtle >> sugar-viewslides >> sugar-write >> sugar-browse >> sugar-irc >> sugar-calculate >> sugar-xomail (sugar-sweetmail) >> sugar-cartoonbuilder >> sugar-clock >> sugar-colors >> sugar-connect >> sugar-drgeo-activity >> xoEditor >> sugar-evince >> sugar-fiftytwo >> sugar-chat >> sugar-terminal >> sugar-journal >> sugar-physics >> sugar-library >> sugar-poll >> sugar-tuxpaint >> >> kind Regards, >> David (nubae) Van Assche >> www.nubae.com >> >> >> ___ >> IAEP -- It's An Education Project (not a laptop project!) >> i...@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/iaep > > > > -- > Caroline Meeks > Solution Grove > carol...@solutiongrove.com > > 617-500-3488 - Office > 505-213-3268 - Fax > > ___ > 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] Success at the Gardner!
On Fri, Jun 5, 2009 at 10:30 AM, James Zaki wrote: > On the macbook front, I've started to chase the trackpad glitch upstream > with fedora. Am now running F11 on macbook5,1, but with external mouse. Will > update trac when I make progress. > James, i used the boothelper CD and if I used a boothelper on an older soas, the trackpad did not work. When the boothelper matched it worked ok. Dave ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Success at the Gardner!
On the macbook front, I've started to chase the trackpad glitch upstream with fedora. Am now running F11 on macbook5,1, but with external mouse. Will update trac when I make progress. Wifi and sound are not so bad to get going, but even then sound is not perfect. Wifi had issues due to broadcom's proprietariness/legelness I think, hence it not being included in Fedora. Is this an issue for deployments? 2009/6/5 Caroline Meeks > The computer lab computers are now working with the 5/28 snapshot and the > broadcom drivers. The broadcom drivers are needed for internet access. > Thank you Sebastian! Is the process documented anywhere? I think other > people with driver issues may want to try it. > > I've updated the wiki: > http://wiki.sugarlabs.org/go/Gardner_Pilot_Academy#How_you_can_help_-_Technical_Tickets > > We will be writing more on various lists next week but I wanted to share > the good technical news immediately. > > Also they will not be using Macs very much this summer so we have a bit of > breathing space on that till the fall. Macbook support is still important > for the Lila Fredrick school, but for the Gardner having the computer lab > working is a huge step forward. > > Thanks everyone! > Caroline > > > > -- > Caroline Meeks > Solution Grove > carol...@solutiongrove.com > > 617-500-3488 - Office > 505-213-3268 - Fax > > ___ > 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] [GSoC] progress report
I gave up the pickling idea when I realised that XPCOM and GObject are messy about that. Activities have data and state, right? data is persistent throughout different states and states are saved to the Journal. Browse already saves the current page, the contents of the page and some metadata about the page. It does not however do anything special about extension data in the mozilla profile. They are carried along as part of the activity's data, persistent, and are the same for all states saved in the Journal. I was thinking whether it is correct to have the Gears entire profile saved to the Journal, or for that matter the entire profile of any other extension. 2009/6/5 Tomeu Vizoso : > On Fri, Jun 5, 2009 at 16:01, Lucian Branescu > wrote: >> 2009/6/5 Tomeu Vizoso : >>> On Thu, Jun 4, 2009 at 22:42, Lucian Branescu >>> wrote: 2009/6/4 Tomeu Vizoso : > On Wed, Jun 3, 2009 at 22:00, Lucian Branescu > wrote: >> Since I missed the meeting, here goes. >> >> I've had a really hectic past few days, with 2 exams, just getting my >> laptop back and constantly fighting my Uni network restrictions. But >> it's better now, finished with exams and I figured out how to trick >> the proxies. >> >> I played around with a template Site Specific Browser based on Browse, >> almost identical up to now. I think I have SSB generation mostly >> figured out, I need to start implementing it. I will probably have to >> either change the existing bookmark mechanism or add a new one, >> because bookmarks (specifically bookmarklets) should be part of data, >> not state. >> >> I also tried Tomeu's technique for getting Gears to work, but that >> xulrunner bug prevents any permissions being granted. My initial plan >> was to test Gears with GMail, but it's not quite possible right now. >> I'll look into it, but I'd rather not have to build xulrunner. > > I think we can workaround the dialog sizing issue in hulahop, ping me > in IRC and we can see what we can do. Sizing isn't really an issue. The permission dialog appears and is the size I would expect, but there's nothing in it. >>> >>> That sounds like a problem with the gears installation (cannot find >>> the chrome). Once you solve that, you will find that the user cannot >>> grant privileges to the site because the dialog is too small. >>> >> >> Oh. >> >> Also, now I'm more inclined to do the dbus functionality through >> pyxpcom, mostly because of security issues. > > In my experience with Flash activities using Gnash, rather than giving > access to the full DataStore API it's much more practical to provide > some very simple state-saving functionality at first. If the python > side can tell the JS side to load a buffer of data, and can ask it to > hand a buffer to save in the DS, we can make 90% of activities work > with very little effort. We can always make available later the full > API or even generic DBus access. Saving state is not really an issue. At least current web apps are built so that they do not lose any data if they suddenly die and some of them also resume from where the left off. For most, it would be enough to save the URL. >>> >>> Well, I was talking about saving state to the journal. >>> Ideally, it would be better to serialise the webview, if possible. >>> >>> What do you mean by that? >> >> I had this wild idea that I should be able to pickle the WebView and store >> that. > > I'm not sure if that would work, my guess is that debugging that would > be quite hard. Keep also in mind that there are XPCOM and GObject > instances as part of WebView's state, so pickling all that would be a > problem. > >> However, since I decided to use Browse as much as possible, I realised >> that Browse already does all the integration with the Journal, except >> for extensions (like Gears). So Browse should probably be fixed to >> store the extension profiles as part of state, not data, but I'm not >> sure if that is correct behaviour. > > What do you mean by extension profiles? And about state vs. data? > > When I talk about the journal, I use to refer to all the stuff that > the activity stores in the journal as the "activity state". "Metadata" > would be the structured part of the state and "data" would be a blob > containing the rest of the state. > > Regards, > > Tomeu > > >>> >>> Thanks, >>> >>> Tomeu >>> > > Regards, > > Tomeu > >> This >> http://sandbox.movial.com/wiki/index.php/Browser_DBus_Bridge#Gecko_version_notes >> would provide dbus accessibility directly to javascript and I'd need >> to handle security around that. Since my dbus needs are limited, I >> prefer to instead do everything python-side and inject javascript >> objects that do simple things (notifications, sounds, etc.). Of >> course, dbus is still a secondary object
Re: [Sugar-devel] Packaging Team (Was: Journal activity release 101 not tagged in Git)
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Fri, Jun 05, 2009 at 03:10:12PM +0200, Tomeu Vizoso wrote: >On Fri, Jun 5, 2009 at 15:00, Jonas Smedegaard wrote: >> On Fri, Jun 05, 2009 at 02:19:47PM +0200, Tomeu Vizoso wrote: >>>On Fri, Jun 5, 2009 at 14:11, Jonas Smedegaard wrote: On Fri, Jun 05, 2009 at 12:25:38PM +0200, Tomeu Vizoso wrote: >On Fri, Jun 5, 2009 at 12:22, Jonas Smedegaard wrote: >> http://wiki.sugarlabs.org/go/Journal >> >> http://wiki.sugarlabs.org/go/Sugar_Application_Stack >> >> (and possibly more - I keep loosing track of all the "homepages" >> of Sugar pieces) >> >> ...or for the places that is inappropriate to display historical >> info, it might make sense to _remove_ mentioning Journal instead. > >Well the journal exist, it's just that it's incorporated in the >shell module instead of living in its own module. I guess this is >only of concern to packagers, not to regular users? Yeah, I guess you are right. I just felt that more places than Gitorious targeted packagers, but maybe not. >>> >>>Well, I would like to see one day a Packaging Team in Sugar Labs with >>>its space in the wiki, meetings, etc but I'm not aware of any >>>movement yet in that direction. >> >> I fail to understand the purpose of such team. >> >> If you mean a team that produces various packages compatible with >> various distributions, then that won't replace the needs of most >> distributions, who would still want to care for its own official >> packages. >> >> If you mean a team that provides source to distributors, then isn't >> that a core task for the ReleaseTeam? > >Would be a team formed by the people that are working with each distro >to deliver a good Sugar experience for their users. > >Sugar on Debian would be a product of Debian, and Sugar on Fedora >would be a product of Fedora, but the packagers of each distro may >find useful a space in Sugar Labs to pool information and resources. >Or not, that's for packagers to decide. Thanks for clarifying. As I see it, we already share info today, e.g. through the wiki and this list. Ideally we distributors only customize as little as required to fit our individual distribution policies. Ideally reusable customization is adopted by Sugarlabs in the core code. I still fail to see what we might _coordinate_ that would not fit better to do in existing sugarlabs team. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkopKh8ACgkQn7DbMsAkQLj9cQCfbovMn9cLpuh7yJiZnAtnqIPh Ra0An02pL7IKoPkGwSJVtofVvV0Vw9+2 =iOqL -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] collaboration testing session
On 5 Jun 2009, at 09:24, Tomeu Vizoso wrote: > On Fri, Jun 5, 2009 at 06:09, David Van Assche > wrote: >> Hi folks, >>We are having a collaborative sugar testing session next week >> Wednesday >> 10th June at 20:00 UTC (That is 4 pm EDT, 3pm EST, 2 pm CST, 1 pm >> MST, and >> 12 pm PST, most of Europe that will be 9 pm, 8 pm for the UK) >> >> So far we have 5 people signed up, but more are welcome as we >> really want to >> see how collaboration works on many activities where it isn't quite >> obvious. >> We will be taking notes and storing log files of the sessions, and >> will >> suggest ways in which the activity in question might be more >> collaborative, >> or may need less of it (who knows :-) >> >> We will be testing the activities that come preinstalled on the >> openSUSE >> sugar images, but we'd like to test various distribution methods >> (virtual >> appliance, cd, usb, hd) and various distros (at least Fedora SoaS, >> openSUSE >> sugar, Mandriva or Caixa Magica) I dont believe 0.82 images are >> compatible >> with 0.84 for collaboration, so am afraid this is for 0.84 only... > > What do you mean by "compatible for collaboration" and why do you > think it won't work between 0.82 and 0.84? Just wanted to chime in here, and great idea by the way! FWIW, I don't remember any Activity releases announcing they had broken collaboration with previous releases, so issues should be down to general collaboration bugs within an Activity, Sugar collaboration code, the server/network infrastructure, or possibly the dirsto/ platform (e.g a few months back Fedoras default firewall setting was blocking local collaboration). It's very much worth keeping track of Sugar version, activity version, distro as you test, that way you can re-test a bug with different combinations to help isolate where the fault is (also testing later in a local salute environment can isolate issues caused by Jabber server use). You will bump into faults... if you want to make a real difference, finding clearly repeatable cases is the absolute gold standard in getting fixes (random fail reports are interesting but rarely actionable). Wednesday 10th June (I'll be there) will be a fair shake of the tree. Later, in more controlled version/release/network/distro environments each issue can be re-tested, confirmed-reproducible, isolated as far as possible and trac reported. Regards, --Gary > Regards, > > Tomeu > >> Please >> post your willingness to participate so we have an idea on who/how >> many will >> be collaborating. We also need a volunteer to take notes, and a >> volunteer to >> store logs files. There will of course be a transcript of the irc >> session >> too (we will meet at #sugar-collaboration) We forsee this taking >> between 1 >> and 2 hours... >> >> Here is the list of activities we will be testing, so make sure you >> have >> them installed if you plan to take part (not all have collaborative >> abilities, and for those that don't it can be a brainstorming >> session on >> whether/how we can make them collaborative: >> >> sugar-finance >> sugar-flipsticks-activity >> sugar-freecell >> sugar-imageviewer >> sugar-implode >> sugar-infoslicer >> sugar-jigsaw-puzzle-activity >> sugar-joke-machine-activity >> sugar-jukebox >> sugar-labyrinth >> sugar-maze >> sugar-memorize >> sugar-moon >> sugar-paint-activity >> sugar-pippy >> sugar-playgo >> sugar-read >> sugar-readetexts-activity >> sugar-record >> sugar-slider-puzzle-activity >> sugar-speak >> sugar-storybuilder >> sugar-tamtam-common >> sugar-tamtam-edit >> sugar-tamtam-jam >> sugar-tamtam-mini >> sugar-tamtam-synthlab >> sugar-analyze >> sugar-turtleart >> sugar-typing-turtle >> sugar-viewslides >> sugar-write >> sugar-browse >> sugar-irc >> sugar-calculate >> sugar-xomail (sugar-sweetmail) >> sugar-cartoonbuilder >> sugar-clock >> sugar-colors >> sugar-connect >> sugar-drgeo-activity >> xoEditor >> sugar-evince >> sugar-fiftytwo >> sugar-chat >> sugar-terminal >> sugar-journal >> sugar-physics >> sugar-library >> sugar-poll >> sugar-tuxpaint >> >> kind Regards, >> David (nubae) Van Assche >> www.nubae.com >> >> >> ___ >> IAEP -- It's An Education Project (not a laptop project!) >> i...@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/iaep >> > ___ > 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] Using Trac via email
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Fri, Jun 05, 2009 at 03:05:56PM +0200, Sascha Silbe wrote: > On Fri, Jun 05, 2009 at 02:19:52PM +0200, Jonas Smedegaard wrote: > ...and finally creating an account for myself at that Trac thingy. Does it have an email interface, [...] >>> There's a Trac plugin for creating new tickets for incoming emails, >>> but nothing to manipulate (including commenting on) existing bug >>> reports. :( >> There's a Perl Net::Trac module: >> http://search.cpan.org/dist/Net-Trac/ but I failed to locate any >> sample scripts atually using it. > It'd probably be best to write/use a Trac plugin instead, as the > XML-RPC interface obviously needs online access. There's a generic one > for email interfaces [1] that includes creating a new ticket as a > sample script, but probably could be used to manipulate tickets as > well. I would be more interested in a terminal-based generic Trac client, even if it had no offline mode, than an email-based Sugar-spcific interface. Why? Because I am involved in many projects, not only Sugar, and I do not want to juggle too many custom interfaces. So if Trac generically had some client-server ABI that I could expect would be available at many other Trac installations, then sure it would make more sense to use that in favor of some externally hacked-together Perl library. But it seems to me that Trac do *not* have such ABI, only a server-side API that could be used to _develop_ some custom client-server interaction creature. Mailman also has no client-server ABI. I quite efficiently handle moderator duties with the Perl-based "listadmin" tool. It is an ugly hack for an ugly web-only interface, and I would not expect to find anything nicer for Trac. I was hoping to find something comparable to PyBugz: http://www.liquidx.net/pybugz/ Apparently no such thing currently exist. > As always, somebody with enough time needs to step up to actually do > the work... Not always: only until someone does the work, in a good enough quality that it is kept alive, if not by the author then by others with interest in same tool. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkopKCkACgkQn7DbMsAkQLgGPwCgpIPYA2Itvk2gX/CTHRmtkWkX hPwAnRvokRxay7ixbFDInCye87wiV2Vx =i4FN -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [GSoC] progress report
On Fri, Jun 5, 2009 at 16:01, Lucian Branescu wrote: > 2009/6/5 Tomeu Vizoso : >> On Thu, Jun 4, 2009 at 22:42, Lucian Branescu >> wrote: >>> 2009/6/4 Tomeu Vizoso : On Wed, Jun 3, 2009 at 22:00, Lucian Branescu wrote: > Since I missed the meeting, here goes. > > I've had a really hectic past few days, with 2 exams, just getting my > laptop back and constantly fighting my Uni network restrictions. But > it's better now, finished with exams and I figured out how to trick > the proxies. > > I played around with a template Site Specific Browser based on Browse, > almost identical up to now. I think I have SSB generation mostly > figured out, I need to start implementing it. I will probably have to > either change the existing bookmark mechanism or add a new one, > because bookmarks (specifically bookmarklets) should be part of data, > not state. > > I also tried Tomeu's technique for getting Gears to work, but that > xulrunner bug prevents any permissions being granted. My initial plan > was to test Gears with GMail, but it's not quite possible right now. > I'll look into it, but I'd rather not have to build xulrunner. I think we can workaround the dialog sizing issue in hulahop, ping me in IRC and we can see what we can do. >>> >>> Sizing isn't really an issue. The permission dialog appears and is the >>> size I would expect, but there's nothing in it. >> >> That sounds like a problem with the gears installation (cannot find >> the chrome). Once you solve that, you will find that the user cannot >> grant privileges to the site because the dialog is too small. >> > > Oh. > > Also, now I'm more inclined to do the dbus functionality through > pyxpcom, mostly because of security issues. In my experience with Flash activities using Gnash, rather than giving access to the full DataStore API it's much more practical to provide some very simple state-saving functionality at first. If the python side can tell the JS side to load a buffer of data, and can ask it to hand a buffer to save in the DS, we can make 90% of activities work with very little effort. We can always make available later the full API or even generic DBus access. >>> >>> Saving state is not really an issue. At least current web apps are >>> built so that they do not lose any data if they suddenly die and some >>> of them also resume from where the left off. For most, it would be >>> enough to save the URL. >> >> Well, I was talking about saving state to the journal. >> >>> Ideally, it would be better to serialise the webview, if possible. >> >> What do you mean by that? > > I had this wild idea that I should be able to pickle the WebView and store > that. I'm not sure if that would work, my guess is that debugging that would be quite hard. Keep also in mind that there are XPCOM and GObject instances as part of WebView's state, so pickling all that would be a problem. > However, since I decided to use Browse as much as possible, I realised > that Browse already does all the integration with the Journal, except > for extensions (like Gears). So Browse should probably be fixed to > store the extension profiles as part of state, not data, but I'm not > sure if that is correct behaviour. What do you mean by extension profiles? And about state vs. data? When I talk about the journal, I use to refer to all the stuff that the activity stores in the journal as the "activity state". "Metadata" would be the structured part of the state and "data" would be a blob containing the rest of the state. Regards, Tomeu >> >> Thanks, >> >> Tomeu >> Regards, Tomeu > This > http://sandbox.movial.com/wiki/index.php/Browser_DBus_Bridge#Gecko_version_notes > would provide dbus accessibility directly to javascript and I'd need > to handle security around that. Since my dbus needs are limited, I > prefer to instead do everything python-side and inject javascript > objects that do simple things (notifications, sounds, etc.). Of > course, dbus is still a secondary objective. > ___ > 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] [GSoC] progress report
2009/6/5 Tomeu Vizoso : > On Thu, Jun 4, 2009 at 22:42, Lucian Branescu > wrote: >> 2009/6/4 Tomeu Vizoso : >>> On Wed, Jun 3, 2009 at 22:00, Lucian Branescu >>> wrote: Since I missed the meeting, here goes. I've had a really hectic past few days, with 2 exams, just getting my laptop back and constantly fighting my Uni network restrictions. But it's better now, finished with exams and I figured out how to trick the proxies. I played around with a template Site Specific Browser based on Browse, almost identical up to now. I think I have SSB generation mostly figured out, I need to start implementing it. I will probably have to either change the existing bookmark mechanism or add a new one, because bookmarks (specifically bookmarklets) should be part of data, not state. I also tried Tomeu's technique for getting Gears to work, but that xulrunner bug prevents any permissions being granted. My initial plan was to test Gears with GMail, but it's not quite possible right now. I'll look into it, but I'd rather not have to build xulrunner. >>> >>> I think we can workaround the dialog sizing issue in hulahop, ping me >>> in IRC and we can see what we can do. >> >> Sizing isn't really an issue. The permission dialog appears and is the >> size I would expect, but there's nothing in it. > > That sounds like a problem with the gears installation (cannot find > the chrome). Once you solve that, you will find that the user cannot > grant privileges to the site because the dialog is too small. > Oh. Also, now I'm more inclined to do the dbus functionality through pyxpcom, mostly because of security issues. >>> >>> In my experience with Flash activities using Gnash, rather than giving >>> access to the full DataStore API it's much more practical to provide >>> some very simple state-saving functionality at first. If the python >>> side can tell the JS side to load a buffer of data, and can ask it to >>> hand a buffer to save in the DS, we can make 90% of activities work >>> with very little effort. We can always make available later the full >>> API or even generic DBus access. >> >> Saving state is not really an issue. At least current web apps are >> built so that they do not lose any data if they suddenly die and some >> of them also resume from where the left off. For most, it would be >> enough to save the URL. > > Well, I was talking about saving state to the journal. > >> Ideally, it would be better to serialise the webview, if possible. > > What do you mean by that? I had this wild idea that I should be able to pickle the WebView and store that. However, since I decided to use Browse as much as possible, I realised that Browse already does all the integration with the Journal, except for extensions (like Gears). So Browse should probably be fixed to store the extension profiles as part of state, not data, but I'm not sure if that is correct behaviour. > > Thanks, > > Tomeu > >>> >>> Regards, >>> >>> Tomeu >>> This http://sandbox.movial.com/wiki/index.php/Browser_DBus_Bridge#Gecko_version_notes would provide dbus accessibility directly to javascript and I'd need to handle security around that. Since my dbus needs are limited, I prefer to instead do everything python-side and inject javascript objects that do simple things (notifications, sounds, etc.). Of course, dbus is still a secondary objective. ___ 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] [Marketing] [IAEP] ASLO - rebranding
Yes, much better integration with the rest of the site sections thanks Josh Sean On Fri, Jun 5, 2009 at 3:25 PM, David Farning wrote: > Hey, > > That is awesome! > > david > > On Fri, Jun 5, 2009 at 12:23 AM, Josh Williams wrote: >> Hi everyone, >> >> I've been working on the css for ASLO, you can see where I'm at >> http://activities-devel.sugarlabs.org/en-US/sugar/ . I've tried to make >> this fairly consistent with the design of sugarlabs.org. >> >> If any developers would be kind enough to upload some activities it >> would help with checking for inconsistencies it would be greatly >> appreciated. >> >> I'd like to push this to the live site in the near future, so please let >> me know what you think. >> >> Cheers, >> >> Josh >> >> >> ___ >> IAEP -- It's An Education Project (not a laptop project!) >> i...@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/iaep >> > ___ > Marketing mailing list > market...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/marketing > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] ASLO - rebranding
Hey, That is awesome! david On Fri, Jun 5, 2009 at 12:23 AM, Josh Williams wrote: > Hi everyone, > > I've been working on the css for ASLO, you can see where I'm at > http://activities-devel.sugarlabs.org/en-US/sugar/ . I've tried to make > this fairly consistent with the design of sugarlabs.org. > > If any developers would be kind enough to upload some activities it > would help with checking for inconsistencies it would be greatly > appreciated. > > I'd like to push this to the live site in the near future, so please let > me know what you think. > > Cheers, > > Josh > > > ___ > IAEP -- It's An Education Project (not a laptop project!) > i...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Packaging Team (Was: Journal activity release 101 not tagged in Git)
On Fri, Jun 5, 2009 at 15:00, Jonas Smedegaard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: RIPEMD160 > > On Fri, Jun 05, 2009 at 02:19:47PM +0200, Tomeu Vizoso wrote: >>On Fri, Jun 5, 2009 at 14:11, Jonas Smedegaard wrote: >>> On Fri, Jun 05, 2009 at 12:25:38PM +0200, Tomeu Vizoso wrote: On Fri, Jun 5, 2009 at 12:22, Jonas Smedegaard wrote: > http://wiki.sugarlabs.org/go/Journal > > http://wiki.sugarlabs.org/go/Sugar_Application_Stack > > (and possibly more - I keep loosing track of all the "homepages" of > Sugar pieces) > > ...or for the places that is inappropriate to display historical > info, it might make sense to _remove_ mentioning Journal instead. Well the journal exist, it's just that it's incorporated in the shell module instead of living in its own module. I guess this is only of concern to packagers, not to regular users? >>> >>> Yeah, I guess you are right. I just felt that more places than >>> Gitorious targeted packagers, but maybe not. >> >>Well, I would like to see one day a Packaging Team in Sugar Labs with >>its space in the wiki, meetings, etc but I'm not aware of any movement >>yet in that direction. > > I fail to understand the purpose of such team. > > If you mean a team that produces various packages compatible with > various distributions, then that won't replace the needs of most > distributions, who would still want to care for its own official > packages. > > If you mean a team that provides source to distributors, then isn't that > a core task for the ReleaseTeam? Would be a team formed by the people that are working with each distro to deliver a good Sugar experience for their users. Sugar on Debian would be a product of Debian, and Sugar on Fedora would be a product of Fedora, but the packagers of each distro may find useful a space in Sugar Labs to pool information and resources. Or not, that's for packagers to decide. Regards, Tomeu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Using Trac via email
On Fri, Jun 05, 2009 at 02:19:52PM +0200, Jonas Smedegaard wrote: ...and finally creating an account for myself at that Trac thingy. Does it have an email interface, [...] There's a Trac plugin for creating new tickets for incoming emails, but nothing to manipulate (including commenting on) existing bug reports. :( There's a Perl Net::Trac module: http://search.cpan.org/dist/Net-Trac/ but I failed to locate any sample scripts atually using it. It'd probably be best to write/use a Trac plugin instead, as the XML-RPC interface obviously needs online access. There's a generic one for email interfaces [1] that includes creating a new ticket as a sample script, but probably could be used to manipulate tickets as well. As always, somebody with enough time needs to step up to actually do the work... (I find the Debian mail-based bugtracker quite convenient) Me too - except for the SPAM (due to the email addresses being published). [1] http://trac-hacks.org/wiki/MailToTracPlugin CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Packaging Team (Was: Journal activity release 101 not tagged in Git)
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Fri, Jun 05, 2009 at 02:19:47PM +0200, Tomeu Vizoso wrote: >On Fri, Jun 5, 2009 at 14:11, Jonas Smedegaard wrote: >> On Fri, Jun 05, 2009 at 12:25:38PM +0200, Tomeu Vizoso wrote: >>>On Fri, Jun 5, 2009 at 12:22, Jonas Smedegaard wrote: http://wiki.sugarlabs.org/go/Journal http://wiki.sugarlabs.org/go/Sugar_Application_Stack (and possibly more - I keep loosing track of all the "homepages" of Sugar pieces) ...or for the places that is inappropriate to display historical info, it might make sense to _remove_ mentioning Journal instead. >>> >>>Well the journal exist, it's just that it's incorporated in the shell >>>module instead of living in its own module. I guess this is only of >>>concern to packagers, not to regular users? >> >> Yeah, I guess you are right. I just felt that more places than >> Gitorious targeted packagers, but maybe not. > >Well, I would like to see one day a Packaging Team in Sugar Labs with >its space in the wiki, meetings, etc but I'm not aware of any movement >yet in that direction. I fail to understand the purpose of such team. If you mean a team that produces various packages compatible with various distributions, then that won't replace the needs of most distributions, who would still want to care for its own official packages. If you mean a team that provides source to distributors, then isn't that a core task for the ReleaseTeam? - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkopFvoACgkQn7DbMsAkQLiGIACfQYiBpjqifclq/wpAowW9iQmy sLwAn0cS3t12hxwe4YjKMJRI58CqU6k0 =BFDV -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] collaboration testing session
Hi David, Will you be using the server hosted by Solution Grove/Zill? We would be very happy if you did. We have seen mysterious spikes in resource usage that is not correlated to the number of users connected. I am suspicious that some of the activities use too many resources when they are shared. I'd like to set it up so that someone on your team has access to what is going on on the server so you can try to correlate any spikes to specific activities. Thanks, Caroline On Fri, Jun 5, 2009 at 12:09 AM, David Van Assche wrote: > Hi folks, >We are having a collaborative sugar testing session next week Wednesday > 10th June at 20:00 UTC (That is 4 pm EDT, 3pm EST, 2 pm CST, 1 pm MST, and > 12 pm PST, most of Europe that will be 9 pm, 8 pm for the UK) > > So far we have 5 people signed up, but more are welcome as we really want > to see how collaboration works on many activities where it isn't quite > obvious. We will be taking notes and storing log files of the sessions, and > will suggest ways in which the activity in question might be more > collaborative, or may need less of it (who knows :-) > > We will be testing the activities that come preinstalled on the openSUSE > sugar images, but we'd like to test various distribution methods (virtual > appliance, cd, usb, hd) and various distros (at least Fedora SoaS, openSUSE > sugar, Mandriva or Caixa Magica) I dont believe 0.82 images are compatible > with 0.84 for collaboration, so am afraid this is for 0.84 only... Please > post your willingness to participate so we have an idea on who/how many will > be collaborating. We also need a volunteer to take notes, and a volunteer to > > store logs files. There will of course be a transcript of the irc session > too (we will meet at #sugar-collaboration) We forsee this taking between 1 > and 2 hours... > > Here is the list of activities we will be testing, so make sure you have > them installed if you plan to take part (not all have collaborative > abilities, and for those that don't it can be a brainstorming session on > whether/how we can make them collaborative: > > sugar-finance > sugar-flipsticks-activity > sugar-freecell > sugar-imageviewer > sugar-implode > sugar-infoslicer > sugar-jigsaw-puzzle-activity > sugar-joke-machine-activity > sugar-jukebox > sugar-labyrinth > sugar-maze > sugar-memorize > sugar-moon > sugar-paint-activity > sugar-pippy > sugar-playgo > sugar-read > sugar-readetexts-activity > sugar-record > sugar-slider-puzzle-activity > sugar-speak > sugar-storybuilder > sugar-tamtam-common > sugar-tamtam-edit > sugar-tamtam-jam > sugar-tamtam-mini > sugar-tamtam-synthlab > sugar-analyze > sugar-turtleart > sugar-typing-turtle > sugar-viewslides > sugar-write > sugar-browse > sugar-irc > sugar-calculate > sugar-xomail (sugar-sweetmail) > sugar-cartoonbuilder > sugar-clock > sugar-colors > sugar-connect > sugar-drgeo-activity > xoEditor > sugar-evince > sugar-fiftytwo > sugar-chat > sugar-terminal > sugar-journal > sugar-physics > sugar-library > sugar-poll > sugar-tuxpaint > > kind Regards, > David (nubae) Van Assche > www.nubae.com > > > ___ > IAEP -- It's An Education Project (not a laptop project!) > i...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep > -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Using Trac via email (was: Re: hulahop autotools seems broken)
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Fri, Jun 05, 2009 at 12:26:21PM +0200, Sascha Silbe wrote: > On Fri, Jun 05, 2009 at 12:07:46PM +0200, Jonas Smedegaard wrote: > >> ...and finally creating an account for myself at that Trac thingy. >> Does it have an email interface, [...] > There's a Trac plugin for creating new tickets for incoming emails, > but nothing to manipulate (including commenting on) existing bug > reports. :( There's a Perl Net::Trac module: http://search.cpan.org/dist/Net-Trac/ but I failed to locate any sample scripts atually using it. (I find the Debian mail-based bugtracker quite convenient) - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkopDWgACgkQn7DbMsAkQLhcYQCeKjrtHt6GRXybucQ5fUl5rdfO TxkAn3GbN5NY+m8xQkTCjP35rEMAqJpS =+ld4 -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal activity release 101 not tagged in Git
On Fri, Jun 5, 2009 at 14:11, Jonas Smedegaard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: RIPEMD160 > > On Fri, Jun 05, 2009 at 12:25:38PM +0200, Tomeu Vizoso wrote: >>On Fri, Jun 5, 2009 at 12:22, Jonas Smedegaard wrote: >>> On Fri, Jun 05, 2009 at 10:52:08AM +0200, Tomeu Vizoso wrote: Please note that the journal is not an independent module since 0.84, so only if you are packaging 0.82 you should worry about it (and go to OLPC machines for tarballs etc.). >>> >>> Ah, that explains why such a core part is not "up-to-date". >>> >>> Perhaps you should add an end-of-life note, detailing whether it is >>> harmless or not to have the old activity installed on newer Sugar, at >>> these places: >>> >>> http://git.sugarlabs.org/projects/journal/repos/mainline >> >>It's already in http://git.sugarlabs.org/projects/journal > > Ah, ok. > > >>> http://wiki.sugarlabs.org/go/Journal >>> >>> http://wiki.sugarlabs.org/go/Sugar_Application_Stack >>> >>> (and possibly more - I keep loosing track of all the "homepages" of >>> Sugar pieces) >>> >>> ...or for the places that is inappropriate to display historical >>> info, it might make sense to _remove_ mentioning Journal instead. >> >>Well the journal exist, it's just that it's incorporated in the shell >>module instead of living in its own module. I guess this is only of >>concern to packagers, not to regular users? > > Yeah, I guess you are right. I just felt that more places than > Gitorious targeted packagers, but maybe not. Well, I would like to see one day a Packaging Team in Sugar Labs with its space in the wiki, meetings, etc but I'm not aware of any movement yet in that direction. Regards, Tomeu > At least I got the message now. :-D > > > - Jonas > > - -- > * Jonas Smedegaard - idealist og Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEAREDAAYFAkopC4QACgkQn7DbMsAkQLiIagCdGlH3WWvzrxY1tZFCvm/jKQqD > rnoAnju+UkYBjJsJoL80xRN+Z6FZ+KQg > =TT+e > -END PGP SIGNATURE- > ___ > 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] Journal activity release 101 not tagged in Git
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Fri, Jun 05, 2009 at 12:25:38PM +0200, Tomeu Vizoso wrote: >On Fri, Jun 5, 2009 at 12:22, Jonas Smedegaard wrote: >> On Fri, Jun 05, 2009 at 10:52:08AM +0200, Tomeu Vizoso wrote: >>>Please note that the journal is not an independent module since 0.84, >>>so only if you are packaging 0.82 you should worry about it (and go >>>to OLPC machines for tarballs etc.). >> >> Ah, that explains why such a core part is not "up-to-date". >> >> Perhaps you should add an end-of-life note, detailing whether it is >> harmless or not to have the old activity installed on newer Sugar, at >> these places: >> >> http://git.sugarlabs.org/projects/journal/repos/mainline > >It's already in http://git.sugarlabs.org/projects/journal Ah, ok. >> http://wiki.sugarlabs.org/go/Journal >> >> http://wiki.sugarlabs.org/go/Sugar_Application_Stack >> >> (and possibly more - I keep loosing track of all the "homepages" of >> Sugar pieces) >> >> ...or for the places that is inappropriate to display historical >> info, it might make sense to _remove_ mentioning Journal instead. > >Well the journal exist, it's just that it's incorporated in the shell >module instead of living in its own module. I guess this is only of >concern to packagers, not to regular users? Yeah, I guess you are right. I just felt that more places than Gitorious targeted packagers, but maybe not. At least I got the message now. :-D - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkopC4QACgkQn7DbMsAkQLiIagCdGlH3WWvzrxY1tZFCvm/jKQqD rnoAnju+UkYBjJsJoL80xRN+Z6FZ+KQg =TT+e -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] collaboration testing session
On 05.06.2009, at 12:10, David Van Assche wrote: Ok, etoys included too.. Thanks :) Is it preinstalled on the "openSUSE sugar images" you mentioned? Are these the images you are referring to? http://download.opensuse.org/repositories/Education/images/ Which collab server do you intend to use? Is there a wiki page to sign up and coordinate, or what's the procedure? - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] collaboration testing session
On Fri, Jun 5, 2009 at 12:09, David Van Assche wrote: > Well as we just discussed in irc, some activities will actually share and > allow for collaboration, but the vast majority do not and/or dont work > between different distribution methods. In any case we can certainly try > some out and send you the log files to dissect, in case u cannot make it. I think that the vast majority won't have changed the collaboration protocol and should work. If they don't, I would suspect a problem in the collaboration infrastructure. Regards, Tomeu > kind regards, > David (nubae) > > On Fri, Jun 5, 2009 at 10:24 AM, Tomeu Vizoso wrote: >> >> On Fri, Jun 5, 2009 at 06:09, David Van Assche >> wrote: >> > Hi folks, >> > We are having a collaborative sugar testing session next week >> > Wednesday >> > 10th June at 20:00 UTC (That is 4 pm EDT, 3pm EST, 2 pm CST, 1 pm MST, >> > and >> > 12 pm PST, most of Europe that will be 9 pm, 8 pm for the UK) >> > >> > So far we have 5 people signed up, but more are welcome as we really >> > want to >> > see how collaboration works on many activities where it isn't quite >> > obvious. >> > We will be taking notes and storing log files of the sessions, and will >> > suggest ways in which the activity in question might be more >> > collaborative, >> > or may need less of it (who knows :-) >> > >> > We will be testing the activities that come preinstalled on the openSUSE >> > sugar images, but we'd like to test various distribution methods >> > (virtual >> > appliance, cd, usb, hd) and various distros (at least Fedora SoaS, >> > openSUSE >> > sugar, Mandriva or Caixa Magica) I dont believe 0.82 images are >> > compatible >> > with 0.84 for collaboration, so am afraid this is for 0.84 only... >> >> What do you mean by "compatible for collaboration" and why do you >> think it won't work between 0.82 and 0.84? >> >> Regards, >> >> Tomeu >> >> > Please >> > post your willingness to participate so we have an idea on who/how many >> > will >> > be collaborating. We also need a volunteer to take notes, and a >> > volunteer to >> > store logs files. There will of course be a transcript of the irc >> > session >> > too (we will meet at #sugar-collaboration) We forsee this taking between >> > 1 >> > and 2 hours... >> > >> > Here is the list of activities we will be testing, so make sure you have >> > them installed if you plan to take part (not all have collaborative >> > abilities, and for those that don't it can be a brainstorming session on >> > whether/how we can make them collaborative: >> > >> > sugar-finance >> > sugar-flipsticks-activity >> > sugar-freecell >> > sugar-imageviewer >> > sugar-implode >> > sugar-infoslicer >> > sugar-jigsaw-puzzle-activity >> > sugar-joke-machine-activity >> > sugar-jukebox >> > sugar-labyrinth >> > sugar-maze >> > sugar-memorize >> > sugar-moon >> > sugar-paint-activity >> > sugar-pippy >> > sugar-playgo >> > sugar-read >> > sugar-readetexts-activity >> > sugar-record >> > sugar-slider-puzzle-activity >> > sugar-speak >> > sugar-storybuilder >> > sugar-tamtam-common >> > sugar-tamtam-edit >> > sugar-tamtam-jam >> > sugar-tamtam-mini >> > sugar-tamtam-synthlab >> > sugar-analyze >> > sugar-turtleart >> > sugar-typing-turtle >> > sugar-viewslides >> > sugar-write >> > sugar-browse >> > sugar-irc >> > sugar-calculate >> > sugar-xomail (sugar-sweetmail) >> > sugar-cartoonbuilder >> > sugar-clock >> > sugar-colors >> > sugar-connect >> > sugar-drgeo-activity >> > xoEditor >> > sugar-evince >> > sugar-fiftytwo >> > sugar-chat >> > sugar-terminal >> > sugar-journal >> > sugar-physics >> > sugar-library >> > sugar-poll >> > sugar-tuxpaint >> > >> > kind Regards, >> > David (nubae) Van Assche >> > www.nubae.com >> > >> > >> > ___ >> > IAEP -- It's An Education Project (not a laptop project!) >> > i...@lists.sugarlabs.org >> > http://lists.sugarlabs.org/listinfo/iaep >> > > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Using Trac via email (was: Re: hulahop autotools seems broken)
On Fri, Jun 05, 2009 at 12:07:46PM +0200, Jonas Smedegaard wrote: ...and finally creating an account for myself at that Trac thingy. Does it have an email interface, [...] There's a Trac plugin for creating new tickets for incoming emails, but nothing to manipulate (including commenting on) existing bug reports. :( CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] collaboration testing session
On 05.06.2009, at 06:09, David Van Assche wrote: Hi folks, We are having a collaborative sugar testing session next week Wednesday 10th June at 20:00 UTC (That is 4 pm EDT, 3pm EST, 2 pm CST, 1 pm MST, and 12 pm PST, most of Europe that will be 9 pm, 8 pm for the UK) So you mean 19:00 UTC (because of daylight saving): http://timeanddate.com/worldclock/fixedtime.html?month=6&day=10&year=2009&hour=19&min=0&sec=0&p1=0 - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal activity release 101 not tagged in Git
On Fri, Jun 5, 2009 at 12:22, Jonas Smedegaard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: RIPEMD160 > > On Fri, Jun 05, 2009 at 10:52:08AM +0200, Tomeu Vizoso wrote: >>On Sat, May 30, 2009 at 10:32, Jonas Smedegaard wrote: >>> As subject says, newest Journal release available at >>> http://dev.laptop.org/pub/sugar/sources/Journal/ (and not at >>> sugarlabs.org!), released january 2009, is not reflected as a Git tag >>> at git://git.sugarlabs.org/journal/mainline (neither at the git at >>> dev.laptop.org). >> >>Actually, the tag was in dev.laptop.org but not in git.sugarlabs.org, >>I have updated gitorious. >> >>http://git.sugarlabs.org/projects/journal/repos/mainline/commits/c70633c93154b8438321e253ed3b21f9c48dc7aa >> >>Please note that the journal is not an independent module since 0.84, >>so only if you are packaging 0.82 you should worry about it (and go to >>OLPC machines for tarballs etc.). > > Ah, that explains why such a core part is not "up-to-date". > > Perhaps you should add an end-of-life note, detailing whether it is > harmless or not to have the old activity installed on newer Sugar, at > these places: > > http://git.sugarlabs.org/projects/journal/repos/mainline It's already in http://git.sugarlabs.org/projects/journal > http://wiki.sugarlabs.org/go/Journal > > http://wiki.sugarlabs.org/go/Sugar_Application_Stack > > (and possibly more - I keep loosing track of all the "homepages" of > Sugar pieces) > > ...or for the places that is inappropriate to display historical info, > it might make sense to _remove_ mentioning Journal instead. Well the journal exist, it's just that it's incorporated in the shell module instead of living in its own module. I guess this is only of concern to packagers, not to regular users? Regards, Tomeu > > Kind regards, > > - Jonas > > - -- > * Jonas Smedegaard - idealist og Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEAREDAAYFAkoo8d0ACgkQn7DbMsAkQLjdPACfbFPYfn+o0VZW9zST2+9+VStA > Ib0AmwWfqcKZm8GFvZt2Wy7Ty3uZbGua > =LrzJ > -END PGP SIGNATURE- > ___ > 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] Journal activity release 101 not tagged in Git
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Fri, Jun 05, 2009 at 10:52:08AM +0200, Tomeu Vizoso wrote: >On Sat, May 30, 2009 at 10:32, Jonas Smedegaard wrote: >> As subject says, newest Journal release available at >> http://dev.laptop.org/pub/sugar/sources/Journal/ (and not at >> sugarlabs.org!), released january 2009, is not reflected as a Git tag >> at git://git.sugarlabs.org/journal/mainline (neither at the git at >> dev.laptop.org). > >Actually, the tag was in dev.laptop.org but not in git.sugarlabs.org, >I have updated gitorious. > >http://git.sugarlabs.org/projects/journal/repos/mainline/commits/c70633c93154b8438321e253ed3b21f9c48dc7aa > >Please note that the journal is not an independent module since 0.84, >so only if you are packaging 0.82 you should worry about it (and go to >OLPC machines for tarballs etc.). Ah, that explains why such a core part is not "up-to-date". Perhaps you should add an end-of-life note, detailing whether it is harmless or not to have the old activity installed on newer Sugar, at these places: http://git.sugarlabs.org/projects/journal/repos/mainline http://wiki.sugarlabs.org/go/Journal http://wiki.sugarlabs.org/go/Sugar_Application_Stack (and possibly more - I keep loosing track of all the "homepages" of Sugar pieces) ...or for the places that is inappropriate to display historical info, it might make sense to _remove_ mentioning Journal instead. Kind regards, - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkoo8d0ACgkQn7DbMsAkQLjdPACfbFPYfn+o0VZW9zST2+9+VStA Ib0AmwWfqcKZm8GFvZt2Wy7Ty3uZbGua =LrzJ -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] hulahop autotools seems broken
On Fri, Jun 5, 2009 at 12:07, Jonas Smedegaard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: RIPEMD160 > > On Fri, Jun 05, 2009 at 10:43:19AM +0200, Tomeu Vizoso wrote: >>On Sat, May 30, 2009 at 10:20, Jonas Smedegaard wrote: >>> The autotools shipped with hulahop 0.4.9 seems broken. >> >>Hi, have entered this ticket about it: >> >>http://dev.sugarlabs.org/ticket/936 >> >>Do you have already a patch for this? If so, please attach it to the ticket. > > Done. Thanks a lot. > ...and finally creating an account for myself at that Trac thingy. Does > it have an email interface, or am I forced to use web interface for > interactions with it? Not that I know of, but I would also like to avoid the web interface if possible (or at least speed it up). Regards, Tomeu > I tried to use moap[1] but a) it seems to only provide reading access, > not posting new bugreports or adding info to existing ones, and b) moap > failed to recognize your URL as a Trac brugtracker (perhaps because it > expects all Tracs to include trailing /trac/ in the URL?). > > > > - Jonas > > [1] http://thomas.apestaart.org/moap/trac/ > > - -- > * Jonas Smedegaard - idealist og Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEAREDAAYFAkoo7nIACgkQn7DbMsAkQLikqwCgiSqla8MV99IFY5MU+WmUnXAH > IMYAnisssc1nUrdizaPb2WkAonV/grfM > =XTnv > -END PGP SIGNATURE- > ___ > 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] collaboration testing session
Ok, etoys included too.. On Fri, Jun 5, 2009 at 11:35 AM, Bert Freudenberg wrote: > > On 05.06.2009, at 06:09, David Van Assche wrote: > > Hi folks, >We are having a collaborative sugar testing session next week Wednesday > 10th June at 20:00 UTC (That is 4 pm EDT, 3pm EST, 2 pm CST, 1 pm MST, and > 12 pm PST, most of Europe that will be 9 pm, 8 pm for the UK) > > So far we have 5 people signed up, but more are welcome as we really want > to see how collaboration works on many activities where it isn't quite > obvious. We will be taking notes and storing log files of the sessions, and > will suggest ways in which the activity in question might be more > collaborative, or may need less of it (who knows :-) > > We will be testing the activities that come preinstalled on the openSUSE > sugar images, but we'd like to test various distribution methods (virtual > appliance, cd, usb, hd) and various distros (at least Fedora SoaS, openSUSE > sugar, Mandriva or Caixa Magica) I dont believe 0.82 images are compatible > with 0.84 for collaboration, so am afraid this is for 0.84 only... Please > post your willingness to participate so we have an idea on who/how many will > be collaborating. We also need a volunteer to take notes, and a volunteer to > > store logs files. There will of course be a transcript of the irc session > too (we will meet at #sugar-collaboration) We forsee this taking between 1 > and 2 hours... > > Here is the list of activities we will be testing, so make sure you have > them installed if you plan to take part (not all have collaborative > abilities, and for those that don't it can be a brainstorming session on > whether/how we can make them collaborative: > > > What's the reason you exclude Etoys, which does support collaboration? > > - Bert - > > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] collaboration testing session
Well as we just discussed in irc, some activities will actually share and allow for collaboration, but the vast majority do not and/or dont work between different distribution methods. In any case we can certainly try some out and send you the log files to dissect, in case u cannot make it. kind regards, David (nubae) On Fri, Jun 5, 2009 at 10:24 AM, Tomeu Vizoso wrote: > On Fri, Jun 5, 2009 at 06:09, David Van Assche > wrote: > > Hi folks, > >We are having a collaborative sugar testing session next week > Wednesday > > 10th June at 20:00 UTC (That is 4 pm EDT, 3pm EST, 2 pm CST, 1 pm MST, > and > > 12 pm PST, most of Europe that will be 9 pm, 8 pm for the UK) > > > > So far we have 5 people signed up, but more are welcome as we really want > to > > see how collaboration works on many activities where it isn't quite > obvious. > > We will be taking notes and storing log files of the sessions, and will > > suggest ways in which the activity in question might be more > collaborative, > > or may need less of it (who knows :-) > > > > We will be testing the activities that come preinstalled on the openSUSE > > sugar images, but we'd like to test various distribution methods (virtual > > appliance, cd, usb, hd) and various distros (at least Fedora SoaS, > openSUSE > > sugar, Mandriva or Caixa Magica) I dont believe 0.82 images are > compatible > > with 0.84 for collaboration, so am afraid this is for 0.84 only... > > What do you mean by "compatible for collaboration" and why do you > think it won't work between 0.82 and 0.84? > > Regards, > > Tomeu > > > Please > > post your willingness to participate so we have an idea on who/how many > will > > be collaborating. We also need a volunteer to take notes, and a volunteer > to > > store logs files. There will of course be a transcript of the irc session > > too (we will meet at #sugar-collaboration) We forsee this taking between > 1 > > and 2 hours... > > > > Here is the list of activities we will be testing, so make sure you have > > them installed if you plan to take part (not all have collaborative > > abilities, and for those that don't it can be a brainstorming session on > > whether/how we can make them collaborative: > > > > sugar-finance > > sugar-flipsticks-activity > > sugar-freecell > > sugar-imageviewer > > sugar-implode > > sugar-infoslicer > > sugar-jigsaw-puzzle-activity > > sugar-joke-machine-activity > > sugar-jukebox > > sugar-labyrinth > > sugar-maze > > sugar-memorize > > sugar-moon > > sugar-paint-activity > > sugar-pippy > > sugar-playgo > > sugar-read > > sugar-readetexts-activity > > sugar-record > > sugar-slider-puzzle-activity > > sugar-speak > > sugar-storybuilder > > sugar-tamtam-common > > sugar-tamtam-edit > > sugar-tamtam-jam > > sugar-tamtam-mini > > sugar-tamtam-synthlab > > sugar-analyze > > sugar-turtleart > > sugar-typing-turtle > > sugar-viewslides > > sugar-write > > sugar-browse > > sugar-irc > > sugar-calculate > > sugar-xomail (sugar-sweetmail) > > sugar-cartoonbuilder > > sugar-clock > > sugar-colors > > sugar-connect > > sugar-drgeo-activity > > xoEditor > > sugar-evince > > sugar-fiftytwo > > sugar-chat > > sugar-terminal > > sugar-journal > > sugar-physics > > sugar-library > > sugar-poll > > sugar-tuxpaint > > > > kind Regards, > > David (nubae) Van Assche > > www.nubae.com > > > > > > ___ > > IAEP -- It's An Education Project (not a laptop project!) > > i...@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/iaep > > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] hulahop autotools seems broken
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Fri, Jun 05, 2009 at 10:43:19AM +0200, Tomeu Vizoso wrote: >On Sat, May 30, 2009 at 10:20, Jonas Smedegaard wrote: >> The autotools shipped with hulahop 0.4.9 seems broken. > >Hi, have entered this ticket about it: > >http://dev.sugarlabs.org/ticket/936 > >Do you have already a patch for this? If so, please attach it to the ticket. Done. ...and finally creating an account for myself at that Trac thingy. Does it have an email interface, or am I forced to use web interface for interactions with it? I tried to use moap[1] but a) it seems to only provide reading access, not posting new bugreports or adding info to existing ones, and b) moap failed to recognize your URL as a Trac brugtracker (perhaps because it expects all Tracs to include trailing /trac/ in the URL?). - Jonas [1] http://thomas.apestaart.org/moap/trac/ - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkoo7nIACgkQn7DbMsAkQLikqwCgiSqla8MV99IFY5MU+WmUnXAH IMYAnisssc1nUrdizaPb2WkAonV/grfM =XTnv -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] collaboration testing session
On 05.06.2009, at 06:09, David Van Assche wrote: Hi folks, We are having a collaborative sugar testing session next week Wednesday 10th June at 20:00 UTC (That is 4 pm EDT, 3pm EST, 2 pm CST, 1 pm MST, and 12 pm PST, most of Europe that will be 9 pm, 8 pm for the UK) So far we have 5 people signed up, but more are welcome as we really want to see how collaboration works on many activities where it isn't quite obvious. We will be taking notes and storing log files of the sessions, and will suggest ways in which the activity in question might be more collaborative, or may need less of it (who knows :-) We will be testing the activities that come preinstalled on the openSUSE sugar images, but we'd like to test various distribution methods (virtual appliance, cd, usb, hd) and various distros (at least Fedora SoaS, openSUSE sugar, Mandriva or Caixa Magica) I dont believe 0.82 images are compatible with 0.84 for collaboration, so am afraid this is for 0.84 only... Please post your willingness to participate so we have an idea on who/how many will be collaborating. We also need a volunteer to take notes, and a volunteer to store logs files. There will of course be a transcript of the irc session too (we will meet at #sugar-collaboration) We forsee this taking between 1 and 2 hours... Here is the list of activities we will be testing, so make sure you have them installed if you plan to take part (not all have collaborative abilities, and for those that don't it can be a brainstorming session on whether/how we can make them collaborative: What's the reason you exclude Etoys, which does support collaboration? - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Searchable Tagging
On Wed, Jun 3, 2009 at 22:25, kartik rustagi wrote: > Hello, > > I have started working on adding the feature of "Search able tags" to Sugar. > This will allow > the users to tag them self or any else in the network. These tag will be > generalized tags. Users > will have the option to search for users having a particular tag. Say for > example I tag my self > as : "I love python". Then if a user in the network searches for "python", > the result will show > me. Here are some of the use cases (contributed by tomeu): > > Use case 1: Finding people with similar interests: > Pepe enjoyed during the weekend his first rock climbing experience and would > like to find other > people in his school who also like it. > > Use case 2: Limiting the mesh view to a subset defined locally: > Maria is a teacher and would like that during her classes, only her students > in that class appear in > the mesh view. > > Proposed user experience > > Use case 1: finding people with similar interests: > Pepe tags itself as climbing, and when someone searches in the mesh view for > "climbing", Pepe will > appear in the results. > > Use case 2: limiting the mesh view to a subset defined locally: > Maria tags each of the students in that class with the tag "my_class", so > that when searches in the > mesh view for that text, only her students appear. In the case that someone > else has tagged himself > with that same tag, it will appear as well in the results, but will be > marked differently as the local matches. > > As it can be seen, this feature will be a precursor to add "Groups" to > Sugar. I am right now trying to > add these tags to /source/sugar-presence-services/src/buddy.py and try to > read these using D-Bus interface. > > Feedback and suggestions are requested. If some one wants to add some new > and interesting use case, they > can do it at: http://wiki.sugarlabs.org/go/Tagging_Proposal > > ps: I have ejabberd set up in my system and wanted to know how to use gadget > on it. If any one has done some > thing similar, please let me know. Looks like you are on the right track. Keep it up! Regards, Tomeu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] More information on font scaling problem
On Wed, Jun 3, 2009 at 16:40, James Simmons wrote:
> I mentioned before that I'm having a font sizing problem on the XO
> running .82. When I set a font on a textviewer it looks OK running
> under sugar-devel or SoaS by is *much* larger on the XO.
Sorry, in an earlier email i replied to you what would work in 0.84,
didn't realized you were talking about 0.82.
In 0.84 Pango knows the resolution of the screen and scales all fonts
accordingly. This means that by using, say 10, the font will always
look good in all hw.
In 0.82 didn't knew about the screen, so we were scaling all fonts by
using style.zoom().
Aleksey, do you have an idea about what can do activity authors that
wish to provide a single bundle that looks good both in 0.82 and 0.84?
Thanks,
Tomeu
> This is the
> code I'm currently using:
>
> self.scrolled = gtk.ScrolledWindow()
> self.scrolled.set_policy(gtk.POLICY_NEVER, gtk.POLICY_AUTOMATIC)
> self.scrolled.props.shadow_type = gtk.SHADOW_NONE
> self.textview = gtk.TextView()
> self.textview.set_editable(False)
> self.textview.set_cursor_visible(False)
> self.textview.set_left_margin(50)
> self.textview.connect("key_press_event", self.keypress_cb)
> buffer = self.textview.get_buffer()
> buffer.connect("mark-set", self.mark_set_cb)
> self.font_desc = pango.FontDescription("sans %d" % style.zoom(10))
> self.textview.modify_font(self.font_desc)
> self.scrolled.add(self.textview)
> self.textview.show()
> self.scrolled.show()
> v_adjustment = self.scrolled.get_vadjustment()
> self.clipboard = gtk.Clipboard(display=gtk.gdk.display_get_default(),
> selection="CLIPBOARD")
> self.page = 0
> self.textview.grab_focus()
>
> The "sans 10" font is really too small for SoaS but on the XO it makes
> 80 columns of text fill the width of the screen. Any ideas?
>
> James Simmons
>
>
>
>
> ___
> 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] Journal activity release 101 not tagged in Git
On Sat, May 30, 2009 at 10:32, Jonas Smedegaard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: RIPEMD160 > > Hi, > > As subject says, newest Journal release available at > http://dev.laptop.org/pub/sugar/sources/Journal/ (and not at > sugarlabs.org!), released january 2009, is not reflected as a Git tag at > git://git.sugarlabs.org/journal/mainline (neither at the git at > dev.laptop.org). Actually, the tag was in dev.laptop.org but not in git.sugarlabs.org, I have updated gitorious. http://git.sugarlabs.org/projects/journal/repos/mainline/commits/c70633c93154b8438321e253ed3b21f9c48dc7aa Please note that the journal is not an independent module since 0.84, so only if you are packaging 0.82 you should worry about it (and go to OLPC machines for tarballs etc.). Regards, Tomeu > Kind regards, > > - Jonas > > - -- > * Jonas Smedegaard - idealist og Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEAREDAAYFAkog7yMACgkQn7DbMsAkQLh68wCfQazWH8DWk5gZVQXbr7Zk+ZkZ > u3oAnjSn4SgnkTQJxx3r58h54JPShIby > =TAbd > -END PGP SIGNATURE- > ___ > 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] hulahop autotools seems broken
On Sat, May 30, 2009 at 10:20, Jonas Smedegaard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: RIPEMD160 > > Hi, > > The autotools shipped with hulahop 0.4.9 seems broken. Hi, have entered this ticket about it: http://dev.sugarlabs.org/ticket/936 Do you have already a patch for this? If so, please attach it to the ticket. Thanks, Tomeu > * The option --disable-maintainer-mode is unsupported > * libtool fails, seemingly treating compile flags as build options > > I have worked around it for now in the Debian packaging by regenerating > autotools, but ideally it should be fixed upstream. > > As a related note, I noticed (because I now keep close track of *all* > licensing info. including autogenerated files) that the autotools files > shipped do not always progress: sometimes (I believe it was with > sugar-toolkit but might be another core library) a newer release ship > with older autotools files (e.g. not shipping the - funny in our context > - - m4/ltsugar.mk file). > > > Kind regards, > > - Jonas > > - -- > * Jonas Smedegaard - idealist og Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEAREDAAYFAkog7FsACgkQn7DbMsAkQLg85QCbBHi7nw+LKxiPyeURHOdZtb0/ > 4NoAnjKAqC8iklP3E6k5ocmz7+vTJyxD > =8Wys > -END PGP SIGNATURE- > ___ > 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] Differing font sizes on the XO and in Sugar Emulation
On Fri, Jun 5, 2009 at 00:12, James Simmons wrote:
> Tomeu,
>
> Did you have a chance to try my Activity now that it has a font problem?
> Any ideas?
Sorry, haven't had time yet, please ping me again until I do it.
> Also, is there some way I could tell if my Activity was running on an XO and
> adjust the font size accordingly?
You could, but activities shouldn't have to worry about it, because
for an activity author is close to impossible to anticipate to all the
hardware out there and plan for it.
X desktops including Sugar have mechanisms for scaling the font size
given by applications so it ends up having a correct font size on the
screen. For some reason (a bug in the geode driver?) X is unable to
determine the correct resolution of the XO display so we are using a
hack in SoaS so that X knows it. This hack has been broken in recent
SoaS images but has been fixed in the last image.
Could you give it a try and see?
Thanks,
Tomeu
> James Simmons
>
>
> Tomeu Vizoso wrote:
>
> On Mon, Jun 1, 2009 at 18:26, James Simmons
> wrote:
>
>
> This weekend I attempted to resolve a bug report on Read Etexts where
> there was some strange behavior with font resizing. When I investigated
> I remembered how this bug came to be.
>
> It seems that if you DON'T explicitly set a font in your Sugar Activity
> it will look identical in sugar-emulator and on an XO. Unfortunately if
> you *do* set a font what looks like a reasonable sized font in the
> development environment will be a MUCH LARGER font on the XO. My goal
> with Read Etexts was to give a text view with the default font and allow
> the users to make it larger or smaller, just like Read has the Zoom In
> and Zoom Out feature. Now there does not seem to be a way to find out
> what font a text viewer is currently using. All you can do, from what I
> have seen, is to set it to a font and then change the font you have
> set. I wanted to set it to "sans 12". Looks good in sugar-emulator,
> ridiculously large on the XO.
>
>
> Hmm, setting a fixed font size of 10 should give you the same font
> size as used anywhere in the UI.
>
>
>
> Any insight on this problem would be appreciated. I tried the following
> code from one of Tomeu's postings:
>
> from sugar.graphics import style
> pango.FontDescription("sans %d" % style.zoom(72))
>
>
> We don't need to scale ourselves any more because Pango is already
> doing it for us.
>
> In the last soas image I have (almost one month old), the XO has a
> very small font size, not sure why but I will try a more recent one.
>
> Regards,
>
> Tomeu
>
>
>
> It did not have any effect.
>
> Thanks,
>
> James Simmons
>
>
> ___
> 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] [IAEP] collaboration testing session
On Fri, Jun 5, 2009 at 06:09, David Van Assche wrote: > Hi folks, > We are having a collaborative sugar testing session next week Wednesday > 10th June at 20:00 UTC (That is 4 pm EDT, 3pm EST, 2 pm CST, 1 pm MST, and > 12 pm PST, most of Europe that will be 9 pm, 8 pm for the UK) > > So far we have 5 people signed up, but more are welcome as we really want to > see how collaboration works on many activities where it isn't quite obvious. > We will be taking notes and storing log files of the sessions, and will > suggest ways in which the activity in question might be more collaborative, > or may need less of it (who knows :-) > > We will be testing the activities that come preinstalled on the openSUSE > sugar images, but we'd like to test various distribution methods (virtual > appliance, cd, usb, hd) and various distros (at least Fedora SoaS, openSUSE > sugar, Mandriva or Caixa Magica) I dont believe 0.82 images are compatible > with 0.84 for collaboration, so am afraid this is for 0.84 only... What do you mean by "compatible for collaboration" and why do you think it won't work between 0.82 and 0.84? Regards, Tomeu > Please > post your willingness to participate so we have an idea on who/how many will > be collaborating. We also need a volunteer to take notes, and a volunteer to > store logs files. There will of course be a transcript of the irc session > too (we will meet at #sugar-collaboration) We forsee this taking between 1 > and 2 hours... > > Here is the list of activities we will be testing, so make sure you have > them installed if you plan to take part (not all have collaborative > abilities, and for those that don't it can be a brainstorming session on > whether/how we can make them collaborative: > > sugar-finance > sugar-flipsticks-activity > sugar-freecell > sugar-imageviewer > sugar-implode > sugar-infoslicer > sugar-jigsaw-puzzle-activity > sugar-joke-machine-activity > sugar-jukebox > sugar-labyrinth > sugar-maze > sugar-memorize > sugar-moon > sugar-paint-activity > sugar-pippy > sugar-playgo > sugar-read > sugar-readetexts-activity > sugar-record > sugar-slider-puzzle-activity > sugar-speak > sugar-storybuilder > sugar-tamtam-common > sugar-tamtam-edit > sugar-tamtam-jam > sugar-tamtam-mini > sugar-tamtam-synthlab > sugar-analyze > sugar-turtleart > sugar-typing-turtle > sugar-viewslides > sugar-write > sugar-browse > sugar-irc > sugar-calculate > sugar-xomail (sugar-sweetmail) > sugar-cartoonbuilder > sugar-clock > sugar-colors > sugar-connect > sugar-drgeo-activity > xoEditor > sugar-evince > sugar-fiftytwo > sugar-chat > sugar-terminal > sugar-journal > sugar-physics > sugar-library > sugar-poll > sugar-tuxpaint > > kind Regards, > David (nubae) Van Assche > www.nubae.com > > > ___ > IAEP -- It's An Education Project (not a laptop project!) > i...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] cool animation w/ all-javascript space invaders
regrettably, i haven't tried it on the XO. given that there is no wireless where i am right now, probably won't try it immediately I see no reason why js animations can't work on the XO. It all depends on the particular user used. On Fri, 2009-06-05 at 10:03 +0200, NoiseEHC wrote: > Bryan Berry wrote: > > http://static.boundvariable.com/space-invaders/ > > > > does most of the animation that we need using raphaeljs, which uses svg > > and not canvas http://www.raphaeljs.com > > > > > Have you tried it on an XO? I just had this "experience". Seems to me > that we will not do animation with js ever... > -- Bryan W. Berry Technology Director OLE Nepal, http://www.olenepal.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [GSoC] progress report
On Thu, Jun 4, 2009 at 22:42, Lucian Branescu wrote: > 2009/6/4 Tomeu Vizoso : >> On Wed, Jun 3, 2009 at 22:00, Lucian Branescu >> wrote: >>> Since I missed the meeting, here goes. >>> >>> I've had a really hectic past few days, with 2 exams, just getting my >>> laptop back and constantly fighting my Uni network restrictions. But >>> it's better now, finished with exams and I figured out how to trick >>> the proxies. >>> >>> I played around with a template Site Specific Browser based on Browse, >>> almost identical up to now. I think I have SSB generation mostly >>> figured out, I need to start implementing it. I will probably have to >>> either change the existing bookmark mechanism or add a new one, >>> because bookmarks (specifically bookmarklets) should be part of data, >>> not state. >>> >>> I also tried Tomeu's technique for getting Gears to work, but that >>> xulrunner bug prevents any permissions being granted. My initial plan >>> was to test Gears with GMail, but it's not quite possible right now. >>> I'll look into it, but I'd rather not have to build xulrunner. >> >> I think we can workaround the dialog sizing issue in hulahop, ping me >> in IRC and we can see what we can do. > > Sizing isn't really an issue. The permission dialog appears and is the > size I would expect, but there's nothing in it. That sounds like a problem with the gears installation (cannot find the chrome). Once you solve that, you will find that the user cannot grant privileges to the site because the dialog is too small. >>> Also, now I'm more inclined to do the dbus functionality through >>> pyxpcom, mostly because of security issues. >> >> In my experience with Flash activities using Gnash, rather than giving >> access to the full DataStore API it's much more practical to provide >> some very simple state-saving functionality at first. If the python >> side can tell the JS side to load a buffer of data, and can ask it to >> hand a buffer to save in the DS, we can make 90% of activities work >> with very little effort. We can always make available later the full >> API or even generic DBus access. > > Saving state is not really an issue. At least current web apps are > built so that they do not lose any data if they suddenly die and some > of them also resume from where the left off. For most, it would be > enough to save the URL. Well, I was talking about saving state to the journal. > Ideally, it would be better to serialise the webview, if possible. What do you mean by that? Thanks, Tomeu >> >> Regards, >> >> Tomeu >> >>> This >>> http://sandbox.movial.com/wiki/index.php/Browser_DBus_Bridge#Gecko_version_notes >>> would provide dbus accessibility directly to javascript and I'd need >>> to handle security around that. Since my dbus needs are limited, I >>> prefer to instead do everything python-side and inject javascript >>> objects that do simple things (notifications, sounds, etc.). Of >>> course, dbus is still a secondary objective. >>> ___ >>> 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] cool animation w/ all-javascript space invaders
2009/6/5 NoiseEHC : > Have you tried it on an XO? I just had this "experience". Seems to me > that we will not do animation with js ever... Well, I don't think the js in that game is optimised at all. Very jerky on my mid-range (non-XO) laptop. There's lots of nice tricks you can do when scripting games in HLLs. I wrote fairly snappy games with Macromind Director 3 in the era of 1x CDROMS and the 'MPC' ;-) More recently, I've seen Mihai Suncan's Paintweb go from unusably slow to very usable on the XO. The xulrunner behind Browse.xo is fairly fast, you just have to be smart in how you use it :-) 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] cool animation w/ all-javascript space invaders
Bryan Berry wrote: > http://static.boundvariable.com/space-invaders/ > > does most of the animation that we need using raphaeljs, which uses svg > and not canvas http://www.raphaeljs.com > > Have you tried it on an XO? I just had this "experience". Seems to me that we will not do animation with js ever... ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Random numbers and the Journal
On Fri, Jun 5, 2009 at 01:54, Benjamin M. Schwartz wrote: > I'm using python's random.getrandbits() to generate unique identifiers in > my program. However, I've discovered that when I start it from the > Journal, I get errors, which I can trace to the random number generator > producing the same sequence of random numbers that was generated when I > started it the first time. It is as if the random seed is being reset > every time I launch from the Journal. > > Does anyone know what's going on here? No idea without more details. AFAICS, Sugar is not explicitly seeding the rng, that is done implicitly from python. Launching an activity from the journal is not that different, for activities not using sugar-toolkit it just boils down to an arg being added to the command line of the activity. For the other activities, some code will be executed about initializing the DS object and asking the concrete activity to do something with the journal entry. If you haven't done it yet, I would recommend doing the simplest activity you can think of, and try to reproduce this issue, to rule out a problem in your activity. Regards, Tomeu > Thanks, > Ben > > > ___ > 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
