Aththiwaaram - THE FOUNDATION

“Aththiwaaram”

THE FOUNDATION

Story for ScriptNet SL

By
B.Thavapalan

September 2006

---

Synopsis

The great displacement that occurred in 1996 Sri Lanka shook the foundations of many people’s lives. Kavari was one of the victims. Kethees loved her, faced challenges, and tried to overcome them. But the circumstances of that time led to misunderstandings.

Eventually, they overcame everything and fulfilled their parents’ dream by getting married.

---

Treatment

Kanthasamy, father of Kavari, was a contractor in their hometown. They were doing well, but they lost their property and wealth during the displacement in 1996. When they returned home as the peace talks started, Kavari lost one of her legs and her mother to landmines near their house entrance. As she used a Jaipur Leg for a long time, she did not appear disabled. But Kanthasamy became a heart patient.

Later, with some help from distant relatives, Kavari and her father shifted their lives to Negombo. As Kavari had attended a sewing training course organized by an NGO during their displacement, she was able to earn some income for the family. Kanthasamy became an active land broker, and Kavari worked in a tailor shop. Together, father and daughter developed themselves with the help of their knowledge and friends.

After years of hard work, Kanthasamy bought a three-wheeler on lease with the bank manager’s recommendation. He became a three-wheeler driver as well as continuing land brokering. He was known as KK, “Kaani Kanthasamy.” The vehicle also helped with his daughter’s transport.

Katheeswaran, called Kethees, was 30 years old but looked younger. He worked in a textile shop as a salesperson in Negombo town. Kethees lived with his parents; his father was a retired mathematics teacher, and his mother was a housewife. In his mind, Kethees dreamed of owning his own textile business. His ability and interest in business encouraged his boss, Sundaram, the shop owner, to support him. Kethees often visited Colombo with his boss, sometimes alone, for business purposes.

In the late 1990s, Sundaram decided to expand his business into ready-made and tailor-made garment manufacturing. While developing this idea, Kethees met Kavari. As she was hardworking and active, she caught his interest. They became friends—business friends and family friends.

Later, Kethees learned about her disability and her family situation. He helped her start her own tailor shop and arranged for her products to be sold in Sundaram’s shop.

One day, Kethees expressed his love for her. Initially, Kavari pretended to accept his love, but later she said she had no intention of marrying and that her father meant everything to her. Kethees became sad and hopeless, and his performance at work declined. Sundaram noticed and discussed it with him. With his boss’s encouragement, Kethees decided to speak to KK.

When Kethees talked to Kanthasamy about his love for Kavari, KK respected his feelings but gave him a challenge: Kethees must own a house before marrying Kavari. If he could do that, KK promised to convince his daughter. Kethees agreed and promised not to disturb them until he owned a house. But Kavari knew nothing of this arrangement, even as her feelings for Kethees deepened.

Kethees discussed the matter with his boss, who agreed to help him financially and look after Kethees’s family for a while. Kethees then left Negombo for Colombo.

During the peace talks, property development in the capital boomed as many migrated Sri Lankans wished to invest. Numerous flats were being constructed in and around Colombo. With his business talent and textile contacts, Kethees decided to supply curtain materials to the new flats. Thanks to his pricing, wide range, and quality, he became a known supplier to leading companies and property developers.

Meanwhile, Kavari and KK were also doing well and learned of Kethees’s progress. Kethees had selected a house with land and updated Sundaram, who informed KK that Kethees might marry soon. KK began expecting Kethees’s visit.

However, at the same time, Kethees’s father fell ill. To care for his parents, Kethees moved to Dehiwala, postponing his house purchase. KK, upset by the missed visit, believed that Kethees had abandoned his daughter because of her disability. He grew ill from worry.

Eventually, Kethees resumed his house search and located a property in Wattala. But before he could finalize it, KK suffered another heart attack and was admitted to Negombo hospital. The day Kethees came to speak to KK, doctors had already advised transferring him to Colombo. KK was taken by ambulance while Kethees followed later by van. Their vehicles crossed, but neither realized.

When Kethees reached Negombo, neighbors told him KK had been moved to Colombo. On his way back, he met Kanesh, who wrongly claimed KK had promised his daughter to a Colombo textile businessman, and that Kavari’s love for a local man had caused conflict and KK’s heart attack. Heartbroken, Kethees returned to Colombo, refusing to meet KK or Kavari.

At the hospital, doctors required funds for KK’s bypass surgery. After deep thought, Kavari contacted Kethees for help. Understanding the situation, Kethees provided the money without conditions. The operation succeeded.

