The WebBrowser control is the heart of Internet Explorer. It can. Using the WebBrowser Control. Chapter 19

Size: px

Start display at page:

Download "The WebBrowser control is the heart of Internet Explorer. It can. Using the WebBrowser Control. Chapter 19"

Collin James
5 years ago
Views:

1 Chapter 19 Using the WebBrowser Control In This Chapter Discover the versatile WebBrowser control, and create your own dialog boxes using plain HTML templates Enumerate and access DHTML elements Link script procedures to DHTML buttons using GetRef, and bypass Internet Explorer security dialogs Control your WebBrowser form window through HTML commands Validate HTML form input, and color-code missing form fields Let your COM object respond to events fired by the WebBrowser control, and disable the context menu this way Use radio buttons and determine which radio button was selected Customize your HTML dialog container, change caption text, and disable sizing The WebBrowser control is the heart of Internet Explorer. It can display HTML documents and is a very versatile design element you can incorporate into your own dialog boxes. In this chapter, learn how to use the WebBrowser control to create fully configurable HTML-based custom dialog boxes and transfer the results back into your scripts. The WebBrowser Control: Mastering Real-World Tasks Microsoft has stuffed all kinds of controls into Windows, and while most s of them are busy working for the operating system, your scripts can access those components, too. One of the most versatile controls is the WebBrowser control. It works inside of any Internet Explorer window, and because Microsoft keeps expanding the role HTML plays, you ll see this control in many Windows 2000 system dialog boxes, too. The WebBrowser control is actually a miniature Web browser. It contains everything necessary to load and display HTML content.

2 540 Part V: Accessing Hidden Components Actually, Internet Explorer is just a wrapping around the WebBrowser control. The Internet Explorer application provides the toolbars and other gadgets helpful to navigate the Web, but the true power comes from the WebBrowser control embedded in Internet Explorer. The WebBrowser control is by no means limited to displaying Web pages. In Chapter 5, I showed you how to use Internet Explorer as a versatile Scripting Host output window. Now it s time to take a close look at the real heart of Internet Explorer. The WebBrowser control is the perfect foundation for truly customizable dialog boxes. It makes much more sense to use the WebBrowser control directly instead of accessing it through Internet Explorer and paying the price for all of the overhead involved. Creating custom dialog boxes There s a definite need for custom dialog boxes. The built-in set of dialog boxes accessible to the Scripting Host is very limited, and it s impractical to create COM objects for any custom dialog box you may need. A much more versatile approach are HTML dialog boxes. You can create them with your favorite HTML editor in a matter of minutes, and it s easy to design these dialog boxes just as you can design a Web page. All you need is a way to display your HTML dialog boxes. Displaying is easy just feed the HTML template to the WebBrowser control. In addition, you ll need some extra tricks to be able to retrieve the results typed into your dialog box. I ve designed a COM object that uses the WebBrowser control and includes many fascinating tricks for interacting with the user. Install the COM object \install\webdialog\setup.exe. Full source code is provided at \components\webdialog\webdialog.vbp. Designing your form: Creating an HTML template The first thing needed is an HTML template. This template defines the elements of your dialog box. Here s a simple example. Type it into your favorite text editor and save it as TEMPLATE.HTM in the same folder you are going to use for the sample scripts: <html> <head> <style> p {font: 12pt Arial} </style> </head> <body bgcolor = #CCCCCC scroll= no > <p>your name: <input type= text name= namefield ></p> <input type= button name= help value= Help > </body> </html>

3 Chapter 19: Using the WebBrowser Control 541 Next, open the template file. Internet Explorer displays the form, and you can check whether everything looks the way you planned. Displaying the template dialog box Now you are ready to display the form template with your new custom dialog COM object (see Figure 19-1). Make sure the following sample script is stored in the same folder you stored your HTML template! 19-1.VBS set tool = CreateObject( Web.dialog ) current path myname = WScript.ScriptFullName cp = left(myname, InstrRev(myname, \ )) template template = cp & template.htm size dialog tool.width = 400 tool.height = 300 tool.title = My Form tool.seticon shell32.dll, 3 tool.resizable = true display dialog and return object reference set webcontrol = tool.showdialog(template) MsgBox TypeName(webcontrol) Figure 19-1: Use an HTML template to design your own dialog box. The script creates a dialog box and displays your HTML template. Once you click OK, the COM object returns a reference to the element collection. You ll need this reference in a minute. First, take a look at your options in Table 19-1.

542 Part V: Accessing Hidden Components Table 19-1 Method/Property Properties and Methods to Control the WebBrowser Dialog Box Property CancelButton As String Function DisplayDialog As Object

4 542 Part V: Accessing Hidden Components Table 19-1 Method/Property Properties and Methods to Control the WebBrowser Dialog Box Property CancelButton As String Function DisplayDialog As Object Property Height As Long Function LoadDialog(ByVal template As String) As Object Property OKButton As String Property Resizable As Boolean Sub SetIcon(ByVal iconlib As String, ByVal index As Long) Sub ShowButtons(ByVal mode As Boolean) Function ShowDialog(ByVal template As String) As Object Property Title As String Property Width As Long Description Caption name of Cancel button. Shows dialog box and returns element collection. Height of dialog box in pixels. Loads dialog template and returns element collection. Caption name of OK button. True: Dialog box is resizable. Sets the dialog box icon. Supply name of icon file and icon index. True: Dialog box displays OK and Cancel buttons. Combines LoadDialog and ShowDialog: Loads a template file, displays the dialog box, and returns element collection. Title of dialog box. Width of dialog box in pixels. Getting access to template elements Displaying your HTML template alone won t be enough. You need a way to access the elements in your HTML template in order to query their values. After all, you want to know what the user has entered into your form (see Figure 19-2). Figure 19-2: Examine the elements accessible in your HTML template.

5 Chapter 19: Using the WebBrowser Control 543 The COM object returns a reference to the element collection. This collection contains references to all the elements you placed onto your HTML page. Let s check out how to read this collection: 19-2.VBS set tool = CreateObject( Web.dialog ) current path myname = WScript.ScriptFullName cp = left(myname, InstrRev(myname, \ )) template template = cp & template.htm size dialog tool.resizable = true tool.width = 400 tool.height = 300 tool.title = My Form tool.seticon shell32.dll, 3 display dialog and return object reference set webcontrol = tool.showdialog(template) read all named elements for each element in webcontrol on error resume next elname = element.name if not err.number=0 then element has no name tag! elname = no name property, type: & TypeName(element) on error goto 0 list = list & elname & vbcr next MsgBox list This time, once you click OK, the script returns a list of all the elements inside your HTML template. There are a lot of unnamed control elements, but you also see all the named elements. Named elements are elements you assigned a NAME= tag. Now it s easy to retrieve the results someone has entered into your form: 19-3.VBS set tool = CreateObject( Web.dialog ) current path myname = WScript.ScriptFullName cp = left(myname, InstrRev(myname, \ ))

544 Part V: Accessing Hidden Components template template = cp & template.htm size dialog tool.resizable = true tool.width = 400 tool.height = 300 tool.title = My Form tool.seticon shell32.

6 544 Part V: Accessing Hidden Components template template = cp & template.htm size dialog tool.resizable = true tool.width = 400 tool.height = 300 tool.title = My Form tool.seticon shell32.dll, 3 display dialog and return object reference set webcontrol = tool.showdialog(template) read input if TypeName(webcontrol)= Nothing then MsgBox You cancelled! else MsgBox You entered: & webcontrol.namefield.value Expand your HTML template to ask for more than one piece of information. It s completely up to you how complex you want your dialog window to get! Figure 19-3: It works your script retrieves the input. Designing dialog box templates The most obvious advantage of HTML dialog boxes is their versatility. You can change the design of your dialog box templates without having to change the COM object in any way, and you don t need any complicated subclassing techniques to dynamically add or remove form elements. There s only one thing you need to ensure, and that s to supply a NAME= tag for each input element you want to query. Without the NAME= property, your script can t access the element s value. Also take a look at the BODY tag. This tag defines the background color and turns off the vertical scroll bar.

