Archive for June, 2010

Lightspark 0.4.1 released

Posted by Alessandro Pignotti in Lightspark on June 5, 2010

Lightspark 0.4.1 has been released today, fea­tur­ing ini­tial YouTube sup­port, and of course the usual per­for­mance improve­ments. As the plu­gin is cur­rently very sta­ble every­one is invited to test and mea­sure the CPU con­sump­tion of lightspark ver­sus Adobe’s player. Dur­ing my pre­lim­i­nary tests lightspark resulted up to twice as fast! This is of course not a com­pletely fair com­par­i­son, as Lightspark is not fea­ture com­plete yet.

It should be noted that only the YouTube videos served using the new AS3 player are sup­ported, those are the ones with the new UI. YouTube cur­rently uses a legacy AS2/Flash8 player for older con­tent and that should be fully sup­ported by Gnash.

More­over, with this release, Lightspark has been reli­censed from GPL3 to LGPL3 to avoid licens­ing issue when dis­trib­ut­ing the plu­gin with non GPLed browsers such as Chrome

, , ,

19 Comments

Lightspark 0.4.1 released

Posted by Alessandro Pignotti in Lightspark on June 5, 2010

Lightspark 0.4.1 has been released today, fea­tur­ing ini­tial YouTube sup­port, and of course the usual per­for­mance improve­ments. As the plu­gin is cur­rently very sta­ble every­one is invited to test and mea­sure the CPU con­sump­tion of lightspark ver­sus Adobe’s player. Dur­ing my pre­lim­i­nary tests lightspark resulted up to twice as fast! This is of course not a com­pletely fair com­par­i­son, as Lightspark is not fea­ture com­plete yet.

It should be noted that only the YouTube videos served using the new AS3 player are sup­ported, those are the ones with the new UI. YouTube cur­rently uses a legacy AS2/Flash8 player for older con­tent and that should be fully sup­ported by Gnash.

More­over, with this release, Lightspark has been reli­censed from GPL3 to LGPL3 to avoid licens­ing issue when dis­trib­ut­ing the plu­gin with non GPLed browsers such as Chrome

, , ,

19 Comments

Getting Things GNOME! — GSoC review (#2)

Posted by Luca Invernizzi in Getting Thing GNOME!, Google Summer of Code on June 4, 2010

Aloha again, planet Gnome!
This has been a nice week for my Google Sum­mer of Code project on Get­ting Things GNOME, fea­tur­ing:

  • A great speedup (via the refac­tor­ing of how the file con­tain­ing all the tasks is han­dled): the time for adding 1000 tasks in GTG has been reduced from 30 to 5 seconds!
  • A new test­ing class, which helped me find-n-fix a few bugs (ehi! test­ing works!)
  • The first request to merge of part of my code  (~3600 lines). I have to thank my men­tor Lionel Dri­cot, who has found the time to go through it.
  • A new twit­ter back­end. It still misses the UI to con­fig­ure the user­name and pass­word, but the basic func­tion­al­ity is there. Cur­rently, it adds to GTG any direct mes­sage match­ing a set of cho­sen tags (e.g., #todo).

I’m still work­ing on twit­ter authen­ti­ca­tion. I’m cur­rently doing it via the userid/password combo, but the cor­rect way to go should be Oauth. Unfor­tu­nately, python-twitter does not sup­port this. I’ve found a few libraries around the web, but none seem to work so far. Any hint  will be welcome.

Next week I’m plan­ning to fin­ish the twit­ter back­end, expand­ing the frame­work as I go. A nice thing is that, thanks to the frame­work, the twit­ter back­end (which is all a devel­oper should write to add a new back­end) is less than 100 lines long.

4 Comments

Getting Things GNOME! — GSoC review (#2)

Posted by Luca Invernizzi in Getting Thing GNOME!, Google Summer of Code on June 4, 2010

Aloha again, planet Gnome!
This has been a nice week for my Google Sum­mer of Code project on Get­ting Things GNOME, fea­tur­ing:

  • A great speedup (via the refac­tor­ing of how the file con­tain­ing all the tasks is han­dled): the time for adding 1000 tasks in GTG has been reduced from 30 to 5 seconds!
  • A new test­ing class, which helped me find-n-fix a few bugs (ehi! test­ing works!)
  • The first request to merge of part of my code  (~3600 lines). I have to thank my men­tor Lionel Dri­cot, who has found the time to go through it.
  • A new twit­ter back­end. It still misses the UI to con­fig­ure the user­name and pass­word, but the basic func­tion­al­ity is there. Cur­rently, it adds to GTG any direct mes­sage match­ing a set of cho­sen tags (e.g., #todo).

I’m still work­ing on twit­ter authen­ti­ca­tion. I’m cur­rently doing it via the userid/password combo, but the cor­rect way to go should be Oauth. Unfor­tu­nately, python-twitter does not sup­port this. I’ve found a few libraries around the web, but none seem to work so far. Any hint  will be welcome.

Next week I’m plan­ning to fin­ish the twit­ter back­end, expand­ing the frame­work as I go. A nice thing is that, thanks to the frame­work, the twit­ter back­end (which is all a devel­oper should write to add a new back­end) is less than 100 lines long.

4 Comments