Comme à l’habitude maintenant, Canal + nous propose un reportage plein d’émotions sur le dernier match des verts au Soudan! Nous tenons à remercier Guillaume Pivot et son équipe, pour avoir suivi l’EN durant toute cette phase retour! Chapeau Canal +.

RBAHNAKOUM YA L’MASSRI YA RASS L’AHMAR AHAHAH !
L’AALAMAT WAJDIN, ON VA CELEBRER LA VICTOIRE DES HOMMES, ARD EL AHRAR YA YEMAKOUM !!!
QULIFiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii SKARA F’EL AADYAAAAAAAAAAAN !!!
TAHYA EL DJAZAYEEEEEEEEEEEEEEEEEEEEEEEER !!!!

(ou mazal…)

[Vidéo: Algérie-Egypte. Soyons sages, ce n'est qu'un jeu]

Voilà, on s’y attendait presque tous ici, les avertissements de la FIFA il y a quelques jours à l’encontre de l’Égypte relativement au respect des conditions de sécurité qui devaient encadrer l’arrivée et le séjour des Verts au Caire dans de bonnes conditions nous laissaient présager le pire, surtout en connaissant la légendaire “hospitalité” égyptienne en matière footballistique envers les équipes étrangères qui viennent disputer des rencontres chez eux. Mais en réalité, quelque part, personne ne croyait vraiment à un tel scénario catastrophe et les algériens, bien que quelque peu méfiants, ont préféré faire de cette évènement une grande fête dans le plus pur esprit sportif, défilant dans les rues depuis des jours et jusqu’à des heures tardives, poussant des cries de joie et d’espoir, bardés de bananiers multicolores, agitant des drapeaux Algériens et scandant les innombrables chants de supporteurs aux rythmes endiablés pour soutenir les Fennec dans l’attente insoutenable de l’un des match les plus important de toute l’histoire du football Algérien avec, à la clé, une délivrance, un objectif pour ce collectif vert et rouge porté par tout un peuple, voir s’ouvrir les portes tant convoitées, tant attendues, de la coupe du monde de football, du Mondial 2010, cet été, en Afrique du sud.

Suivant comme jamais toute l’actualité de son équipe nationale, c’est à la fois la stupeur et la douche froide qui s’est abattue sur les Algériens ce jeudi soir quand ils apprirent qu’à son arrivée au Caire, tout le convois de l’équipe Algérienne a littéralement été conduit droit dans un traquenard, une embuscade en bonne et due forme, tendue lors de son trajet en bus entre l’aéroport et l’hôtel par une horde de supporteurs égyptiens comme possédés par le démon et sans que les forces de l’ordre n’interviennent. Se faisant caillasser par divers projectiles, insultés et injuriés comme les derniers des mal propre et avec une violence rarement observée. C’est une équipe nationale traumatisée et dénombrant plusieurs blessés (notamment à la tête) qui est arrivée tant bien que mal tard le soir à son hôtel dans un autocar complètement cabossé et aux vitres brisées qu’on aurait dit échappé d’une zone de guerre.

