AGHost.js Strategy

Hot Topic

Does VISTA Ultimate not support BDD2007 deployment ??
pesky DLM file
When does workflow instance released?
Port binding in Vista
Time Zone problem in Vista
What is the Proper Way to Build VistaBridge Sample in Vista SDK RTM?
UAC Shield in menus?
Problem with Delay activity in listener activity Sharepoint Workflow
Problem calling web service with more than 1 Windows Workflow at a time
How to use in my app the preview provided by IPreviewHandler?

Windows Vista

Conflict bewteen Volume Mixer and global hook in Vista
Request for Swimlane tool for WF
Please add the ability of image repeat to the Stretch
Smartcard based authentication with CardSpace
Mobile center on Vista X64 RTM
Understanding Directshow better - filter context
How to get the list of Running Instances?
DLL priority
XAML caching issues
Why using "javascript:functionName"?

AGHost.js Strategy

I've been looking into how aghost.js works and I am curious about something. I like the strategy that YouTube and their ilk use for allowing visitors to embed their player in your site and wonder if the Dev Team could explain why this same strategy isn't used in WPF/E. This works with WPF/E:

 
  <object id="theHost" width="400" height="400" 
        classid="CLSID:32C73088-76AE-40F7-AC40-81F62CB2C1DA">
   <param name="Source" value="plugin.xaml" />
   <param name="BackgroundColor" value="White" />
   <embed id="theHost" width="400" height="400" 
         pluginspage="http://go.microsoft.com/fwlink/ LinkID=77792&clcid=0x409" 
         Source="plugin.xaml" BackgroundColor="White" 
         type="application/ag-plugin" />
  </object>

Note that the embed tag is inside of the object tag. This works on Windows on both IE and FireFox. (Don't have a Mac to test Safari and Firefox). Any reason we don't use this strategy

I do understand one specific reason for the way that aghost works in that by writing to innerHtml you are avoiding the "click this control to activate it" but that the IE lost Patient fight forces IE to introduce. But even if you are using that strategy, it would seem easier to just output this than to have to detect the browser.

TIA




Answer this question

AGHost.js Strategy

  • Marcos Torres

    As you saw in the other post, I don't have anything between the script tag and the first element. Still wonky. I've posted a full sample on the other post.

  • Greenwu

    Couple of quesitons about your comment:

    1. You mention the document.write (for the activation hack), but the versions of aghost.js that I have do not do that, but instead set the innerHtml. Did you mispeak or did I have an old aghost.js
    2. Do you know of any issues with FireFox (on Windows, haven't tested under Mac) using <embed /> and using SourceElement instead of Source I can't seem to get it to work at all.


  • ram013

    We have the embed and object tags structured like that just for compatibility across all browsers that we support. Aghost.js is just a helper function for doing the document.write (activation for IE).

    You are welcome to modify the aghost.js file for your own needs (such as not using document.write except on IE).

    -mark
    Program Manager
    Microsoft
    This post is provided "as-is"

  • Aleniko29139

    Did you mispeak or did I have an old aghost.js
    Sorry I did -- setting innerHtml is what occurs.
    #2 - there were some known issues with SourceElement and FireFox regarding using innerHtml actually. I thought they were fixed. Make sure you do not have any carriage returns/line breaks after the <script> tag and before the first element.

    -mark
    Program Manager
    Microsoft
    This post is provided "as-is"
  • AGHost.js Strategy
Answer this question