Search This Blog

Showing posts with label technology. Show all posts
Showing posts with label technology. Show all posts

Wednesday, 4 January 2012

CES 2012: Ultrabooks and quad-core mobile devices likely to take center stage


CES 2012: Ultrabooks and quad-core mobile devices likely to take center stage
Takeaway: Hardware trends that you should be watching for at CES 2012.

In less than a week, thousands of reporters, vendors, and technology enthusiasts will descend on Las Vegas for CEA’s International Consumer Electronics Show 2012.  As hardware manufactures show off their latest creations, a few trends always emerge. Last year, it was tablets. The year before, 3D TVs were all the rage. So what will be this year bring?
Television and computer display makers will be showing off new OLED TV and 4K displays, but these technologies are still a few years from being ready for mass consumption. Two technologies that will be will affect the tech markets in 2012, and be front and center at CES, are ultrabooks and quad-core mobile devices.

Ultrabooks

These thin, energy-efficient laptops are designed to be ultraportable and almost as powerful as full-size notebooks. Driven by Intel, they’re basically the Windows version of Apple’s MacBook Air. I expect PC makers to unveil several new ultrabooks at CES 2012 and release many of them this year. Prices are likely to start around $1,000 (US) but drop as more models enter the market.

Quad-core tablets and smartphones

The first quad-core Android tablet, Asus’ Transformer Prime, hit the market in December. Tablet and smartphone manufactures are expected to unveil several quad-core devices at CES 2012, and like ultrabooks, many will hit the market in early 2012.

Windows 8 Tablet - Wildcard

Microsoft released the Windows 8 Developer Preview last year and is expected to release the full version in 2012. A big part of Windows 8 is the operating system’s support for ARM mobile processors and the new touch-centric Metro UI. Microsoft is clearly looking to break Apple and Google’s stranglehold on the tablet OS market. Rumors are swirling that Acer, Lenevo, HP and perhaps even Microsoft itself will unveil a WIndows 8 tablet at CES and release it late 2012. Having seen Microsoft CEO Steve Ballmer hype a Windows-powered HP tablet at CES in 2010, only to have HP kill it shortly thereafter, I won’t believe the rumors until a device actually hits the market.

Friday, 19 August 2011

Motorola Photon 4G, The Perfect Combination for Business and Entertainment

Motorola Photon 4G, The Perfect Combination for Business and Entertainment
Motorola Photon 4G
Motorola introduces new mobile phone called the Motorola Photon 4G.
Motorola Photon 4G is a dual GSM/CDMA which comes with octagona design. Comes with a screen size is fairly large, 4.3-inch QHD-based, Motorola Photon 4G equipped with a processor Tegra 2 like any other Motorola devices, Motorola Atrix 4G.

In addition to having a dual-core CPU-based, Motorola Photon 4G will also offer a variety of other trim specifications, such as RAM and internal memory capacity of 16 GB which can be expanded up to 32GB via microSD card.

Motorola Photon 4G It also provides the main camera with a resolution of 8 MP who has the ability to capture 720p video. While the VGA camera is available as a secondary camera located in front of the device is useful for video calls.

For connectivity, Motorola Photon 4G will be presented with features such as Bluetooth 2.1, Wi-Fi b/g/n, and HDMI output.

Motorola Photon 4G, will carry the Android 2.3 Gingerbread OS by MOTOBLUR style UI customization. Motorola Photon 4G will also be equipped with a kickstand that can be used activities such as watching videos without the need to hold the device.


Specifications of Motorola Photon 4G:
  • 2G CDMA 800/1900, GSM 850/900/1800/1900 
  • 3G CDMA2000 1xEV-DO
  • Dimensions: 126.9 x 66.9 x 12.2 mm
  • Weight: 158 grams
  • Screen: 4.3 inch, TFT capacitive touchscreen, 16M colors, 540 x 960 pixels, Multi-touch input method, Accelerometer sensor for UI auto-rotate, Proximity sensor for auto turn-off, Touch-sensitive controls
  • Main camera: 8 MP, 3264x2448 pixels, autofocus, dual-LED flash, Geo-tagging, face detection, image stabilization, Video 720p @ 30fps
  • Secondary Camera: VGA;
  • Memory: 16 GB storage, 1 GB RAM, 2 GB ROM, microSD up to 32GB;
  • Connectivity: Wi-Fi 802.11 b/g/n, DLNA, Wi-Fi hotspots
  • WiMAX 802.16 e
  • 3G Rev. A, up to 3.1 Mbps, LTE
  • Bluetooth v2.1 with A2DP, EDR
  • CPU: 1GHz NVIDIA Tegra 2 AP20H Dual Core processor
  • Android OS, v2.3 (Gingerbread)
  • Messaging: SMS (threaded view), MMS, Email, IM, Push Email
  • Browser: HTML
  • GPS: A-GPS support
  • Java MIDP emulator
  • Battery: 1700 mA Li-Po
  • Other Features: SNS integration, digital compass, HDMI port, Active noise cancellation with dedicated mic, MP3/WAV/WMA/AAC + player, MP4/WMV/H.263/H.264 player, Google Search, Maps, Gmail, YouTube, Google Talk, Built-in kickstand, Document viewer, Photo viewer/editor, Organizer, Adobe Flash 10.1, Voice memo/dial/commands, Predictive text input (Swype), 3.5 mm audio jack

Wednesday, 17 August 2011

Four ways the Google-Motorola deal will change the tech industry


Four ways the Google-Motorola deal will change the tech industry
Takeaway: While Google’s acquisition of Motorola Mobility won’t be one of the most expensive acquisitions of this era, it will be one the tech industry’s most influential events.
Google’s $12.5 billion purchase of Motorola Mobility will go down as one of the most important events in tech during this era. Other deals, such as AT&T’s $39 billion buyout of T-Mobile USA, are worth more money, but none of them will have as big of an impact on the tech industry (and as much fallout) as the Google-Motorola deal. This is the most important acquisition in the technology space since the HP-Compaq $25 billion deal a decade ago.
Google-Motorola
Here are the top four ways that Googlerola will change the course of the tech industry.

1. The Android patent wars are over

Before Google bought Motorola, the Android ecosystem was in real danger of having innovation stymied by litigation. Microsoft, Oracle, and Apple were all bearing down on Google as well as Android partners Samsung and HTC over patent infringements. Motorola hadn’t entered the fray yet, but with its long history in the wireless business there was the potential that it could use its treasure chest of patents to pile on to its chief Android rivals, Samsung and HTC. On August 11, my ZDNet colleague James Kendrick posted, “If Motorola turns its patents on other Android phone makers the platform will implode.” And, that was on top of the overall intellectual property issues with Android itself, which affects all of the Android device makers. The problem for Google was that it didn’t have enough mobile patents to fight back. That’s the way these things usually work. One big company typically says to another big company, “Yeah, we might be infringing you there, but you’re infringing us over here” and then it turns into a draw. With Motorola’s 17,000 patents on its side, Google has essentially put an end to the Android patent wars. There will still be some final skirmishes, but don’t expect much carnage.

2. Vertical integration has won

While Google is pledging to keep Android an open ecosystem and claiming that it will run Motorola as a separate business, it’s pretty clear that Google also wants to have the option of producing its own hardware devices so that it can build prototypes, concept hardware, and leading edge devices to demonstrate its vision and point its ecosystem partners in the right direction. Google wanted to do this with the Nexus One smartphone and we also saw Google’s hardware itch in the CR-48 laptop running Chrome OS. Of course, Google didn’t have the expertise or infrastructure in place to handle the hardware business. With the Motorola Mobility acquisition, it will add over 19,000 new employees with supply chain, customer service, and hardware development skills. When Google wants to do its next leading edge Android device like the Nexus One, Nexus S, or Motorola Xoom, we have to assume that it’s going to use its new hardware division to build it so that it can deliver exactly the device it wants and get it to market much more quickly. With Apple’s continued success in mobile, BlackBerry’s large (albeit fading) market share, HP’s new hardware/software unification with WebOS, and now the Google-Motorola deal, it’s becoming clear that vertical integration is winning in mobile. Going forward, look for the latest, greatest, high-end devices to all be vertically integrated, while many of the low-cost, copy-cat devices will come to the market later and be made by mass market manufacturers like Samsung.

3. Mobile consolidation has begun

Over the past couple years, the arrival of new mobile platforms and the expansion of mobile vendors have given buyers lots of new choices in smartphones and now tablets. However, even in a fast-growing market like mobile, the good times can’t last forever. In 2011, we’ve already seen BlackBerry and Nokia drastically losing momentum, Windows Phone 7 and WebOS struggling to gain market share, and Android and Apple increasingly hogging the spotlight. Even within the Android ecosystem itself, there have been lots of new upstarts recently, including LG, Lenovo, Acer, and ASUS. All of them have been grasping for a piece of the expanding Android market, which has been dominated by the big three — HTC, Samsung, and Motorola. However, leading up to the Google deal, Motorola was the only one of the Android vendors that lost market share in the smartphone market in Q2. Obviously, that’s likely to change if and when Motorola morphs into the Google-branded Android devices. Nevertheless, Motorola’s Q2 struggles are a sign that the Android market itself is already beginning to whittle down to fewer big players.

4. Google has to grow up

As a company, Google is only a little over a decade old. Despite its recent kerfuffles with government regulators and its dust-up with China, the company has lived a bit of an idyllic, Peter Pan existence. Its offices are like college campuses with free food, free transportation, and free personal services (cleaners, barbers, etc). Its employees are loosely organized, don’t have to deal with a bunch of overbearing middle managers and bean counters (in most cases), and even get the ability to use work time to dabble with some of their own pet projects. Because Google’s search engine has been such a major cash cow, it has given the company freedom to hire lots of engineers and computer scientists and loosely organize them in this unique environment. However, with search under greater pressure than ever from the social web, it could finally be time for Google to grow up and act like an adult company that has to closely manage expenses and account for the value that each of its employees brings to the organization. The Motorola acquisition could hasten the process, since it will add over 19,000 employees to a Google that currently has 29,000, and Motorola is a much more established company with traditional organizational standards. Of course, Google will talk about wanting to maintain its startup-like culture, but it will be interesting to watch and see if Motorola influences Google to become more of an accountable, grown-up company.




*********************************

Tuesday, 16 August 2011

10 things you should know about HTML5


10 things you should know about HTML5
Takeaway: HTML5 may not be a fully finalized standard yet, but it isn’t changing much — and adoption is on the rise. Some of the key aspects of the new specification.
A year or two ago, HTML5 seemed like a vague idea that only a few Internet wonks cared about. Now, it feels like HTML5 is everywhere. Thanks to rapid releases from Mozilla and Chrome, and the deployment of IE9 from Microsoft (and IE10 already in “tech preview” status), browser support for HTML5 is available to nearly everyone in a limited (or better than limited) amount. Developers are starting to take advantage of the widely implemented features. With full HTML5 support probably less than a year away, and the specification quickly reaching an unchanging state, this is a great time to look at some things you should know about HTML5.

1: XHTML is no more; long live HTML5 with XML syntax

XHTML was the choice of people who favored precision, particularly for parsing. HTML has always looked a lot like XML, but it never was quite exactly like XML, and as a result, trying to parse it like XML would fail. So a while ago, the XHTML spec was made, to take the HTML language and put it into the XML lingo. When HTML5 first got started, there was work on XHTML 2 as well, but that was eventually mothballed. Instead, the HTML5 spec is written so that you can write HTML5 with strict XML syntax and it will work. And if you send it with an XML MIME type, user agents will parse it as an XML document too. This gives developers the best of both worlds.

2: The 2022 myth, the 2011 reality

One of the persistent misconceptions around HTML5 is that “it won’t be done until 2022.” The typical supporting evidence for this is an interview conducted with Ian Hickson, the HTML5 specification editor, a few years ago. Ironically enough, even in that interview, he was clear about the 2022 date. But a few people got really worked up about it, and their angry articles got a lot more attention than the actual facts.
The truth is that 2022 is when Hickson expects the HTML5 spec to become a full W3Crecommendation, which means that there are two 100% complete, verifiable implementations. To get an idea of why that is both fairly meaningless and a huge leap at the same time, consider that no other version of the HTML spec has ever achieved that status, mainly because they were too vague for any implementation to be provably correct. The HTML5 specification is getting close to being solidified and unchanging, right now in 2011.

3: It is a Flash and Silverlight killer for many developers

