Sign in to follow this  
Followers 0
Valuater

IE.au3 Library / Builder

124 posts in this topic

#1 ·  Posted (edited)

Updated to ver 2.0.1

Fixed: formatting of submitted code

Fixed: clicking twice on same view made it disappear

Fixed: a few layout issues

Fixed: naming of variables

Updated: all functions

Added: function syntax population

To-Do: Update examples

Requirements:

IE.au3 version T2.0-3 or later, and latest beta of course

IE-Builder v2.0

previous dowloads 900 +/-

Credits to Dale Hohm for the Internet Explorer UDF Library

**** This is The Public Release of IE-Builder, a helpful tool in creating IE objects

The new look!!!

Posted Image

Builder, Internet, Source, Syntax, and Examples ...

All at your finger-tips

Enjoy!!!

Valuater

8)

UpDated 6-15-2006 ver 2.0.0

by big_daddy

*************

UpDated 2-18-2006 ver 1.0.3

added - Check all locations for Beta

*************

UpDated 1-12-2006. ver 1.0.2

added - list All Html Elements

added - list Image view

added - list Anchor Tags view

added - list Form Elements view

added - Objects Error handling ( ie... when user presses forward, and there was no previous page )

and more

*************

UpDated 1-7-2006 Alpha Release

added - minimize button

added - ini file and favorites button

added - search stop/continue through source

added - error checking

and more

Edited by Valuater

NEWHeader1.png

Share this post


Link to post
Share on other sites



This looks like it might be a really nice utility, but I'm unable to get it to run!

I'm using AutoIt version 3.1.1.97 Beta, and have downloaded IE.au3 from the forum posting Internet Explorer Automation UDF library

When running it under the Beta, I get the message:

C:\Program Files\AutoIt3\beta\Include\IE.au3 (275) : ==> The requested action with this object has failed.:

If (ObjName($o_window.document) = "DispHTMLDocument") Then

If (^ ERROR

The call "_IEAttach ($oIE)" on line 73 is failing within the _IEAttach() function in IE.au3.

Any thoughts?

Share this post


Link to post
Share on other sites

#3 ·  Posted (edited)

yes..

as i found out recently... i always downloaded "include files" into

C:\Program Files\Autoit\include\...

but there is a second include folder for the beta ( thx LxP )

copy IE.au3 to

C:\Program Files\Autoit\beta\include\..

that is where the program is looking

8)

Edited by Valuater

NEWHeader1.png

Share this post


Link to post
Share on other sites

yes..

as i found out recently... i always downloaded "include files" into

C:\Program Files\Autoit\include\...

but there is a second include folder for the beta ( thx LxP )

copy IE.au3 to

C:\Program Files\Autoit\beta\include\..

that is where the program is looking

8)

Valuater,

No, that is not the problem. The script gives a clear error message if IE.AU3 is not under beta\include, and I dutifully put a copy there too (as well as under the production Include directory). The script will does not run in either interpreted or compiled mode.

Maybe if you post the IE.AU3 you used - or a compiled version of the script.

Share this post


Link to post
Share on other sites

Valuater,

No, that is not the problem. The script gives a clear error message if IE.AU3 is not under beta\include, and I dutifully put a copy there too (as well as under the production Include directory). The script will does not run in either interpreted or compiled mode.

Maybe if you post the IE.AU3 you used - or a compiled version of the script.

i found the "_IEattach()" on line 73 of MY script... this was not utilized

so try to comment-out this section

; start at line 73
;_IEAttach ($oIE)
;If Not IsObj($oIE) Then
;   MsgBox(0, "IE test", "Failed")
;   $oIE = _IECreate ()
;   _IENavigate ($oIE, $sUrl)
;EndIf

i originally created this object with autoit-objects... not the library and tried to attach the library there after

let me know if that worked

8)


NEWHeader1.png

Share this post


Link to post
Share on other sites

i found the "_IEattach()" on line 73 of MY script... this was not utilized

so try to comment-out this section

; start at line 73
;_IEAttach ($oIE)
;If Not IsObj($oIE) Then
;   MsgBox(0, "IE test", "Failed")
;   $oIE = _IECreate ()
;   _IENavigate ($oIE, $sUrl)
;EndIf

i originally created this object with autoit-objects... not the library and tried to attach the library there after

let me know if that worked

8)

Yep. It's running now. Thanks.

Share this post


Link to post
Share on other sites

If I install AutoIt with this command:

Autoit_v3.1.1.exe /S /D=C:\AutoIt

Then install Scite4AutoIt3 like this

SciTe4AutoIt3_17.12.05.exe /S

Then the Beta goes into the AutoIt folder then your hardcoded code below will not work. This is not to mention that people may have program files on another drive where atleast the @ProgramFilesDir macro may have helped the success more.

If Not FileExists("C:\Program Files\AutoIt3\beta\Autoit3.exe") Then 
    MsgBox(64, "IE.au3 Error #1", "Autoit3 Beta is required   " & @CRLF & "Please download form www.Autoit3.com   ")
    Exit
EndIf
If Not FileExists("C:\Program Files\AutoIt3\beta\Include\IE.au3") Then 
    MsgBox(64, "IE.au3 Error #2", "IE.au3 Library is required   " & @CRLF & "Please download form www.Autoit3.com   ")
    Exit
EndIf

Look to the registry for AutoIt installation directory could be a better idea ?

I have not played with it yet to give applause but the picture tells the story. Looks like a cool program. :P

Share this post


Link to post
Share on other sites

thx MHz

updated 1-7-2006

added @ProgramFilesDir... as the file name is the same in beta and release version... and figured its for users here that should understand the difference

8)


NEWHeader1.png

Share this post


Link to post
Share on other sites

wouldnt it be better an script that enumerate all objetcs form etc in a txt file, so that we can use the ie functions ¿¿¿¿¿

objetcts:

1

2

3

4

forms:

1

2

3

4

5

tables:

1

2

3

explain to use into ie funcs

BUILDER IS USABLE AND QUICKER THAN SCITE IF YOU USE THIS enumetation

THANKS


Autoit.es - Foro Autoit en Español Word visitors Image Clustrmap image: - Football Spanish team - Spanish team: Casillas, Iniesta, Villa, Xavi, Puyol, Campdevilla, etc..Programando en Autoit+Html - Coding Autoit-Html - Arranca programas desde Internet - Preprocesador de Autoit a http

Share this post


Link to post
Share on other sites

the idea behind the builder is

1

to simplify using all of the original IE UDF Library features and help at your finger-tips.

you can quickly switch between....

A view the page you want to work on

B View the source of that page

C Search the source of that page

D Find references in the Syntax

E Find examples to follow

F Catagorized Functions ( per Dales catagories )

G Build your script

2

to follow the original design and help as explained by Dale Hohm

3

the Builder Form is designed so you can add/remove/edit all lines of text and also you can type in AU3 commands. for example... Sleep(200)

4

You can Test the script with the *Test Run Form* button. This calls the *beta exe* to run your script

5

the button *Copy to ClipBoard* allows you to paste your script wherever you want... a text file or the SciTE Program or ????

Thanks for the response

8)


NEWHeader1.png

Share this post


Link to post
Share on other sites

#11 ·  Posted (edited)

You know Valuater, BasicOs makes an interesting suggestion... I think adding information from the document element discovery examples would make this really useful... take look and see what you think.

Dale

Edited by DaleHohm

Free Internet Tools: DebugBar, AutoIt IE Builder, HTTP UDF, MODIV2, IE Developer Toolbar, IEDocMon, Fiddler, HTML Validator, WGet, curl

MSDN docs: InternetExplorer Object, Document Object, Overviews and Tutorials, DHTML Objects, DHTML Events, WinHttpRequest, XmlHttpRequest, Cross-Frame Scripting, Office object model

Automate input type=file (Related)

Alternative to _IECreateEmbedded? better: _IECreatePseudoEmbedded  Better Better?

IE.au3 issues with Vista - Workarounds

SciTe Debug mode - it's magic: #AutoIt3Wrapper_run_debug_mode=Y Doesn't work needs to be ripped out of the troubleshooting lexicon. It means that what you tried did not produce the results you expected. It begs the questions 1) what did you try?, 2) what did you expect? and 3) what happened instead?

Reproducer: a small (the smallest?) piece of stand-alone code that demonstrates your trouble

