- Posted: Jan 09, 2012 at 6:00 AM
- 13,655 Views
- 2 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Today's Mobile Monday post (I don't know if we're actually going to be doing "Mobile Monday" posts as a regular feature, like we do "Hardware Friday" posts, but it rhymed... is on an updated Windows Phone 7 toolkit, one that you might of heard of before...
- Slider touch area
- ColorSlider bug that was due to an adjustment in behavior to SuperSlider. this also effects the ColorPicker control as well.
- MetroFlow control
- Disabled look for ColorSlider
- Disabled look for SuperSlider
- Disabled look for ColorPicker
- Title added for SuperSlider
- Larger hit area on SuperSlider
- Custom Dialog Title for TimeSpanPicker
- identity tag no longer required, this was caused by a change in behavior with Mango
- Updated to Nov Silverlight Toolkit
- SuperSlider now defaults to proper height without having to manually putting one in
- update to movement monitor to prevent bubbling
- Fix for fast app switching in TimeSpanPicker
- TimeSpanPicker now mimics code base from SL Toolkit
- Fix for prompt positioning when SystemTray has an Opacity is less than 1 but greater than 0
- Fix for ColorSlider when given a 360 value would give a hue of black instead of red
- Fix for SuperSlider wasn't layout being set toggling from Collapse to Visible
Interested in seeing more about the new MetroFlow control? Den Delimarsky has written up a nice summary of it here, Addition to the Coding4Fun Toolkit - MetroFlow
Not seen the Coding4Fun.Phone.Toolkit before?
This wouldn't be a Coding4Fun post if we didn't look at the Solution...
Four projects, with one being a sample app where you can see all the controls in action.
What's the Coding4Fun.Phone.Site.Controls? WP7 is smart in how it loads assemblies/DLL's into memory, only loading those actually used, as they are used. The Toolkit has some "About" Channel9/C4f info, bitmaps, text, etc. Why should you, the Toolkit consumer have to have that "About" overhead in your app, just because you're using the Toolkit? You don't. That's what the Coding4Fun.Phone.Site.Controls project is;
These controls are for Coding4Fun projects. Namely our C4F About control which, if included in the Coding4fun.Phone.Control kit, would increase the DLL's size for selfish reasons.
The other projects, Coding4Fun.Phone.Controls and Coding4Fun.Phone.Toolkit are the meat of the Toolkit (funny that);
What's nice about the Toolkit is that each feature is very approachable. It's not an overly complication project and just about everything is easily discoverable and spelunkable. Interested in the code behind the new MetroFlow Control? Right here;
The important point is that not only is the Toolkit easily used in binary form (which of course you can get via NuGet, Coding4Fun.Phone.Controls.Complete, Coding4Fun.Phone.Controls [without TimeSpan], Coding4Fun.Phone.Controls.TimeSpan) but you can also easily see just how everything is done, letting you take you next project to the next [no, I'm not going to/ say level... must not say level...]
If you're building WP7.1(5) apps or toolkits for apps, you might want to check this project out...
Here’s a few more links you might find interesting: