Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
News
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Unifying Hardware Access across Windows Phone, Android, and iOS
Posted by Jonathan Allen on Dec 01, 2011
When .NET developers target mobile devices they have three API sets to choose from: Windows 7, MonoTouch, and Mono for Android. While the .NET framework standardizes a lot of stuff, there are many hardware features that simply aren’t covered by the Base Class Library. Xamarin.Mobile looks to greatly increase the amount of reusable code by standardizing the API across the platforms.
Like .NET itself, Xamarin.Mobile is an abstraction layer that sits on top of the native API. In exchange for giving up some of the underlying operating system capabilities, developers no longer need to re-implement common functionality for each of the three platforms. The areas Xamarin.Mobile is proposing to cover are:
- Contacts
- Geolocation
- Compass and Accelerometer
- Video and Audio
- Notifications
The most notable area missing from the list is the user interface itself. Much like its predecessors Ximian and Novell, Xamarin is still dedicated to their vision of platform specific, first-class user interfaces written in .NET/Mono.
RelatedVendorContent
Building HTML5 Apps in Hours, Not Days
Adopting Git for the Enterprise: Risks and Considerations
Why NoSQL? A Primer on the Rise of NoSQL
No comments
Watch Thread Reply