Cocoa (API) in the context of Graphical widget


Cocoa (API) in the context of Graphical widget

Cocoa (API) Study page number 1 of 1

Play TriviaQuestions Online!

or

Skip to study material about Cocoa (API) in the context of "Graphical widget"


HINT:

In this Dossier

Cocoa (API) in the context of Firefox 3.5

The project that became Firefox today began as an experimental branch of the Mozilla Suite called m/b (or mozilla/browser). Firefox retains the cross-platform nature of the original Mozilla browser, using the XUL user interface markup language. The use of XUL made it possible to extend the browser's capabilities through the use of extensions and themes. The development and installation processes of these add-ons raised security concerns, and with the release of Firefox 0.9, the Mozilla Foundation opened a Mozilla Update website containing "approved" themes and extensions. The use of XUL sets Firefox apart from other browsers, including other projects based on Mozilla's Gecko layout engine and most other browsers, which use interfaces native to their respective platforms (Galeon and Epiphany use GTK+, K-Meleon uses MFC, and Camino uses Cocoa). Many of these projects started before Firefox, and may have served as inspiration.

Hyatt, Ross, Hewitt and Chanial developed their browser to combat the perceived software bloat of the Mozilla Suite (codenamed, internally referred to, and continued by the community as SeaMonkey), which integrated features such as IRC, mail, news, and WYSIWYG HTML editing into one internet suite. After it was sufficiently developed, binaries for public testing appeared in September 2002 under the name Phoenix. This name carried the implication of the mythical firebird that rose triumphantly from the ashes of its dead predecessor, in this case Netscape Navigator which lost the "First browser war" to Microsoft's Internet Explorer. The name Mozilla began as the internal codename for the original 1994 Netscape Navigator browser aiming to displace NCSA Mosaic as the world's most popular web browser. The name for this would-be "Mosaic killer" was meant to evoke the building-crushing Godzilla.

View the full Wikipedia page for Firefox 3.5
↑ Return to Menu

Cocoa (API) in the context of OpenStep

OpenStep is an object-oriented application programming interface (API) specification developed by NeXT. It provides a framework for building graphical user interfaces (GUIs) and developing software applications. OpenStep was designed to be platform-independent, allowing developers to write code that could run on multiple operating systems, including NeXTSTEP, Windows NT, and various Unix-based systems. It has influenced the development of other GUI frameworks, such as Cocoa for macOS, and GNUstep.

OpenStep was principally developed by NeXT and Sun Microsystems, to allow advanced application development on Sun's operating systems, specifically Solaris. NeXT produced a version of OpenStep for its own Mach-based Unix OS, stylized in all capital letters as OPENSTEP. The software libraries that shipped with OPENSTEP are a superset of the original OpenStep specification, including many features from the original NeXTSTEP.

View the full Wikipedia page for OpenStep
↑ Return to Menu

Cocoa (API) in the context of UIKit

UIKit is an application development environment and graphical user interface toolkit from Apple Inc. used to build apps for the iOS, iPadOS, watchOS, tvOS, and visionOS operating systems.

UIKit provides an abstraction layer of iOS, the operating system for the iPhone, iPod Touch, and iPad. UIKit is similar to AppKit from the macOS Cocoa API toolset, and it too is primarily written in the Objective-C language. UIKit allows the use of hardware and features that are not found in macOS computers and are thus unique to the iOS range of devices. Like AppKit, UIKit follows a Model–View–Controller (MVC) software architecture.

View the full Wikipedia page for UIKit
↑ Return to Menu

Cocoa (API) in the context of GUI widget

In a graphical user interface (GUI), a graphical widget (also graphical control element or control) is an element of interaction, such as a button or a scroll bar. Controls are software components that a computer user interacts with through direct manipulation to read or edit information about an application. User interface libraries such as Windows Presentation Foundation, Qt, GTK, and Cocoa, contain a collection of controls and the logic to render these.

Each widget facilitates a specific type of user-computer interaction, and appears as a visible part of the application's GUI as defined by the theme and rendered by the rendering engine. The theme makes all widgets adhere to a unified aesthetic design and creates a sense of overall cohesion. Some widgets support interaction with the user, for example labels, buttons, and check boxes. Others act as containers that group the widgets added to them, for example windows, panels, and tabs.

View the full Wikipedia page for GUI widget
↑ Return to Menu

Cocoa (API) in the context of Objective-C

Objective-C is a high-level general-purpose, object-oriented programming language that adds Smalltalk-style message passing (messaging) to the C programming language. Originally developed by Brad Cox and Tom Love in the early 1980s, it was selected by NeXT for its NeXTSTEP operating system. Due to Apple macOS’s direct lineage from NeXTSTEP, Objective-C was the standard language used, supported, and promoted by Apple for developing macOS and iOS applications (via their respective application programming interfaces (APIs), Cocoa and Cocoa Touch) from 1997, when Apple purchased NeXT, until the introduction of the Swift language in 2014.

Objective-C programs developed for non-Apple operating systems or that are not dependent on Apple's APIs may also be compiled for any platform supported by GNU GNU Compiler Collection (GCC) or LLVM/Clang.

View the full Wikipedia page for Objective-C
↑ Return to Menu