On the heels of the Windows Phone Developer Tools and Silverlight for Windows Phone Toolkit releases I saw a lot of exhaling going on in the hallways today.  Apparently Jeff saved his largest one for an avalanche of knowledge on Twitter in the late afternoon.  Jeff Wilcox is a developer on the Silverlight team and has been working on the Silverlight for Windows Phone initiative as well as the toolkit released today.  He was headed out on vacation but decided to throw out some words of wisdom for Windows Phone developers working in Silverlight.  Here’s some of those nuggets – I wanted to capture them before he left because who knows how long they’ll stay in Twitter.  It reads like a true guide to developing great apps on Windows Phone…

• Panorama looks nice, but Pivot will offer faster start time.
• You can also set a Background image to a Pivot. You won't get the parallax effect, but it is another option.
• Be aware of how many pano and pivot items you do have. Memory expands quick when you have a lot of views and images!
• Even if you have a 30k compressed JPEG image, at runtime that becomes an uncompressed surface that may take several MBs of memory
• Pivot and Panorama can have UI element headers and titles, too, but you'll need to apply your own styling (fonts and sizes)
• Beware that UI elements larger than 2000x2000 pixels that are bitmap cached clip on Windows Phone 7. We know it isn't perfect, but beware k?
• Setting SelectedIndex before the items are set on a Pivot causes an exception. Wrap in a try/catch or wait for loaded (sorry!)
• A slideshow app in 5 minutes: Pivot with null Header and Title and item headers. Beware memory use though.
• A lot of people try building 'wizard' screens with panorama & pivot control. Please don't do this! Thx, the "UX gods"
• Layout is a killer. But like death, you eventually have to pay it for everything.
• So consider delay loading controls and screens. A Panorama with a billion items will take forever to load due to layout.
• If you're not using PerformanceProgressBar, I'll send @JustinAngel after you ProgressBar for Windows Phone 7
• If your app rocks and starts really quick *on a device* consider not using a splash screen
• It's true. Your 6-core machine running the wp7 emulator is NOT indicative of device (single core!) performance. Beware!
• We've talked perf before... Content over Resources for images means fast startup time http://bit.ly/9DhVbd
• If you're using Panorama, a Resource background will load immediately compared to Content
• Remember that for ingestion to the marketplace, your apps need to consume under 90MB of memory
• However on devices with > 256MB, its cool to use more *in those cases
• long deviceTotalMemory = (long)DeviceExtendedProperties.GetValue("DeviceTotalMemory");
• long applicationCurrentMemoryUsage = (long)DeviceExtendedProperties.GetValue("ApplicationCurrentMemoryUsage");
• long applicationPeakMemoryUsage = (long)DeviceExtendedProperties.GetValue("ApplicationPeakMemoryUsage")
• Your compositor thread should rock out around 60fps all the time please. #wp7dev perf counters: http://bit.ly/busJIi
• If your UI thread gets pegged, your compositor thread will suffer... remember your BackgroundWorker kids!
• Unfortunately the "Analytics" type from desktop Silverlight is not on the phone today, so you can't measure CPU in a regular app
• Having a single DispatcherTimer in your app can affect your battery life regardless of interval. Chose wisely
• You can set the Foreground property on Pivot to set the title and header text color
• Using a map control inside a Panorama or Pivot is not recommended for a number of UX and technical reasons. Navigate to a subpage.
• Please use text styles and never hardcode sizes or default fonts.
• The panorama/pivot items expect most their contents to have a 12px margin left/right for UX reasons. The default styles have this.
• So if you have something in a pano/pivot item with 0 margin & padding, your UX will be funky
• Fill rate is super important. Keep it under 2.5 please
• What is fill rate? 1.00 means one screen of pixels being rendered every frame.
• Check your apps for extra, un-needed background colors on pages, controls, etc.. They impact perf.
• That sexy "tilt" effect? Use Peter's behavior http://bit.ly/90Z1yR and/or check out the MSDN docs
• DataTemplates with a bunch of StackPanels and Grids? Try to simplify to a Grid with the right col/rows instead for perf wins.
• Unit testing in a quick and dirty way is possible on the Windows Phone thx to the sl unit test fx. http://bit.ly/a0DWah
• Only use Dispatcher.BeginInvoke when you must. Look at SmartDispatcher (ps old code sry) http://bit.ly/axHh36
• For a "wide" Panorama item, set the item's Orientation to "Horizontal"
• Play with the cache and redraw vis. settings to see what's being cached in your app http://bit.ly/busJIi
• Things in a list/scroll viewer are often automatically bitmap cached by Silverlight for Windows Phone runtime
• If you have a progress bar with IsIndeterminate="True" in your app, even if its hidden those storyboards are costly! Set to False!
• We did work on Windows Phone 7 to move more networking to the background thread - hope it helps
• When a Panorama loads, all its items go through a render pass. For pivot, it is done incrementally for neighboring items.
• When making web requests, see if the service lets you scope down the fields that are returned for quicker perf (and JSON over XML!)
• If you navigate to a subpage, the old page will stick around - so complex pano/pivot pgs stay in memory unless you're proactive
• The "app deployment tool" installed with the dev tools lets you run others apps in emulator/device without needing source
• We optimize for loading some things from isolated storage. Images from an isostore stream may load faster than a MemoryStream
• If your source files have "Black" or "White", you might be doing it wrong. PhoneForegroundBrush, PhoneBackgroundBrush instead!
• If your control's dep. property has a change handler, animating that prop. will always happen on the UI thread (no gpu accel.)
• Animating Opacity on a CacheMode="BitmapCache" element = compositor thread (GPU!)
• In the RTM tools, scroll viewers all have the "bounce" effect automatically
• If you ignore the phone's theme (and go all light bg, like the mail app), your scrollbarsmust be retemplated or you won't see them!
• Although data binding is not evil, an observable col. with a complex data temp. and 200k items is evil.
• The web browser control won't let you NavigateToString until it has loaded.
• If you have an app with a lot of different web browser controls, think about consolidating to one, so it only has to load once.
• Panorama is designed to be a starting place. Think whitespace. Not tons of data
• Free performance win: when you use Panorama the way the UX guidelines recommend, it is faster! http://bit.ly/9zTxtU
• Those theme xamls for #wp7? Yeah they are in %ProgramFiles%\Microsoft SDKs\Windows Phone\v7.0\Design\
• Resist the urge to Panorama every app.  It is a sweet UX thing when used right…but not just because.
• Resist the urge to iPhone gradient your apps. Think outside the box! Also it avoids color banding...