While HTML5 does make numerous improvements in how it is used for marking up documents, the big focus is in applications. The number of features that HTML5 introduces to support application development is staggering. This isn’t to say that Flash and Silverlight are going away anytime soon. But Microsoft has already announced that it’s refocusing Silverlight on the out-of-browser experience. Flash and Silverlight still have capabilities that HTML5 does not have, but the gap is nonexistent for many common purposes now, thanks to HTML5’s new capabilities. It probably isn’t worth rewriting existing applications, but you should see whether HTML5 makes sense for new applications.

4: It is the basis of many new tools

With HTML5 becoming a full-blown application framework, toolmakers are now using it as the foundation technology for their products, particularly those designed to overcome cross-platform development issues. If you are looking to write an application that runs cross platform, and it is within the capabilities of an HTML5 application, you should consider one of these tools. This is especially important in the mobile space, where the alternative is to learn an entirely different language, API, and framework for each phone platform you want to target.

5: The <video> tag is important but controversial

My personal pick for “best new HTML5 feature” is the <video> tag. Before <video> (there is also an <audio> tag), you would find yourself having to turn to Flash or Silverlight to provide a media player on your site. With these new tags, those days are, in theory, over. Why only “in theory”? Sadly, the different browser makers can’t quite decide on which formats to support yet, due to patent concerns. When the dust settles on that, Flash and Silverlight both lose their #1 use case.

6: Google led the way

If it seems like the Chrome browser has a huge head start with HTML5, there is a good reason for that. The HTML5 specification process put a heavy premium and emphasis on written, deployed code. I’m not saying that they “rubber stamped” whatever browser vendors did. But it was hard to convince those involved to write specifications for unimplemented features, and implemented features were likely to become the basis of new items in the specification. Because Chrome seems to have a new version every few weeks, features that Google put into it had an excellent chance of making it into the HTML5 spec.

7: “Standards compliant” is finally provable

Whenever someone claims that a browser is or is not “standards compliant,” I have got to laugh. Before HTML5, it is literally impossible to be provably standards compliant. In many cases, the current specs are too vague or simply silent on important issues (like handling parsing errors) and the result is that different browsers can do wildly different things and still be either standards compliant or fall into the category of “not provably out of compliance.” Even the famous ACID test does not prove too much, since it tests only a subset of the HTML specification. With HTML5, the bar has been raised quite a bit, and it will finally be possible to prove that a user agent is standards compliant. Indeed, one of the reasons behind the 2022 date for “recommendation” status is the need to write full test suites.

8: “Standards compliant” still does not guarantee how it will look

Standards compliance in Web browsers does not do what people often think it does, and HTML5 does not change that fact. A big confusion with HTML is that many Web designers and developers believe that the HTML specification controls the look of items on the screen; it does not. For example, a Web browser can make the <strong> tag use a bigger or different colored font instead of a heavier font, if it likes and still be compliant. Many times, when designers say a browser is not standards compliant, what they are really encountering is the flexibility given to user agents in how to render tags. HTML5 does not change this fact. If you absolutely need a tag to be rendered in a precise way, do not count on the browser’s default behavior; specify your needs in CSS.

9: Parsing is more precise

The HTML5 specification finally introduces precise parsing rules and defines things like what the user agent should do when it encounters a parsing error. As a result, you can expect that some things that used to pass as acceptable or even “valid” HTML in the past will no longer cut the mustard. You will want to get familiar with HTML5’s parsing rules and make sure that your code adheres to them.

10: HTML5 goes far beyond the browser

In previous versions of HTML, there was an inherent assumption that a traditional Web browser was the user agent of choice. While other user agents and content types were supported, there was an implication that they were not as important. HTML5, on the other hand, has a good number of changes to put non-browser, non-desktop-size-screen user agents on more equal footing with traditional Web browsers. There have been a lot of advances with things like how well it works with screen readers and mobile phones. As a result, well-written HTML5 can be a “write-once, view anywhere” framework for developers who need it, and it can reach users (particularly those with a variety of disabilities) who otherwise would struggle with the Web.




***********************************************

Wednesday, 10 August 2011

Nokia 500 - Symbian Anna smartphone with a 1 GHz Processor


Nokia 500 with Symbian Anna
Nokia 500 - Symbian Anna smartphone with a 1 GHz Processor

According to the latest news Nokia has reportedly announced the Nokia 500, the latest smartphone which comes with the same operating system with Nokia E6 and Nokia X7 is Symbian Anna

Looking at the specifications of the Nokia 500 is similar to the Nokia C5-03. Nokia 500 comes with a 3.2-inch capacitive screen with a resolution of 640 x 360 pixels and a 5 MP camera which is located at the rear of the device. Interestingly, the Nokia 500 is touted as Nokia's first Symbian phone which comes with a 1 GHz processor.

For connectivity, the Nokia 500 uses 14.4Mbps HSDPA and 5.8Mbps HSUPA, Wi-Fi, GPS, microUSB port, and standard 3.5mm audio jack.

The phone also comes with a capacity of 2 GB of internal memory and a microSD card slot for expanding memory capacity storage.

Another excellent feature is also offered is the back cover is replaceable, including two that are included. Like the Nokia N79, Nokia 500 will adjust the background color of the screen according to the fitted cover.

Nokia 500 black version will be launched in the third quarter, while for the white version would be present in the fourth quarter. Tag of the Nokia 500 is quite affordable, which according to estimates it costs around 150 euros.

Nokia 500 Specifications:
  • Network: 2G Network GSM 850 / 900 / 1800 / 1900
  • 3G HSDPA 850 / 900 / 1700 / 1900 / 2100
  • Dimensions: 111.3 x 53.8 x 14.1 mm, 73 cc Weight: 93 grams
  • Screen: 3.2 inch, TFT capacitive touchscreen, 16M colors, 360 x 640 pixels, Accelerometer sensor for auto-rotate, Proximity for auto turn-off
  • Camera: 5 MP, 2592Ñ…1944 pixels, Geo-tagging, VGA @ 15fps
  • Memory: 2 GB, microSD, up to 32GB
  • Connectivity: Wi-Fi 802.11 b / g, Bluetooth v2.1 with A2DP, EDR, 3G HSDPA, 14.4 Mbps
  • HSUPA, 5.76 Mbps, v2.0 microUSB
  • CPU: 1 GHz processor
  • Operating system: Symbian OS Anna
  • Messaging: SMS (threaded view), MMS, Email, Push Mail, IM
  • Browser: WAP 2.0/xHTML, HTML, RSS feeds
  • GPS: A-GPS support
  • Java: MIDP 2.1
  • Battery: Li-Ion 1110 mAh (BL-4U)
  • Other Features: Exchangeable battery covers with multiple home screens (2 included in the retail box), Digital compass, MP4/H.263/H.264 player, MP3/WAV/еAAC + / WMA player, Photo editor, Organiser, Voice command / dial, Flash Lite 4.0, Predictive text input, 3.5 mm audio jack


    *****************************

Monday, 8 August 2011

HTML5: Using structural elements for header, footer, and navigation


HTML5: Using structural elements for header, footer, and navigation
Takeaway: The use of structural elements in the new HTML5 specification, specifically header, footer, and navigation elements, and examples of each.
The HTML5 specification has defined a set of sectional and structural elements that improves semantic markup within HTML coding for web developers. These new sectional and structural elements are a panacea for moving away from the common use of divisions or the <div> element that has taken over a large part of web page structures in recent years.
The sectional and structural elements include the header <header>, footer <footer>, and navigation <nav> elements which will be addressed in this segment. The article <article>, aside <aside>, section <section>, and headings group <hgroup> elements were explained in the previous post on HTML5: Using sectional elements.
The only rule for limiting the use of the <header> and <footer> elements is that they cannot be nested within another <header> or <footer> element. Other than that limitation, the use of these two elements is fairly open; examples of their utilization will be displayed for both.

Header <header>

This element represents a group of introductory or navigational aids for web pages. A <header> element is intended to contain the section’s heading such as an <h1-h6> element or an <hgroup> element, but this is not required. The header element can also be used to wrap a section’s table of contents, a search form, sub headings, bylines, version history information, or any relevant logos.
The header element is not to be used for sectioning content as it is more of a structural element, and it does not introduce a new section. The <header> element can be used many times on a single web page; for example, it can be nested within each <article> element. Here are several examples of using the <header> element in HTML code.
<header> Example 1: The following snippet shows how the element is used to markup a page header.
<header>
  <hgroup>
    <h1>Gardening Times</h1>
    <h2>Getting started with flowers</h2>
  </hgroup>