7 Chapter 19: Using the WebBrowser Control 545 The STYLE section uses a style sheet to change the font the P element uses. Style sheets are a great way to globally assign formatting information to your form elements. Revealing implementation details Before I show you more tricks you can do with your new HTML dialog box tool, here are some implementation details. If you don t care how the COM object does its work, skip this part! The Resizable property is one of the most remarkable features: This property controls whether or not your form window is resizable. This may not seem to be a big deal, but actually it is. You can t change properties like this one during run-time. The window frame which determines whether the form is resizable or not needs to be defined at design-time. There are ways to overcome this limitation, but they are very complex. The COM object uses a much simpler approach. It actually uses two forms one is resizable, and the other one isn t. The Resizable property sets a global reference to one of the two forms, and all other properties and methods use this reference. This is why you should use the Resizable property before you use any of the other properties and methods. Generally, your dialog box is centered onscreen. Again, there are many complex ways to center a form, but they are completely unnecessary. The form contains a property called StartUpPosition, and this property just needs to be set to CenterScreen. That s all there is to it. The VBScript has some interesting parts, too! It uses ScriptFullName to retrieve its own file path and extracts the pure path information. This way, the script knows the folder name it is stored in. This folder is appended to the template filename, and as a result, you don t need to fiddle around with template file paths. Just make sure the template file is stored in the same folder you stored your script in. Advanced WebBrowser Tricks Let s take a quick look at the architecture of your HTML dialog boxes. Three components are involved. Your script is part one. It launches the COM object, which in turn displays the WebBrowser control. This is part two. Part three is your HTML template, shown inside the WebBrowser control. To get the most out of this architecture, you need ways to communicate between these components. Communication requires handles to the participating objects, and in the preceding examples, you saw how this works. CreateObject returns a handle to the COM object so your script can call its internal methods. ShowDialog in turn again returns a handle. To be exact, it returns an element collection, and this element collection contains the

8 546 Part V: Accessing Hidden Components handles of all the elements inside your HTML template. Both your script and your COM object can access any single HTML element in your template, and the example used this handle to retrieve the value entered into the text field. Calling script procedures through your HTML template Maybe you noticed the Help button on the sample form. It was of no use clicking the button didn t do a thing. Not yet, anyway. Test your new knowledge about inter-component communications and hook up a script procedure to this button (see Figure 19-4). Your script needs to access the button. That s easy, because your script knows the element s reference so it can access all properties. How can your script ask the button to execute a script procedure? Your script needs to get a reference to the script procedure and pass it to the onclick event of the button. Sounds complicated, but it isn t! 19-4.VBS set tool = CreateObject( Web.dialog ) current path myname = WScript.ScriptFullName cp = left(myname, InstrRev(myname, \ )) template template = cp & template.htm size dialog tool.width = 400 tool.height = 300 tool.title = My Form load template first! This way, you get a handle to the HTML elements without displaying the form yet set webcontrol = tool.loaddialog(template) configure the dialog hook up a script procedure to the help button webcontrol.help.onclick = GetRef( showhelp ) now display the dialog. Note that the help button now invokes the showhelp procedure! set webcontrol = tool.displaydialog read input if TypeName(webcontrol)= Nothing then MsgBox You cancelled!

Chapter 19: Using the WebBrowser Control 547 else MsgBox You entered: & webcontrol.namefield.value sub ShowHelp MsgBox Please enter your full name! Now it works!

9 Chapter 19: Using the WebBrowser Control 547 else MsgBox You entered: & webcontrol.namefield.value sub ShowHelp MsgBox Please enter your full name! Now it works! Every time you click the Help button, a help message appears. This help message comes from your script. The help button remotely invokes the ShowHelp procedure defined in your script. You now can call any script procedure while the dialog box is still visible. Imagine the possibilities not only can you supply Help buttons for any input field, you can also update form elements through a database, or you can check the form contents before you allow the user to quit the form. Figure 19-4: The Help button invokes the help procedure of your own script. The magic behind this is GetRef. This method returns a reference to the script procedure, which in turn can be attached to the button onclick event. Communication between the HTML template and the COM object So far, your script has communicated with both the COM object and the HTML template elements. Is there a way your HTML template can communicate with the COM object, too? The COM object hosts your HTML template, and it can be nice to include buttons in your template that control the COM object. For example, you can include a button that closes the dialog box. But how? Your HTML document needs a reference to your COM object. This is why the COM object tries to insert such a reference into your HTML document. hookquit tries to assign the reference to a variable called parentobj. However, this fails because there is no such variable inside your HTML document.

548 Part V: Accessing Hidden Components But, you can change your HTML template. Open it inside a text editor and add a script block. Then save it as TEMPLATE2.

10 548 Part V: Accessing Hidden Components But, you can change your HTML template. Open it inside a text editor and add a script block. Then save it as TEMPLATE2.HTM: (see Figure 19-5) <html> <head> <style> p {font: 12pt Arial} </style> </head> <body bgcolor = #CCCCCC scroll= no > <script language= VBScript > set parentobj = Nothing sub Quit if not TypeName(parentobj)= Nothing then parentobj.quit false sub Leave if not TypeName(parentobj)= Nothing then parentobj.quit true </script> <p>your name: <input type= text name= namefield ></p> <input type= button name= help value= Help > <input type= button name= quit value= Quit! onclick= Quit() > <input type= button name= leave value= Done! onclick= Leave() > </body> </html> Now try your script again: Exchange TEMPLATE.HTM inside the script with TEMPLATE2.HTM, or use script VBS. The form has changed, and there are two more buttons Quit and Done. Quit does exactly what your Form window Cancel button does, and Done mimics the OK button. Figure 19-5: You new template features a Quit button that closes the form.