KK later sold his three-wheeler to repay Kethees. When they visited Kethees’s home, his parents revealed how much hope he had placed on KK and Kavari, and how devastated he was by the misunderstanding. After clarifying the truth, everyone realized the mistake and set out to find Kethees.

They found him at the house he had planned to buy, just after he had canceled the booking. There, the truth was revealed to him.

Kethees married Kavari. He bought land in Wattala, and both families attended the house foundation ceremony together.

---

End

How CSS class attributes have to be ordered

How to order a CSS class attributes.

The poll result of http://css-tricks.com/poll-results-how-do-you-order-your-css-properties/ shows many uses or suggest to order them by Randomly or Grouped by type.
But here is my point, when you have number of attributed stacking up, there are changes for attributes to get duplicate. see the following example

.selector {
    position: absolute;
    z-index: 10;
    top: 0;
    font-family: sans-serif;
    right: 0;
    bottom: 0;
    left: 0;
    width: 100px;
    height: 100px;
    padding: 10px;
    border: 10px solid #333;
    margin: 10px;
    background: #000;
    color: #fff;
    font-size: 16px;
    text-align: right;
    display: inline-block;
    overflow: hidden;
    padding: 10px;
    box-sizing: border-box;
}

Padding is duplicated on the above sample, which is bit difficult to find it out. So Randomly is a bad habit.

My selection will be Alphabetic, where you got to know A-Z to sort them up and will easily out the above issue.

.selector {
    background: #000;
    border: 10px solid #333;
    bottom: 0;
    box-sizing: border-box;
    color: #fff;
    display: inline-block;
    font-family: sans-serif;
    font-size: 16px;
    height: 100px;
    left: 0;
    margin: 10px;
    overflow: hidden;
    padding: 10px;
    padding: 10px;
    position: absolute;
    right: 0;
    text-align: right;
    top: 0;
    width: 100px;
    z-index: 10;
}

Yes, as sampled here https://github.com/necolas/idiomatic-css#format, grouping by type is cool. But I still recommend to sort by name with in the group.
So my finals will be


.selector {
    /* Positioning */
    bottom: 0;
    left: 0;
    position: absolute;
    right: 0;
    top: 0;
    z-index: 10;
   
    /* Display & Box Model */
    border: 10px solid #333;
    box-sizing: border-box;
    display: inline-block;
    height: 100px;
    margin: 10px;
    overflow: hidden;
    padding: 10px;
    width: 100px;
   
    /* Other */
    background: #000;
    color: #fff;
    font-family: sans-serif;
    font-size: 16px;
    text-align: right;
}


I have no plan to discuss about Line length here as its the baddest way, I think.

24 Hours of Australia - The Book

On 2010 Feb 3rd, I have been to Brisbane city council library on the next week of my arrival, rather than talk about the library now I wish to mention about a a book. I have red, seen and heard about many books but I do remember some of them only. May be those are the ones impressed me, a lot.

I wish to make a record of a book here, 01.01.2000 – 24 Hours of Australia. This is a collection of photographs around thousand numbers by may be two hundred Australia's leading photographers. The specialty of the photos are they have been taken between mid-night 31 December 1999 to mid night of 1 January 2000, yes on the millennium day; the first day of this 20th century.

What an idea, its actually sponsored by Fuji Films. As you think it contains photos from party, fun, celebration, events, people, hope, diving, underwater, recreational activities and happiness. Although contains floods, accidents, deaths, injuries, eyes with expectation, a doctor on his way by an aircraft while speaking to the patient over the phone until he reach him as so many. Because for the nature it is just another day.

http://www.biblio.com/book/112000-24-hours-life-australia-j/d/647335447

A better way to show, Unfortunately Java script is disable in your Browser

Introduction

For better user experience and for great user interface .. bla bla ...
Enabling JavaScript is A must on each websites.(period)

Scenario

Let me point out the issues on notifying the visitor to enable JavaScript if that is disabled on the current browser.
There are enough sites pop-up to guide you when you Google it.

But let me walk you through the tricks of handling it.

1. We should be able to place a text on the web page it self. as follows

Unfortunately JavaScript is disable in your Browser. We suggest you enable JavaScript for a better web experience.

2. But we need ti display this message only when the JavaScript is disabled

<noscript>
    Unfortunately Javascript is disable in your Browser. We suggest you enable java script for a better web experience.
</noscript>

