பாட்டி வைத்தியம்!

தீராத விக்கலை நிறுத்த...
வழிகள் இரண்டு (2)

1. ஒரு 30 வினாடிகள்...
இரு காது துவாரங்களை விரல்களால் ....
அடைத்துக்க ொள்ளு ங்கள் ........
நின்று போகும் தீராத விக்கல்!

2. ஒரே ஒரு (1) கரண்டி அளவுக்குச் சமமாக சர்க்கரை
வாயில் போட்டு சுவையுங்கள ் ...
பறந்து போகும் விக்கல்!

தலைச்சுற்றுக்கு கறிவேப்பிலை தைலம்!

பெரியோர் முதல் சிறியோர் வரை தலைவலியை உணராதவங்களே இருக்க முடியாது.. அதோடு தலைச்சுற்று வந்தால் சொல்லவே வேணாம்.. இதிலிருந்து விடுதலை பெற இயற்கையின் வரப்பிரசாதமான கறிவேப்பிலை நமக்கு பெரிதும் உதவுகிறது. தலைச்சுற்றை அடியோடு விரட்டும் கறிவேப்பிலை தைலம் இதோ....

கறிவேப்பிலை - 200 கிராம்
பச்சை கொத்தமல்லி - 50 கிராம்
சீரகம் - 50 கிராம்
நல்லெண்ணை - 600 கிராம்
பசுவின் பால் - 200 மில்லி
கறிவேப்பிலையை காம்புகள் நீக்கி நன்றாக அரைத்துக் கொள்ளவும். பச்சைக் கொத்துமல்லியையும் மையாக அரைத்துக் கொள்ளவும்.
சீரகத்தை சுத்தம் செய்து மண் சட்டியில் போட்டு 200 மி.லி. பாலை ஊற்றி ஆறு மணி நேரம் மூடி வைத்திருந்து சீரகத்தை எடுத்து நன்றாக அரைத்துக் கொள்ளவும்.
ஒரு மண்பானையில் நல்லெண்ணையை ஊற்றி அடுப்பில் வைத்து சிறிது சூடேறியதும் அரைத்து வைத்துள்ள கறிவேப்பிலையை போடவும். ஐந்து நிமிடங்கள் மேலும் சூடேறியப் பிறகு பச்சை கொத்துமல்லியைப் போடவும். அதன் பின் ஐந்து நிமிடங்கள் கழித்து சீரகத்தையும் போட்டு, தைலப்பதம் வந்ததும் இறக்கி ஆறவிடவும். ஆறியதும் மெல்லிய துணியில் வடிகட்டிக் கொள்ளவும்.
நான்கு நாட்களுக்கு ஒரு முறை நல்லெண்ணைக்கு பதிலாக கறிவேப்பிலைத் தைலத்தை தேய்த்து குளிக்கலாம். தைலத்தை தேய்த்து குளிக்கும் அன்று குளிர்ந்த உணவு வகைகளை தவிர்க்க வேண்டும்.

How to Test Mobile Web Pages and Applications

When you are building web pages and applications for mobile devices, one of the most important steps you can take is testing. Testing gives you a good idea of what your readers are going to experience when they come to your site, and by fixing the major problems ahead of time, you can avoid issues with your customers later.
Testing a page or application for mobile uses the same checklist as testing for a full-sized browser. You need to check that the page looks good before you post it, and then check it after it’s live. But one step that many designers ignore is testing on mobile devices. Even if you don’t have a separate page for mobile users, you should test your pages on mobile devices—especially tablets. Tablet devices are growing in popularity every year and it’s becoming more and more likely that some of your visitors will be on tablets. Touch screen tablets have some different design requirements, even if you expect them to use your standard full-sized site.
The more devices you can test your website on, the better, but your priorities should be:

• iPad
• iPhone and iPod touch
• Android tablets
• Android phones
• other smartphones
• standard cellphones

Most people browsing the web on older cellphones and less-capable smartphones will be fairly tolerant of design problems. But as the devices get more sophisticated, so will the expectations of your readers.

How to Test

There are a few steps you should follow for all your web pages to test effectively for both mobile and desktop browsers.

1. First you should validate your HTML to make sure that there are no egregious errors. The HTML doesn’t have to be 100% valid, but knowing what errors there are can help you eliminate them as the cause of any problems you discover later.
2. Then you should test your site on all the browsers you have on your computer. I recommend downloading and installing Firefox, Chrome, Safari, and Opera if you don’t already have them installed. These are available for Windows and Macintosh.
3. If you have another computer with a different operating system (such as Mac OS or Linux) you should test your site on that computer’s browsers as well. A site might look fine on Windows Internet Explorer and then completely break on Macintosh Safari.
4. Once you’re confident that the site looks okay on desktop computers, you should change the window size of one of the browsers to a smaller size. If you’re using CSS3 media queries, this may even make the design look different. You can use a plugin like Web Developer Tools to resize your browser window to different pre-set sizes to see how it might look on smaller mobile screens.
5. If you don’t have access to a different machine, you should test in an online tool like BrowserCam.
6. Then test on as many mobile devices as you can. The more different devices you test on, the better your website or application will work for your customers.

Options for Testing on Mobile Devices

Test on the Real Devices
The best way to test a website on a mobile device is to load it on a mobile device. In general, this means posting the page or site to a live web server and then browsing to the page on the devices to test them.
Most people, of course, don’t have access to multiple mobile devices, but there are some options:

• Buy the devices
• Rent the devices
• Borrow one from a friend or relative or ask them to test it and send you a screen shot and their thoughts
• Go to a store that sells them and visit your site on the test machines
• Use a testing company (such as uTest) to help test your site on mobile
• Hire people with devices to test your site

