Re: Browser Use
John Stalberg <[email protected]> Sat, 21 Feb 2009 11:15:07 +0100
| Newsgroups | gmane.comp.web.omniweb |
|---|---|
| Message-ID | <[email protected]> |
On 11 feb 2009, at 10.30, Andrew Zima wrote: > > Would the last person mind sharing an example of Firefox's lack of =20 > Contextual menu support? YMMV but I've never had a problem with =20 > contextual menus [finding them or using them on G4/G5/intel]. > > In the future, could the person having problems atleast mention what =20= > OS [ 10.3, 10.4, 10.5] and what platform [PPC vs intel] ? > I=92m not the person you are referring to but I have a Cocoa favourite I = =20 use a lot. The mini Dictionary view you can access by hovering over a =20= word and hit a key combination. The correct keys is located in System =20= Preferences/Keyboard and Mouse/Keyboard shortcuts. I have changed my =20 settings and cant remember the original. It might have been ctrl + d? There are probably a plug-in for FF that will do this and this =20 illustrates a bit the different approach between OW and FF. OW comes =20 jammed with integrated features and FF needs to be taken care of by =20 the user until it shines. I don't know when the Dictionary feature were introduced but it has =20 been there for Cocoa apps for at least a couple of OS X versions and =20 it is CPU agnostic. My biggest issue with FF is it=92s inability to scale performance wise. =20= With some (large) amount of heavily tabbed windows, perhaps with lots =20= of scripts and/or flash, it stalls on me. I find OW reaches crawling =20 speeds in a more direct proportion to the load as does Safari. FF =20 however suddenly hits the limit and if I'm less than very patient I =20 have to force quit it. This is with latest FF 3.0.6 on latest OS X =20 10.5.6 on both Intel and PPC. With faster hardware the problem gets =20 easier to get out of since it all depends on waiting for the browser =20 underpinnings to finnish whatever it is doing. The whole OS wide user =20= interface often gets stalled when this is happening to me and =20 sometimes I find it easier to remotely login (I have a couple of Macs =20= sitting on my desktop connected with Gbit) and kill FF from a command =20= line. OW might not be perfect (yet) but all in all it is one of the things =20 that really makes my choice of OS platform extra worthwhile. When I =20 think about it OS X would be significantly less attractive if OW =20 disappeared! And yet it would be pretty nice anyway in such a case. I think Apple should make their http://www.me.com/ page to recognise =20 OW as a capable browser with the default browser settings. Or is it =20 perhaps OmniGroup that should think twice about it and come up with a =20= solution? In any case there should be an non issue to surf right in on = http://www.me.com/=20 with a WebKit based browser such as OW. John Stalberg