3. Ok, where do we need to place this snip on the html. Yes, with in the <body>, But placing it at the top is not a good idea for SEO. So place it at the bottom, but before </body> tag.
4. But we need to hilight this piece of text and show up on the browser, here we need css to come in.
4.1 First lets add a <div > to the text
<noscript>
    <div id="noscript">
        Unfortunately Javascript is disable in your Browser. We suggest you enable Javascript for a better web experience.
    </div>
</noscript>
4.2 Now we need css to target #noscript to show up this.
#noscript {
    clear: both;
    left: 0;
    padding: 4px 10px;
    position: absolute;
    top: 0;
    width: 100%;
    z-index: 2000;
}

4.3 If I add some colours to this, then
#noscript {
    background: none repeat scroll 0 0 #000;
    clear: both;
    color: yellow;
    font-weight: bold;
    left: 0;
    padding: 4px 10px;
    position: absolute;
    text-align: center;
    top: 0;
    width: 100%;
    z-index: 2000;
}

5. Cool, but we need to hide this again if javascript is enabled, let use js to hide this when document is ready

<script>
    $(document).ready(function() {
        $('#noscript').hide();
    });
</script>


6. Enjoy

My Visual Studio 2008 Installation got broken : Fixed

Visual Studio 2008 is not working properly in my PC. Its show the message '{Project Name} could not be opened because the Microsoft Visual C# 2008 compiler not be created, Please re-install Visual Studio'.

I have tried as it is in http://connect.microsoft.com/VisualStudio/feedback/details/417251/cannot-create-new-projects-or-open-existing-projects, issue not solved. Yes, the command "devenv /resetskippkgs" works but not improvement on the VS2008.

So my next options is reinstall, but I have tried to reinstall / repair / Un-install  VS2008 ended up as following

Visual-Studio-2008-Repair-error

Visual-Studio-2008-Uninstall-error

Then, I was searching Microsoft tools and found the following which can un-install Visual Studio 2008 even when its failing with the standard uninstall option.

http://download.microsoft.com/download/5/3/3/533A214F-86D6-47DA-A052-7242F6B1A06D/sqlpubwizinstaller.exe

10 Laws of Productivity

You might think that creatives as diverse as Internet entrepreneur Jack Dorsey, industrial design firm Studio 7.5, and bestselling Japanese novelist Haruki Murakami would have little in common.

In fact, the tenets that guide how they – and exceptionally productive creatives across the board – make ideas happen are incredibly similar. Here are 10 laws of productivity we’ve consistently observed among serial idea executors:

1. Break the seal of hesitation.

A bias toward action is the most common trait we’ve found across the hundreds of creative professionals and entrepreneurs we’ve interviewed. While preparing properly as you start a new project is certainly valuable, it’s also easy to lose yourself in planning (and dreaming) indefinitely. We must challenge ourselves to take action sooner rather than later. The minute that you start acting (e.g. building a physical prototype, sharing a nascent concept with your community), you start getting valuable feedback that will help refine your original idea – and move forward with a more informed perspective.

2. Start small.

When our ideas are still in our head, we tend to think big, blue sky concepts. The downside is that such thinking makes the barrier to entry – and action – quite high. To avoid “blue sky paralysis,” pare your idea down to a small, immediately executable concept. Can you trial the idea of a multi-day festival with a smaller performance series? Take an idea for a skyscraper and model it in miniature? Work out the flow of an iPhone app by sketching on paper? Once you’ve road-tested your idea on a small scale, you’ll have loads more insight on how to take it to the next level.

3. Protoype, prototype, prototype.

Trial and error is an essential part of any creative’s life. As Ze Frank says, usually when we execute an idea for the first time, it kinda sucks. The important thing is to synthesize the knowledge gained during the process to refine the idea, and create a new-and-improved version. Serial idea-makers like Jack Dorsey, Ben Kaufman, and Studio 7.5 all attest: Prototyping and iteration is key to transforming a so-so idea into a game-changing product. Rather than being discouraged by your “failures,” listen closely and learn from them. Then build a new prototype. Then do it again. Sooner or later, you’ll hit gold. To avoid ‘blue sky paralysis,’ pare your idea down to a small, immediately executable concept.

4. Create simple objectives for projects, and revisit them regularly.

When working on in-depth projects, we generate lots of new ideas along the way. This can lead to a gradual expansion of the project’s goals, or “scope creep.” This insidious habit can make it impossible to ever really complete anything. The best way to avoid it is to write down a simple statement summarizing your objective at the start of each project. (If you have collaborators, make sure there is agreement about the objective.) And then – this is the part we overlook! – revisit it regularly. When scope creep starts to happen, you’ll notice.

5. Work on your project a little bit each day.