So as you can see, he sort of knows what he’s talking about :-).  Go subscribe to his blog and follow him on Twitter.  Other helpful links:

• Jeff on Hanselminutes talking about Windows Phone 7 application performance
• Creating High Performance Silverlight for Windows Phone Applications (whitepaper)
• Shane Guillet on optimizing Windows Phone Silverlight Applications (video)

Thanks Jeff for sharing your awesomeness!

Hope this helps!

Well, the official Windows Phone Developer Tools are out!  Go get them. (warning likely some caching issues..direct installer here.)

The awesome Silverlight toolkit team is at it again, this time for Windows Phone 7.  The team is releasing a series of controls/libraries to help WP7 developers fill some gaps and simply make things easier and more consistent.  The initial set includes the following:

• ContextMenu control
• DatePicker and TimePicker controls
• ToggleSwitch control
• GestureHelper library
• WrapPanel control

These controls are available for download including the source code.  Here’s a quick synopsis of them for you to enjoy.  Note that the “toolkit” prefix on the controls is declared in the app as:

   1: xmlns:toolkit="clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone.Controls.Toolkit" 

   2: xmlns:toolkitPrimitives="clr-namespace:Microsoft.Phone.Controls.Primitives;assembly=Microsoft.Phone.Controls.Toolkit"

after adding a reference to the Microsoft.Phone.Controls.Toolkit assembly.

