• Testing & ALM

    Leveraging Browser Quirks in WinJS

    Finally, browser quirks can be taken advantage of safely and effectively in WinJS. Read about my favorite quirk in Windows Store Applications and WinJS.
    January 31, 2013
  • .NET

    Windows 8 – Conference Buddy and Remote Data

    Windows API provides an excellent option for storing data on a server for use with your Windows 8 application.
    January 30, 2013
  • Testing & ALM

    Adding and Editing Records with AppBar Flyouts

    In my last post, I showed how to simple it is to remove commands from the user interface and place them into the AppBar. The commands for editing records and adding new records are both hardcoded to which record gets edited and what data gets added. That is not a very user friendly way to edit/add records. Windows 8 applications can take advantage of Flyouts for tasks such as getting data into an application, presenting a screen for editing a record, and any other interaction with the user. A Flyout is essentially a mini-form or user control (neither term is technically correct, but you get the point, I believe). Instead of swapping the currently displayed content with another screen for editing records and another screen for adding records, using Flyouts can help keep your users focused on their data and the task at hand.
    January 17, 2013
  • Testing & ALM

    Windows 8 AppBars in WinJS

    Microsoft’s guidance for Windows 8 applications is based on content over chrome. Development styles for prior versions of Windows often included navigation controls, buttons, tabs, and other non-content related items intermixed with the data, often obscuring the information that the application was trying to convey. This isn’t to say that we were all doing it wrong all of these years, as there wasn’t a mechanism (or even guidance) in place to provide an alternative.
    January 17, 2013
  • Testing & ALM

    MVVM in WinJS Part 2 – Observable Collections

    As I explained in my last post on MVVM in WinJS, the goal of the MVVM pattern (as well as the Presentation Model pattern) is to create a separation of concerns between the model and the view. This eliminates the need for the model to have knowledge of the view, and leverages data binding techniques to make sure the state of the model is always accurately represented by the view. The next step in implementing the MVVM pattern is Observable Collections. Just as important as having individual items being Observable by the View for changes are collections that will notify the View when items are added or deleted. Fortunately, Microsoft has made this extremely simple with the WinJS.Binding.List.
    December 20, 2012