My Rants and Raves about technology, programming, everything else...
I spent most of the last week with my early demo Windows Phone 7 (e.g. WP7) phone as my primary phone. See I am a Verizon customer currently and therefore I couldn't use Verizon on the demo phone (as it takes SIM cards and Verizon can't spell SIM). So I took the opportunity while in Europe to get a pre-paid SIM card and use it as my main phone (since my Droid was useless there). You're probably wondering what my impressions were? Well, two caveats to start with...I have bet pretty heavily on the phone so I am not exactly a neutral party, but I'll try to be. Also, I've never owned an iPhone (AT&T is true evil incarnate) so take that for what its worth.
History with Android
The last two stops of the Silverlight Tour are headed to Atlanta and Portland (OR) in the next two months. The Silverlight Tour Workshop is a three-day course on Silverlight 4. It divides the content into three distinct areas: Design, Development and the Server-Side. Students should be able to develop Silverlight 4 applications once attending the workshop. The Workshop is structured with a mix of didactic lessons, demonstrations and hands-on labs. Each student will leave the workshop having created several small Silverlight applications. This variety of learning techniques will ensure that all students become proficient in the technology quickly and in an exciting way.
The Silverlight Tour Workshop also includes a complimentary license to Telerik's RadControls for Silverlight for every attendee* (a $999.00 value). For more information on RadControls, you can visit there site at http://telerik.com.
This week I am in Zeist, The Netherlands at the SDC conference. This morning I did a talk on "Drinking from the Fire Hose" which included a discussion on how I keep up with technology. A couple of key think I shared in this session were:
In response to watching smart people online, I was asked to mention which RSS Feeds and Twitter accounts I follow. I separate the RSS feeds I follow into two different types: daily blogs that post often (e.g. Engadget) and smart people who I need to hear when they only blog once a month. For the first group I use iGoogle to keep panes of headlines so I can quickly scan the headlines for things I am interested in, but I don't need to keep up. Here are some of those blogs:
While I recognize my original schedule is slipping, let's continue the ten part Windows Phone 7 architecture discussion. In this sixth part of the article series, I want to discuss messaging in phone applications. If you've missed the past parts of the series, you you can visit them here:
When I say "Messaging", I don't mean SMS or IM, but instead I mean smart ways of being able to talk between different parts of the application.
In this fifth part of my Architecting Windows Phone 7 applications I will tackle the nature of tombstoning. If you've missed the past parts of the series, you you can visit them here:
For the uninitiated, I think its important to understand the nature of how applications run on the Windows Phone 7. The nature of the phone is very different from Windows Mobile before it and Android is now. The way it works is to only allow one application to run at one time inside the sandbox. While some applications will have the ability to run in the background, they are specialized applications that do not run in 'the sandbox'. Your applications will have to live without background processing. But how does this work?
OAs some of you know, in learning to build Windows Phone 7 applications, i've come up with several applications for the phone. Some of the apps started as Demo's for conferences (e.g. Winning the Lottery) and others are ones I wanted to write to get familiar with other parts of the phone API's.
These applications are now on the Windows Phone Marketplace. Obviously most of you won't have phones, but for the developers who have received their phones, these apps are available.
In this fourth part of my Architecting Windows Phone 7 series, I will tackle client-side data. If you've missed the past parts of the series, you you can visit them here:
One of the main complaints about Silverlight on the phone (especially to WinMo veterans) is the lack of a local database store. But being able to store data is still really possible, it is just that any data you store locally is not necessarily in a database format. But maybe that doesn't matter as much as you might expect.
Blogging everyday is getting exhausting. But seriously folks (and don't forget to tip your wait staff)... Here in day three of Architecting Windows Phone 7 applications, I want to talk about locating the view-model. If you've missed the past parts of the series, you you can visit them here:
I will take the assumption that you've read about the MVVM pattern in Silverlight (my MSDN article is here if you want a refresher).
In this second part of my Architecting Windows Phone 7 applications, I want to tackle the use of the Pivot and Panorama control. If you missed the first part of the series, you you can visit it here:
As I've seen, many developers want to use these controls so determining the best path here is an important discussion.