GUI Programming - Revision history

Costel Mincea: /* ASL */

2022-04-06T10:14:43Z

ASL

← Older revision		Revision as of 10:14, 6 April 2022
Line 64:		Line 64:
	[[ASL_Library\|ASL]] is a datastructure-based toolkit. It is implemented as a single library and is not extensible.		[[ASL_Library\|ASL]] is a datastructure-based toolkit. It is implemented as a single library and is not extensible.

	The Application ~~Standard~~ Library (ASL) is a toolkit designed to ease the programming of common requesters. There are currently three types of requester available: file requester, font requester and screenmode requester.		The Application Support Library (ASL) is a toolkit designed to ease the programming of common requesters. There are currently three types of requester available: file requester, font requester and screenmode requester.

	=== ReAction ===		=== ReAction ===

Costel Mincea at 08:55, 6 April 2022

2022-04-06T08:55:15Z

← Older revision		Revision as of 08:55, 6 April 2022
Line 64:		Line 64:
	[[ASL_Library\|ASL]] is a datastructure-based toolkit. It is implemented as a single library and is not extensible.		[[ASL_Library\|ASL]] is a datastructure-based toolkit. It is implemented as a single library and is not extensible.

	The ~~Amiga~~ Standard Library (ASL) is a toolkit designed to ease the programming of common requesters. There are currently three types of requester available: file requester, font requester and screenmode requester.		The Application Standard Library (ASL) is a toolkit designed to ease the programming of common requesters. There are currently three types of requester available: file requester, font requester and screenmode requester.

	=== ReAction ===		=== ReAction ===

Daniel Jedlicka: Added some notes about GadTools.

2015-09-13T15:39:40Z

Added some notes about GadTools.

← Older revision		Revision as of 15:39, 13 September 2015
Line 50:		Line 50:
	== GUI toolkits ==		== GUI toolkits ==

	While the Intuition Library originally provided a datastructure-based set of basic GUI elements (screens, windows, menus, buttons & string gadgets, etc.) they have been supplanted by more modern tools for user interface programming. Most of the GUI-related functionality is now provided through various extensions to Intuition, or ''toolkits''. The following toolkits are installed by default in AmigaOS:		While the Intuition Library originally provided a datastructure-based set of basic GUI elements (screens, windows, menus, buttons & string gadgets, etc.) they have been supplanted by more modern tools for user interface programming. Most of the GUI-related functionality is now provided through various extensions to Intuition, or ''toolkits''. The following toolkits are installed by default in AmigaOS:

	=== GadTools ===		=== GadTools ===
Line 57:		Line 57:

	GadTools was introduced in AmigaOS 2.x as a ready-made toolkit for easier, faster and more consistent GUI design. GadTools extended the original Intuition set with fancy new controls such as the [[GadTools_Library#Cycle_Gadgets\|cycle gadget]], the [[GadTools_Library#Mutually-Exclusive_Gadgets\|radiobutton]], or the [[GadTools_Library#Listview_Gadgets\|listview]]. The gadgets shared similar imagery, thus giving Amiga GUIs a more uniform, standardized look. Apart from improving the gadget set, GadTools also greatly simplified the creation of menus (GadTools uses standard Intuition menus but provides its own build and layout system for them). On the other hand, there is a very limited support for images in GadTools.		GadTools was introduced in AmigaOS 2.x as a ready-made toolkit for easier, faster and more consistent GUI design. GadTools extended the original Intuition set with fancy new controls such as the [[GadTools_Library#Cycle_Gadgets\|cycle gadget]], the [[GadTools_Library#Mutually-Exclusive_Gadgets\|radiobutton]], or the [[GadTools_Library#Listview_Gadgets\|listview]]. The gadgets shared similar imagery, thus giving Amiga GUIs a more uniform, standardized look. Apart from improving the gadget set, GadTools also greatly simplified the creation of menus (GadTools uses standard Intuition menus but provides its own build and layout system for them). On the other hand, there is a very limited support for images in GadTools.

			As of AmigaOS 4.1 Final Edition, GadTools is basically a legacy toolkit retained for compatibility.

	=== ASL ===		=== ASL ===
Line 86:		Line 88:
	== Choosing Toolkits ==		== Choosing Toolkits ==

	* Choose the toolkit that works best for your application and your end customers.		* Choose the toolkit that works best for your application and your end users/customers.

	* GadTools gadgets are incompatible with all others and have their own [[GadTools_Library#Function_Reference\|set of functions]] to be used with. There is no automatic layout system: GadTools gadgets are not scalable and are at fixed positions and dimensions. ~~Using~~ ~~GadTools~~ ~~for~~ ~~GUI~~ ~~programming is no longer recommended~~, ~~with~~ ~~the~~ ~~exception~~ of ~~the~~ ~~menu~~ ~~build~~ ~~and~~ ~~layout~~ ~~system~~.		* GadTools gadgets are incompatible with all others and have their own [[GadTools_Library#Function_Reference\|set of functions]] to be used with. There is no automatic layout system: GadTools gadgets are not scalable and are at fixed positions and dimensions. Due to its inherent limitations, using GadTools in modern applications can no longer be recommended.

⚫	* The original BOOPSI set built in Intuition is usable but somewhat limited. Some BOOPSI ~~objects~~ are now actually wrappers for ReAction ~~objects~~.

	* If you require modern features like scalability, font sensitivity, automatic (re)layouting, or window iconification (the ability to collapse the program window into an icon on the Workbench screen), then use one of the object-oriented toolkits: ReAction or MUI.		* If you require modern features like scalability, font sensitivity, automatic (re)layouting, or window iconification (the ability to collapse the program window into an icon on the Workbench screen), then use one of the object-oriented toolkits: ReAction or MUI.

	* The ASL toolkit is utilized by ReAction and MUI through dedicated classes. There is little need to use ASL directly in object-oriented GUIs.		* The ASL toolkit is utilized by ReAction and MUI through dedicated classes. There is little need to use ASL directly in object-oriented GUIs.

		⚫	* The original BOOPSI class set built in Intuition is usable but somewhat limited. Some BOOPSI classes are now actually wrappers for ReAction classes.

	* Prefer not to mix datastructure-oriented and object-oriented GUI programming. Functions designed for Intuition windows, gadgets or images are not meant to be used on GUI objects created via ReAction. BOOPSI objects must solely be manipulated using [[BOOPSI_-_Object_Oriented_Intuition#Function_Reference\|BOOPSI functions]] (methods).		* Prefer not to mix datastructure-oriented and object-oriented GUI programming. Functions designed for Intuition windows, gadgets or images are not meant to be used on GUI objects created via ReAction. BOOPSI objects must solely be manipulated using [[BOOPSI_-_Object_Oriented_Intuition#Function_Reference\|BOOPSI functions]] (methods).

Daniel Jedlicka: Fixed links to Intuition wiki pages that had been renamed.

2015-04-10T09:19:08Z

Fixed links to Intuition wiki pages that had been renamed.

← Older revision		Revision as of 09:19, 10 April 2015
Line 1:		Line 1:
	== Background ==		== Background ==

	In AmigaOS, the face a program shows you – its [http://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] (GUI) – is created through a subsystem called [[~~Intuition_and_the_Amiga_Graphical_User_Interface~~\|Intuition]]. Older literature sometimes used to refer to Intuition as “the Amiga user interface” but this is really not the case. Despite being responsible for much of what you can ''see'' in the OS (including its windowing desktop environment, the [[UserDoc:Workbench\|Workbench]]), Intuition itself remains ''invisible'' to the user. It is merely a system component providing ready-made [[#GUI elements\|elements]] to build GUIs from, and a set of functions through which these elements are manipulated. Intuition also interconnects GUIs with the operating system and handles various communications that underlie application usage and control.		In AmigaOS, the face a program shows you – its [http://en.wikipedia.org/wiki/Graphical_user_interface graphical user interface] (GUI) – is created through a subsystem called [[Intuition_Library\|Intuition]]. Older literature sometimes used to refer to Intuition as “the Amiga user interface” but this is really not the case. Despite being responsible for much of what you can ''see'' in the OS (including its windowing desktop environment, the [[UserDoc:Workbench\|Workbench]]), Intuition itself remains ''invisible'' to the user. It is merely a system component providing ready-made [[#GUI elements\|elements]] to build GUIs from, and a set of functions through which these elements are manipulated. Intuition also interconnects GUIs with the operating system and handles various communications that underlie application usage and control.

	Intuition’s functionality is further extended by a number of auxiliary system components, or [[#GUI toolkits\|toolkits]]. Like most AmigaOS subsystems, Intuition and its extensions are implemented as libraries of functions that can be accessed from a higher-level programming language like C, C++, Modula-2 or AmigaE.		Intuition’s functionality is further extended by a number of auxiliary system components, or [[#GUI toolkits\|toolkits]]. Like most AmigaOS subsystems, Intuition and its extensions are implemented as libraries of functions that can be accessed from a higher-level programming language like C, C++, Modula-2 or AmigaE.
Line 25:		Line 25:
	\| [[Intuition_Images,_Line_Drawing_and_Text#Creating_Images\|images]] \|\| Non-selectable elements showing graphics or text. \|\| Intuition Library, ReAction, MUI		\| [[Intuition_Images,_Line_Drawing_and_Text#Creating_Images\|images]] \|\| Non-selectable elements showing graphics or text. \|\| Intuition Library, ReAction, MUI
	\|-		\|-
	\| [[~~Intuition_Requesters_and_Alerts#Intuition_Requesters_and_Alerts~~\|requesters]] \|\| Means for displaying information and for requesting input from the user. They would be called “dialogs”, “dialog boxes” or “dialog windows” in other OSes. \|\| Intuition Library, ASL Library, ReAction, MUI		\| [[Intuition_Requesters\|requesters]] \|\| Means for displaying information and for requesting input from the user. They would be called “dialogs”, “dialog boxes” or “dialog windows” in other OSes. \|\| Intuition Library, ASL Library, ReAction, MUI
	\|-		\|-
	\| [[~~Intuition_Requesters_and_Alerts#Alerts~~\|alerts]] \|\| A method of emergency communication (such as system errors). \|\| Exec Library, Intuition Library		\| [[Intuition_Alerts\|alerts]] \|\| A method of emergency communication (such as system errors). \|\| Exec Library, Intuition Library
	\|-		\|-
	\| [[Application_Library#Pop-up_notifications_(Ringhio_messages)\|pop-up notifications]] \|\| Automatic messages informing the user when things happen. Unlike requesters, notifications are “unobtrusive” and do not require any input from the user. \|\| [[Application Library]]		\| [[Application_Library#Pop-up_notifications_(Ringhio_messages)\|pop-up notifications]] \|\| Automatic messages informing the user when things happen. Unlike requesters, notifications are “unobtrusive” and do not require any input from the user. \|\| [[Application Library]]

Rob Cranley: /* Choosing Toolkits */ Fixed typo

2015-03-12T15:23:00Z

Choosing Toolkits: Fixed typo

← Older revision		Revision as of 15:23, 12 March 2015
Line 92:		Line 92:
	* The original BOOPSI set built in Intuition is usable but somewhat limited. Some BOOPSI objects are now actually wrappers for ReAction objects.		* The original BOOPSI set built in Intuition is usable but somewhat limited. Some BOOPSI objects are now actually wrappers for ReAction objects.

	* It you require modern features like scalability, font sensitivity, automatic (re)layouting, or window iconification (the ability to collapse the program window into an icon on the Workbench screen), then use one of the object-oriented toolkits: ReAction or MUI.		* If you require modern features like scalability, font sensitivity, automatic (re)layouting, or window iconification (the ability to collapse the program window into an icon on the Workbench screen), then use one of the object-oriented toolkits: ReAction or MUI.

	* The ASL toolkit is utilized by ReAction and MUI through dedicated classes. There is little need to use ASL directly in object-oriented GUIs.		* The ASL toolkit is utilized by ReAction and MUI through dedicated classes. There is little need to use ASL directly in object-oriented GUIs.

Daniel Jedlicka: /* ReAction */

2014-06-30T07:04:26Z

ReAction

← Older revision		Revision as of 07:04, 30 June 2014
Line 68:		Line 68:
	[[ReAction]] is an object-oriented toolkit based on BOOPSI which is highly extensible.		[[ReAction]] is an object-oriented toolkit based on BOOPSI which is highly extensible.

	ReAction is a more modern toolkit which hides much of the complexity. It covers all the functionality of GadTools and ASL and uses and extends the original BOOPSI class set built into Intuition Library. ReAction is considered to be the standard Amiga GUI toolkit.		ReAction is a more modern toolkit which hides much of the complexity. It covers all the functionality of GadTools and ASL and uses and extends the original BOOPSI class set built into Intuition Library. ReAction is considered to be the standard Amiga GUI toolkit. Over the years it has been integrated into the Intuition/BOOPSI framework, and is no longer considered a separate component.

	=== MUI ===		=== MUI ===

Paul Sadlik: /* GUI toolkits */

2013-04-21T19:15:25Z

GUI toolkits

← Older revision		Revision as of 19:15, 21 April 2013
Line 50:		Line 50:
	== GUI toolkits ==		== GUI toolkits ==

	~~The~~ Intuition Library ~~itself~~ ~~does~~ ~~not~~ ~~provide~~ ~~all~~ ~~the~~ ~~necessary~~ ~~tools~~ ~~for~~ modern user interface programming. ~~Much~~ of the GUI-related functionality is now provided through various extensions, or ''toolkits''. The following toolkits are installed by default in AmigaOS:		While the Intuition Library originally provided a datastructure-based set of basic GUI elements (screens, windows, menus, buttons & string gadgets, etc.) they have been supplanted by more modern tools for user interface programming. Most of the GUI-related functionality is now provided through various extensions to Intuition, or ''toolkits''. The following toolkits are installed by default in AmigaOS:

	=== GadTools ===		=== GadTools ===

Daniel Jedlicka: /* GUI Elements */

2012-10-10T06:49:14Z

GUI Elements

← Older revision		Revision as of 06:49, 10 October 2012
Line 17:		Line 17:
	\| [[Intuition_Screens\|screens]] \|\| Virtual desktops on which windows are opened. \|\| Intuition Library		\| [[Intuition_Screens\|screens]] \|\| Virtual desktops on which windows are opened. \|\| Intuition Library
	\|-		\|-
	\| [[Intuition_Windows\|windows]] \|\| Rectangular areas containing an interface through which a program communicates with the user, and vice versa. \|\| Intuition Library		\| [[Intuition_Windows\|windows]] \|\| Rectangular areas containing an interface through which a program communicates with the user, and vice versa. \|\| Intuition Library, ReAction, MUI
	\|-		\|-
	\| [[Intuition_Menus\|menus]] \|\| Programmable sets of commands displayed as a pull-down list of options. \|\| Intuition Library, GadTools Library		\| [[Intuition_Menus\|menus]] \|\| Programmable sets of commands displayed as a pull-down list of options. \|\| Intuition Library, GadTools Library

Daniel Jedlicka: /* Choosing Toolkits */

2012-10-10T06:47:03Z

Choosing Toolkits

← Older revision		Revision as of 06:47, 10 October 2012
Line 98:		Line 98:
	* Prefer not to mix datastructure-oriented and object-oriented GUI programming. Functions designed for Intuition windows, gadgets or images are not meant to be used on GUI objects created via ReAction. BOOPSI objects must solely be manipulated using [[BOOPSI_-_Object_Oriented_Intuition#Function_Reference\|BOOPSI functions]] (methods).		* Prefer not to mix datastructure-oriented and object-oriented GUI programming. Functions designed for Intuition windows, gadgets or images are not meant to be used on GUI objects created via ReAction. BOOPSI objects must solely be manipulated using [[BOOPSI_-_Object_Oriented_Intuition#Function_Reference\|BOOPSI functions]] (methods).

	* Many programmers seem to be confused about window programming. It's fairly easy:		* Many new programmers seem to be confused about window programming. It's fairly easy:
	** ReAction elements (objects) must reside in a ''ReAction window'', that is, a window created through the Window Class, which is part of the toolkit. Such a window is manipulated as any other BOOPSI object.		** ReAction elements (objects) must reside in a ''ReAction window'', that is, a window created through the Window Class, which is part of the toolkit. Such a window is manipulated as any other BOOPSI object.
	** Intuition or GadTools elements must reside in an ''Intuition window'', that is, a window created through functions OpenWindow() or OpenWindowTags(), which are both part of the Intuition Library. Such windows are manipulated using dedicated functions.		** Intuition or GadTools elements must reside in an ''Intuition window'', that is, a window created through functions OpenWindow() or OpenWindowTags(), which are both part of the Intuition Library. Such windows are manipulated using dedicated functions.

Daniel Jedlicka: /* Choosing Toolkits */

2012-10-10T06:37:31Z

Choosing Toolkits

← Older revision		Revision as of 06:37, 10 October 2012
Line 89:		Line 89:

	* GadTools gadgets are incompatible with all others and have their own [[GadTools_Library#Function_Reference\|set of functions]] to be used with. There is no automatic layout system: GadTools gadgets are not scalable and are at fixed positions and dimensions. Using GadTools for GUI programming is no longer recommended, with the exception of the menu build and layout system.		* GadTools gadgets are incompatible with all others and have their own [[GadTools_Library#Function_Reference\|set of functions]] to be used with. There is no automatic layout system: GadTools gadgets are not scalable and are at fixed positions and dimensions. Using GadTools for GUI programming is no longer recommended, with the exception of the menu build and layout system.

		⚫	* The original BOOPSI set built in Intuition is usable but somewhat limited. Some BOOPSI objects are now actually wrappers for ReAction objects.

			* It you require modern features like scalability, font sensitivity, automatic (re)layouting, or window iconification (the ability to collapse the program window into an icon on the Workbench screen), then use one of the object-oriented toolkits: ReAction or MUI.

	* The ASL toolkit is utilized by ReAction and MUI through dedicated classes. There is little need to use ASL directly in object-oriented GUIs.		* The ASL toolkit is utilized by ReAction and MUI through dedicated classes. There is little need to use ASL directly in object-oriented GUIs.
Line 94:		Line 98:
	* Prefer not to mix datastructure-oriented and object-oriented GUI programming. Functions designed for Intuition windows, gadgets or images are not meant to be used on GUI objects created via ReAction. BOOPSI objects must solely be manipulated using [[BOOPSI_-_Object_Oriented_Intuition#Function_Reference\|BOOPSI functions]] (methods).		* Prefer not to mix datastructure-oriented and object-oriented GUI programming. Functions designed for Intuition windows, gadgets or images are not meant to be used on GUI objects created via ReAction. BOOPSI objects must solely be manipulated using [[BOOPSI_-_Object_Oriented_Intuition#Function_Reference\|BOOPSI functions]] (methods).

			* Many programmers seem to be confused about window programming. It's fairly easy:
⚫	* The original BOOPSI set built in Intuition is usable but somewhat limited. Some BOOPSI objects are actually wrappers for ReAction objects.
			** ReAction elements (objects) must reside in a ''ReAction window'', that is, a window created through the Window Class, which is part of the toolkit. Such a window is manipulated as any other BOOPSI object.
			** Intuition or GadTools elements must reside in an ''Intuition window'', that is, a window created through functions OpenWindow() or OpenWindowTags(), which are both part of the Intuition Library. Such windows are manipulated using dedicated functions.

	* Despite both being based on BOOPSI, MUI and ReAction classes are not interchangeable. You cannot extend the functionality of ReAction with MUI classes and vice versa.		* Despite both being based on BOOPSI, MUI and ReAction classes are not interchangeable. You cannot extend the functionality of ReAction with MUI classes and vice versa.