Bruce Sterling on Earth-Friendly Pervasive Computing

Noting that the word 'computer' is disappearing from technologists' vocabularies, science fiction author and futurist Bruce Sterling believes that as the Internet subsumes computing, we are truly on the path toward a highly embedded wireless network in which nearly everything is a node:

In 2007 the computer gave up taking over the world. Instead the world took over the computer. The Internet became a wholly owned subset of Reality 2.0. When the actual world invades the virtual world, it scatters the computer into tiny physical pieces, some no bigger than dust. "Intelligent printing," another modern darling, is semiconductor ink sprayed on cardboard. There's never been a humbler, cheaper "computer."

Sterling envisions a world in which the chips that drive it are powered by tiny amounts of ambient energy -- nearly any form of heat or light will do. Such chips would have such low power requirements that they wouldn't need a dedicated power source, and would use up hardly any natural resources.

Source: Futurismic

Updated SDK Tools and ADT revision 17

Today we are releasing an update to the SDK Tools and the Eclipse plugin. Revision 17 brings a lot of new features and bug fixes in various areas such as Lint, the build system as well as the emulator.

Lint is a static checker which analyzes Android projects for a variety of issues around correctness, security, performance, usability and accessibility, checking your XML resources, bitmaps, ProGuard configuration files, source files and even compiled bytecode. It can be run from within Eclipse or from the command line.
New for r17:

• Added check for Android API calls that require a version of Android higher than the minimum supported version. You can use the new @TargetApi annotation to specify local overrides for conditionally loaded code. For more information, read here.
• Added over 40 new Lint rules for a total of over 80, including checks for performance, XML layouts, manifest and file handling. For a full list read here.
• Added ability to suppress Lint warnings in Java code with the new @SuppressLint annotation, and in XML files with the new tools: namespace prefix and ignore attribute. For more information, read here.
• Improved HTML and XML reporting and Eclipse integration. For more information, read here.

We've also made improvements to the build systems for Eclipse and Ant:

• Added strict dependency support for 3rd party Jar files. You can read more information here.
• Added support for custom views with custom attributes in libraries. Layouts using custom attributes must use the namespace URI http://schemas.android.com/apk/res-auto instead of the URI that includes the app package name. This URI is replaced with the app specific one at build time.
• Added a feature that allows you to run some code only in debug mode. Builds now generate a class called BuildConfig containing a DEBUG constant that is automatically set according to your build type. You can check the (BuildConfig.DEBUG) constant in your code to run debug-only functions such as outputting debug logs.

The emulator is seeing some big improvements as well:

• Thanks to contributions to AOSP from Intel, the emulator now supports running x86 system images in virtualization mode on Windows and Mac OS X. This allows the emulator running at near native speed. The drivers are available through the SDK Manager. Read more here.
• After adding webcam support and sensor emulation, we are adding experimental support for Multi-Touch input through a tethered Android device. (Read more here)

Finally, we are also releasing an updated Support Library with the following improvements:

• ShareCompat provides easy helper classes for both sending and receiving content for social sharing apps.
• NavUtils and TaskStackBuilder provide cross-version support for implementing the Android Design guidelines for navigating within your app including the action bar's 'Up' button.
• NotificationCompat.Builder provides a compatibility implementation of Android 3.0's Notification.Builder helper class for creating standardized system notifications.
• A new Library Project adds support for GridLayout back to API level 7 and higher.

You can get more information about these changes in the SDK Tools Release Notes and ADT Release Notes.

Calc-ConveR es mi primer proyecto para Tablets de 10' pulgadas, la idea parte de otro anterior proyecto para dispositivos móviles la Calculadora V.4.0 y de ahí parte la idea de llevar a las tabletas de 10' pulgadas y así tener mi primera experiencia con pantallas de mayor tamaño con Calc-ConveR.  Básicamente su funcionamiento es muy sencillo , tiene la parte gráfica de las banderas  que

Introducing Android 4.1 (Jelly Bean) preview platform, and more

[This post is by Angana Ghosh, Product Manager on the Android team]

At Google I/O today we announced the latest version of the Android platform, Android 4.1 (Jelly Bean). With Jelly Bean, we've made the great things about Android even better with improved system performance and enhanced user features.

Improvements include a smoother and more responsive UI across the system, a home screen that automatically adapts to fit your content, a powerful predictive keyboard, richer and more interactive notifications, larger payload sizes for Android Beam sharing and much more. For a lowdown on what's new, head over to the Jelly Bean platform highlights.

Of course, Jelly Bean wouldn't be complete without a healthy serving of new APIs for app developers. Here are some of the new APIs that Jelly Bean introduces:

Expandable notifications: Android 4.1 brings a major update to the Android notifications framework. Apps can now display larger, richer notifications to users that can be expanded and collapsed with a pinch. Users can now take actions directly from the notification shade, and notifications support new types of content, including photos.

Android Beam: In Android 4.1, Android Beam makes it easier to share images, videos, or other payloads by leveraging Bluetooth for the data transfer.

Bi-directional text support: Android 4.1 helps you to reach more users through support for for bi-directional text in TextView and EditText elements.

Gesture mode: New APIs for accessibility services let you handle gestures and manage accessibility focus. Now you can traverse any element on the screen using gestures, accessories, you name it.

Media codec access: Provides low-level access to platform hardware and software codecs.

Wi-Fi Direct service discoverability: New API provides pre-associated service discovery letting apps get more information from nearby devices about the services they support, before they attempt to connect.

Network bandwidth management: New API provides ability to detect metered networks, including tethering to a mobile hotspot.

For a complete overview of new APIs in Jelly Bean, please read the API highlights document. Note that this is a preview of the Jelly Bean platform. While we're still finalizing the API implementations we wanted to give developers a look at the new API to begin planning app updates. We'll be releasing a final platform in a few weeks that you should use to build and publish applications for Android 4.1.

For Android devices with the Google Play, we launched the following at Google I/O today:

Smart app updates: For Android 2.3, Gingerbread devices and up, when there is a new version of an app in Google Play, only the parts of the app that changed are downloaded to users' devices. On average, a smart app update is a third the size of a full apk update. This means your users save bandwidth and battery and the best part? You don't have to do a thing. This is automatically enabled for all apps downloaded from Google Play.

App encryption: From Jelly Bean and forward, paid apps in Google Play are encrypted with a device-specific key before they are delivered and stored on the device. We know you work hard building your apps. We work hard to protect your investment.

Google Cloud Messaging for Android: This is the next version of C2DM and goes back to Froyo. Getting started is easy and has a whole bunch of new APIs than C2DM has to offer. If you sign-up for GCM, you will be able to see C2DM and GCM stats in the Android developer console. Most importantly, the service is free and there are no quotas. [Learn more.]

Starting from today, over 20 Android sessions at Google I/O will deep-dive in many of these areas. Join us in-person or follow us live.

Updated SDK Tools and ADT revision 17

Today we are releasing an update to the SDK Tools and the Eclipse plugin. Revision 17 brings a lot of new features and bug fixes in various areas such as Lint, the build system as well as the emulator.

Lint is a static checker which analyzes Android projects for a variety of issues around correctness, security, performance, usability and accessibility, checking your XML resources, bitmaps, ProGuard configuration files, source files and even compiled bytecode. It can be run from within Eclipse or from the command line.
New for r17:

• Added check for Android API calls that require a version of Android higher than the minimum supported version. You can use the new @TargetApi annotation to specify local overrides for conditionally loaded code. For more information, read here.
• Added over 40 new Lint rules for a total of over 80, including checks for performance, XML layouts, manifest and file handling. For a full list read here.
• Added ability to suppress Lint warnings in Java code with the new @SuppressLint annotation, and in XML files with the new tools: namespace prefix and ignore attribute. For more information, read here.
• Improved HTML and XML reporting and Eclipse integration. For more information, read here.

We've also made improvements to the build systems for Eclipse and Ant:

• Added strict dependency support for 3rd party Jar files. You can read more information here.
• Added support for custom views with custom attributes in libraries. Layouts using custom attributes must use the namespace URI http://schemas.android.com/apk/res-auto instead of the URI that includes the app package name. This URI is replaced with the app specific one at build time.
• Added a feature that allows you to run some code only in debug mode. Builds now generate a class called BuildConfig containing a DEBUG constant that is automatically set according to your build type. You can check the (BuildConfig.DEBUG) constant in your code to run debug-only functions such as outputting debug logs.

The emulator is seeing some big improvements as well:

• Thanks to contributions to AOSP from Intel, the emulator now supports running x86 system images in virtualization mode on Windows and Mac OS X. This allows the emulator running at near native speed. The drivers are available through the SDK Manager. Read more here.
• After adding webcam support and sensor emulation, we are adding experimental support for Multi-Touch input through a tethered Android device. (Read more here)

Finally, we are also releasing an updated Support Library with the following improvements:

• ShareCompat provides easy helper classes for both sending and receiving content for social sharing apps.
• NavUtils and TaskStackBuilder provide cross-version support for implementing the Android Design guidelines for navigating within your app including the action bar's 'Up' button.
• NotificationCompat.Builder provides a compatibility implementation of Android 3.0's Notification.Builder helper class for creating standardized system notifications.
• A new Library Project adds support for GridLayout back to API level 7 and higher.

You can get more information about these changes in the SDK Tools Release Notes and ADT Release Notes.

http://feedproxy.google.com/~r/PocketPcLive/~3/qF-srUIktoA/mango-gives-microsofts-plan-for-tango-and-wpv.html

Folks watch this week's Windows Phone view as the video content has a bunch of this week's good and bad stuffs about Microsoft's Windows Phone platform. This edition speaks more about the Windows Phone Mango devices being leaked and of course, great credits go to some developers posting their App testing logs.

http://feedproxy.google.com/~r/PocketPcLive/~3/Z2dh_TEixCY/windows-7-catches-up-market-share-in-us.html

It was recently revealed that after about 5 monthes of AT&T and T-Mobile phones running the OS, its market share has grown to almost 2%.