With projects that require a serious infusion of creative juice – developing a new business plan, writing a novel, or just learning a new skill – it’s incredibly important to maintain momentum. Just as when you run everyday, the exercise gets easier and easier, the same thing happens with your brain. Stimulate it regularly each day, and those juices start to flow more freely. As Jack Cheng argues in a great blog post, “Thirty Minutes A Day”: “the important thing isn’t how much you do; it’s how often you do it.”

6. Develop a routine.

Part of being able to work on your project a little bit each day is carving out the time to do so. Routines can seem boring and uninspiring, but – on the contrary – they create a foundation for sparking true insight. In his recent memoir, What I Talk About When I Talk About Running, famed Japanese author Haruki Murakami writes about how a rigorous routine – rising at 5am and going to bed at 10pm every day – is crucial to his impressive creative output. (In a side note: Alex Iskold derives a series of lessons for start-up entrepreneurs from Murakami here.)

7. Break big, long-term projects into smaller chunks or “phases.”

To help manage expectations and stay motivated for year-long or even multi-year endeavors, break each project into smaller chunks that only take a few weeks or a month to complete. The dual benefit of this approach is: (1) making the project feel more manageable, and (2) providing incremental rewards throughout the project. It’s crucial to pause periodically to take stock of what has been accomplished – even if there’s a long way to go. With projects that require a serious infusion of creative juice, it’s incredibly important to maintain momentum.

8. Prune away superfluous meetings (and their attendees).

Few activities are more of a productivity drain than meetings. If you must meet (and this should be a big “if”), make sure everyone knows what needs to be accomplished from the outset. If people are present who don’t help out with achieving that objective, let them leave. Qwest COO Teresa Taylor, recently interviewed in the NYT‘s Corner Office, starts her meetings with the question, “Do we all know why we’re here?” and then follows with, “Does everyone need to be here?” To trim the runtime of internal meetings, you can also try the standing meeting.

9. Practice saying “No.”

Creative energy is not infinite. Seasoned idea-makers know that they must guard their energy – and their focus – closely. Take author Jim Collins for example. His books Built to Last and Good to Great have sold millions of copies. His business acumen and insights are in demand. Yet, “even though Collins demands over $60,000 per speech, he gives fewer than 18 per year.” More than that and Collins wouldn’t have enough time to focus on the research and writing that yield those bestselling books. When you’re in execution mode, keep in mind that “unexpected opportunities” also mean distraction from the work at hand. Saying no is an essential part of the productivity equation.

10. Remember that rules – even productivity rules – are made to be broken.

Did we say develop a routine? This and other tips here should only be followed as long as they are working. If forward motion has become impossible with your current routine, try something else. Whether it’s taking a long distance trip, popping into the art museum, walking around the block, or talking to a perfect stranger, make sure you occasionally shake up your normal routine. Breaking habits offers new perspective and helps recharge us to head back into the fray.


How About You?
Is there an idea you could break the “seal of hesitation” on and start executing right now?
Are there other rules of thumb you’ve found particularly useful for making ideas happen?

by Behance Team

'Tsunami Bomb' - The water bomb for distruction

The United States and New Zealand conducted secret tests of a "tsunami bomb" designed to destroy coastal cities by using underwater blasts to trigger massive tidal waves. The tests were carried out in waters around New Caledonia and Auckland during the Second World War and showed that the weapon was feasible and a series of 10 large offshore blasts could potentially create a 33-foot tsunami capable of inundating a small city. The top secret operation, code-named "Project Seal", tested the doomsday device as a possible rival to the nuclear bomb. About 3,700 bombs were exploded during the tests, first in New Caledonia and later at Whangaparaoa Peninsula, near Auckland.


The plans came to light during research by a New Zealand author and film-maker, Ray Waru, who examined military files buried in the national archives. "Presumably if the atomic bomb had not worked as well as it did, we might have been tsunami-ing people," said Mr. Waru.


"It was absolutely astonishing. First that anyone would come up with the idea of developing a weapon of mass destruction based on a tsunami ... and also that New Zealand seems to have successfully developed it to the degree that it might have worked." The project was launched in June 1944 after a US naval officer, E A Gibson, noticed that blasting operations to clear coral reefs around Pacific islands sometimes produced a large wave, raising the possibility of creating a "tsunami bomb".

Waru told the UK Telegraph:

“Presumably if the atomic bomb had not worked as well as it did, we might have been tsunami-ing people,” said Mr Waru. “It was absolutely astonishing. First that anyone would come up with the idea of developing a weapon of mass destruction based on a tsunami … and also that New Zealand seems to have successfully developed it to the degree that it might have worked.”

More