Does your phone eat Ice-cream Sandwich?

Posted on by
Reply

What will you think if I say that I made a high utility application for android phones using cupcake? Or if I say that my friend just bought a brand new tiger and it works just fine. Or if I say that Google uses a porky pig to answer your questions? Confused? You must be thinking I am joking. In fact I am not. These are the real names given to software/projects by Android, Apple and Google respectively. Only these are the internal code names and not their commercial names.

These project code names are given to the projects being developed by companies, academicians or government. Code names are used to refer to the projects before they are released, and the commercial names for these projects, yet to be finalized. This way it also helps to differentiate the software in its development phase and release or pre-release phase. These are also used because they are easy to remember and a lot of fun.

Sometimes they are also used to maintain secrecy of the projects developed from their competitors and their codenames are also changed from time to time.

Some of the companies like Microsoft use and publicize their code names openly while companies like apple use them as internal name with their products. Some other never let their internal names out. It highly depends on individual company policy.

Some of the many code names that got popular are:

1) Microsoft:WIndows 7

 

Windows 95 Chicago
Windows xp Whistler
Windows vista Longhorn
windows 7 Vienna
Windows phone Mango

2) Apple:

Mac OS X 10.5 Leopard
Mac OS X 10.3 Panther 
Mac OS X 10.1 Puma
Mac OS X 10.6 Snow Leopard 
Mac OS X 10.4 Tiger

3) Android:"Ice-cream sandwich"

API level 3, NDK 1, Version 1.5 Cupcake
API level 4, NDK 2, Version 1.6 Doughnut
API level 8, NDK 4 Version 2.2x Froyo
API level 9-10, NDK 5, Version 2.3 – 2.3.2- 2.3.3 – 2.3.7 Ginger Bread
API level 11-12-13, Version 3.0-3.1 Honeycomb
API level 14-15, NDK 7, Version 4.0.1 – 4.0.2-4.0.3 Ice-cream sandwich

4) Mozilla:

 Firefox 1.0 Phoenix
 Firefox 1.5 Deer Park
 Firefox 2.0 Bon Echo
 Firefox 3.0 Gran Paradiso
 Firefox 3.5 Shiretoko
 Firefox 3.6 Namoroka

5) Google:

Similarly Google also comes up with real funny names for its search engine project. Like the projects for selecting top results were name panda and caffeine. And the project for Google’s feature of answering the questions was first named DAFFIE and then Porky Pig.  “Leaf”, “Foby”, “SweatNovember” and “Old Possum” are some among the others.

Now that you have a bit of extra knowledge about the internal code names of projects, you can go ahead and confuse your friends by using them instead of the commercial names.

 

Tools to make tag soup healthy

Posted on by
Reply

Anybody who has ever attempted to make a web page knows what a tag soup is. It’s the innocent crime that most of us, unwantedly make. An ill-structured,invalid HTML file is basically a tag soup. Since such a file never provides us with reliable output, it’s nothing but a soup of tag. The initial standards of web browsers were not equipped to parse the HTML files and so most of us ended up creating invalid HTML files or tag soups. Presently the web browsers have what we call the tag soup parser to detect and parse even an invalid HTML file.

A tag soup essentially refer to mistakes such as:

  • Incomplete tags
  • Mismatched tags
  • Improper styling(files lacking proper indentation)
  • Incorrect use of escape characters
  • Use of proprietary HTML extensions

Here is a small example of a very unhealthy and painful tag soup:

<html>

    <head>

<title>Lets nurture</title

<body>

        <h1> This is the case of mismatched tags</h2>

<img src=”letsnurture.jpg”, border=”5>

    </body>

        </html>

As a general practice, on receiving unexpected output from a file like that, one would go back to HTML file, manually scan the document and find the invalid or missing tags, correct them and try of run again. But in case of long html files containing multiple web pages (which is usually the case), this is a rather long and tiring process.

HTML5 comes to rescue at this point. Web browsers that are HTML5 compatible are able to handle tag soups. HTML5 has both forward as well as backward compatibility in the sense that in addition to supporting HTML4 it also houses many of the new features.HTML5 has laid down rules for parsing the HTML parsing which were not present before.

Apart from HTML5 there are a couple of tools that help fix the tag soup. Lets look at each one of them briefly:

1)HTML Tidy:  Developed by Dave Raggett  of World Wide Web Consortium (W3C) is a library which has its source code written in ANSI C. It is a tool for a number of platforms.  Fixes provided by HTML tidy includes:

  • Correcting missing or mismatched tags
  • Add missing items such as quotations, escape character
  • Provide proper styling and indentation to HTML files
  • Reporting use of propriety HTML extensions

2)Tag soup: Tag soup is a java library that parses HTML file.Although it is not as efficient as HTML tidy, it corrects the HTML file on the go. It does guarantee well-structured results: tags will wind up properly nested, default attributes will appear appropriately, and so on. It is free and open source.

3)Beautiful soup: It is a python library that turns the invalid HTML file into a parse tree. A Beautiful Soup constructor takes an XML or HTML document in the form of a string (or an open file-like object). It parses the document and creates a corresponding data structure in memory. If you give Beautiful Soup a perfectly-formed document, the parsed data structure looks just like the original document. But if there’s something wrong with the document, Beautiful Soup uses heuristics to figure out a reasonable structure for the data structure.

After a proper use of any of the above solutions one should have a properly structured file as follows:

<html>

    <head>

        <title>Lets nurture</title>

    <head>

    <body>

        <h1> This is the case of mismatched tags</h1>

        <img src=”letsnurture.jpg”, border=”5></img>

    </body>

</html>

So go ahead and drink a healthy tag soup.

One night at lets nurture ;)

Posted on by
Reply

Yesterday, we had a cracking night shift, few chaps in Lets nurture wanted to go home one  day before for Kite flying festival. So we decided to finish work in night. There are plenty of work going on Analysis of android app , our live reporting system as well as pile of digital marketing campaigns.

It was kind of night out then nightshift we can say music, snacks, cracking jokes and remembering few same kind of days. All in all we all felt it’s good to have one night stand sometime..

Its very unfortunate that we did not take any picture.. but it was fun though…

 

so here it is… our first post

Posted on by
Reply

It has been nice journey so far in 2011, Our Team Size grown , we expanded our wings in various technologies, we tried, failed , succeed and we enjoyed…… We know next year will bring more challenges and we are ready for that..

Our Blog was in “coming soon” state at least 6 months,so, now I am posting first blog post  .. We promise our blog posts will keep “lets nurture” meaning intact…

Thanks