New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
News
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
PyBinding: Python Scripting for XAML
Posted by Jonathan Allen on Feb 04, 2010
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.
RelatedVendorContent
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
A practical guide to choosing the right agile tools
What's wrong with code behind
by
clem clem
Posted
Re: What's wrong with code behind
by
Assaf Stone
Posted
-
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. -
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).
2 comments
Watch Thread Reply