The Japanese have always loved fresh fish. But the water close to Japan has not held many fish for decades. So to feed the Japanese population, fishing boats got bigger and went farther than ever. The farther the fishermen went, the longer it took to bring the fish. If the return trip took more time, the fish were not fresh.

To solve this problem, fish companies installed freezers on their boats. They would catch the fish and freeze them at sea. Freezers allowed the boats to go farther and stay longer.

However, the Japanese could taste the difference between fresh and frozen fish. And they did not like the taste of frozen fish. The frozen fish brought a lower price. So, fishing companies installed fish tanks. They would catch the fish and stuff them in the tanks, fin to fin.

After a little thrashing around, they were tired, dull, and lost their fresh-fish taste. The fishing industry faced an impending crisis! But today, they get fresh-tasting fish to Japan.

How did they manage? To keep the fish tasting fresh, the Japanese fishing companies still put the fish in the tanks but with a small shark.

The fish are challenged and hence are constantly on the move.

The challenge they face keeps them alive and fresh!!!!!

Some of us are also living in a pond but most of the time tired and dull ?

Basically in our lives, sharks are new challenges to keep us active. If one steadily conquers challenges, one can be happy.

Challenges keep one energized. We have the resources, skills and abilities to make a difference. Put a shark in the tank and see how far one can really go!





"Weakness of attitude becomes weakness of character" – Albert Einstein

Master Page Framework (Using default.master – Top Down approach)

· Basic idea is to overwrite default css class (core.css, calendar.css).
· Create custom.master page under _catalog\masterpages by save as from default.master
· Do not rename any page by share point designer
· Keep check in & publish by major version, time to time as MOSS automatically control version.
· Attach custom.css in master page under tag.……….< link href="GHI.CSS" type="text/css" rel="stylesheet" >
· Use multiple classes to overwrite necessary attribute.
· Overwrite only those classes which are required to change.Example master page has these entry Now “ms-body” is written in core.css and its linked with master page by default.ms-body{background-color: blue;padding-left: 10px;}now we have two ways to change it from blue to green(1) Write own class i.e. .bg-color{background-color: green;}and use it inside tag’s class attribute Note: It will only overwrite background-color property not “padding-left” property.(2) Otherwise overwrite “ms-body” class inside custom.css.ms-body{background-color: green;}
· Always separate css class, by properly commenting them, according to their use in master page./*======== for top nav bar ============*/css classescss classes/*======== for left nav bar ============*/css classescss classes/*======== for Calendar===============*/
· Do not delete any single thing from master page
· Never drag any table portion while designing master page. It will cause the absolute position. Always change in code by typing. Remember that “design view” is to understand the structure and we can reach to the code quickly, by selecting desire component
· Hide component, when it’s not require, but never delete it.
· Concentrate on all css class while changing one css class. like while changing color attribute “ms-banner”, one need to go through “DIV.ms-banner” & “SPAN.ms-banner” & “DIV.ms-banner A”
· Remove changes immediately in master pages while it’s not effecting. Concept is to make only useful changes and keep master page as clean as possible.
· Save as master page into hard disk while sing anybody. Never roll back this operation.Do not restore css files which saved under hard disk. Its cause’s css class partition.
· Check master page in all possible pages.