Share this post


Link to post
Share on other sites

#12 ·  Posted (edited)

You know Valuater, BasicOs makes an interesting suggestion... I think adding information from the document element discovery examples would make this really useful... take look and see what you think.

Dale

I took a quick look... and i will see if i can incorporate them into the builder for the next update

thx

8)

Edited by Valuater

NEWHeader1.png

Share this post


Link to post
Share on other sites

added @ProgramFilesDir... as the file name is the same in beta and release version... and figured its for users here that should understand the difference

Thanks Valuater, I appreciate the effort that you do to share your nice program for us all.

Share this post


Link to post
Share on other sites

Thanks Valuater, I appreciate the effort that you do to share your nice program for us all.

I consider that a compliment.... with your Scripting Knowledge and Abilities...

and your "Just simple" approach to this Forum

8)

PS

New release forth-comming


NEWHeader1.png

Share this post


Link to post
Share on other sites

#15 ·  Posted (edited)

as BasicO's requested... and Dale Hohm suggested

Updated 1-12-2006 ver 1.0.2

thx

8)

Edited by Valuater

NEWHeader1.png

Share this post


Link to post
Share on other sites

MHz mentioned above to use the @ProgramFilesDir macro to find the installation of AutoIt beta and IE.au3. The only problem with this idea is that @ProgramFilesDir still only looks at 1 drive. On my computer, I have C: and D: drives, and my AutoIt installation is on my D: drive. Therefore, @ProgramFilesDir doesn't find the installation and returns errors.

My suggestion is to also search the registry for the AutoIt installation, or use DriveGetDrive ("fixed") to get every drive on the computer, and check each one of those in the program files dir.

Share this post


Link to post
Share on other sites

#17 ·  Posted (edited)

maybe something more along the lines, if not found where expected in the registry, then let the user select it, for example:

#include <GuiConstants.au3>

Dim $radio[10], $Input[10], $Combo[10]
Dim $count = 1, $prg = 0
Dim $wloc = @ScriptDir & "\web.ini"
Dim $AutoItBetaLocation
$ver = "1.0.2"

; Set a COM Error handler -- only one can be active at a time (see helpfile)
$oMyError = ObjEvent("AutoIt.Error", "MyErrFunc")
$AutoItBetaLocation = RegRead("HKEY_LOCAL_MACHINE\SOFTWARE\AutoIt v3\AutoIt","betaInstallDir")
If $AutoItBetaLocation = "" Then
    $AutoItBetaLocation = FileSelectFolder("Select Folder where the Beta AutoIt is installed","c:\",4,@ProgramFilesDir & "\AutoIt3\beta")
    If $AutoItBetaLocation = "" Then
        MsgBox(262208, "IE.au3 Error #1", "Autoit3 Beta is required   " & @CRLF & "Please download from www.Autoit3.com   ")
    ;Exit
    EndIf
EndIf
If Not FileExists($AutoItBetaLocation & "\Include\IE.au3") Then
    MsgBox(262208, "IE.au3 Error #2", "IE.au3 Library is required   " & @CRLF & "Please download from www.Autoit3.com   ")
;Exit
EndIf

#include <IE.au3>
Edited by gafrost

SciTE for AutoItDirections for Submitting Standard UDFs

 

Don't argue with an idiot; people watching may not be able to tell the difference.

 

Share this post


Link to post
Share on other sites

then how to handle the next line

$Program_2 = @TempDir & "\Temp.exe"

FileInstall("C:\Program Files\AutoIt3\beta\Autoit3.exe", $Program_2)

FileInstall requires a true path, not a variable

??

8)


NEWHeader1.png

Share this post


Link to post
Share on other sites

don't think you would need to do a fileinstall just

$Program_2 = $AutoItBetaLocation & "\Autoit3.exe"
;~ $Program_2 = @TempDir & "\Temp.exe"
;~ FileInstall(@ProgramFilesDir & "\AutoIt3\beta\Autoit3.exe", $Program_2)

SciTE for AutoItDirections for Submitting Standard UDFs

 

Don't argue with an idiot; people watching may not be able to tell the difference.

 

Share this post


Link to post
Share on other sites

You could even use the current script you're running (assuming it's compiled) as the AutoIt exe.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0