Your scripts don't care or know which browser is getting the messages. When you're finished re-launch Microsoft. If you want to try something in Netscape, quit Microsoft and launch Netscape. The scripts automatically communicate with correct browser. The suite determines, thru the use of an agent script, which web browser is running. It made sense to merge the interface table for both browsers into a new suite called "webBrowser". Anything that inspires developers to do great stuff is good for Netscape, and standards as always are key. We think it's really great that Microsoft has chosen to emulate our Mac Navigator scripting interface, as it provides a clear path for developers to take. I asked Marc Andreessen, the founder of Netscape, how he felt about this. It's more likely that Netscape and/or Microsoft will respond. If you hit a dead-end in your web browser scripting, make your needs known on the "Frontier-talk" list. This means that bugs will likely be fixed, and new features added. It also makes the scripting interface part of the competition between both browsers. This is good news for script writers, because, at least in theory, all the scripts that have been written to work with Netscape will also work with Microsoft. In this case MSIE implements the Netscape 2.0 AE interface. With the introduction of Microsoft Internet Explorer for the Macintosh we have a new situation in the Mac scripting world: one program emulating the Apple Event interface of another. Netscape Navigator and Microsoft Internet Explorer support compatible Apple Event interfaces.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |