This blog is NOFOLLOW Free!

Archive for June, 2010

How to put movies on Sciphone?

Ok, so in my review of the Chinese phone Sciphone I9+++, I was telling you that I wasn’t able to discover how to play the movies, other than the bad quality movies taken with the built-in camera. Now Iknow.

The key is to convert the movies to mp4 format and 177 x 144 size. That’s pretty ridiculous because the screen is huge, 320 x 240, and a movie which is 177 x 144 will become pixelated – but, at least, it will work.

The movies can be converted with the Super tool from Eright Soft:

Now, a little bonus. In addition to the review I must say that I have discovered a new interesting function of this phone: call recording. Simply put, the phone can record any conversation you have. As far as I know, this is avoided by the other phone manufacturers because of privacy concerns. But the Sciphone works great as a mobile phone with recording facility.

Player fatigue, the cause of bad results at World Cup?

Some surprising results emerged in the second round of group games played at the World Cup. France-Mexico 0-2, England-Algeria 0-0 and Italy-New Zealand 1-1. For some people the results are surprising, but let’s study a little bit the player’s fatigue. Let’s throw an eye on the following statistics: how many matches the initial 11 players of every team played this season for the club team, prior to the World Cup?

  • France vs. Mexico:  327 matches  vs. 241 matches (averages: 29,7 vs.  21,9 matches)
  • England vs. Algeria: 339 matches vs. 232 matches (averages: 30,81 vs. 21,09 matches)
  • Italy vs. New Zealand: 325 matches vs. 248 matches (averages: 29,54 vs. 22,54 matches)

Let’s analyse another 4 matches: Nigeria – Greece 1-2, Cameroon – Denmark 1-2, Germany – Serbia 0-1 and Spain – Switzerland 0-1.

  • Nigeria vs. Greece: 214 matches vs. 262 matches (averages: 19,45 vs. 23,81 matches)
  • Cameroon vs. Denmark: 291 matches vs. 272 matches (averages: 26,45 vs. 24,72 matches)
  • Germany vs. Serbia: 340 matches vs. 268 matches (averages: 30,90 vs. 24,36 matches)
  • Spain vs. Switzerland: 364 matches vs. 326 matches (averages: 33,09 vs. 29,63 matches)

What about some other teams?

  • Argentina’s last 11 (against South Korea): 319 matches (average: 29 matches for each player, but Messi played 35 matches this season; without him, the average is 27,4)
  • Brazil’s last 11 (against North Korea): 310 matches (average: 28,18 matches for each player)
  • Paraguay’s last 11 (against Slovakia): 250 matches (average: 22,72 matches for each player)
  • Chile’s last 11 (against Honduras): 301 matches (average: 27,36 matches for each player)
  • Uruguay’s last 11 (against South Africa): 310 matches (average: 28,18 matches for each player)
  • Netherlands last 11 (against Japan): 324 matches (average: 29,45 matches for each player)
  • Australia last 11 (against Ghana): 243 matches (average: 22,09 matches for each player)
  • Ghana last 11 (against Australia): 190 matches (average: 17,27 matches for each player)
  • USA’s last 11 (against Slovenija): 277 matches (average: 25,18 matches for each player)
  • Ivory Coast’s last 11 (against Brazil): 280 matches (25,45 matches for each player)
  • Portugal’s last 11 (against Ivory Coast): 248 matches (22,54 matches for each player)

Simply put, France, England, Italy and Germany played against a much fresher teams, while Nigeria is very unexperienced (in fact they even have a player, Shittu, that didn’t made any single appearance for its club team, Bolton Wanderers). Spain played against a tired Swiss team, but Spain’s team is extremely tired (in fact they are the most tired team in the tournament!). Based on this, my predictions are as follows:

  • Spain, Germany, England and Switzerland  will exit the tournament very soon (France is already out): this teams are physically and mentally too tired for such great competition.
  • Italy and Netherlands will be the European teams that will make the best result.
  • The new World Champion will be chosen between Argentina, Brazil or Uruguay. These teams gathered enough experience and, on the other hand, they are still fresh. The Final will be played between Argentina vs. Brazil or Argentina and Uruguay.

Nice forms with CSS3

Today I will start writing about CSS3. In fact, I’m waiting for IE9 in order to be finally able to use CSS3 code in my designs. Until then, we’ll only make… exercises.

Today I will show you how you can make nice forms using CSS3 selectors and properties. I will use the following: border-radius, box-shadow, :nth-child and :checked pseudo-classes.

What can you do with :checked pseudo-class?

Well, the :checked pseudo-class is gold for form designers because it makes possible to display or hide certain form elements function of what you’ve checked. If you need to show some form fields only to the people the filled-in certain preceding fields, :checked does the job.

Let’s take a look at the form (the screen below contains all the nice improvements):

Nice form using CSS3- The orange shadow under the title and the bevel effect were made with text-shadow property.

	h1 {
		text-shadow: 1px 1px White, 1px 1px 3px Orange;

- The rounded corners on the form are made using the famous border-radius property.

- The yellow tooltips appear only when you roll-over an element and are shown with the help of :nth-child pseudo-class. The <div> inside the second <td> of every <tr> row has by default display:none on it. But if you :hover the td, the <div> will show up.

	tr td:nth-child(2) div {
		border:1px solid #FFCC99;
		left: 210px;
	tr td:nth-child(2):hover div {

- The nice green focus effect appears because of the :focus pseudo-class. You can apply a box-shadow property on focused inputs and you get a nice usability effect.

- The last 2 fields, Business name and Business address, appear only if you check the “business owner” option. The syntax is very simple:

	div.forbusiness {display:none;} /* the content is hidden */
	input:checked + div.forbusiness {display:block} /* using the +
	selector we'll display the content when the preceding
	input is checked! */


  • On Internet Explorer 8, almost everything is broken. Quite normal!
  • On Firefox 3.6.3, a very fine shadow, marking the former top border place, will persist on the screen when you check the first input and show the <legend>.
  • On Opera 10.5+ when you want to display the <legend> the browser will “forget” the border-radius property.
  • On Safari 4.0 and Google Chrome instead of <legend> you will see a line.

View the live sample here.