AutoHotkey Community

[tank]

k I have several pending updates to iWeb and the tool plus yours to merge and i intend to try to merge the idea Sinkfaze is exploreing into the gui somehow
I will wait and see how far he gets before doing that look for some code updates saturday

i intend on changeing the layout but all of the gui element names will remain the same
_________________
Basic Webpage Controls with JavaScript / COM - Tutorial by Jethrow

[sinkfaze]

[tank]

tryupdating the iweb library i tinkered with it over the last day or so
_________________
Basic Webpage Controls with JavaScript / COM - Tutorial by Jethrow

[sinkfaze]

[tank]

[tank]

The iWebBrowser2 Learner has been updated and now adds some finer detail and a very basic script writing tool which we will be building upon
I could not download Sinkfaze latest script version so i had to hope i did as well as he was doing.

As well the iWeb library has been updated and is in need of testing here is the current api list. The functions in red are the source of the most changes

iWeb_getwin supports a blank title which will capture the active window
iWeb_Checked should only be used on check boxes and radio buttons and will return the checked status of either checked=true
iWeb_SelectOption relies on a numeric value for selected
iWeb_TableParse allows you to enter table information table row and cell each allows name id and 0 based index. If the cell reference is invalid Error level is set allowing things like the following to be done without knowing for sure which cells are valid

[sinkfaze]

[jethrow]

I like the new GUI - especially the addition of tabs. A couple things, however, that I personally liked about the old GUI were the Element Tag Name listing, and the frames being on multiple lines. Also, if the broswer information is going to be shown (specifically position and size), I think it should be updated regardless of if the curser is over the web page document or not (perhaps even if the program is paused). Overall though, it looks sharp.

I made a few changes to the Element Outline GUI support:

• Outline GUIs will be removed if window HWND stays the same, but the window either moves, changes size, or changes WinTitle
• The Outline GUI's window Z-order will be set to directly below the window that is directly above the window accessed by the IE_HtmlElement() function (rather than set to an Always-On-Top status)

I updated my link - however, the scripts in the iWebBrowser2 Learner download didn't reflect the current build. So I extracted the script from the .exe file. This caused all the previous comments to be deleted.

Also, and this is purely IMO, this program should be a tool to gather information about webpages, with the additional awsome functionality of recording & creating scripts. What I'm getting at is I think we should make the GUI narrower (like AHK Window Info 1.7 or Window Spy), and have the Script Writer be a separate pop-up ToolWindow. What are other people's thoughts\opinions? (I could come up with a sample GUI, but I would like opinions before I spend that time)
_________________
AHKL, COM_L,Webpage Controls,Donate to AHK

[sinkfaze]

[tank]

[jethrow]

I updated my script/link such that the outline will move if the IE window is moved (rather than removing the outline).

[sinkfaze]

Hmmm...I'm not sure I'd be in favor of that change for a couple of reasons:

1. Using jballi's creation puts an additional burden on us to understand how his program works and support it in the event that some future update of AHK causes a conflict. jballi is an AHK wizard but he visits the forums sporadically and he may not necessarily update QuickAHK (or notify the forum that he has updated it) when he does visit. Granted, he usually does update his scripts and notifies the forum as such but we cannot rely on his assistance for our modifications of his creation.
   
   Adding this makes him an (unwitting?) party in the project which could put us all in difficult spots when people ask us questions about his QuickAHK and people potentially ask him questions about our Learner.
   
   
2. I think a tool like QuickAHK is a little beyond the grasp of the audience we're targeting. And there's no offense intended to jballi at all, but I think a user similar to his skill level is not the type of user we would (or should) expect to be using the Learner. We're trying to de-mystify web automation to a group of people for whom automation in general is probably a bit mystifying, and providing a script tester/recorder that overwhelms them kind of defeats the purpose.

My personal opinion is that we're better off trying to find ways to create our own recorder that emphasizes simple execution over robust features.

[tank]

I agree its a bit large but cant you see how all we need to do is actually send the text of the script to it and have a very useable ahk script writing environment that we dont have to support really. Does fincs support everything he includes in Scite ?? i dont think he does but i could be wrong.
i like the syntax highlighting but I am not bent on this If i add such it wouldnt be till near the end of this deveopment so if we find something with some simple syntax highlighting im open to it
_________________
Basic Webpage Controls with JavaScript / COM - Tutorial by Jethrow

[sinkfaze]

What is the purpose of iWeb_FireEvents? Ever since I updated to your latest version of the iWeb functions I get a ton of "onfocus", "onblur", "onclick" and/or "onchange" errors in scripts that were previously error-free. I'm assuming the addition of iWeb_FireEvents to the other functions is the cause of this?

I tried uncommenting COM_Error(0) in iWeb_FireEvents to no avail. I also tried commening out the added sections referring to iWeb_FireEvents inside the functions with no luck. The only thing that seems to work is to add COM_Error(0) before calling each function and adding that to my scripts a hundred times strikes me as an ugly way to upgrade.
_________________
Try Quick Search for Autohotkey or see the tutorial for newbies.

[tank]

yea i forgot and left COM_Error(0) commented out
essenually some forms rely on events to perform actions enabling othe elements performing validation etc
I'll post an update to the code to prevent errors this evening sometime sorry for the confusion
_________________
Basic Webpage Controls with JavaScript / COM - Tutorial by Jethrow