AppSuite:Extending the UI (Hands-on introduction) - Revision history

Khgras: Replaced content with "The content on this page has moved to https://documentation.open-xchange.com/latest/ui/extension-points/01-introduction.html Note: Open-Xchange is in the process of migra..."

2017-05-22T09:41:56Z

Replaced content with "The content on this page has moved to https://documentation.open-xchange.com/latest/ui/extension-points/01-introduction.html Note: Open-Xchange is in the process of migra..."

Show changes

Frank.paczynski at 11:54, 10 February 2016

2016-02-10T11:54:43Z

← Older revision		Revision as of 11:54, 10 February 2016
Line 1:		Line 1:
			<!-- !!! -->
			<!-- PLEASE APPLY CHANGES ONLY TO THE NEW TECHNICAL DOCUMENTATION: wd/frontend/web/documentation -->
			<!-- !!! -->

	{{Stability-experimental}}		{{Stability-experimental}}

Mark.schmidts: /* Trouble finding the right extension point? */

2013-10-22T12:26:22Z

Trouble finding the right extension point?

← Older revision		Revision as of 12:26, 22 October 2013
Line 188:		Line 188:
	[[Category:Extension points]]		[[Category:Extension points]]

	=== Trouble finding the right extension point? ===		== Trouble finding the right extension point? ==

	You don't know where to append your plugin's content / which extension point you should use?		You don't know where to append your plugin's content / which extension point you should use?
	A good way to find the suitable extension point, is to search in the OX Source Code for an HTML-element displayed in the user interface. For example an easy to identify text. Once found the HTML-element in the source, you can see which extension point was used appending this element to the UI and append your content there aswell.		A good way to find the suitable extension point, is to search in the OX Source Code for an HTML-element displayed in the user interface. For example an easy to identify text. Once found the HTML-element in the source, you can see which extension point was used appending this element to the UI and append your content there aswell.

Mark.schmidts at 12:13, 22 October 2013

2013-10-22T12:13:56Z

← Older revision		Revision as of 12:13, 22 October 2013
Line 191:		Line 191:

	You don't know where to append your plugin's content / which extension point you should use?		You don't know where to append your plugin's content / which extension point you should use?
	A good way to find the suitable extension point, is to search in the OX Source Code for an HTML-element displayed in the user interface. For example an easy to identify text. Once found the HTML-element in the source, you can see which extension point was used appending this element to the UI		A good way to find the suitable extension point, is to search in the OX Source Code for an HTML-element displayed in the user interface. For example an easy to identify text. Once found the HTML-element in the source, you can see which extension point was used appending this element to the UI and append your content there aswell.

Mark.schmidts at 12:12, 22 October 2013

2013-10-22T12:12:43Z

← Older revision		Revision as of 12:12, 22 October 2013
Line 187:		Line 187:
	[[Category:UI]]		[[Category:UI]]
	[[Category:Extension points]]		[[Category:Extension points]]

			=== Trouble finding the right extension point? ===

			You don't know where to append your plugin's content / which extension point you should use?
			A good way to find the suitable extension point, is to search in the OX Source Code for an HTML-element displayed in the user interface. For example an easy to identify text. Once found the HTML-element in the source, you can see which extension point was used appending this element to the UI

Frank.paczynski: removed debuggers from code examples

2013-09-06T09:14:40Z

removed debuggers from code examples

← Older revision		Revision as of 09:14, 6 September 2013
Line 141:		Line 141:
	<pre class="language-javascript">		<pre class="language-javascript">
	require(["io.ox/core/extensions", "io.ox/mail/util", "io.ox/core/date"], function (ext, util, date) {		require(["io.ox/core/extensions", "io.ox/mail/util", "io.ox/core/date"], function (ext, util, date) {
	~~debugger;~~
	ext.point("io.ox/mail/detail/header").replace({		ext.point("io.ox/mail/detail/header").replace({
	//current extension will extended not fully replaced		//current extension will extended not fully replaced
Line 171:		Line 170:
	// From the extension point 'io.ox/mail/detail' get the extension with		// From the extension point 'io.ox/mail/detail' get the extension with
	// the id 'subject' (which is passed to the callback)		// the id 'subject' (which is passed to the callback)
	~~debugger;~~
	ext.point("io.ox/mail/detail/header").get("subject", function (extension) {		ext.point("io.ox/mail/detail/header").get("subject", function (extension) {
	// Put it last		// Put it last

Tierlieb: /* change order */

2013-05-08T10:03:07Z

change order

← Older revision		Revision as of 10:03, 8 May 2013
Line 188:		Line 188:
	[[Category:AppSuite]]		[[Category:AppSuite]]
	[[Category:UI]]		[[Category:UI]]
			[[Category:Extension points]]

Tierlieb at 14:30, 25 April 2013

2013-04-25T14:30:51Z

← Older revision		Revision as of 14:30, 25 April 2013
Line 1:		Line 1:
			{{Stability-experimental}}

	<div class="title">Extension points:<br>Hands-on introduction</div>		<div class="title">Extension points:<br>Hands-on introduction</div>
	~~{{Status-Draft}}~~

	'''Abstract'''		'''Abstract'''

Tierlieb at 14:16, 22 April 2013

2013-04-22T14:16:27Z

← Older revision		Revision as of 14:16, 22 April 2013
Line 1:		Line 1:
			<div class="title">Extension points:<br>Hands-on introduction</div>
	{{Status-Draft}}		{{Status-Draft}}
	~~<div class="title">Extension points:<br>Hands-on introduction</div>~~

	'''Abstract'''		'''Abstract'''

Tierlieb: added draft warning...

2013-04-22T14:14:15Z

added draft warning...

← Older revision		Revision as of 14:14, 22 April 2013
Line 1:		Line 1:
			{{Status-Draft}}
	<div class="title">Extension points:<br>Hands-on introduction</div>		<div class="title">Extension points:<br>Hands-on introduction</div>