SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Microcap & Penny Stocks : Zulu-tek, Inc. (ZULU) -- Ignore unavailable to you. Want to Upgrade?


To: wlcnyc who wrote (14924)10/19/1998 6:36:00 PM
From: Joe Copia  Read Replies (1) | Respond to of 18444
 
I use both Explorer 4 and Netscape 4+ "behind" AOL. I find the AOL version of IE when used within in AOL, a real pain in the ass! Among other little "annoyances" it seems to be somewhat slower.

Netscape behind AOL is the only way to go, imo. IE4 I have problems with.

In total agreement.

Joe PTG&LI !!!



To: wlcnyc who wrote (14924)10/19/1998 10:48:00 PM
From: Jon Tara  Respond to of 18444
 
OT - Yes, I have used AOL. I dropped my AOL account just after they went to the IE-based browser, but I did load the software, and verified that it was using IE. In fact, this was a job requirement to do so. :)

I worked on a product that included, among other things, a web browser that "wraps around" IE in a similar manner to AOL. So I know JUST what they are doing. Since IE 3.0, Microsoft has provided an OLE control that implements the IE browser window. But you have to do the user-interface yourself - that is, any menus, including context menus, button bars, etc. - and there is a LOT to implement! Nevertheless, 90% of the functionality of MSIE is in the WebBrowser control, which is what AOL wrapped around.

The one that we did was basically an EXACT copy of the MSIE 3.0 UI. Of course, we came up with our own button images, but otherwise the functionality was identical. Too bad AOL didn't do that. :)

I can't think of any reason why the AOL browser - which is really the MSIE browser - would be any slower than MSIE "behind" AOL.

BTW, I was pretty proud of that browser, though I didn't write it. I was the system architect. One of the very talented people I worked with on that project basically wrote it himself. I did write some other code that wraps around the MSIE WebBrowser control in a different context, though, so I'm quite familiar with what it does.

The 4.0 control is much more capable than the 3.0 control that we used, and exposes more of the MSIE functionality. And the just-released MSVC 6.0 make it VERY easy to work with, providing some nice C++ wrappers, including one for the "cool bar" (the cool toolbar that was introduced with MSIE 3.0). We had to write a similar wrapper ourselves... You are going to see a LOT of neat stuff that wraps around MSIE 4.0 over the coming months!

Oh, incidently, I am NOT "defending" MSIE. In fact, I use Netscape 4.5 myself, with @Home. I do think that if I ever did another product that had to "wrap" around a web browser, I would still choose MSIE again for that application, though. Netscape is very difficult to embed in an application - it just wasn't designed for that. We did have a project to wrap our product around Netscape, and they (Netscape) had to make some modifications for us to get it to work. It was still clunky after they did that.