If you then had a bunch of HTML content to display then life became a little difficult for this class of apps because there was no browser around any more and so HTML display wasn’t possible for out of browser apps until… When Silverlight 3 came along, it was possible to take a Silverlight application out of the browser and you ended up with a situation like this Īnd it’s possible for these applications to run online/offline and to automatically update themselves. ![]() ![]() Silverlight has a pretty strong interoperability layer between the CLR code running inside the plug-in and the HTML DOM and JavaScript of the surrounding page so you could use Silverlight to exercise some “control” over the hosting HTML/JS and vice versa but HTML was the starting point.Īnd so if you had a bunch of HTML content to display and wanted to mix in a bit of Silverlight then it was fairly clear what your options were until… The HTML was hosting Silverlight rather than the other way around. ![]() ![]() In the early days of Silverlight, it was fairly easy to understand that Silverlight content would always be rendered inside of a browser window (whether that be IE, Chrome, Firefox or Safari) where it was surrounded by the hosting HTML content and JavaScript.
0 Comments
Leave a Reply. |