Hey Jer,
Back then at Siemens we were starting to talk about using some SL within WPF and one path we were thinking of exploring was to render Silverlight withing the WPF web browser, and to use the JavaScript bridge to communicate. Unfortunately i never had time to try this and then i left Siemens.
Would you say that what you did here is similar to that, or did I miss something? One advantage i can think of for your solution is that it should perform better, right? How about the Windowless area, is it square or can it have any shape? I was out yesterday but will check your mails on a real computer soon.
Thanks,
Laurent
--
Sent from mobile
-original message-
Subject: Re: [WPF Disciples] Re: Silverlight rendered in WPF with no-airspace and interactivity!
From: Jeremiah Morrill <
jeremiah...@gmail.com>
Date: 15.12.2009 07:21
Shawn,
I'm just speculating from what I understand as of yet...Hw acceleration
(BitmapCache) in SL aside, I believe windowless mode performs worse in a
browser because the browser must compose both the rendered browser
html/document and the rendered silverlight screen together. I believe this
is why with windowless, you can have html content on top of silverlight
content. In the end, SL, windowless or not, still renders with GDI, the
only difference here would be the hDC it renders to. That's why with the
hosted solution I've hacked together the overhead of composition with the
browser is non-existent...but I won't pretend there's no overhead with WPF
composition ;). WriteableBitmap is a turd cake. I suspect InteropBitmap
will be even better, but and if I can't get the dirty area region, it might
be the way to go.
-Jer
> The thing with Windowless mode isn't that it takes more CPU, its that is
> performs more poorly with lots of animations.
>
>
>
> *From:*
wpf-di...@googlegroups.com [mailto:
>
wpf-di...@googlegroups.com] *On Behalf Of *Cory Plotts
> *Sent:* Monday, December 14, 2009 10:55 PM
> *To:*
wpf-di...@googlegroups.com
> *Subject:* Re: [WPF Disciples] Re: Silverlight rendered in WPF with