Easily done.
So basically, (to oversimplify) it would go something like this.
The hosting UI application could simply have a panel on an WPF form.
Assign the Form.Content with appropriate XAML from remote process.
At appropriate time, parse the Controls collection looking for known input
types
Ignoring anything else
Harvest input values and marshal to remote process.
If this works out, perhaps now I'll have the justification to actually spend
some time with WPF. I like this MUCH better than fighting HTML, which I
generally loath for integration into rich/"thick" apps. It's like that
quote from VB classic. Something to the effect of "VB makes the easy stuff
trivial, and the hard stuff almost impossible." Having been graced with
very particular usability requirements/experts, getting that last little
"but it has to look like this" mile has been nothing but hassle with HTML in
any flavor/framework...
Russ
-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Curt Hagenlocher
Sent: Friday, July 27, 2007 3:04 PM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: Re: [ADVANCED-DOTNET] Dynamic remote UI - XAML?
On 7/27/07, Russ Alan <[EMAIL PROTECTED]> wrote:
>
>
> If I could easily(?) instantiate that XAML, show it to the user, then
> harvest results (via reflection?) to marshal back to the remote machine,
> that would be spot on.
The instantiation part is certainly easy -- you can replace the content of a
Window from XAML with pretty much one line of code. If the XAML is
accessible through a Stream,
this.Content = XamlReader.Load(stream);
--
Curt Hagenlocher
[EMAIL PROTECTED]
===================================
This list is hosted by DevelopMentorR http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
