OMNIWEB WIKI MAC OS X
OMNIWEB WIKI WINDOWS

On August 11, 2004, the Omni Group released version 5.0 of OmniWeb which included a number of new features. In OmniWeb version 4.5, the Omni Group adopted Apple's KHTML-based WebCore rendering engine, which was created by Apple for its Safari browser. > However, this engine was very slow, particularly when scrolling, and was not fully compatible with all of the most recent web standards, such as Cascading Style Sheets. OmniWeb originally employed its own proprietary HTML layout engine that used standard API NSText components. It uses Quartz to produce images and smooth text, it will use multiple processors if available, and features an interface that makes use of Aqua UI features such as drawers, sheets and customizable toolbars.

OMNIWEB WIKI MAC OS X

OmniWeb is developed using the Cocoa API which allows it to take full advantage of Mac OS X features. From version 4.0 onwards, OmniWeb has been developed solely for the Mac OS X platform. After Lighthouse Design was bought by Sun Microsystems, the Omni Group released the product themselves, from version 2.5 onwards.

OMNIWEB WIKI WINDOWS

OmniWeb also was able to run on Microsoft Windows through the Yellow Box or the OpenStep frameworks.

As NextStep evolved into OpenStep and then Mac OS X, OmniWeb was updated to run on these platforms. Each of the links in that page also has an %accesskey=$% declaration in front of it, which enables a specific access key for that link.OmniWeb was originally developed by Omni Group for the NextStep platform, and was released by Lighthouse Design on 17 March 1995 after only one month's development time. That page contains the links that the default PmWiki skin, and many other skins, use to generate links such as 'View' 'Edit' and 'History' that appear on most pages (other than editing screens). One location where those links can be viewed is Site.PageActions.

The list of access key assignments in default PmWiki installations generally work throughout a site because links have been created in PmWiki skins and editing screens that incorporate access key parameters using the access key translation phrases. Note that this AKey+x access key only works this way on this page, because it is simply a shortcut for accessing the link that exists only on this page. That same action key link could be created in PmWiki markup by typing %accesskey='x'%]%%, like this: Example. Note, in cases of conflicts between the keyboard shortcuts assigned by browsers and access keys assigned by links and other markup on webpages, many browsers, including Mozilla, Netscape and Internet Explorer, allow access keys to override the browser defaults and require a different sequence to continue using overridden browser assignments (typically, by pressing and releasing the Alt key, instead of holding it down).Īccess keys are implemented in html as optional parameters that can be added to links and many other types of markup.Įxample: Example would create a link to that could be triggered by clicking on the linked word 'example' or using the access key Akey+x.

Firefox versions 1.5 and earlier simply use Alt, while Firefox version 2.0 uses Shift+Alt.

Internet Explorer requires that the Enter key be pressed at the end of the sequence for versions 5 and up under Windows, but not under Macintosh (where access keys were not supported until after version 4.5).

With Chrome, press SHIFT + ALT + the access keyĮxceptions exist for specific browsers, and specific versions.

With Konqueror, press Ctrl to enter (or exit) access-key mode.

With Opera press Shift+Esc to enter (or exit) access-key mode.

With Safari (Version 4.0.2) press Ctrl + Option + the access key.

On a Macintosh with Firefox, Omniweb, Internet Explorer, press Ctrl + the access key.

With Firefox, press SHIFT + ALT + the access key.

On Windows with Internet Explorer, press ALT + the access key.

Using access keys in different operating systems and browsersĪccess keys require you to hold down two or more keys.

Omniweb wiki