PyBinding: Python Scripting for XAML
- Share
-
- |
Read later
My Reading List
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.
What's wrong with code behind
by
clem clem
At least it's the code behind is strongly typed.
Re: What's wrong with code behind
by
Assaf Stone
Educational Content
Writing Usable APIs in Practice
Giovanni Asproni May 19, 2013
Concurrency in Clojure
Stuart Halloway May 17, 2013
Hello stranger!
You need to Register an InfoQ account 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