Version 0.95 Beta of the WebExplorer is now available by anonymous
ftp from ftp.ibm.net in /pub/WebExplorer, or via the Retrieve Software
Updates icon in the Internet Connection Folder.
This version of the WebExplorer is going through our final internal
tests, and is planned to be included in the next major release of OS/2 Warp.
The next version posted on the net will be WebExplorer 1.0.
IBM is committed to providing our customers with competitive, stable
code in the fast-paced Internet applications market. The WebExplorer
was built from scratch in less than 6 months by a highly motivated
team of four individuals. We are now ramping up a major development
effort to continue the WebExplorer to add the many features that you,
our customers, have been asking for. The following items are at the
top of our list for future releases:
o Enhanced point-and-click newsreader support, including support
for threaded news articles (via XHDR).
o Embedded SMTP and POP mailer support for handling
mailto: URLs.
o Optimizations for 14.4k modem users, including streaming
graphics and multiple, concurrent document retrieval.
This version fixes the following bugs reported in
comp.os.os2.networking.tcp-ip:
o On some display devices, WebExplorer 0.94 would
occasionally leave blank areas. This has been fixed.
o When the WebExplorer exits, a dialog box asks you to confirm.
You can disable this protective feature by starting WebExplorer
with the "-q" option.
o In forms, WebExplorer now remembers and resets menu selections
correctly.
o SaveAS now works for plain text documents
o In some cases, WebExplorer 0.94 would trap when you clicked
on graphics. This has been fixed.
o SELECT fields of size 1 no longer put data in reverse order.
o TEXTAREAs in forms may now contain up to 32,000 bytes of data.
o Font changes with form windows in view will now reformat
properly.
o Local jumps (to #anchor) will not cause images and forms
to disappear.
o INPUT fields without a MAXLENGTH field will now use
the SIZE attribute as MAXLENGTH, instead of the nominal
value of 32.
o Changing the user name at an FTP host should no longer trap.
o QUOTE and BLOCKQUOTE are now supported.
o Miscellaneous 8-bit ISO-Latin-1 characters were added.
o WebExplorer 0.95 no longer flashes the screen twice
on a resize operation.
o WebExplorer 0.95 no longer brings itself to the foreground when
a document load completes.
o Numerous keyboard accelerators were added.
o Drag/drop of jpeg images uses the ".jpg" extension instead of ".jpe".
o Hitting return on a shadowed quicklist item while a document is
being loaded will no longer cause PM to freeze.
We thank you for your time and patience with the IBM WebExplorer. Your
postings to Usenet newsgroups and your personal notes have greatly
accelerated the maturation of this application. We will continue to
address more of the suggestions and comments in future releases.
The IBM WebExplorer Development Team
Thanks,
=-=-=-=-=-=-=-=-=-=-=-=-=
= Brian Chapman =
= Using NewsReader/2 =
= I'm WARPED! =
=-=-=-=-=-=-=-=-=-=-=-=-=
I agree they should add "proxy except" fields like Netscape. In the
meantime you could always patch a copy of EXPLORE.EXE about 0x0a100 to
use LXPLORE.INI instead of EXPLORE.INI, then run that as your in-house
browser...
--
Tom Neff [email] tn...@panix.com [web] http://www.panix.com/tneff/
That shouldn't be necessary. I use a command line parm
"-I \tcpip\etc\internet.ini" to pick up the ini with
proxy info." So I have two icons (one modified with a big
"I" in the middle) for both inside and Internet browsers. I don't
think this is in the help doco for WebExplorer--just took a stab
that it might support the same command line parm as Mosaic.
//---------------------------------------------------------
// Brian Hunt bh...@teleport.com Portland, Oregon
// Software Engineer, OS/2, Linux, C++/C. A non-affiliated
// user of Teleport a public access provider.
//---------------------------------------------------------
So something I feel to be quite important, is not mentioned... I
have seen it discussed in this forum before.
Create a way to set a subnet or domain or something like that where
WebExp will NOT use the socks/proxy server. Currently if you configure
a proxy server it is used for everything. If you configure a socks
server (but not a proxy server) the socks server is used for everything.
Inside of HP, we have to use a socks/proxy to get out on the internet,
but cannot use socks and some cannot use proxy to reach hosts inside
of HP. This means that with WE we have to keep adding/removing the
socks/proxy server settings. Bah, humbug!
sdb
--
| This post does not represent Hewlett-Packard. Is it my opinion? Maybe! |
| Sylvan Butler-Boise,ID | sbu...@boi.hp.com | ...!hplabs!hpdmd48!sbutler |
"Don't Tread On Me!"
Do you guys have the plan to add DBCS (Double Byte Character Set) for
Korean, Japanese and Chinese versions of OS/2? I can read Korean WWW
pages using Netscape under Hangul (Korean) WinOS2, but Windows is
something I want to get rid of....
> We thank you for your time and patience with the IBM WebExplorer. Your
> postings to Usenet newsgroups and your personal notes have greatly
> accelerated the maturation of this application. We will continue to
> address more of the suggestions and comments in future releases.
>
> The IBM WebExplorer Development Team
THANK YOU! Please remember that if some manager from the old
IBM wants to cut your budget, limit your staffing, or limit your vision,
just let us know. We will give you more positive user testimonials
than any group in IBM has ever received. Guaranteed!
Thankye-Thankye-Thankye,
Brad Bueche
I don't know much about proxy servers(just a little general info),
but perhaps its the fact that your proxy server doesn't allow
incoming connections to the internal network which causes
the problem. If thats the case, and you have a spare machine to do it,
would it be possible to set up a SECOND proxy server? This one
would connect any machine to the internal network, and for requests
going out the internal proxy server would connect to the external
proxy server(that way your network is still as secure externally
since to access the internal proxy server you have to first
get past the external proxy server if your coming from outside).
-Gary Mort
g...@panix.com
For your consideration:
1. If you happen to open WE without a slip (network?) connection then
the whole desktop locks up for an extended period. After a while WE will
open and things go back to normal. If one is not aware of this one just
may consider a reboot during this long period of inactivity.
2. FTP file lists are still very strange unless you like to scroll or
have the image loading disabled.
3. If the FTP site refuses the connection WE will cache the returned error
so that it is very difficult to try again using the typed entry. On busy sites
retries are a way of life..... (Some users may wonder why a site is SO BUSY).
Thanks for the -q option & keep up the good, no make that great, work.
**Bill
: 3. If the FTP site refuses the connection WE will cache the returned
: error so that it is very difficult to try again using the typed entry.
I think all you have to do is hit F5 for "Reload". Reloading ignores
cached pages (that's what it's for).
--
William McBrine | In the morning, laughing, happy fishheads
wmcb...@clark.net | In the evening, floating in the soup
Thank You! This is greatly appreciated as until now I always needed to
do a rename of my Drag'n'Dropped JPEG's.
Is there any more info on the FTP problem? Some people seem to have no
problems with FTP'ing from inside WE. Others, including me, do. When I
try to FTP, it''l just stop transferring after a short while and sits
there doing nothing. Is this 'operator error', A problem with the sites
I try to access or a setup-problem?
Please try <A HREF="http://www.iaehv.nl/users/paul/index.html">
And eg. try to ftp the Miro /Warp fix. That's an ftp: URL and used to
work until WE 0.91.
Merry X'mas.
--__
/_/ |/ E-mail: pa...@serena.iaehv.nl
/aul |\olenbrander WWW : http://www.iaehv.nl/users/paul/
-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-
>: 3. If the FTP site refuses the connection WE will cache the returned
>: error so that it is very difficult to try again using the typed entry.
>I think all you have to do is hit F5 for "Reload". Reloading ignores
>cached pages (that's what it's for).
Hooray! Thanks for that F5 tip!
+-----------------------------------------+-------------------------------+
| Charles Robinson Mpls, Minnesota | "You can't have everything... |
| email: charles....@medtronic.com | where would you put it?" |
+-----------------------------------------+-------------------------------+