Patrick, Carl, Martin,
Lots of interesting techniques mentioned, some are overkill for my needs.
After experimenting for a few days I think my solution with a markup
extension is the one I like so far, mainly because it's done in XAML and
it's nicely terse. I don't have vast numbers of strings like some of you do
which might require extra infrastructure to help
I'm really impressed by what you can do with markup extensions and I find
they're a great way of doing tricky things in XAML without bloating the
size. I've got a growing number of extensions now to make coding easier. My
combined resource and converter extension can do this in XAML and the resx
file. I join the Uid and Property name to get the resx string.
<TextBox x:Uid="DemoText" Text='{util:FooRes}' ToolTip={util:FooRes}
Width="{util:FooRes}"... />
(in resx)
DemoTextText=This is the text for the box
DemoTextToolTip=This is the tool tip for the box
DemoTextWidth=120
I can also set Icon and ImageSource properties.
Greg
_______________________________________________
ozwpf mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
