Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. COM
  4. Scriptable ActiveX and javascript

Scriptable ActiveX and javascript

Scheduled Pinned Locked Moved COM
c++comquestionjavascriptadobe
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    gialli
    wrote on last edited by
    #1

    Thanks to nice articles on the site I was able to get my COM project going nicely. I decided to do this without ATL/MFC as my needs are quite basic and I really want to understand what I'm doing. I'm not saying ATL/MFC are bad, I've worked with MFC for years so this really isn't about what's good and what's bad, I just chose this approach and try to live with my decision. Enough of introduction, here's the problem. Being new to COM, I'm having some problems in adding support for every interface required by Internet Explorer to use it. IDispatch and invoke seem to work nicely, but do I need something more? Do I need to mark the component safe for scripting if I sign the code? Also, I need some interoperability with another ActiveX component, namely Macromedia Flash. I'd be happy to handle this via javascript functions, but how do I retrieve the scripting host and is there a solution which would work on other browsers than IE?

    A 1 Reply Last reply
    0
    • G gialli

      Thanks to nice articles on the site I was able to get my COM project going nicely. I decided to do this without ATL/MFC as my needs are quite basic and I really want to understand what I'm doing. I'm not saying ATL/MFC are bad, I've worked with MFC for years so this really isn't about what's good and what's bad, I just chose this approach and try to live with my decision. Enough of introduction, here's the problem. Being new to COM, I'm having some problems in adding support for every interface required by Internet Explorer to use it. IDispatch and invoke seem to work nicely, but do I need something more? Do I need to mark the component safe for scripting if I sign the code? Also, I need some interoperability with another ActiveX component, namely Macromedia Flash. I'd be happy to handle this via javascript functions, but how do I retrieve the scripting host and is there a solution which would work on other browsers than IE?

      A Offline
      A Offline
      Anonymous
      wrote on last edited by
      #2

      If all you need is to invoke few methods in your component, then there is no need to implement other interfaces, IDispatch is enough (although ISupportErroInfo could be useful for error reporting) Whether to mark it "safe for scripting" or not is up to you. If you won't, the IE behavour will depend on IE security setting "SCript ActiveX controls marked safe for scripting" : "disable", "prompt", "enable" Edward

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups