tank wrote:
...as for your mproposed tag functions there is a problem there is also document.forms
document.frames
document.images....
Really that's not much of a problem beyond my chosen naming convention for "links", is it? You can access everything in this format, no?
Code:
COM_Invoke(pwb,"document.all.tags[A].length") ; in lieu of document.links.length
COM_Invoke(pwb,"document.all.tags[form].length")
COM_Invoke(pwb,"document.all.tags[img].length")
COM_Invoke(pwb,"document.all.tags[frame].length")
Code:
iWeb_getTagLen(pdsp,tag,t="-1",r="-1",frm="") {
If pWin:=iWeb_DomWin(pdsp,frm) ; doesn't this cover the frames already?
result:=COM_Invoke(pWin,"document.all.tags[" tag "]"
. ((tag="table" && t>=0) ? ".item[" t "].rows" : "") ((tag="table" && r>=0) ? "[" r "].cells" : "")
. ".length")
COM_Release(pWin)
return result
}
tank wrote:
no lets leave this level of detail to com_invoke users we cant attempt to solve every likelyhood when that level of detail will be need to just use com_invoke
My counter to that would be that we've had many cases in Ask for Help where looping through elements of a particular tag type (that isn't a table) was what someone needed to do to solve a problem (click on an input button with no name/id/value, click on text based on its relative position to text in a span tag, etc.). The functions would not only make it easier for the new user (and save us the trouble of trying to explain too much), it would also make it easier for the more experienced user.
Here are two examples using COM_Invoke and the proposed functions to grab the link text for every topic that has a poll in the Wish List forum:
Code:
; using COM_Invoke
Loop % COM_Invoke(pwb,"document.all.tags[table].item[4].rows.length") {
current:=COM_Invoke(pwb,"document.all.tags[table].item[4].rows[" A_Index-1 "].cells[1].innertext")
if InStr(current,"[ Poll ]")
res.=RegExReplace(current,"^\[ Poll \] ") "`n"
}
; using proposed functions
Loop % iWeb_getTagLen(pwb,"table",4) {
current:=iWeb_getTagObj(pwb,"table",4,A_Index-1,1)
if InStr(current,"[ Poll ]")
res.=RegExReplace(current,"^\[ Poll \] ") "`n"
}
More simple and more clean, just what iWeb is for, no?
tank wrote:
We really cant hope to make an all inclusive function list with iweb we would end up with a function list and property list as large as that in the msdn
instead we target the simple types of scenerios and like the other script writers leave the more complex stuff to the none novice
I think these functions fall under the simple types of scenarios (with a lengthy solution) that iWeb can help with. If we can simplify this in iWeb it makes it less difficult for the new user to grasp and easier for the experienced user to use. But it's your show boss, you be the judge.
FYI - I was using iWeb stuffs to determine the post distribution for the main contributors on this project, not bad at all really:
Post Count wrote:
tank: 57
sinkfaze: 49
jethrow: 30
P.S.S. - Linking to a
bug report with the ahk web recorder.
Login
Register
FAQ
Search
- I would say either put the line back in and leave it the way it was, or possibly allow an optional hwnd param, so you can specify the window if more that one IE window has a tab with the same name.