Phone Tools reaches Beta!
Url: http://phoney.codeplex.com
I am proud to announce the Beta version of the Phoney Tools. This version (v0.5) includes a few new features that are detailed below. The official release is still slated for MIX11!
Changes in this version include:
SelectSwitch Control
This control is used to show a toggling button that shows a 'indicator' to indicate enabling and an optional piece of text to indicate the choice. The control is meant to be a replacement for ToggleSwitch which users tend to want to swipe instead of tap. This is especially problematic on Pivots or Panoramas. You can see the control here:
SimpleLongListSelector Control
This control is used to replace the existing LongListSelector in the Silverlight Toolkit for the Windows Phone 7. In fact it derives from that control. The problem that this control is solving is that the LongListSelector requires you create a lot of templates and custom data structures to work well. While this is often going to be the right way, this derived version has default values to show a standard look and feel for the control.
Don't forget the complete feature list:
- FadingMessage class
- SelectSwitch Control
- SimpleLongListSelector Control
- BitlyHelper class
- PhoneLogger class
- ObservableObject class
- Phone Resources classes
- Converters
- GameTimer class
- MicrophoneRecorder class
- SoundEffectPlayer class
- PhoneNetworking class
You can get the library by going to http://phoney.codeplex.com or using NuGet to get the latest Phoney Tools package!
Let me know what you think!
Based on a work at wildermuth.com.
Good idea!
I like your Phoney library - using e.g. some converters and teh Phone Resource classes in an actual project. But I discovered one disadvantage so far: Because of some classes like the MicrophoneRecorder class the marketplace discovers some features in the submitted XAP the main application is never using. This wouldn't be so bad but in the marketplace are a few dependencies listed (e.g. "microphone"), causing some bafflement.
Perhaps you could split the library so you can add only those parts you really need? OK, I always could use the source code and remove those unneeded classes, but I like the idea of using NuGet ;-)
Greets,
Gordon