BT

New Early adopter or innovator? InfoQ has been working on some new features for you. Learn more

PyBinding: Python Scripting for XAML

| by Jonathan Allen on Feb 04, 2010. Estimated reading time: 1 minute |

WPF developers often find themselves with an unappetizing choice. They have to either pollute their code-behind files with special case logic or create value converter classes, most of which will only be used once. PyBinding offers a third option, embedding small scripts right inside the XAML.

For example, let us say you want a block of text to be visible only if a data-bound property is non-zero. With PyBinding, you can set do this by binding the Visibility property to a fragment of IronPython code.

<TextBlock Visibility="{p:PyBinding BooleanToVisibility($[.OpenIssues]>0)}">

BooleanToVisibilty is a straight IronPython function that is defined in your application’s StartupScript.py file. The fragment “($[.OpenIssues]” refers to the OpenIssues property of the current data context. If you omit the leading dot, it would instead bind to a control with the name OpenIssues.

In testing, we have found PyBinding to have a brief performance impact while the DLR and IronPython are loaded. Once in memory, an informal review showed no significant difference between using PyBinding and fully compiled value converters.

PyBinding is available on Codeplex under the MIT license. It currently works with VS 2008 and .NET 3.5, but you can recompile it to target .NET 4.0. It does not currently support Silverlight.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

What's wrong with code behind by clem clem

That's a good tip but why do so many developers in the MVVM world try to have zero code in the code behind ?
At least it's the code behind is strongly typed.

Re: What's wrong with code behind by Assaf Stone

Code behind couples how the client looks with how it behaves. This causes brittleness that force you to rewrite your behavioral code when you wish to either reskin your application, or out-source your GUI+user-experience to a UX expert (3rd party firm, or even the designer in the next cubical).

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

2 Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and dont miss out on content that matters to you

BT