Cet article a pour objectif de rassembler et de centraliser toutes les vidéos, les témoignages, les articles de presse et tout ce qui concerne cette agression au fur et à mesure que les informations seront publiées tout au long de la journée. N’hésitez pas à nous faire partager vos propres infos, vidéos ou liens. [ Dernière mise à jour le 19/Nov à 23H00. Merci à tous les lecteurs qui ont contribué à cet article. Les Verts sont Qualifiés mais l'histoire n'est pas encore finie , les suites incroyables de cette affaire dans un nouvel article à paraitre sous peu, restez dans l'coin... ].

Les Vidéos:

[↑] Vidéo prise à l’intérieur du bus (Via. DzFoot).

[↑] Arrivée à l’hôtel.

[↑] Interview de Mansouri pour i>Télé.

[↑] Témoignage des supporters sur place.

[↑] La horde Égyptienne poursuivant l’équipe nationale.

[↑] La question de la sécurité. Matin de l’agression.

[↑] Déclarations mensongères du chauffeur du bus (Via. OBAlgier).

[↑] Des images qui font froid dans le dos. Rarouraoui, Saifi. Canal + Sport.

[↑] Le Chauffeur qui a témoigné n’était pas celui qui conduisait (Via. DZmag).

[↑] Agression des supporters algériens par les civiles et la police égyptienne.

[↑] Guet-apens organisé : L’Agression egyptienne en images (DzFoot/Canal+)

[↑] Le Ministre des sports Hachemi Djiar interpellé par les supporters Algériens.

[↑] Après le Match, les Algériens retenus en otage !

[↑] Wassila, journaliste de l’ENTV agréssée sur le terrain.

[↑] 15 Novembre, Aéroport, il n’est plus question de Football…

[↑] Arrivée des Algériens à Khartoum, les soudanais solidaires.

[↑] Redha City 16 témoigne pour El Chourouk du massacre du Caire.
(Âmes sensibles, attention!)

[↑] Reportage Canal+ en immersion avec l’EN: “Le Piège”.

[↑] L’agence Djezzy de Guelma proie des flammes et du saccage (15 nov. vers 20h).

[↑] Siège social Djezzy Orascom d’Alger, Dar el-Beida saccagé (15 nov. 21h).

[↑] Saccage et incendie de l’agence Djezzy de Constentine. (15 nov. vers 22h).

[↑] Saccage et incendie de l’agence Djezzy de Constentine 2. (15 nov. vers 22h).

[↑] Saccage de l’agence Djezzy de la Place Maurice Audin, Alger (15 nov).

[↑] Saccage de l’agence Djezzy de Bab El Oued, Alger (15 nov. vers 23h).

[↑] Saccage de l’agence Djezzy de Djelfa (16 nov. vers midi).

[↑] Saccage et incendie de l’agence Djezzy de Bejaïa (16 nov. vers 20h).

[↑] Agence Djezzy de Béchar détruite et incendiée (16 nov. vers 22h).

[↑] L’agence Air Egypte à Alger mise à sac et brulée (16 nov. vers 15H).

[↑] Manifestation à l’ambassade d’Egypte à Alger (15 nov. 23H).

[↑] Message de Rabah Madjer pour le match à Khartoum.

[↑] Témoignage de Souilah Salah Aougrout de retour d’Egypte.

[↑] Les Algerois déterminés à être présents au Soudan pour l’honneur.

[↑] Arrivée des premiers supporteurs algériens à Khartoum.

[↑] Le bus des joueurs egyptiens caillassé à Khartoum.

[↑] Message des supporteurs Algériens aux “journalistes” Égyptiens.

[↑] Musique: Réponse aux insultes des médias égyptiens: “Ya L’masri Ya Rass Lehmar”.

[↑] France 24: Attaque des intérêts égyptiens en Algérie + Témoignages des supporteurs de retour d’Egypte + Ambiance dans les rues d’Alger avant le match à Khartoum.

[↑] Pour ceux qui n’ont pas encore compris les enjeux cachés dans nos coeurs, voici.

[↑] Entrainement des Fennecs: Des soudanais fraternels.

[↑] Bande annonce Algerie Egypte à Khartoum le 18 novembre.

[↑] Prière du groupe algérien avant d’aller refermer les portes du Mondial aux égyptiens comme se sont refermées les eaux de la mer rouge sur Pharaon.

[↑] Un à ZERO, Win yesskoun echitan ya mhaynek

[↑] Fi Khater El Djazayer, Hna Rjal, Machi MOUNAFIKINES.

[↑] Joie !

[↑] 18 novembre, Palestine, Gaza, sans commentaire

Les Articles:

Jeune Afrique: Les algériens accusés d’avoir mis en scène l’attaque de leur bus.
Jeune Afrique: Algérie-Egypte : la Fifa pourrait prendre de lourdes sanctions.

El Watan: Après le guet-apens: Le ton monte entre Alger et Le Caire.
El Watan: Les élucubrations de la presse égyptienne.
El Watan: Jour du Match: Nous Somme Déterminés !
El Watan: Égypte 2 – Algérie 0. la minute de trop dans un match stressant.
El Watan: Un mort, 3 disparus et des dizaines de blessés.
El Watan: Mise en place d’un pont aérien entre Alger et Khartoum.
El Watan: Le siège de Djezzy à Alger saccagé.

Le Temps d’Algérie: Karim Matmour: «Un guet-apens».
Le Temps d’Algérie: Mourad Medelci :«Une grave agression».
Le Temps d’Algérie: Djezzy accuse Nedjma d’inciter à la violence contre eux.
Le Temps d’Algérie: 50 blessé et aucun mort selon l’ambassadeur Hadjar.

Liberté Algérie: Egypte-Algérie: La bataille du Net.
Liberté Algérie: Match maintenu pour aujourd’hui, la main molle de la FIFA.
Liberté Algérie: Point de presse de Hachemi Djiar, ministre des Sports.
Liberté Algérie: Dispositif impressionnant, mesures humiliantes pour les algériens.
Liberté Algérie: Nous sommes préparés pour jouer au Soudan.
Liberté Algérie: Oran, Air Algérie prise d’assaut.

Le Buteur: Des Journalistes Algériens et de France 2 Agressés.
Le Buteur: Au moins un algérien tué au Caire et des dizaines de blessés.

Tout sur l’Algérie: Un mort et 52 blessés parmi les supporteurs DZ.
Tout sur l’Algérie: Deux égyptiens travaillant pour djezzy agressés à Alger.
Tout sur l’Algérie: Confusion générale sur le nombre de morts en Egypte.
Tout sur l’Algérie: Le corps du supporteur algérien assassiné au Caire rapatrié.
Tout sur l’Algérie: Saccage complet du siège de l’opérateur Djezzy à Alger.
Tout sur l’Algérie: Les employés de Djezzy rapatriés d’urgence vers Egypte.
Tout sur l’Algérie: Le Bus de l’équipe Égyptienne attaqué à Khartoum.
Tout sur l’Algérie: Démonstration de force des Algériens à l’hôtel des égyptiens.
Tout sur l’Algérie: Témoignage de Rabah Saadane sur les événements du Caire.
Tout sur l’Algérie: (DGI) Redressement fiscal de 600 millions de dollars pour Djezzy.
Tout sur l’Algérie: Accrochage mercredi matin entre Algériens et Égyptiens à Khartoum.

AFP: Après le Match, les supporteurs algériens caillassés au Caire.
AFP: L’Égypte demande à l’Algérie d’assurer la sécurité de ses citoyens.

Le Parisien: Walter Gagg de la FIFA raconte l’agression.
Le Parisien: Egypte-Algérie : Au Caire, la rue ne croit pas à l’agression.
Le Parisien: Egypte-Algérie sous tension, Karim Ziani : «On n’a pas peur».
Le Parisien: Ambassadeur d’Algérie au Caire “Aucun mort coté algérien“.
Le Parisien: Lundi 16. Déjà plus de 20.000 algériens à Khartoum.

L’express: Les journaux égyptiens parlent d’un coup monté.

Football.fr: Lettre ouverte à M. Joseph Blatter, président de la FIFA.
Football.fr: Égypte-Algérie, rendez-vous est pris au Soudan.
Football.fr: Un supporteur Algérien à été tué au Caire.
Football.fr: Et pendant ce temps, la FIFA…

FIFA: L’Algérie au plus haut.
FIFA: Egypte-Algérie: La presse doit calmer les esprits.
FIFA: Communiqué concernant Égypte – Algérie.
FIFA: Saadan défie Shehata.
FIFA: Ruée des Algériens pour obtenir un billet pour Khartoum.
FIFA: 17 Nov. Nous étudions avec le plus grand sérieux les événements du Caire.

En Plus:

FIFA FAIL : Un site algérien lancé aujourd’hui pour dénoncer le traitement honteux de la FIFA envers l’équipe nationale algérienne. Url: http://fifafailed.info/

[Insolite] Boycott de Djezzy: Depuis quelques heures on assistes à la publication spontanée de plusieurs vidéos d’algériens face caméra détruisant leurs cartes SIM Djezzy du fameux opérateur égyptien Orascom, invitant les internautes à leur emboiter le pas, appelant ainsi au boycott de cette compagnie de téléphonie mobile implantée en Algérie depuis de années. (voir les vidéos ici).

.

Check out the video of Fennec(beta 4 ) running on n900..yes it looks brilliant !!

It sports the ‘awesome bar’ which helps in automatic url completion from web history.

It supports syncing with desktop browser,plug-ins and the tabbed browsing

Mozilla, the non-profit organization behind the awesome Firefox has released a Fifth beta version of its Firefox browser for Maemo platform.

Find the release notes at the below link.

http://www.mozilla.org/projects/fennec/1.0b5/releasenotes/

Beta 5 is supposed to have better user experience, bug fixes and performance.

This release is available for the Maemo OS2008 and Maemo 5 software platforms running on the Nokia N810 and N900 Internet Tablets

It has been almost 2 months since my last post and I have been heads down on bringing a new framework to life.

I discussed the 4 pieces involved in bringing automation to a new platform, and now we have what is shaping up to be a great approach for resolving the infrastructure and harness development.

What we have is a device specific agent which is written in a native language (C/C++) and does a small number of things (launch process, collect output, copy files to and from, query status such as processes, memory, cpu, disk, and lastly identify the device and os). This tool needs to act as a telnet server allowing us to telnet to it and execute a series of commands. Brad Lassey has developed such a tool for WinMo/CE which works partially on Win32 as well. I spent a couple days testing this interface and hammering out a python library to interact with a remote device. Now scripting file copy and process launching is easy. Clint has also used this tool to get mochitest and xpcshell running on Windows CE based devices!

That takes care of most of our infrastructure, now we need to get this stuff working on our test harnesses. My first task (only cleaned up one atm) is talos (see attached patch). This required massive changes to the Talos codebase, but no changes functionally for desktop based talos.

I found that in adding support to Talos for a remote device (as well as initial work for xpcshell and mochitest) that once we develop a DeviceAgent for a given platform there will be almost no additional work required to start running tests! I might be out of a job!!!

Next week I am going to work with Aki to get talos up and running (trial runs…don’t expect true miracles) on winmo and reporting to a staging graph server. Following that, we will start cleaning up our other harness code and getting mochitest, xpcshell, and reftests underway.

Stay tuned for progress updates and more details about a much needed updating to the way automation is run!

This is a non technical post

Read full story at ZooBorns

Sure, you’re up on Android smartphones and perhaps other Linux-based phone platforms, but the freewheeling world of open source includes many hugely useful telephony applications and platforms that are more unusual. There are useful offerings for businesses and consumers, and you can download and start using many of them for free. Here are eight flexible choices, including several brand new ones.

Birthing Voice Mashups — Jaduka, which has been an influential young company in the VoIP arena, offers open APIs that facilitate many of the “voice mashups” — voice, data and applications that are combined to create new services — appearing on the web. You can find out more about Jaduka here.

Android On the Desktop — Check out Cloud Telecomputers’ desktop VoIP phone based on the open-source Android OS. The touchscreen device runs on an open development platform called Glass, which former Motorola CEO Ed Zander has said “all business phones will look like” in 3-5 years — with Android at the core. Cloud Telecomputers is targeting OEMs that want to design around its hardware and software platform.

Central Communications Hub — Asterisk is an extremely powerful open-source telephony engine and platform that is especially popular with small businesses trying to keep communication costs down. It’s a full-blown PBX that includes call waiting, caller ID, distinctive ring, text-to-speech recognition and more. Businesses can also get subscription support for it.

Skype Meets Asterisk — Speaking of Asterisk, Digium, the company behind it, recently announced the availability of Skype for Asterisk. With the new download, Asterisk users can call landlines, cellular devices and other Skype users, right from any Asterisk-based phone. Cool, and another example of Skype’s focus on all aspects of business telephony.

See Me, Hear Me — Linphone is a free VoIP app for Windows and Linux that includes instant messaging capabilities and works with almost any web camera for either audio or video conferencing. It complies with the SIP protocol, an open standard for online telephony, and interoperates with most SIP-compatible phones and proxies.

Kissing Cousins — Open-Xchange and Racksoft recently announced a partnership that combines Open-Xchange’s open-source groupware with Racksoft’s telephony products. The combined solutions they’re working on could make conference calls, desktop calendars and mobile calendars work together seamlessly.

A Small Fox — Fennec, Mozilla’s mobile version of the open-source browser Firefox , is now out in an advanced beta that works on several platforms, and is native in Nokia’s new N900 device. Fennec is loaded with numerous imaginative user interface implementations, and is slated to work with many of the more useful Firefox extensions. Download it for Windows, Mac OS X or Linux here.

No Name, No Trail — Many people use the open-source application Tor on the desktop for anonymous browsing sessions. Thanks to a grant from the UC Berkeley Human Rights Center Mobile Challenge and the people behind The Guardian Project, now Android mobile phone owners can use it to do the same.  You can find the links you need to get going here.

This article also appeared on BusinessWeek.com.

They are geniuses who search for the place where food is concealed. Food and the jerky are served from an unexpected place and I am surprised. … Fennec Fox Pet FennecFox Animals Cute lovely life funny exotic フェネック キツネ 動物 ペット フェネックギツネ

http://www.youtube.com/watch?v=0OhKprdYcH4&hl=en

With little or no chance of ever being able to make it through the draconian approval process of Apple’s (s AAPL) iTunes App Store, Mozilla, the not-for-profit organization behind the Firefox browser, is betting on two major, if emerging, mobile operating platforms: Maemo, Nokia’s (s nok) new Linux-based operating system, and Google’s (s goog) Android OS. But don’t count on Mozilla supporting RIM’s (s rimm) BlackBerry OS anytime soon.

This weekend, during my onstage interview with Mozilla CEO John Lilly, I asked him what his plans were to get Firefox going on mobiles, especially since Webkit had gained so much attention and market share. “It is a different day, same story on the mobile as it was on the desktop,” Lilly quipped. On the desktop, Firefox continues to try to disrupt the entrenched incumbent, Microsoft’s Internet Explorer. “Sure, we are behind, but we didn’t want to do a browser that didn’t do the whole web,” Lilly said. “We wanted to build a browser that did everything — Javascript, CSS, Flash, SVG, video and audio. What that meant was we had to wait for a while for devices to get better to handle this modern browser.” Lilly said that Mozilla’s mobile browser, code-named Fennec, is Firefox with the most advanced rendering engine. “It is the most advanced mobile browser,” he said. Fennec is based on the Firefox 3.6 engine, which is not even available on the desktop just yet.

And Lilly isn’t just tooting his own horn. I’ve been playing around with an early version of Nokia’s N900 device, and Firefox is perhaps its single biggest standout feature. It works just like it does on a desktop and, thanks to the seamless integration of AwesomeBar, a smarter version of a URL bar that uses Mozilla Weave, I can get access to all my bookmarks, my browsing history and other preferences. (Related Post: “Coming Soon: A Mozilla App for the iPhone“)

When I asked Lilly about why Mozilla is interested in the Nokia Maemo, which is still not a viable platform, he explained that Mozilla was betting on the future and Maemo was a modern mobile OS built with the Internet in mind. “Nokia is invisible in the U.S., but that is not the case in rest of the world,” Lilly said. Even if N900 doesn’t prove to be the device that gets explosive adoption, then the next Maemo device will be the one that gets traction. Mozilla will release Firefox for Windows Mobile and then Android, he said.

Why? Because he thinks there is a lot of overlap among folks who use Firefox and those who might buy Android-based devices.  When I asked why not develop Firefox for BlackBerry, Lilly said that because the BlackBerry is a Java-based platform, Mozilla had no interest in building a browser for it, regardless of the number of devices in use. Mozilla also has some misgivings about Symbian, preferring to develop for Maemo instead.

“Until recently, Android was Java, but they released Android NDK which uses C/C++ and that is what we program in, so we are now looking at developing Firefox for Android,” said Jay Sullivan, vice president of Mobile for Mozilla.

“Mozilla Firefox will be the first mobile browser to support add-ons,” boasted Sullivan, pointing to the fact that nearly 2 billion Firefox add-ons have been downloaded to date, and they’ve spawned successful companies such as StumbleUpon. He expects similar traction for Firefox on the mobile. “We have been spending a lot of time on making sure that JavaScript and our engine work really fast on ARM processors,” Sullivan said. “That has taken some time.”

Subscribe to GigaOM Pro and get this indepth analysis of the mobile apps market for $79.

The reason: Mozilla wants developers to embrace the more open HTML5 standards instead of developing separately for different mobile platforms. “For a company of 20 people, it is hard to support multiple platforms,” Lilly said. “Even if one platform takes 20 percent of the  market, there are other platforms you still need to develop for, and that isn’t easy for a small company. So that is why we are with Google in supporting HTML5 technologies.”

Like Lilly, Sullivan acknowledges that they have their work cut out for them: Webkit-based browsers and Opera are the dominant players in mobile, and Firefox will need to prove itself.  The good news is that mobile is a much bigger market than desktops; multiple browsers and companies can thrive. With Nokia, Mozilla has a willing (and somewhat desperate) ally, and that is a good start.

This video is in German, but don’t worry if you’re Anglophone-only. This is a hands on demo of the N900’s Mozilla Browser, and the alternative Fennec Browser Beta demonstrated via TV out. Compared to the default Mozilla Browser, Fennec has side loading tabs, different icons/buttons and it seems it doesn’t load flash content (at least not the youtube video).

Hmmm…TV-out from a 3.5mm jack – it’s still something pretty extraordinary, and I’m guessing a lot of people aren’t really aware that their Nokia devices might have it. It’s just another one of those features Nokia didn’t really emphasize to make consumers aware and let them take advantage of such a cool feature.

Maybe if Apple decide to go TV-out via the 3.5mm jack, Nokia will follow suit and mention it as a feature (like, er, 3.5mm jacks in general and “copy and paste”….features Nokia pretty much took for granted, but something Apple spun around as being new)

Are you mobile browser addict that tired and bored using the damn famous Opera Mini?
Even Opera Mini has reach their 5 version, (still in beta) but it’s a impresive development. Most people only know that Opera is the only one web broser for their handheld. This post show that Opera Mini just one of many web browser for your mobile phone. Opera Mini not standing alone buddy.

UCWEB Browser

The UCWEB Browser home display just like Opera Mini version 4 or below. Compact and simpe to use. But UCWEB Browser is better on tabbed browsing that allow user to open various website on the same time.

Online media playback function is available in UCWEB 6.3. You may watch the hottest TV channels and the splendid original video clips, as well as listen to the latest popular songs on your phone with UC Browser 6.3.

If you are using two or more email account of Google or Yahoo then doing it from one browser could be more hectic as it is little difficult to type username and password from mobile key pad . So, Lets move towards our second option, UCWEB. Its well and good browser which have option to resume download if it fails due to any reason. Beside that it provides convenient way to copy and paste any urls or contents.

UCWEB also support RSS, google search, online media streaming.

Visit UC Browser web | Download Free

Bolt Browser

Bolt built using Webkit core as same as Apple’s Safari. Bolt is the rising rival for Opera Mini. With their bunch of new feature on their Beta 3. You can enhance favourite site and rearrange your favorite entries using the ‘Grab’ feature, automatic detection of device security capabilities, ability to disable images, non JSR-75 Build for BlackBerry platforms, improved support for file upload feature, BlackBerry-specific settings confirmation improvement for Preferences page and so many features lies.

Bolt also comes with the lite version which created in response to user requests, to allow Bolt to run on resource-constrained mobile devices with limited memory, CPU power, and bandwidth. While not as feature-rich as the regular version, BOLT lite features a small footprint (~140 KB).

Visit web | Download Free

TeaShark Browser

Just like Bolt, TeaShark using the webkit as web engine not only support multitab browsing, but colorful tab. Color tagging helps user to keep favorite pages organized. There are 8 pre-defined colors from which user can choose from.

There’s an intelligent mouse for easy navigation. The cursor jumps to the next link to click, saving you the trouble. Navigate as fast or slow as you need with page up and down, left and right shortcuts. Jump to content: the display snaps to the text you’re reading.

Visit web | Download Free

SkyFire

Skyfire is the only mobile browser that supports full Flash and Windows Media videos, including Flash 10 and Silverlight 2.0. It’s awesome.

But unfortunately, currently, Skyfire runs on Windows Mobile (smartphones and PPC) and Nokia N and E Series (Symbian S60, 3rd Edition) phones. Where is for Java?

Visit web | Download Free

Fennec

Fennec is Mozilla’s reach on mobile browsing experience. The wellknown Firefox goes mobile? Yes, They said all Firefox feature build for your handset are ready to smack the Opera Mini down.

Built on the same core technology as Firefox, Fennec has many of the same great features as the desktop version including tabs that let you browse multiple sites at once, one-click bookmarking to quickly organize websites, the Awesome Bar for super-easy navigation, a growing collection of add-ons that let you customize your mobile browser plus, Fennec boasts a touch-enabled interfaced optimized for the small screen.

Sad news, The Fennec only runs on Maemo based handheld, which is develop by Nokia in N770, N800, N810 and their next  N900.

Visit Fennec Web | Visit Maemo web | Visit Nokia Project on Maemo

In a recent discussion with ctalbert, we discussed what is the right course to take for getting automation running on windows mobile and how we could avoid this 6 month nightmare for the next platform. The big question we want to answer is how can we implement our automation for talos and unittests on Windows Mobile and not have to reinvent the wheel for the next platform?

Our current approach to date has been to take what we have for Firefox (which works really good) and adapt it to work on a mobile device. This approach has not been very successful in the development of Fennec (functionality, UI, performance) nor the automation of unittests and talos.

After further thought on this subject, I find there are 4 area to focus on:

1. Infrastructure and Tools
2. Porting Harnesses and Tests
3. Managing Automation and Failures
4. Mobile Specific Automation

Each of these 4 areas are tightly coupled yet require a much different solution than the others. Let me outline each area in a bit more detail describing the problem, our solution, and a longer term solution.

Infrastructure and Tools:

This is the area of all the assumptions. The OS you run on, network connectivity, available disk space for test and log files, tools to manage your environment and processes and a method for doing this all automatically. I am going to leave out the build and reporting infrastructure from this topic as those take place separately and don’t run on the device.

Our first port of this to maemo was not as difficult because we could use python to manage files, network, and processes just as we do on a desktop OS. Minor adjustments had to be made for running on storage cards, using different python libraries (we have a limited set available on maemo) and system tools, as well as changing requirements for process names and directory structures. Also maemo has ssh functionality, a cli terminal, and a full set of command line tools to manage stuff.

Moving onto Windows Mobile, we don’t have the tools and infrastructure like we do on Maemo. This means we need to spend a lot of time hacking our communications required for automation and scripting tools like python. Almost all process interaction (create, query, kill), need custom code to take care of it. This has presented us with a problem where we don’t have the luxury of our OS support and tool support. Our approach to date has been to write (or in the case of python, port) our tools to make them work on the device. Unfortunately after 4 months we don’t have a working set of automation that people are happy with.

How can we create infrastructure that is scalable to all platforms? From what I have seen, we need to move away from our reliance on all tools on the device. This means no python or web server on the device, no test data on the device, and assume we won’t be able to store log files or use common system tools. I would like to see a custom communication layer for each OS. So for Windows Mobile, we would create a server that lives on the device which: ensures we have ip connectivity, provides file system tools, process management tools, and allows for the OS to reboot and come back connected. The other half of this is a job server which sends commands to the device and serves/collects test data via a web interface. I know this is a big step from where we are now, but in the future it seems like the easiest approach.

Porting Harnesses and Tests:

This focus area is more about making sure the environment is setup correctly, the right tests are run and useful logs are created. This can be developed without a full infrastructure in place, but it really requires some knowledge about the infrastructure.

For Maemo, a lot of work was done to extract the unittests from the source tree and retrofit the tools and harnesses to manage tests in “chunks” rather than running them all at once. We have done a lot of work to clean up tests that assume preferences or ones that look for features.

The challenge on Windows Mobile is without an infrastructure the tests rely on we need to do things differently. Very few bugs were found that prevented tests from running while porting tests to Maemo. For WinMo, that is a different story. We cannot run the web server locally, cannot load our mochitests in an iframe, and have trouble creating log files. All of these issues force us to morph our testing even further away from where it was and realize that we need to do this differently.

What I see as the ultimate solution here is to setup a “test server” which serves all our test data. Each test would remove the dependencies it has on localhost and work with a test server given that it has an IP address. We would then have an extension for Firefox/Fennec which would serve as the test driver to setup, run, and report the test results. This would allow for any mobile device (that supports addons), desktop, or community member to install the addon and start testing.

Managing Automation and Failures:

This is a much smaller topic than the previous two, but once we do have data generated, how do we keep generating it reliably and use it to our advantage?

Right now our toolset of Tinderbox and Buildbot do a great job for Firefox. I believe that we can still utilize them for mobile. There might be specific issues with them, but for the purposes of running Talos and Unittests, we need something that will take a given build, send it to a machine, run tests, and figure out when it is done. We even have great tools to notify us via IRC when a test suite fails.

The danger here is when testing on a new device or product, we find hundreds if not thousands of failures. The time required to track those down and file bugs is a big job by itself. When you have a large number of bugs waiting to be fixed it won’t happen in the same week (or quarter). This brings up a problem where nobody pays attention to the reported data because there are always so many failures.

The other problem that occurs is with so many crashes and running tests in smaller chunks or 1 by 1, we end up with smaller log files and lose the ability to get the pass/fail status that our test harnesses for Firefox rely upon. I know simply looking for a TEST-UNEXPECTED string in *.log is a reasonable solution, but as we have learned there are a lot of corner cases and that doesn’t tell you which tests were not run.

How can we make this better? Our first step to solving this problem is LogCompare. This is a log parser that uploads data to a database and lets us compare build by build. This solves the problem of finding new failures and ignoring known failures if we want to. A final solution to this would be to expand on this idea and have test runners (via the addon) upload test result blobs to a database. Adding more tools to query status of a test run, missed tests, etc… can be done giving us more detailed reports than just pass/fail. In the long term a tool like this can be used to look at random orange results as well as getting status of many community members pitching in CPU time.

Mobile Specific Automation:

The last piece of the puzzle is to create specific test cases to exercise mobile features. This is fairly trivial and great work has already been done for bookmarks and tabs using browser-chrome. This is important as the more developers we have working on mobile and the more branches we have, the greater the frequency of regressions.

Here is the problem, the mobile UI is changing so rapidly that it would take a full time job to keep up with the automation. This is assuming you have comprehensive tests written. It is actually faster to install a build and poke around the UI for 10 minutes than it is to keep the tests maintained. I know in reality there will be moving pieces on a regular basis, but right now we are ripping big pieces out and rewriting everything else. As a reference point the tab functionality has changed 4 times in the last year.

Looking at the regressions found in the last couple weeks we would not have found those with automation. There is a great list of stuff we want to automate in the Fennec UI and almost none of those would have failed as the result of a recent regression. This means we need many more tests than a few hundred core functionality tests. It also points out that we are not going to catch everything even if we all agree that our tests are comprehensive.

What is the best way to utilize automation? Until a 1.0 release, we have to expect that things will be very volatile. We should fix the automation we currently have and require developers to run it on their desktop or device before checking in. This should be a 1.0 requirement. If a developer is changing functionality, fix the tests. Why this works is we don’t have a lot of tests right now. This will serve more of a purpose to fix the process than finding bugs. Post 1.0, lets build up the automation to have decent coverage of all the major areas (pan, zoom, tabs, controls, awesomebar, bookmarks, downloads, addons, navigation), and keep the requirement that these tests need to run for each patch we checkin. The time to run a test will be fast on a desktop <5 minutes.

Summary:

While we seem to be flopping around like a fish out of water, we just need some clear focus and agreement from all parties about the direction and we can have a great solution. My goal is to be forward looking and not dwell on the existing techniques that work, yet are still being improved. After looking at this from a future point of view I see that developing a great solution to meet our needs now can also allow for greater community involvement leading to greater test coverage for Fennec and Firefox. The amount of work required to generalize this is equivalent to the same work for a specialized solution for Windows Mobile.

I encourage you to think about ways we can reduce our test requirements while allowing for greater flexibility.

Google Chrome

Google lancia la terza versione del browser Chrome
Google ha rilasciato Chrome 3.0 nella sua veste definitiva. Il lancio della nuova versione del browser vuole preparare il terreno per il raggiungimento degli obiettivi che sono stati fissati a Mountain View: la conquista di una fetta di mercato doppia, rispetto a quella attuale, entro dodici mesi con un ulteriore raddoppio nel giro di due anni.

Ecco le date di rilascio di tutte le prossime versioni di Firefox
Stando alla “roadmap” pubblicata sul sito web di Mozilla, Firefox 4.0 potrebbe debuttare nel mese di Ottobre o Novembre 2010. Nello stesso periodo gli sviluppatori contano di rilasciare la seconda versione definitiva di Fennec, il browser destinato ai dispositivi mobili, in particolare agli “smartphone”. Sarà proprio la quarta versione del browser opensource ad introdurre le novità più importanti.

Internet Manifesto, proposta per il futuro
Può un documento redatto dai blogger gettare le basi per la costruzione di una nuova forma di società? Potrebbe, ma solo se tutti ci staranno a leggere e ascoltare.

Il super-WiFi è finalmente nato
IEEE ha ufficialmente ratificato lo standard 802.11n, ultima evoluzione della tecnologia wireless, aprendo la strada all’arrivo dei primi dispositivi basati sulla specifica finale

Yes, I know… very cheesy title.  I really couldn’t think of anything else.  Regardless of the title, the beginning of this week has been very eventful so far.  During Monday’s class, we were given another series of to-do-list by our educators.  Not a very hard list, like last week’s, but lengthy enough.  I’ll summarize them for you in the following:

• Create Wiki accounts on MDC and wikimo
• Consider creating a Twitter account in conjunction with your blog
• Dial-in to a Mozilla status call
• Join a Mozilla mailing list
• Comment on another student’s blog
• Watch online lectures/readings
• Complete lab by Friday

So… not too hard at all.  At this point, I’ve crossed out the ones I’ve done.  But, I’m going to begin by telling you about the item on that list I was most excited about doing… the Mozilla status call.

I’ve been on conference calls before, working at Smart Systems for Health Agency (which merged with eHealth Ontario) over summers in my first couple of years in Seneca.  So, I wasn’t really nervous to begin with… maybe a little anxious.  David emailed us on the day the call was taking place.  I hadn’t had a chance to look at the scheduled calls at that point, and I should’ve done so sooner because I found out that most of the conference calls happens earlier in the week.  So, I was a little unprepared for it but managed to squeeze in the time to be on the call.  I was even a little early and found time to check how the phone system worked (testing the *1 to unmute).  David informed me to join the IRC #planning channel as they would be using it as well.  As can be seen in the picture below, there were plenty of people in the IRC channel during the beginning of the call.  However when I called in, the system told me there were 18 other people on the line.  Therefore, I’m thinking most of the other people on that channel were mostly just idling.  The amount of callers later rises up to 43 people, when my late friend called-in and informed me of the number.

Amount of users in #planning channel during the beginning of the call

It was an interesting setup.  Most of the time, there was one speaker detailing their issues/comments/resolutions on the topic at hand. People also discussed ideas on IRC while there was a speaker.  It gives a bit of freedom for everyone else, even with a solitary speaker talking about more important things.  The general atmosphere in the meeting wasn’t heavy-laden either… especially in IRC.  The following joke was told when doing the Blocker report on IRC.

[14:05] <jimb> Aren’t beta-blockers a class of drugs?
[14:05] <bsmedberg> so are alpha-blockers!

There was also a detailed outline on the items they would be covering… it was posted (require Google login for link) on the Mozilla Planning Group (require Google login for link) in Google Groups.  Even with the outline, I was a little lost throughout most of the call.  I am a little apprehensive in saying this, but I was having a hard time keeping up with some of the subjects they were talking about.  I may still be a little disoriented now, if it wasn’t reading my friend’s, Nadim, post on the subject.  I looked up a link he had on his post, which involved the meeting’s minutes.  Written down and with plenty of links, the meeting was easier for me to follow.  I suppose I’ll have to do a bit of research on past meetings before my next chance at listening-in.

Continuing on my to-do list, I joined two mailing lists that interested me.  The Firefox application development list and the mobile platform development list.  Those were the two lists that most interested me.  Now, I’m not completely sure how they work.  Reading over some of the mail I received, it seems to me that their development conversations between certain people and these conversations get shared to everyone on the list.  I believe you can also participate in said conversations, but you would have to reply to the mailing list in order to do so.  Someone correct me if I’m wrong please, which is very likely.

On to the final item that I’ve completed on my to-do list.  The item is creating an account on the Mozilla Development Centre (or MDC) and Mozilla wiki (aka wikimo).  I’ve also created profiles on them that link back to my email and this blog.  On that note, I will finish up the rest of the items on my list closer to the end of the week.  I have taken a quick look through the article by/in Ars Technica.  It looks promising and has me excited about reading it.  In fact, I’ll probably do that right after this post!

• Much improved panning/scrolling performance
• Improved start-up time
• Revised theme
• Support for running in full screen
• Numerous bug fixes
• Improved painting performance
• Improved UI polish
• Support for touch sensitive directional pad on HTC devices
• Improved kinetic panning with directional locking
• Ability to scroll frames
• Improved zooming support
• Support for multiple screen sizes

A propos de la solution TooFAX® :

TooFAX® est une solution moderne et innovante de Fax dématérialisé, vous permettant l’envoi, la réception, et la sauvegarde de Fax par Internet et ou par e-mail. Depuis votre ordinateur de bureau ou portable, votre PDA, etc, TooFAX® vous permet de faxer par mail sur les 5 continents.

TooFAX® est la synthèse entre les atouts du Fax (rapidité, valeur juridique) et l’aspect pratique de l’e-mail.

Actualité de TooFAX® :

- Site internet : http://www.toofax.com

- Site du service : http://www.service.toofax.com

- Vidéos de démonstration : http://www.video.toofax.com

- Groupe Facebook : http://www.facebook.com/toofax

- Club des utilisateurs de la solution : http://www.club.toofax.com

- Actualités en ligne des services TooFAX® :  http://twitter.com/toofax

- Blog  officiel de la gamme de services TooFAX® : http://toofax.wordpress.com/

- Base de données gratuite de n° de fax pour vos opérations de faxing : http://www.toofaxdata.com // <![CDATA[

function f_protect(mailto,toshow,u,d)
{
if(mailto)
document.write(""+toshow+"")
else
document.write(""+u+"@"+d+"");
}
//
]]>

If you have a Windows Mobile handset, you can now try out Alpha 3 of Mozilla’s Fennec mobile browser. You can download Mozilla’s Fennec Alpha 3 if you redirect your mobile browser to tinyurl.com/fennec3. Check out all of the new updates in Fennec Alpha 3 below, courtesy of WMPowerUser. You can also check it out on Brad’s blog here and Mozilla’s website here.

• Much improved panning/scrolling performance
• Improved start-up time
• Revised theme
• Support for running in full screen
• Numerous bug fixes
• Improved painting performance
• Improved UI polish
• Support for touch sensitive directional pad on HTC devices
• Improved kinetic panning with directional locking
• Ability to scroll frames
• Improved zooming support
• Support for multiple screen sizes

This builds upon the feature set of the previous releases:
Easy navigation to Web content:

• Bookmarks, including tags
• Smart URL bar (“awesome bar”)
• Tabbed browsing with thumbnail images
• Integrated Web search – built into the URL bar
• Easy access to multiple search engines
• Built in error console
• Support for add-ons

Web content:

• Maximize content by auto-hiding controls and URL bar
• Zoom in and out

Security:

• Instant Web site ID (“Larry“)
• Password manager
• Popup blocker
• Clear private data

Devices services integration:

• Click on a phone number to initiate a call
• JavaScript API to get device location

Also:

• Searchable download manager
• Preferences pane
• Add-ons manager, including ability to directly find and install add-ons

[WMPowerUser]

Mozilla released the latest alpha version of their new mobile browser Fennec for Windows Mobile. It brings many new features and fixes, such as improved startup time and a caching system to help scrolling on a page. They have also added support for a wider range of screen resolutions, and for those of us running an HTC Touch Pro support for zoom via the directional pad has been included in this release. Being an alpha release, it’s still a bit on the buggy side, but is very a promising browser for mobile phones. The final release should give other browsers a run for their money.