ContextMenu

In WP7 there is a notion of a context menu, where when the user holds down an item (tap and hold) it pops up a menu in-line with some options.  This is used in areas like the application list, where if you tap and hold an application you get the option to pin it to the start menu, uninstall, etc.  For the toolkit control this is implemented as a ContextMenu service.  For example, if I wanted to enable a context menu on my canvas I would use this markup:

   1: <Canvas HorizontalAlignment="Left" VerticalAlignment="Top" Width="345" Height="91" Margin="0,50,0,0">

   2:     <toolkit:ContextMenuService.ContextMenu>

   3:         <toolkit:ContextMenu>

   4:             <toolkit:MenuItem Header="pin to start menu" Click="OnMenuClicked" Tag="START_MENU" />

   5:             <toolkit:MenuItem Header="delete" Click="OnMenuClicked" Tag="DELETE" />

   6:             <toolkit:MenuItem Header="share" Click="OnMenuClicked" Tag="SHARE" />

   7:         </toolkit:ContextMenu>

   8:     </toolkit:ContextMenuService.ContextMenu>

   9:     <Rectangle Fill="#FFF4F4F5" Height="91" Stroke="Black" Width="345"/>

  10:     <TextBlock TextWrapping="Wrap" Text="Tap and Hold (zoom)" Foreground="Black" Canvas.Left="71" Canvas.Top="27"/>

  11: </Canvas>

And the result would look like:

There is an option to disable ‘zoom’ of the context menu, which follows the UI consistency of the device itself and is the default.  Additionally you could implement the actual command using ICommand on the particular item.

DatePicker and TimePicker

These are two controls I’ve seen attempted to create to mimic the actual device controls in the WP7 OS itself.  Some implementations have been better than others.  Here the UI is matched with the semantics of the device.  When using the control, it will automatically provide you with a TextBox input and when the user selects it, the picker will display.  The markup is very simple:

   1: <toolkit:DatePicker />

to produce the user experience when the user clicks on the input area:

While shown above is the DatePicker, the TimePicker operates in similar fashion.

For the pickers you may notice that in my screenshot above I have the checkmark and the “x” icons in the ApplicationBar.  If you didn’t read the code comments in the toolkit you likely have “x” icon placeholders and are wondering why.  The toolkit provides the necessary icons for these, but you have to bring them into your application.  Once installed, look for them in the SDK folder and then add them using this well-known path:

Once you have the PNG files there, be sure to mark them as Content so they are included correctly and then you should be good!

ToggleSwitch

If you notice areas in WP7 that have simple on/off settings you may want to provide a consistent look in your application.  The ToggleSwitch control does just that, providing not only the actual ToggleButton, but also the area for label/etc.  This area could be templated as well so if you needed more than just a single text heading listing.  The code:

   1: <toolkit:ToggleSwitch Header="my setting name" Height="118" Margin="0,0,-24,-34" Width="480"/>

and the resulting UI:

GestureHelper

Wish you had a library that made it easier to know when a ‘flick’ or ‘pinch’ gesture happened?  Enter GestureHelper.  Using this on elements like this:

   1: <Image x:Name="GesturedImage" Source="dividbyzero.jpg" HorizontalAlignment="Center" VerticalAlignment="Center" Width="450" 

   2:     RenderTransformOrigin="0.5,0.5">

   3:     <Image.RenderTransform>

   4:         <ScaleTransform x:Name="ImageScaling" ScaleX="1" ScaleY="1" />

   5:     </Image.RenderTransform>

   6:     <toolkit:GestureService.GestureListener>

   7:         <toolkit:GestureListener PinchDelta="OnPinchDelta" />

   8:     </toolkit:GestureService.GestureListener>

   9: </Image>

enables you to respond to these events when they happen and react accordingly:

   1: private void OnPinchDelta(object sender, PinchGestureEventArgs e)

   2: {

   3:     ImageScaling.ScaleX = e.DistanceRatio;

   4:     ImageScaling.ScaleY = e.DistanceRatio;

   5: }

