Widget Manager - Revision history

151.229.136.200 at 16:46, 20 March 2017

2017-03-20T16:46:42Z

151.229.136.200 at 16:45, 20 March 2017

2017-03-20T16:45:19Z

151.229.136.200 at 16:38, 20 March 2017

2017-03-20T16:38:07Z

Bablakeluke at 16:37, 18 March 2017

2017-03-18T16:37:10Z

Bablakeluke: Bablakeluke moved page Window Manager to Widget Manager: Renamed to 'widgets' instead of windows.

2017-03-18T16:35:32Z

Bablakeluke moved page Window Manager to Widget Manager: Renamed to 'widgets' instead of windows.

151.229.186.156 at 10:19, 14 January 2017

2017-01-14T10:19:11Z

151.229.186.156 at 10:07, 14 January 2017

2017-01-14T10:07:13Z

151.229.186.156 at 10:05, 14 January 2017

2017-01-14T10:05:25Z

151.229.186.156: Created page with "The window manager is a major subsystem in PowerUI. It creates self contained UI's, each called a window, which can be opened via a web API or via the ..."

2017-01-14T10:04:22Z

Created page with "The window manager is a major subsystem in PowerUI. It creates self contained UI's, each called a window, which can be opened via a web API or via the ..."

New page

The window manager is a major subsystem in PowerUI. It creates self contained UI's, each called a window, which can be opened via a [[Windows (Web API)|web API]] or via the [[Window Protocol|window:// protocol]].

== Scope ==

The window manager is used for more than just typical "window" - it's designed to be used to describe any kind of self contained widget or component of a UI. For example, the [[Dialogue|dialogue system]] uses it to display speech and every [[Context Menu|context menu]] is also a window.

== Templates ==

The visual appearance of a window is described by a [[Window Templates|window template]]. PowerUI has a few built in templates for different kinds of window.

← Older revision		Revision as of 16:46, 20 March 2017
Line 1:		Line 1:
−	The widget manager is ~~a major subsystem in PowerUI. It creates~~ self contained UI's, each called a widget, which can be opened via a [[Widgets (Web API)\|web API]] or via the [[Widget Protocol\|widget:// protocol]]. Example scenes like 'Windows', 'Fading the screen' and 'Pause menu' all make use of the widget manager.	+	The widget manager is used to create self contained UI's, each called a widget, which can be opened via a [[Widgets (Web API)\|web API]] or via the [[Widget Protocol\|widget:// protocol]]. Example scenes like 'Windows', 'Fading the screen' and 'Pause menu' all make use of the widget manager. Widgets can stack on top of each other and fire a range of events so you can easily know when they're ready to go.

	A widget has two parts:		A widget has two parts:

← Older revision		Revision as of 16:45, 20 March 2017
Line 1:		Line 1:
	The widget manager is a major subsystem in PowerUI. It creates self contained UI's, each called a widget, which can be opened via a [[Widgets (Web API)\|web API]] or via the [[Widget Protocol\|widget:// protocol]]. Example scenes like 'Windows', 'Fading the screen' and 'Pause menu' all make use of the widget manager.		The widget manager is a major subsystem in PowerUI. It creates self contained UI's, each called a widget, which can be opened via a [[Widgets (Web API)\|web API]] or via the [[Widget Protocol\|widget:// protocol]]. Example scenes like 'Windows', 'Fading the screen' and 'Pause menu' all make use of the widget manager.
		+
		+	A widget has two parts:
		+
		+	* A [[Widget Templates\|template]] which describes its appearance. These are designed to be highly reusable.
		+	* Optionally some content to display within it. For example, you might have a template for a window and inside that window you display e.g. stats, worn clothing, an inventory etc.

	== Parameters ==		== Parameters ==

← Older revision		Revision as of 16:38, 20 March 2017
Line 1:		Line 1:
−	The widget manager is a major subsystem in PowerUI. It creates self contained UI's, each called a widget, which can be opened via a [[Widgets (Web API)\|web API]] or via the [[Widget Protocol\|widget:// protocol]].	+	The widget manager is a major subsystem in PowerUI. It creates self contained UI's, each called a widget, which can be opened via a [[Widgets (Web API)\|web API]] or via the [[Widget Protocol\|widget:// protocol]]. Example scenes like 'Windows', 'Fading the screen' and 'Pause menu' all make use of the widget manager.

	== Parameters ==		== Parameters ==

@@ Line 1: / Line 1: @@
-The window manager is a major subsystem in PowerUI. It creates self contained UI's, each called a window, which can be opened via a [[Windows (Web API)|web API]] or via the [[Window Protocol|window:// protocol]].
+The widget manager is a major subsystem in PowerUI. It creates self contained UI's, each called a widget, which can be opened via a [[Widgets (Web API)|web API]] or via the [[Widget Protocol|widget:// protocol]].
 == Parameters ==
-You'll find that it's very often useful to pass some extra information to an opening window. For example, maybe you have a window which asks the player to type in a number of items between some given range. It can be done with both the [[Window Protocol|window:// protocol]] and the [[Windows (Web API)|web API]]; both have the same outcome. See their wiki pages for more information on how to do it in each specific case.
+You'll find that it's very often useful to pass some extra information to an opening widget. For example, maybe you have a widget which asks the player to type in a number of items between some given range. It can be done with both the [[Widget Protocol|widget:// protocol]] and the [[Widgets (Web API)|web API]]; both have the same outcome. See their wiki pages for more information on how to do it in each specific case.
 The parameters are made available to the template ''and'' to any scripts inside your content as JavaScript variables.
@@ Line 9: / Line 9: @@
 == Scope ==
-The window manager is used for more than just typical "window" - it's designed to be used to describe any kind of self contained widget or component of a UI. For example, the [[Dialogue|dialogue system]] uses it to display speech and every [[Context Menu|context menu]] is also a window. [[Screen Fading (Fade to black/ Whiteouts)|Screen fading]] is also a more abstract use of the window system.
+The widget manager is designed to be used to describe any kind of self contained widget or component of a UI. For example, the [[Dialogue|dialogue system]] uses it to display speech and every [[Context Menu|context menu]] is also a widget. [[Screen Fading (Fade to black/ Whiteouts)|Screen fading]] is also a more abstract use of the widget system.
 == Templates ==
-The visual appearance of a window is described by a [[Window Templates|window template]]. PowerUI has a few built in templates for different kinds of window. Ideally these templates can be shared or sold to maximize the value of the window manager.
+The visual appearance of a widget is described by a [[Widget Templates|widget template]]. PowerUI has a few built in templates for different kinds of widget. Ideally these templates can be shared or sold to maximize the value of the widget manager.

← Older revision		Revision as of 10:19, 14 January 2017
Line 1:		Line 1:
	The window manager is a major subsystem in PowerUI. It creates self contained UI's, each called a window, which can be opened via a [[Windows (Web API)\|web API]] or via the [[Window Protocol\|window:// protocol]].		The window manager is a major subsystem in PowerUI. It creates self contained UI's, each called a window, which can be opened via a [[Windows (Web API)\|web API]] or via the [[Window Protocol\|window:// protocol]].
		+
		+	== Parameters ==
		+
		+	You'll find that it's very often useful to pass some extra information to an opening window. For example, maybe you have a window which asks the player to type in a number of items between some given range. It can be done with both the [[Window Protocol\|window:// protocol]] and the [[Windows (Web API)\|web API]]; both have the same outcome. See their wiki pages for more information on how to do it in each specific case.
		+
		+	The parameters are made available to the template ''and'' to any scripts inside your content as JavaScript variables.

	== Scope ==		== Scope ==

← Older revision	Revision as of 16:35, 18 March 2017
(No difference)

← Older revision		Revision as of 10:05, 14 January 2017
Line 7:		Line 7:
	== Templates ==		== Templates ==

−	The visual appearance of a window is described by a [[Window Templates\|window template]]. PowerUI has a few built in templates for different kinds of window.	+	The visual appearance of a window is described by a [[Window Templates\|window template]]. PowerUI has a few built in templates for different kinds of window. Ideally these templates can be shared or sold to maximize the value of the window manager.