11 Chapter 19: Using the WebBrowser Control 549 Take a look at the new script block. It defines an object reference called parentobj and sets it to Nothing. Then, it defines two procedures Quit and Leave. These call the Quit method defined in the parentobj object. But what is the parentobj object anyway? To make things work, your COM object inserts a reference to its own Form object into the HTML document parentobj variable. This happens inside hookquit. Parentobj now points to the form object of your COM object, and inside the form, there s now a Quit procedure. Your HTML document now can remotely access your form object s internal procedures (see Figure 19-6). You can expand this concept easily. Your HTML document now can access any internal method your COM object provides. Because now that your HTML document can handle the OK and Cancel operations remotely, your dialog box no longer needs to provide its own buttons. Remove them VBS set tool = CreateObject( Web.dialog ) current path myname = WScript.ScriptFullName cp = left(myname, InstrRev(myname, \ )) template template = cp & template2.htm size dialog tool.width = 400 tool.height = 300 tool.title = My Form remove buttons tool.showbuttons false load template first! This way, you get a handle to the HTML elements without displaying the form yet set webcontrol = tool.loaddialog(template) configure the dialog hook up a script procedure to the help button webcontrol.help.onclick = GetRef( showhelp ) now display the dialog. Note that the help button now invokes the showhelp procedure! set webcontrol = tool.displaydialog read input if TypeName(webcontrol)= Nothing then

550 Part V: Accessing Hidden Components MsgBox You cancelled! else MsgBox You entered: & webcontrol.namefield.value sub ShowHelp MsgBox Please enter your full name!

12 550 Part V: Accessing Hidden Components MsgBox You cancelled! else MsgBox You entered: & webcontrol.namefield.value sub ShowHelp MsgBox Please enter your full name! Figure 19-6: Get rid of the standard buttons and use your own template to control the form. Now, you are absolutely free in your design. Your input elements can access the COM object methods and hook them to their own events. Your own OK and Cancel buttons can use DHTML script to check the input before allowing the form to close. Automatically closing the form on RETURN For example, the next HTML template accesses the document s onkeypress event. It checks for the character codes 13 (RETURN) and 27 (ESC) and calls the COM object methods to either send the input or cancel the dialog box. As a result, the keys [Esc] and [Enter] now are connected to the Cancel and OK buttons. Once you finish your input with [Enter], the form is automatically closed, and you don t need to grab the mouse and click OK. Save this template as TEMPLATE3.HTM and change your scripts accordingly. You can also use script VBS on the CD. <html> <head> <style> p {font: 12pt Arial} </style> </head> <body bgcolor = #CCCCCC scroll= no >

13 Chapter 19: Using the WebBrowser Control 551 <script language= VBScript > set parentobj = Nothing done = false sub Quit if not TypeName(parentobj)= Nothing then parentobj.quit false sub Leave if not TypeName(parentobj)= Nothing then parentobj.quit true sub document_onkeypress() this procedure is executed anytime a key is pressed retrieve key code of key pressed keycode = window.event.keycode is it RETURN? Leave! if keycode = 13 then Leave is it ESC? Quit! elseif keycode = 27 then Quit </script> <p>your name->: <input type= text name= namefield ></p> <input type= button name= help value= Help > <input type= button name= quit value= Quit! onclick= Quit() > <input type= button name= leave value= Done! onclick= Leave() > </body> </html> Hooking COM procedures to individual elements The previous template responds to [Esc] and [Return] no matter which element is currently selected. Maybe you don t like this idea. You can also hook the keyboard checker to specific input elements. Save this template as TEMPLATE4.HTM and change your scripts accordingly, or use script VBS. <html> <head> <style> p {font: 12pt Arial} </style>

14 552 Part V: Accessing Hidden Components <script language = VBScript > sub focusit document.all.namefield.focus() </script> </head> <body bgcolor = #CCCCCC scroll= no onload= call window.settimeout( focusit(), 100) > <p>your name->: <input type= text name= namefield onkeypress= checkkeyboard() ></p> <input type= button name= help value= Help > <input type= button name= quit value= Quit! onclick= Quit() > <input type= button name= leave value= Done! onclick= Leave() > <script language= VBScript > set parentobj = Nothing sub Quit if not TypeName(parentobj)= Nothing then parentobj.quit false sub Leave if not TypeName(parentobj)= Nothing then parentobj.quit true sub checkkeyboard() keycode = window.event.keycode if keycode = 13 then Leave elseif keycode = 27 then Quit </script> </body> </html> This time, the [Esc] and [Enter] keys are recognized only inside your text box element. The script inside the template has placed the keyboard check into a regular procedure called checkkeyboard. This procedure is then hooked to the keypress event of the text box. The script demonstrates another nice advantage your text box element receives the focus automatically, and you no longer have to click the element before entering text. Now, your dialog box is ready, and you can type in text immediately. And [Enter] sends the input to your script. Your HTML dialog box is just as convenient to use as the built-in InputBox method.

15 Chapter 19: Using the WebBrowser Control 553 Assigning the input focus to an element in regular Web pages is easy. Just call the focus method of the element that you want to receive the focus. However, this won t work in the preceding example. The focus() method can switch focus to the element only once it is visible onscreen. This is why the script calls the focus method in the BODY tag onload property. This still isn t enough. Even though the document is loaded when onload is executed, it takes some extra time for the elements to be fully programmable. This is why the script doesn t call the focusit procedure directly. Instead, it uses the timer built into the window object and calls it with a 100-millisecond delay. Note also that the focusit procedure needs to be defined in the HEAD section. It needs to be defined before the WebBrowser control parses the BODY tag. If you want another element to receive the focus, just change the element name in the focusit procedure. Checking for valid form entries Using your own OK and Cancel buttons instead of the buttons the COM object provides has many advantages. For example, you can double-check the user input before you allow the form window to close. Save this template as TEMPLATE5.HTM and change your scripts accordingly, or use script VBS (see Figure 19-7). <html> <head> <style> p {font: 12pt Arial} </style> <script language = VBScript > sub focusit document.all.namefield.focus() </script> </head> <body bgcolor = #CCCCCC scroll= no onload= call window.settimeout( focusit(), 1000) > <p>your name->: <input type= text name= namefield onkeypress= checkkeyboard() ></p> <input type= button name= help value= Help > <input type= button name= quit value= Quit! onclick= Quit() > <input type= button name= leave value= Done! onclick= Leave() > <input type= button name= focus value= Focus! onclick= focusit() > <script language= VBScript > set parentobj = Nothing sub Quit

554 Part V: Accessing Hidden Components if not TypeName(parentobj)= Nothing then parentobj.quit false sub Leave if document.all.namefield.value= then document.all.namefield.style.

16 554 Part V: Accessing Hidden Components if not TypeName(parentobj)= Nothing then parentobj.quit false sub Leave if document.all.namefield.value= then document.all.namefield.style.background = #FF0000 MsgBox You did not fill out the form! document.all.namefield.style.background = #FFFFFF document.all.namefield.focus elseif not TypeName(parentobj)= Nothing then parentobj.quit true sub checkkeyboard() keycode = window.event.keycode if keycode = 13 then Leave elseif keycode = 27 then Quit </script> </body> </html> The Leave procedure now checks whether the user has entered text at all. If the text field is empty, the script flashes the text box background color and displays a message. As long as the text box is empty, the Cancel button is the only way to close the form window. Figure 19-7: Automatically focus and check the input. Use this as a foundation for your own checks. You can check more than one field. You can check the content and make sure the user has entered the type of data you expect. You can even disable the OK button for as long as the user input contains errors.