Very helpful library!!  NOTE: the above sample is actually not goot ‘pinch’ scaling for an image, but merely here to demonstrate a quick point.

WrapPanel

The WrapPanel has been specifically ported for WP7.  Using the similar syntax:

   1: <toolkit:WrapPanel Orientation="Horizontal">

   2:     <Rectangle Fill="Blue" Width="100" Height="100" Stroke="Black" />

   3:     <Rectangle Fill="Red" Width="100" Height="100" Stroke="Black" />

   4:     <Rectangle Fill="Green" Width="100" Height="100" Stroke="Black" />

   5:     <Rectangle Fill="Gray" Width="100" Height="100" Stroke="Black" />

   6:     <Rectangle Fill="Yellow" Width="100" Height="100" Stroke="Black" />

   7:     <Rectangle Fill="Orange" Width="100" Height="100" Stroke="Black" />

   8:     <Rectangle Fill="Teal" Width="100" Height="100" Stroke="Black" />

   9:     <Rectangle Fill="White" Width="100" Height="100" Stroke="Black" />

  10:     <Rectangle Fill="Pink" Width="100" Height="100" Stroke="Black" />

  11:     <Rectangle Fill="Magenta" Width="100" Height="100" Stroke="Black" />

  12: </toolkit:WrapPanel>

would produce the elements within the WrapPanel to be placed accordingly for you:

This will be helpful especially in areas of displaying items in storage locations (i.e., pictures, album art) I think.

Summary

These controls are being made available for you to freely consume in your applications.  Go to the Silverlight Toolkit site right now and download the Silverlight for Windows Phone Toolkit and begin incorporating them into your applications today.  Be sure to leave feedback on the Codeplex site with any issues you may find with your scenarios.

Be sure to visit the Silverlight Toolkit site for the bits and also ensure you subscribe to Jeff Wilcox and David Anson’s blogs for what likely will follow more detailed and useful information about the toolkit items!

Hope this helps!

Today, Seesmic more broadly launched Seesmic Desktop, a refreshed platform for interacting with various social media outlets like Twitter, Facebook, Google Buzz, etc.  Seesmic has been one of the leaders in this space providing client applications on various platforms across web, desktop and mobile and providing us with unified views of our interaction with others online.

You may have remembered seeing Loic on stage at MIX last year demonstrating their first preview of this updated platform and inviting developers to be a part of extending the shell.  That’s right…their platform is extensible!  A great application that I can also modify to my needs?  Double rainbow…what does it mean!?

I went to the evening social session at MIX to hear about how they would be enabling developers to extend the platform.  In introducing the concept of plugins, it was made clear that the Seesmic Desktop Platform (SDP) would be leveraging the Managed Extensibility Framework (MEF) that was to be included as a part of Silverlight.  Seesmic would define MEF contracts that as long as developers adhered to them (and of course implemented any required interfaces for actual functionality) then the plugin would be able to extend the platform.  The most grandiose idea can be simply stated as if you don’t like how Twitter is represented in Seesmic, fine…change it.  Of course, I suspect most people will be just fine with their implementation and choose to extend in other areas as I’ve done.

Admittedly I’ve got a vested interest in being excited about SDP…after all it is built using Silverlight.  However, I’m also very much into being a part of my online connected network via Twitter.  Prior to SDP I did not use Tweetdeck or some of the other popular multi-column ones…but was a user of Twhirl.  I loved the simplicity that it provided but did desire for slightly more.  I never got into Tweetdeck and honestly I don’t know why…it just never stuck to me in how I interacted online.  The thought of customizing my own experience, however, is what intrigued me to SDP.

I immediately got started writing some plugins, starting with something that I use often, a translator for reading messages incoming that aren’t in my native English.  Some may scoff, but when you monitor a lot of different things online, this becomes important as I don’t want to ignore things that might be interesting.  I chose to use Microsoft Translator services and in a few hours had my first rough draft plugin completed.  It was very rough (mostly because I desired a lot of things from Seesmic).  I showed Marco my warez and started to give feedback on what I think the platform needed for this specific use case as well as to make my life easier. 

Since then the platform has significantly evolved to accommodate most developers needs.  Seesmic has been very responsive on the developer forums for the platform to needs and questions.  Getting started writing a plugin couldn’t be easier for a Silverlight developer, but I’ve tried to make it even simpler (as I was sick of doing the same tasks myself).  I created some templates that you can download from the Visual Studio gallery that will help get you started.  Once installed you’ll see a nice new project template in Visual Studio:

This will stub out the initial shell you will need (you’ll still need to add the correct references to the SDP SDK).  From there you can add item templates for the base plugin type or other types: posting actions, timeline items, etc.  Here’s what my templates provide:

These should give you some good jumpstart code to provide some of the necessary plumbing that would be required.  This is NOT a substitute from understanding the platform!  You need to read the docs and understand the interaction of the API with the platform to be successful.

TIP: When you add references to the Seesmic SDK assemblies, change their Copy Local attribute (in properties) to false so you don’t end up shipping them with your plugin.  Since they are already a part of the platform there is no reason to ship them with your plugin (and this makes your plugin size smaller).

To me, I think the easiest plugins to create are those that implement a URL shortener, posting action or a timeline processor.  These are the areas which would allow for very fast customization.  The account providers is likely the most time consuming as you could imagine as you are interacting with authentication schemes, etc. 

I’ve created a few initial plugins that you might be interested in and you can download them here.  I’m really excited about this platform and the fact that I can extend it to make my interaction with things I care about uniquely my own.  Install Seesmic Desktop today and start developing using the SDK!

After a longer-than-should-have-been delay (you can blame me for that) allow me to introduce JetPack.

I’m really excited about this theme and the work that our team put together here.  You may have see Tsitsi talk about theming in general and introduce this theme on Silverlight TV.  The challenge behind this theme was to take some of the excitement around other Silverlight themes and create a great looking overall theme that could be used for line-of-business applications, but also extended as desired by any other application.

Working with the team at Pixel Lab, our small team looked at areas of inspiration from various online and client applications that are popular and what worked well about the user interaction on those themes.  Robby and team did a great job in my opinion of creating a very well designed theme that can be used in almost any circumstance.

During this September refresh of the themes we’ve also updated the previous 3 themes: Cosmopolitan, Windows and Accent Color with some minor fixes and tweaks based on some feedback we got.  You can see a preview of the various styles in JetPack here.

We hope you enjoy JetPack as much as we do!  We’ve provided the theme pack in the same way as we have the others, as templates for Visual Studio 2010 and Expression Blend 4 and the raw assets (resource dictionaries) for you to download.  Each Visual Studio template is build for modeling the Silverlight Navigation Application template and the WCF Ria Services Business Application template.  We’ve provided the VSIX installer formats so you just need to download that, double-click and you’ll have them in your File…New Project window for selection.

Thanks for your patience through the release of JetPack, there were some moving parts in the end (mostly delays in our release management system which underwent some changes) that were human-caused [blame me] but we’re glad to finally get it out in the wild!  Download all the themes here.

Hope this helps!

September is here (apologies for being late - in all honesty I wasn't inspired by this months' selections)…time for an updated Windows 7 Smashing Magazine theme pack!

The September themes seem to be continuing the focus on 'summer' things.  So here is your September 2010 Windows 7 Theme Packs for wallpapers – unfiltered and uncensored – about 75 wallpapers in all.

• Smashing Magazine September 2010 Windows 7 Theme (calendar)
• Smashing Magazine September 2010 Windows 7 Theme (no calendar)
• Smashing Magazine Desktop Wallpaper: September 2010 (original post)

For details on these and to see past ones, visit the Smashing Magazine Windows 7 Theme information for the specifications I used for the theme pack as well as previous themes.  Want to participate and submit yours?  Join in!