Use an Emulator
If there is no way for you to get a real device to test on, you can use an emulator. Emulators don’t give you as good information because they can be slower than the real device, and they don’t show all the features of the devices. For instance, you access emulators with your mouse, not with a finger like on a touch screen.

How to Write Web Pages for Mobile Devices

Chances are you’ve seen how the iPhone can flip and expand web pages. It can show you the entire web page at a glance or zoom in to make the text you’re interested in readable. In one sense, since the iPhone uses Safari, web designers shouldn’t have to do anything special to create a web page that will work on the iPhone.
But do you really want your page to just work? Most designers want their pages to shine!
When you build a web page you need to think about who’s going to view it and how they are going to view it. Some of the best sites take into account what type of device the page is being viewed on, including the resolution, color options, and available functions. They don’t just rely on the device to figure it out.

General Guidelines for Building a Site for Mobile Devices

• Test on as many devices as you can
  The first thing you should do is view your site on an iPhone and as many different mobile devices or emulators as you can. While you can use emulators for all your testing, they really don’t give you the same feel as trying to navigate through a website on the tiny little screen, so test on actual devices as much as possible.
• Make your pages degrade gracefully.
  You can write your pages for Flash-enabled, wide screen browsers, but make sure that the critical information is visible even in a tiny monitor that can’t handle any special features (like cookies, Ajax, Flash, JavaScript, etc.). Anything beyond XHTML Basic will be beyond some cell phones. While most smartphones can handle all those things (except Flash on the iPhone, of course), other mobile devices can’t.
• Build a wireless specific page—and make it easy to find
  If you’re going to build a specific page for your cell phone and wireless customers—make it available. A great way is to put the link to the wireless page at the very top of your document, and then hide that link from non-handheld devices using the handheld media type. After all, most people come to your home page, even on cell phones—and if the link to your wireless page isn’t there, they’ll leave if the page is too hard to use.

Web Page Layout for SmartPhones

The first thing you should remember when writing pages for the smartphone market is that you don’t have to make any changes if you don’t want to. The great thing about most smartphones available is that they use Webkit browsers (Safari on iOS and Chrome on Android) to display web pages, so if your page looks okay in Safari or Chrome, it will look fine on most smartphones (just a lot smaller). But there are things you can do to make the browsing experience more pleasant:

• Remember that the screen is tiny. Smartphones will condense all those columns down into the tiny window, and this can make them very hard to read without zooming. Most users are used to zooming, but it can get tiresome. One long column of text is easier to read.
• Divide pages into smaller chunks. It can be difficult to read long segments of text on a cell phone, so putting them on multiple pages makes them easier to read.

Links and Navigation on iPhones

• The shorter the URLs are, the better. If you’ve ever tried to type in a URL on a cell phone, you’ll know that it’s a pain (except perhaps for teens who are used to sending a lot of text messages). Even on the iPhone it’s tedious to type in long URLs. Keep them short.
• But long link text is easier to tap. When on a page where several separate words are linked to different articles, all right next to each other, it can be very difficult to tap the correct one without zooming. Many people will just give up and go somewhere else. Links with 3-5 words in them are easier to click on the phone than 1-word links.
• Don’t put your navigation at the very top of the screen. There is nothing more annoying than having to page through screens and screens of links to find the information you want. If you’ve looked at web pages that were designed for cell phones, you’ll see that the first things that show up are the content and headline. Then, below that is navigation.
• Don’t be afraid to hide your navigation. Hiding navigation links with CSS or JavaScript and making them appear only when the user asks for it is a way to make the page easier for smartphone users.

Tips for Images on SmartPhones

• The images must be small. Yes, Android and iPhones can zoom and unzoom in on images, but the smaller they are, in both dimensions and download time, the happier your wireless customers will be. Optimizing images is always a good idea, but for cell phone pages, it’s critical.
• Images must download quickly. Images take up a lot of space on web pages when you’re viewing them from a mobile device. And while they are often very nice and make the pages look better when viewed on a full-screen web browser, they often get in the way on a mobile device. Plus when a smartphone user is on the cellular network, the last thing they want to pay for is downloading a bunch of huge images or navigation icons.
• Don’t put large images at the top of the page. Just as with navigation, it can be very tedious to wait for an image that takes up 3-4 screenfuls to load at the very top of the page. And this is extremely common on web pages. The only exception to this is if the reader knows that they’re going to get an image when they click, say in a photo gallery.

What to Avoid When Designing for Mobile

There are several things you should avoid when building a mobile friendly page. As I mentioned above, if you really want to have these on your page, you can, but make sure that the site works without them.

• Flash—most mobile phones do not support Flash, so it’s not a good idea to include it on your wireless pages.
• Cookies—many cell phones have no cookie support. iPhones do have cookie support.
• Frames - even if the browser supports them, think about the dimensions of the screen. Frames just don’t work on mobile devices - they’re very difficult or impossible to read.
• Tables—don’t use tables for layout on a mobile page. And try to avoid tables in general. They aren’t supported on every cellphone (although iPhones and other smartphones support them) and you can end up with strange results.
• Nested tables—if you must use a table, make sure not to nest it in another table. These are difficult for desktop browsers to support, and at best make the page load more slowly.
• Absolute measures—in other words, don’t define the dimensions of objects in absolute sizes (like pixels, millimeters, or inches). If you define something as 100px wide, on one mobile device that might be half the screen and on another it might be two times the width. Relative sizes (like ems and percentages) work best.
• Fonts—don’t assume that any of the fonts you’re used to having access to will be available on the cell phones.