17 Chapter 19: Using the WebBrowser Control 555 Responding to WebBrowser control events So far, your COM object displays any HTML file you provide. But how can you access the events raised by the WebBrowser control? Use the WithEvents statement. The COM object defines a variable called htmldoc of type HTMLDocument as WithEvents. The deeper meaning behind this is that the variable htmldoc now can host a reference to an HTML document and can also handle any events the HTML page may raise. Then, the LoadDialog procedure assigns the handle to the WebBrowser control document to this variable. From now on, your COM object can respond to events raised by the HTML document. And it does. The function htmldoc_oncontextmenu is called anytime a user tries to open a context menu. Because you don t want an Internet Explorerstyle context menu to appear on your dialog box, the function always returns false, effectively disabling context menus. The oncontextmenu event is supported only on IE5. Reading Groups of Radio Buttons HTML forms can consist of more than just text boxes. Radio buttons work like the radio buttons on your old car stereo only one selection in a group can be chosen at any time. Radio buttons are perfect for offering mutually exclusive options. However, how do you create Radio button groups, and even more important, how can your script read the selected option? Creating a group of radio buttons Radio buttons are plain INPUT elements of type radio. Their name property groups them together (see Figure 19-8). Radio buttons work mutually exclusively only when you group them together. Grouping takes place by assigning the same name to all radio button elements in this group. Here s an example file. Save it as TEMPLATE6.HTM. <html> <head> <style> p {font: 12pt Arial}.mystyle {font: 10pt Arial; font-weight: bold} </style> </head> <body bgcolor = #CCCCCC scroll= no >

18 556 Part V: Accessing Hidden Components <fieldset><legend class= mystyle >Choose an Option!</legend> <p><input type= radio value= Option 1 checked name= R1 >Option 1<br> <input type= radio name= R1 value= Option 2 >Option 2<br> <input type= radio name= R1 value= Option 3 >Option 3<br></p> </fieldset> </body> </html> Figure 19-8: Use fixed-sized dialog boxes and display any kind of form element you like. To display this template, use the following script: 19-6.VBS set tool = CreateObject( Web.dialog ) current path myname = WScript.ScriptFullName cp = left(myname, InstrRev(myname, \ )) template template = cp & template6.htm size dialog tool.resizable =false tool.width = 400 tool.height = 200 tool.title = Option Dialog set webcontrol = tool.showdialog(template) read input MsgBox Done! The dialog box form displays nicely, but your script can t read the selected option. If you try to access the webcontrol.r1.value option, you get an error (see Figure 19-9).

Chapter 19: Using the WebBrowser Control 557 Whenever you group an input field by naming all elements the same, it s treated as an array. You can t access individual elements of a group directly.

19 Chapter 19: Using the WebBrowser Control 557 Whenever you group an input field by naming all elements the same, it s treated as an array. You can t access individual elements of a group directly. Instead, you need to determine the size of the array (the number of elements in the group) and pick the one you are interested in. Because there are three elements called r1, you need to treat r1 as an object array. Actually, in your template, there is no element called r1, but there are three elements called r1(0), r1(1), and r1(2). This is how you can read any group of input elements and determine the value of the checked one: read input if TypeName(webcontrol)= Nothing then MsgBox You cancelled! else for x=0 to (webcontrol.r1.length)-1 if webcontrol.r1(x).checked then optionval = webcontrol.r1(x).value next MsgBox You chose: & optionval Figure 19-9: Now you can read in the results from the options dialog box group. Append this code to your script, and you are all set. Here s the complete script: 19-7.VBS set tool = CreateObject( Web.dialog ) current path myname = WScript.ScriptFullName cp = left(myname, InstrRev(myname, \ )) template template = cp & template6.htm size dialog tool.resizable =false tool.width = 400

20 558 Part V: Accessing Hidden Components tool.height = 200 tool.title = Option Dialog set webcontrol = tool.showdialog(template) read input if TypeName(webcontrol)= Nothing then MsgBox You cancelled! else for x=0 to (webcontrol.r1.length)-1 if webcontrol.r1(x).checked then optionval = webcontrol.r1(x).value next MsgBox You chose: & optionval Because the Web is based mainly on JavaScript, the HTML object model returns the number of elements in the group using the length property instead of the VBScript Count property. Still, your VBScript can use this property even though it doesn t follow VBScript naming conventions. A loop checks all elements in the group and returns the value of the element marked as checked. You need to deal with element arrays only when you read form content from within a Web page using script statements. If you submit a form to some Web server, you don t need to care much. Submitting a form sends only the checked elements, so there won t be more than one r1 element, and you can access its value directly. Summary The WebBrowser control is a real gem. This chapter has shown you some of what it can do for you. The COM object I developed serves as a general-purpose dialog box container, and you have seen many examples on how to create your own dialog boxes using plain HTML templates. This is a great foundation for teamwork. You can let a graphic designer create the dialog box design while you provide the COM object to host it. Through advanced event handling, your COM container can be controlled entirely by your HTML template. You can even close the form window from inside your HTML script code.

How to use the Assets panel

Adobe Dreamweaver Guide How to use the Assets panel You can use the Assets panel in Dreamweaver to manage assets in the current site (Figure 1). The Assets panel displays assets for the site associated