AutoHotkey Community

2Sean

Lets try again with DOM.

You said you don't see a point in accessing DOM. The point is that user will be able to create rich looking applications, by constructing them in any Web IDE around, skin them using CSS etc.. You can do so now, but you can't access what the user does with controls on the form. For instance, if there is a button, I should be notiified when button is clicked so I can rise appropriate AHK action. Thus, web design and standard application design can be mixed and the best of both worlds can be taken. Many apps out there use this mechanism. For instance, Ashampoo Uninstaler has complete start up interface in IE but you can not see that unless you use some spy technique.

As you are already most familiar with COM and this topic, I belive you can at least initialise DOM - provide several basic functions so ppl interested can extend your work.

If you provide such features, ppl would literally be able to create apps that can look like the one bellow

_________________

Yes! We want DOM access!

No, really, that would be the ultimate...

_________________
mirror 1 • mirror 2 • mirror 3 • ahk4.me • PM or

While updating IEControl.ahk, I added a function IE_Document(pwb) which is the gateway from WebControl to DOM.
And, the function GetWebControl() can directly access DOM already.

The problem is that DOM provides literally thousands of functions, so, have to decide which ones to include or not.
So, if people show me what they need mostly in any form, e.g. oIE.document.documentElement.outerHTML in VBS syntax, then I could start implementing DOM.

Thx Sean for reconsidering.

I think this is enough for the start

• Ability to access any element by ID (GetElementByID), eventualy list of all elements of the same class (in JS framewors usualy noted as $$, for instance $$("a") will create array of all anchors)
  
• Set/Get InnerHtml property ( <tag> InnerHtml </tag> ) (DOM_SetInnerHtml( domID, ctlID, HTML ) )
• Set/Get Attribute of DOM element ( <tag attrrib="value">... </tag> ) (DOM_SetAttrib( domID, ctlID, "attribname", "attribval" ) )
  
• Click/Change notificiations on DOM elements (for instance in form DOM_ElementClick( domID, ctlID, subroutine)

_________________

Can someone point me to or cut-and-paste a running example of the latest integration of Browser..... bare bones without any special features, just load Google and also call raw HTML. Thank you for any help and direction!!

Here is one example. Need the latest IEControl.ahk & CoHelper.ahk.

Thanks for the example Sean. It runs great here but Windows asks if I'd like to send a report to Microsoft when I close the window (XP Pro SP2). Commenting out AtlAxWinTerm() and CoUninitialize() seems to prevent the message...

Thanks. BTW, that's strange... It doesn't output an error message here with IE7 in XPSP2 Pro.
The sole purpose of these two are just cleaning up, and not absolutely necessary in this case as they will be cleaned up anyway with the exit of AHK.
So, you may just comment out them and there will be no problem at all, I believe.

PS. I changed the order of the initialize/uninitialize of ATL & COM for a purely experimental purpose.
Does it still produce an error?

It seemed a bit strange to me too. I'm not sure if it something machine specific (IE6 here). I'll try on another machine soon.

I still get the message. I also tried commenting out only one or the other...

Thanks for testing it.
I can't explain this, btw.

Hmm... If I destroy the Gui Window first then I don't get the error.

Thanks for the info. So, adding the following will prevent the error message?



OTOH, I'm a bit surprised with this.
Isn't GuiClose: supposed to be executed after the Gui window is destroyed?

GuiClose: seems to be executed before the window is destroyed (at least the window is still visible).

OK, I added DestroyWindow, being commented initially. Thanks for figuring it out.