</header>
<header> Example 2: In this example, the clip shows the <header> element nested within an <article> element.
<article>
  <header>
    <hgroup>
      <h1>Raising Roses</h1>
      <h2>The guide to a perfect rose garden</h2>
    </hgroup>
</header>
</article>
At this time, most browsers do not execute any display information via CSS for HTML5 elements, as is the case for the <header> element, and to be displayed as a block it will need to be specified in the style sheet as shown in the example below along with others:
address, article, aside, canvas,
figcaption, figure, footer, header,
hgroup, nav, section, summary {
display: block;
}

Footer <footer>

This element should be self explanatory at this point; however, the HTML5 <footer> element specification does state that it represents a footer for its nearest ancestor sectioning content or sectioning root element. The footer typically contains information about its section such as who wrote it, links to related documents, copyright data, and social networking and sharing links, such as in a blog post. For this reason it is possible to have more than one <footer> element on a single web page document. The <footer> element does not introduce a new section, similar to the <header> element, but serves to add semantic meaning to the bottom of a <section> or <article>.
Several examples for use of the <footer> element are provided below:
<footer> Example 1: This example shows the <footer> element containing a published timestamp nested within an <article> element:
<article>
<header>
  <h1>Example of a footer nested in an article</h1>
</header>
  <p>This is the article content...</p>
  <p>...</p>
<footer>
  <p>Published: <time datetime="2011-07-22T13:59:47-04:00" pubdate>July 22, 2011 1:59 pm EDT</time></p>
</footer>
</article>
<footer> Example 2: This example shows a site wide <footer> element containing a navigation element:
<footer>
<nav>
<p><a href=”/blog.html”>Blog</a> -
<a href=”/archive.html”>Archive</a> -
<a href=”/index.html”>Home</a></P>
</nav>
<p>Copyright ©2011 Footer Examples</p>
</footer>

Navigation <nav>

This element, as the HTML5 specification requires, corresponds to a section of a web page that links to other web pages or to other parts within the web page; for example, a section with navigation links — which seems self explanatory. What this means is that the <nav> element replaces the idea of having a <div id=”nav”> element, with the new semantic element meant specifically as a navigation area. However, consider that not all groups of links on a web page need to be contained within a <nav> element; the element is primarily intended for sections that consist of major navigation blocks; in addition, the element can appear more than once on any given web page. A global site-wide navigation block and a secondary navigation block can be included on a single web page with individual attributes styled with an id or class designation.
The specification also notes that it is common for footers to have a short list of links to various pages of a site, such as the terms of service, a copyright or disclaimer page. The footer element alone is sufficient for such cases, and while a <nav> element can be used in such cases, it is usually unnecessary.
The specification goes on to state that user agents including screen readers that are targeted at users who can benefit from navigation information being omitted in the initial rendering, or who can benefit from navigation information being immediately available, can use the <nav> element as a way to determine what content on the page to initially skip and/or provide on request.
Typically, the <nav> element can be found within the <header> structural element, which will be reviewed in the next installment on HTML5 coding practices. The contents of links within the <nav> element do not necessarily have to be presented in list form, but can also contain other kinds of content as well, including links within a paragraph block. Several examples of the <nav> element are presented below:
<nav> Example 1: Content linking presented within an unordered list
<h1>The Blog of Examples</h1>
  <nav>
   <ul>
     <li><a href="#">Home</a></li>
     <li><a href="#/events">Events</a></li>
     <li><a href="#/Blog">Blog</a></li>
     <li><a href="#/Products">Products</a></li>
   </ul>
</nav>
<nav> Example 2: Linking content within a paragraph block
<nav>
 <h1>Navigation</h1>
   <p>This is the home page, just below you will find <a href="/blog">The
  Blog</a>, where much ado about something can be found. Just to the right of
   that you will find the <a href="/wiki">Wiki</a>. And continuing
   the path to your left you will find the <a href="/wiki/papers">Wiki Papers</a>.</p>
</nav> 

*********************
Related Posts Plugin for WordPress, Blogger...