0.7.5, Day One

Harris Boldt Edelman hbe at red-eft.la.ca.us
Wed Sep 28 03:07:31 PDT 1994


I haven't catalogued the forms and redirection errors I've encountered
with 0.7.5; they've seemed similar to what others have reported so far.

".jpeg" is now appended to "*.jpg" filenames on save, no matter what.
Having to rename the resulting "*.jpg.jpeg" files is already proving
to be highly irritating.

Single-page documents are reformatted for printing, but documents
longer than what would fit on a single page still remain unformatted,
printing with the top truncated and several lines lost across each
page-break (this on a NeXT Color Printer).

>From "View Source", some pages open in Edit directly, while for others
a Save panel is presented and the pages have to be saved before they
then are opened in Edit.  Why is this so?  Is there a default via which
one may specify an alternate program in which to open HTML source?
Will this eventually be made a Preference item?

The fixed-pitch font remains unresponsive to attempts at configuration
via defaults "OmniWeb NXFixedPitchFont" and "OmniWeb NXFixedPitchFontSize",
remaining at 10pt Ohlfs as if hardwired.  If it's indeed possible to
configure the fixed-pitch font via defaults, what are the correct defaults?

Is there a default (ultimately, another likely Preference item) via
which one may select that a Stuart.app window be opened instead for
telnet sessions instead of a Terminal.app window?  Further, when a link
to a telnet session calls Terminal, why is one Terminal window opened
and not used, then a second window opened for the telnet session?  I've
kept forgetting to mention these telnet/Terminal issues since first
encountering them in the first public test release, for 1) they don't
crop up often and 2) they are so nauseating when they do that I try to
forget them fast.

The history- and hierarchy browsers remain unintuitive and occasionally
downright baffling, albeit of some value at times.  From Wil's vague
remarks, I take it these are to be replaced with something more sensible
and usable in a later release.  Am I wrong?  Now might be the time to go
public with some details: I'm sure I'm not the only one in the test group
who'd prefer to comment on plans rather than misimplementations.

It goes without saying that I think OmniWeb continues to be a good piece
of work in the balance, else I wouldn't continue to expend the energy to
critque it.


-H.


P.S. If anyone would like a copy of the 1-pixel-high, black hrule.tiff
I made to replace my 3-pixel-high, blue hrule.tiff, and which I've been
using since reading Boerre Ludvigsen's comments upon the release of 0.7.4,
let me know.


More information about the OmniWeb-l mailing list