![]() The end user doesn't need to figure out where the picture will go. Wouldn't it be nice if you could just paste a picture directly to SharePoint, like you could in Word, or Windows Live Writer. You can't easily add a picture to your Rich HTML, you need to open a different browser window, upload the picture, then find a link to that picture and insert it back in the HTML. One thing that has always peeved me when using the Rich HTML control in SharePoint is when it comes to imbedding images. That's right, repeat after me: Silverlight, in browser, unmanaged code.Īnd I just happened to have the perfect problem I've been wanting to solve forever. Still, there are a few gems in this version over Silverlight 4, in particular, you can now run trusted mode in browser, and trusted mode now has access to platform invoke. I’m guessing the reason why Microsoft set it up this way to begin with had to do with being able to alter file calls without having to alter pages but that’s just conjecture on my part.īut like I said before: Since the iFrame method works as long as you close your frames properly there is no reason to start screwing around with the more cumbersome old method (unless you really want to that is).Silverlight 5 was quietly released to the world to very little fanfare, considering the looming Windows 8 launch with WinRT next year, and the world (at least, Microsoft)'s shift to HTML5. I can’t say if this is due to my poor knowledge of JavaScript or if it’s something else. I tried doing this with unimpressive (non-existent) results. Seeing as you don’t have access to the header area in a blog post this means you have to insert the JavaScript in the code itself. To make this work in any reasonable manner the source and parentElement parameters have to be defined from within the page itself which means the JavaScript contained within CreateSilverlight.js has to be extracted and somehow inserted into the page itself. The html code creates a wrapper and inserts the object defined in CreateSilverlight.js into it.įor blogging purposes this is pretty much a non-functional process.This file contains the source and parentElement parameters showing the browser where the application is located and where to put it (name of the wrapper). When you create a Silverlight application the file is put in whatever folder you export to but for web purposes it is recommended you use the one posted on the site. This file is (as far as I can tell) the Silverlight controller. If we dissect this process we see what happens: Source: “streaming:/32/SlLogo”,parentElement: Wrapper_SlLogo}) Var Wrapper_SlLogo = document.getElementById(“Wrapper_SlLogo”) Ĭreate a file called CreateSilverlight.js containing the following script: ![]() Insert html where you want the Silverlight application to appear: Insert script references in the header of the page: When you post a Silverlight application the “old” way you have to do three things: You can read the full description of the process here. Originally publishing Silverlight apps in a web page was a bit more cumbersome. Taking the long way round (using the cumbersome original method) The iFrame method works fine in WordPress as long as you close your call with a proper call afterwards. This problem persists regardless of what content is contained within the iFrame itself. The iFrame itself appears as it should but it ruins the rest of the code making the remaining page disappear. There’s clearly something wrong with how WordPress parses iFrame code. This in turn caused havoc on the remaining page. Thus the program auto inserted the full iframe close command right after the src call causing the remainder of the code to remain outside of the code. It seems WordPress isn’t very fond of shorthand endings like /> but prefers the full ending. The problem I had comes from the code from Tim Sneath’s blog: If you do not see the fancy cirlce animation you need to download the Silverlight RC plugin from Microsoft. Although it seems irrelevant considering.īelow is a Silverlight application posted using the iFrame method. The second half of the post still applies tho – the one about the “old” method. Read on to get an idea of what went wrong. My problem seems to arise from a combination of complicated scripts from Microsoft and bad parsing from WordPress not paying attention to the code I was posting. I encountered some weird problems trying to post Silverligth content in my blog and I can’t find anyone outside of who have done it.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |