4.5 features

[Evan de Riel]

On Thursday, Feb 19, 2004, at 13:05 US/Eastern, Manfred Schubert wrote:

> Am 19.02.2004 um 18:22 schrieb Eugene Lee:
>
>> That's true.  Maybe OW should truncate long URLs (or replace long  
>> middle
>> bits with an ellipsis) the way Finder does with long filenames.
>
> Yes, please. Truncate the middle. The end is more important to see.

Not necessarily.  For cgi urls, the end of the url may be some of the  
least significant data.  Here's one from a dictionary entry from  
Perseus:

http://www.perseus.tufts.edu/cgi-bin/ 
ptext?layout.reflookup=moenia&layout.refembed=2&doc=Perseus%3Atext%3A199 
9.04.0059%3Aentry%3D%2329987&layout.refcit=book%3D1%3Aline%3D7&layout.re 
fabo=Perseus%3Aabo%3Aphi%2C0690%2C003&layout.reflang=la&layout.refwordco 
unt=1&layout.refdoc=Perseus%3Atext%3A1999.02.0055

Three important things are located in the middle of the url:  the cgi  
file (ptext), the word I'm looking up (moenia), and the identifier of  
the work in which it's being looked up (1999.04.0059).  The end of the  
url simply tells me what I was looking at before I got there, which is  
not nearly as useful if I want to tell what I'm about to look at.

I also agree with BS's comment that having an editable text field is  
extraordinarily convenient.  And perhaps I'm crazy, but as long as  
there's the spinning progress indicator and a functioning state change  
between the stop and reload pages when OmniWeb finishes rendering a  
page, having the bar at the bottom of the screen isn't even necessary,  
not to mention (IMHO) aesthetically unattractive.  The title bar could  
even be changed for showing window status, eg: "HTTP queued for  
document from example" or some such.

Evan