![]() ![]() I agree that screen space is precious (I spend my days in front of a 12” iBook), but I’m willing to give this extra space to OmniWeb. In terms of screen area, Safari comes out way ahead.īut in every other regard than screen area, OmniWeb’s presentation is superior. Safari’s tabs are displayed in a wide but short strip, across the top of the browser window. The argument against OmniWeb’s tab implementation is that it uses up a lot more screen space than does Safari’s (and Mozilla-based browsers). I’m listing it first in this review, however, because I anticipate it being the most controversial feature - it’s the most visually distinct new feature, and when the peanut gallery gripes about “the interface”, they tend to focus on what an app looks like. I like tabbed-browsing in general, and I like the Omni Group’s implementation, but it’s not even close to being the best or most important new feature in OmniWeb 5. Tabs can also be shown in a list view, sans thumbnails, to fit more tabs in the drawer without needing to scroll. The thumbnails are scaled representations of the page displayed in the tab. In fact, visually, they’re not really tabs at all, but rather thumbnails in a drawer on the side of the window. The idea of which is much the same as it is in Safari and Mozilla-based browsers, but the visual presentation is quite different. Keep in mind, if you download the public beta, that it is very much beta software, replete with crashers and other show-stopping bugs. Here’s an overview of the big new features. OmniWeb 5 is the first release where Omni has been able to focus almost solely on the browser application, rather than the rendering engine. OmniWeb 4.5 was a stop-gap, the first release of the browser that used WebCore instead of the Omni Group’s home-grown (and terribly outdated) rendering engine. OmniWeb 5 is important because it offers an abundance of major new features, including two that are revolutionary. With a rendering engine based on WebCore and JavaScriptCore - the same underlying technologies Safari is built around - OmniWeb 5 renders pages beautifully, and, more importantly, offers robust support for web standards.īut the current version of OmniWeb - version 4.5 - also uses WebCore, and it’s an also-ran browser. Based on today’s beta, and the two alpha releases I’ve used for the last week, OmniWeb 5 has the potential to be a very big deal. Today the Omni Group released the first public beta of OmniWeb 5.0. If you find them as useful as I do, help me spread the word.OmniWeb 5 Public Beta Monday, 2 February 2004 ![]() I am not sure if anyone on the GWT team or over at the Omnigroup knows just how amazingly well GWT and Omniweb work together. And, OmniWeb’s concept of Workspaces allows me to organize my projects in a clean and simple way. So, it still works against the Safari version of the plugin. OmniWeb – the grand daddy of all OSX web browsers is based on WebKit but still runs the WebKit core that ran Safari v5.05. There is a much simpler and more elegant solution – OmniWeb. Many mac users are downgrading Firefox (and turning off upgrade notifications) or finding ways to hack an out of date copy of Safari onto their machines as a work around. Since Mac users do not have access to a modern incarnation of a native version of Explorer, this has hit them pretty hard. And, the plugin is unusably slow in Google’s own Chrome (at least on the Mac platform). The plugin is significantly slower in Firefox v5 (and now v6 is in beta). Unfortunately, the GWT team is having a hard time keeping up with recent changes in browsers. During development, these plugins allow you to preview your changes without needing to stop and compile. One of Google Web Toolkit‘s greatest strengths, and also one of it’s greatest weaknesses, are the Web Developer plugins for Chrome, Safari, Firefox, and Explorer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |