This is just concept of the Apple iPhone 6. . .
Saturday, 28 September 2013
CHECK RAIN IN YOUR CITY ???
Now Check Rain In Your City ? ... Try it
sraining.in, which serves for nothing saying whether or not it's raining in a given city at this very moment (it also shows the current weather conditions)
First Goto
http://isitraining.in/
Type in the name of your city and hit Enter
See the your City rain and Weather result
Its raining Your City Result "YES" Other Wise "No"
sraining.in, which serves for nothing saying whether or not it's raining in a given city at this very moment (it also shows the current weather conditions)
First Goto
http://isitraining.in/
Type in the name of your city and hit Enter
See the your City rain and Weather result
Its raining Your City Result "YES" Other Wise "No"
Friday, 27 September 2013
How to find the IP address of the sender in Gmail.
When you receive an email, you receive more than just the message. The email comes with headers that carry important information that can tell where the email was sent from and possibly who sent it. For that, you would need to find the IP address of the sender. The tutorial below can help you find the IP address of the sender. Note that this will not work if the sender uses anonymous proxy servers.
Finding IP address in Gmail:
1.Log into your Gmail account with your username and password.
2. Open the mail.
3. To display the headers,
* Click on More options corresponding to that thread. You should get a bunch of links.
* Click on Show original.
4. You should get headers like this:Gmail headers : nameLook for Received: from followed by a few hostnames and an IP address between square brackets. In this case, it is 65.119.112.245.That is be the IP address of the sender!
5. Track the IP address of the sender.
Finding IP address in Gmail:
1.Log into your Gmail account with your username and password.
2. Open the mail.
3. To display the headers,
* Click on More options corresponding to that thread. You should get a bunch of links.
* Click on Show original.
4. You should get headers like this:Gmail headers : nameLook for Received: from followed by a few hostnames and an IP address between square brackets. In this case, it is 65.119.112.245.That is be the IP address of the sender!
5. Track the IP address of the sender.
WPF vs WinForms
In the previous Post, we talked about what WPF is and a little bit about WinForms. In this Post, I will try to compare the two, because while they do serve the same purpose, there is a LOT of differences between them. If you have never worked with WinForms before, and especially if WPF is your very first GUI framework, you may skip this chapter, but if you're interested in the differences then read on.
The single most important difference between WinForms and WPF is the fact that while WinForms is simply a layer on top of the standard Windows controls (e.g. a TextBox), WPF is built from scratch and doesn't rely on standard Windows controls in almost all situations. This might seem like a subtle difference, but it really isn't, which you will definitely notice if you have ever worked with a framework that depends on Win32/WinAPI.
A great example of this is a button with an image and text on it. This is not a standard Windows control, so WinForms doesn't offer you this possibility out of the box. Instead you will have to draw the image yourself, implement your own button that supports images or use a 3rd party control. With WPF, a button can contain anything because it's essentially a border with content and various states (e.g. untouched, hovered, pressed). The WPF button is "look-less", as are most other WPF controls, which means that it can contain a range of other controls inside of it. You want a button with an image and some text? Just put an Image and a TextBlock control inside of the button and you're done! You simply don’t get this kind of flexibility out of the standard WinForms controls, which is why there's a big market for rather simple implementations of controls like buttons with images and so on.
The drawback to this flexibility is that sometimes you will have to work harder to achieve something that was very easy with WinForms, because it was created for just the scenario you need it for. At least that's how it feels in the beginning, where you find yourself creating templates to make a ListView with an image and some nicely aligned text, something that the WinForms ListViewItem does in a single line of code.
This was just one difference, but as you work with WPF, you will realize that it is in fact the underlying reason for many of the other differences - WPF is simply just doing things in its own way, for better and for worse. You're no longer constrained to doing things the Windows way, but to get this kind of flexibility, you pay with a little more work when you're really just looking to do things the Windows way.
The following is a completely subjective list of the key advantages for WPF and WinForms. It should give you a better idea of what you're going into.
WPF advantages.
It's newer and thereby more in tune with current standards
Microsoft is using it for a lot of new applications, e.g. Visual Studio
It's more flexible, so you can do more things without having to write or buy new controls
When you do need to use 3rd party controls, the developers of these controls will likely be more focused on WPF because it's newer
XAML makes it easy to create and edit your GUI, and allows the work to be split between a designer (XAML) and a programmer (C#, VB.NET etc.)
Databinding, which allows you to get a more clean separation of data and layout
Uses hardware acceleration for drawing the GUI, for better performance
It allows you to make user interfaces for both Windows applications and web applications (Silverlight/XBAP)
WinForms advantages.
It's older and thereby more tried and tested
There are already a lot of 3rd party controls that you can buy or get for free
The designer in Visual Studio is still, as of writing, better for WinForms than for WPF, where you will have to do more of the work yourself with WPF.
The single most important difference between WinForms and WPF is the fact that while WinForms is simply a layer on top of the standard Windows controls (e.g. a TextBox), WPF is built from scratch and doesn't rely on standard Windows controls in almost all situations. This might seem like a subtle difference, but it really isn't, which you will definitely notice if you have ever worked with a framework that depends on Win32/WinAPI.
A great example of this is a button with an image and text on it. This is not a standard Windows control, so WinForms doesn't offer you this possibility out of the box. Instead you will have to draw the image yourself, implement your own button that supports images or use a 3rd party control. With WPF, a button can contain anything because it's essentially a border with content and various states (e.g. untouched, hovered, pressed). The WPF button is "look-less", as are most other WPF controls, which means that it can contain a range of other controls inside of it. You want a button with an image and some text? Just put an Image and a TextBlock control inside of the button and you're done! You simply don’t get this kind of flexibility out of the standard WinForms controls, which is why there's a big market for rather simple implementations of controls like buttons with images and so on.
The drawback to this flexibility is that sometimes you will have to work harder to achieve something that was very easy with WinForms, because it was created for just the scenario you need it for. At least that's how it feels in the beginning, where you find yourself creating templates to make a ListView with an image and some nicely aligned text, something that the WinForms ListViewItem does in a single line of code.
This was just one difference, but as you work with WPF, you will realize that it is in fact the underlying reason for many of the other differences - WPF is simply just doing things in its own way, for better and for worse. You're no longer constrained to doing things the Windows way, but to get this kind of flexibility, you pay with a little more work when you're really just looking to do things the Windows way.
The following is a completely subjective list of the key advantages for WPF and WinForms. It should give you a better idea of what you're going into.
WPF advantages.
It's newer and thereby more in tune with current standards
Microsoft is using it for a lot of new applications, e.g. Visual Studio
It's more flexible, so you can do more things without having to write or buy new controls
When you do need to use 3rd party controls, the developers of these controls will likely be more focused on WPF because it's newer
XAML makes it easy to create and edit your GUI, and allows the work to be split between a designer (XAML) and a programmer (C#, VB.NET etc.)
Databinding, which allows you to get a more clean separation of data and layout
Uses hardware acceleration for drawing the GUI, for better performance
It allows you to make user interfaces for both Windows applications and web applications (Silverlight/XBAP)
WinForms advantages.
It's older and thereby more tried and tested
There are already a lot of 3rd party controls that you can buy or get for free
The designer in Visual Studio is still, as of writing, better for WinForms than for WPF, where you will have to do more of the work yourself with WPF.
what is WPF
What is WPF?
WPF, which stands for Windows Presentation Foundation, is Microsoft's latest approach to a GUI framework, used with the .NET framework.
But what IS a GUI framework? GUI stands for Graphical User Interface, and you're probably looking at one right now. Windows has a GUI for working with your computer, and the browser that you're likely reading this document in has a GUI that allows you to surf the web.
A GUI framework allows you to create an application with a wide range of GUI elements, like labels, textboxes and other well known elements. Without a GUI framework you would have to draw these elements manually and handle all of the user interaction scenarios like text and mouse input. This is a LOT of work, so instead, most developers will use a GUI framework which will do all the basic work and allow the developers to focus on making great applications.
There are a lot of GUI frameworks out there, but for .NET developers, the most interesting ones are currently WinForms and WPF. WPF is the newest, but Microsoft is still maintaining and supporting WinForms. As you will see in the next chapter, there are quite a few differences between the two frameworks, but their purpose is the same: To make it easy to create applications with a great GUI.
WPF, which stands for Windows Presentation Foundation, is Microsoft's latest approach to a GUI framework, used with the .NET framework.
But what IS a GUI framework? GUI stands for Graphical User Interface, and you're probably looking at one right now. Windows has a GUI for working with your computer, and the browser that you're likely reading this document in has a GUI that allows you to surf the web.
A GUI framework allows you to create an application with a wide range of GUI elements, like labels, textboxes and other well known elements. Without a GUI framework you would have to draw these elements manually and handle all of the user interaction scenarios like text and mouse input. This is a LOT of work, so instead, most developers will use a GUI framework which will do all the basic work and allow the developers to focus on making great applications.
There are a lot of GUI frameworks out there, but for .NET developers, the most interesting ones are currently WinForms and WPF. WPF is the newest, but Microsoft is still maintaining and supporting WinForms. As you will see in the next chapter, there are quite a few differences between the two frameworks, but their purpose is the same: To make it easy to create applications with a great GUI.
Google's 'Hummingbird' hatches new search formula
Google has quietly retooled the closely guarded formula running its internet search engine to give better answers to the increasingly complex questions posed by web surfers.
The overhaul came as part of an update called "Hummingbird" that Google has gradually rolled out in the past month without disclosing the modifications.
The changes could have a major impact on traffic to websites.Hummingbird represents the most dramatic alteration to Google's search engine since it revised the way it indexes websites three years ago as part of a redesign called "Caffeine," according to Amit Singhal, a senior vice president for the company. He estimates that the redesign will affect the analysis of about 90 per cent of the search requests that Google gets.
Any reshuffling of Google's search rankings can have sweeping ramifications because they steer so much of the internet's traffic. Google fields about two of out every three search requests in the US and handles an even larger volume in some parts of Europe. The changes could also drive up the price of Google ads tied to search requests if websites whose rankings are demoted under the new system feel they have to buy the marketing messages to attract traffic.
The search ads and other commercial pitches related to web content account for most of Google's revenue, which is expected to approach $60 billion this year.
Google disclosed the existence of the new search formula on Thursday at an event held in the Menlo Park, California, garage where CEO Larry Page and fellow co-founder Sergey Brin started the company 15 years ago.
Google celebrates its birthday on September 27 each year, even though the company was incorporated a few weeks earlier. The company is now based in Mountain View, California, at a sprawling complex located about seven miles from the 1,900-square-foot home where Page and Brin paid $1,700 per month to rent the garage and a bedroom. The co-founders' landlord was Susan Wojcicki, who is now a top Google executive and Brin's sister-in-law.
Wojcicki sold the home to Google in 2006 and it is now maintained as a monument to the company's humble beginnings.
Google's renovations to its search engine haven't triggered widespread complaints from other websites yet, suggesting that the revisions haven't resulted in a radical reshuffling in how websites rank in the recommendations. The Caffeine update spurred a loud outcry because it explicitly sought to weed out websites that tried to trick Google's search engine into believing their content was related to common search requests. After Caffeine kicked in, hundreds of websites that consistently won a coveted spot near the top of Google's search results had been relegated to the back pages or exiled completely.
Hummingbird is primarily aimed at giving Google's search engine a better grasp at understanding concepts instead of mere words, Singhal said.
The change needed to be done, Singhal said, because people have become so reliant on Google that they now routinely enter lengthy questions into the search box instead of just a few words related to specific topics.
With the advent of smartphones and Google's voice-recognition technology, people also are increasingly submitting search requests in sequences of spoken sentences that resemble an ongoing conversation. That trend also factored into Google's decision to hatch Hummingbird.
Just as Page and Brin set out to do when they started Google in a garage, "we want to keep getting better at helping you make the most of your life," Singhal said.
Besides Hummingbird, Google also announced a few other updates to existing search features aimed at providing information more concisely so people won't need to navigate to another website. These changes are part of Google's effort to adapt to the smaller screens of smartphones that aren't well suited for hopscotching across the Internet.
The additions primarily affect Google's "Knowledge Graph," an encyclopedia-like box that increasingly appears at the top or alongside the search results, and Google Now, a virtual assistant that tailors key information suited to each user's habits, interest and location.
Besides providing informational snapshots of famous people and landmarks, the Knowledge Graph is now capable of comparing the attributes of two different things, such as olive oil and coconut oil. It will also be possible to ask the Knowledge Graph to sort through certain types of information, such as the creative evolution of various artists.
An upcoming update to Google's search application for devices running Apple's mobile operating system will ensure notifications about personal appointments and errand reminders are also delivered on a smartphones or tablets running on Google's competing Android software. Google Now also will start flagging new developments and information about famous people that have previously piqued a user's interest.
Thursday, 26 September 2013
Apple 5s. .
Apple iPhone 5S teardown reveals Touch ID fingerprint scanner, new camera module and other secrets
Apple’s latest offering has only just hit stores in select markets and already it has been taken apart limb from limb. Not surprisingly the people responsible are the team at iFixit, which gave the device their famous teardown treatment. After completely disassembling the iPhone 5S, the team not only found it relatively easy to repair, but also found the much-talked-about Touch ID sensor and a new Sony camera module among others. While removing the front panel, the team found a cable running from the Touch ID sensor to the Lightning port assembly.
The Touch ID assembly (looks same as what leaked a month back) is essentially a bunch of very small capacitors that creates an “image” of the ridges on your finger.Like in the iPhone 4S and the iPhone 5, they found that the image sensor hidden in the rear camera assembly again comes from Sony. But the markings on the module are different and hence the sensor is not Sony’s IMX145, but a newer variant made specifically for the iPhone 5S. That isn’t surprising considering Apple had talked about retaining an 8-megapixel camera while having a bigger sensor in place for better photo quality. Lastly, on prying out the battery, they found it to be a 1,560mAh, which is much bigger than the 1,440mAh on the iPhone 5.
Overall, iFixit gave the iPhone 5S 6 out of 10 in terms of ease of reparability, with 10 being the easiest to repair. The device is overall easy to open and repair, barring a couple of parts like the Pentalobe screws, battery attached with a strong adhesive and Touch ID sensor, which make the process a bit tedious.
Apple’s latest offering has only just hit stores in select markets and already it has been taken apart limb from limb. Not surprisingly the people responsible are the team at iFixit, which gave the device their famous teardown treatment. After completely disassembling the iPhone 5S, the team not only found it relatively easy to repair, but also found the much-talked-about Touch ID sensor and a new Sony camera module among others. While removing the front panel, the team found a cable running from the Touch ID sensor to the Lightning port assembly.
The Touch ID assembly (looks same as what leaked a month back) is essentially a bunch of very small capacitors that creates an “image” of the ridges on your finger.Like in the iPhone 4S and the iPhone 5, they found that the image sensor hidden in the rear camera assembly again comes from Sony. But the markings on the module are different and hence the sensor is not Sony’s IMX145, but a newer variant made specifically for the iPhone 5S. That isn’t surprising considering Apple had talked about retaining an 8-megapixel camera while having a bigger sensor in place for better photo quality. Lastly, on prying out the battery, they found it to be a 1,560mAh, which is much bigger than the 1,440mAh on the iPhone 5.
Overall, iFixit gave the iPhone 5S 6 out of 10 in terms of ease of reparability, with 10 being the easiest to repair. The device is overall easy to open and repair, barring a couple of parts like the Pentalobe screws, battery attached with a strong adhesive and Touch ID sensor, which make the process a bit tedious.
Subscribe to:
Posts (Atom)