Category: XAML

WPF XamDataGrid Configurator Released!

Introduction

Since joining Infragistics, I’ve spent the bulk of my time working on Visual Studio tooling (extensions) for Xamarin.Forms and WPF.  We have shipped an Xamarin.Forms Toolbox, Xamarin.Forms AppMap, and Control Configurators for these Xamarin.Forms and WPF Infragistics controls:

  • XamBulletGraph
  • XamCategoryChart
  • XamDataGrid
  • XamLinearGauge
  • XamPieChart
  • XamRadialGauge

The Infragistics Controls Configurators are a giant leap forward in Visual Studio design-time tooling, providing the developer with an unparalleled experience and feature set.  If you have not tried these or at least watched some of the below videos, I recommend you do so. 

An example of the unparalleled experience is the dynamic, design-time sample data created from your user types. Seeing a data grid or chart filled with live sample data from your users types is an awesome design-time experience.  Unlike the WPF XAML Designer feature that allows for injecting user specified sample data into the designer (I was the Microsoft PM on that feature), the Configurator sample data does not required the developer to do anything except create their types, build the solution, and set up a data binding.  Configurators are the gold standard of excellence for a design-time development experience.

The Infragistics documentation for the Configurators is here:

The Infragistics YouTube videos for the Xamarin.Forms and WPF Configurators are in this list:

The Infragistics YouTube videos for the Xamarin.Forms are in this list

WPF XamDataGrid Control Configurator

configurators

The Infragistics WPF XamDataGrid is a feature rich, performant data grid that meets the needs of demanding enterprise line-of-business applications. I have a lot of real-world experience using this data grid in my WPF enterprise applications before joining Infragistics.

The above image shows the Configurator extension dynamic sample data being rendered.  The Orders collection has 5 Order instances, each Order has 5 OrderDetail instances, and each OrderDetail has 5 Feature instances.  All dynamically created from the DataSource property binding to underlying user data types.

Notice the Customer.Status field, this is an Enum, this is type generated as well.

Configurators enable Infragistics customers to more easily learn and discover the control API’s because as properties or collections are changed at design-time, these changes are immediately reflected in the Configurator UI. The Configurators also have customized property window categories that group properties by feature.

Links to related online Help Topics are also provided in the Help ribbon group.

If you are a WPF line-of-business developer, I strongly encourage you to investigate Ultimate UI for WPF. Feature rich controls, outstanding support, and design-time Control Configurators for visually configuring your controls.

Have a great day,

Just a grain of sand on the worlds beaches.

Xamarin Dev Days Cranbury NJ

Infragistics is hosting Xamarin Dev Days on 19 Nov 2016 at our corporate office in Cranbury, NJ.

The very popular Xamarin Dev Days event sold out in one day, but there is a wait list and you can register here.

In addition to the standard curriculum, there will be an optional Bonus Content session given by Infragistics Engineers that wrote the Infragistics Xamarin Forms product.

Attend the fun day of learning with fellow developers and MVP’s at our excellent facility.

Have a great day,

Just a grain of sand on the world’s beaches

 

 

 

XAML Designer Brush Editor Fixed

Introduction

Since the release of Visual Studio 2015 Update 3, the VS XAML Designer pop up brush editor quit working in the Properties window when properties were sorted by name, or when properties of type brush were not in the Brush category.  This issue affected both Visual Studio and Blend for Visual Studio 2015.

Fix

Microsoft posted the fix in this cumulative servicing update:

Microsoft Visual Studio 2015 Update 3 (KB3165756)  

https://msdn.microsoft.com/en-us/library/mt752379.aspx

I have installed the update and tested various controls and use cases and can confirm the fix corrected the problem.

Close

Have a great day.

Just a grain of sand on the worlds beaches.

 

Xamarin Forms Bindable Picker v2

Introduction

I’ve updated the BindablePicker from a previous blog post, added new features and created a github reopro for the code.

Xamarin Forms is a new and cool API for quickly building native apps for IOS, Android, and Windows UWP in C#.

The Xamarin Forms API comes with a primitive Picker control that lacks typical bindable properties that developers expect a Picker (similar functionally that a desktop ComboBox has) to have.

Xamarin Forms makes it very easy for developers to extend the API, write your own custom controls, or write custom renderers for controls.

This BindablePIcker is the result of studying blog and forum posts and receiving feedback and bug report on the original version.

API Comparison

Xamarin Forms Picker API

  • SelectedIndex (bindable)
  • Items (not bindable)

Bindable Picker API

  • ItemsSource (bindable)
  • SelectedItem (bindable)
  • SelectedValue (bindable)
  • DisplayMemberPath
  • SelectedValuePath

New Features Added

  • Support for collections that implement INotityCollectionChanged like the ObservableCollection

Bug Fixed

The original BindablePicker did not correctly set the SelectedItem after the ItemsSource was refreshed at runtime.

Bindable Picker Source

This repro contains a project that demonstrates scenarios for using this control and it has the source for the BindablePicker.

https://github.com/Oceanware/XamarinFormsBindablePicker

Training Video – XAML Power Toys BindablePicker Scenarios

This short video explains three common use cases for the BindablePicker.

Close

Have a great day.

Just a grain of sand on the worlds beaches.

Visual Studio XAML Designer Needs Culture Support

Introduction

I just got back from a trip to Japan.  It’s amazing when you leave your country and discover how developers around the world are solving problems.

One problem that should be very easy to address is actual globalization and culture support in the XAML Designer.

I met with several customer that ship WPF products that support Japanese, Chinese, and English.  These customers use the XAML Designer to view their forms in all supported languages.  Currently it is a real pain to quickly display XAML forms in other languages.

One customer actually wrote their own localization system to get around the pain of using the current culture support in the Visual Studio 2015 XAML Designer to render their forms in multiple languages.

There is a very good article on Code Project that helps developers to be productive:  http://www.codeproject.com/Articles/35159/WPF-Localization-Using-RESX-Files

Solution

I’m proposing to the XAML Tools Team that they provide a ComboBox at the bottom of the XAML Designer that allows the developer to switch cultures and when they do, reload the designer using that culture.

Microsoft is a global company, it’s customers write software all over the world in many languages. The XAML Designer has an opportunity to come along side these developers and enable them to be more productive.  I hear the term “productive” in many Microsoft keynotes and presentations.  Thank you for helping international developers all over the world.

MicrosoftPlease

Close

Hope this helps someone and have a great day.

Just a grain of sand on the worlds beaches.