VLC HowTo/Integrate with Google Web Toolkit - Revision history

DoesItReallyMatter: Layout, markup

2019-06-09T08:04:27Z

Layout, markup

← Older revision		Revision as of 08:04, 9 June 2019
Line 1:		Line 1:
	{{howto\|integrate with Google Web Toolkit}}		{{howto\|integrate with Google Web Toolkit}}
	{{Example code}}		{{Example code}}
	~~== GWT ==~~		__FORCETOC__
	VLC can be integrated in Google Web Toolkit (GWT) web applications. The easiest way is to embed the VLC browser plugin in your web application. This also ensures that no question arises whether your web application is derivative work or not, as a clean separation between the web application and VLC exists. Alternatively, a build of VLC can be integrated in a web app, using applicable bindings. This article discusses integration based on the VLC plugin. There are two levels of integration:		VLC can be integrated in Google Web Toolkit (GWT) web applications. The easiest way is to embed the VLC browser plugin in your web application. This also ensures that no question arises whether your web application is derivative work or not, as a clean separation between the web application and VLC exists. Alternatively, a build of VLC can be integrated in a web app, using applicable bindings. This article discusses integration based on the VLC plugin. There are two levels of integration:
	* Static integration in the main HTML file (MyProject.html as generated by GWT/applicationCreator)		* Static integration in the main HTML file (MyProject.html as generated by GWT/applicationCreator)
Line 7:		Line 7:
	(In any case, remember that VLC treats the browser plugin for Firefox/Mozilla only as an installation option. You might have to go back and install this option and also point out in your documentation that this option needs to be installed if users run your web application with Mozilla/Firefox.)		(In any case, remember that VLC treats the browser plugin for Firefox/Mozilla only as an installation option. You might have to go back and install this option and also point out in your documentation that this option needs to be installed if users run your web application with Mozilla/Firefox.)

	=== Static integration in MyProject.html ===		== Static integration in MyProject.html ==
	Static integration is straightforward and based on methods described in two separate articles:		Static integration is straightforward and based on methods described in two separate articles:
	* Mozilla/Firefox plug-in: [[Documentation:Play HowTo/Advanced Use of VLC#Use the Mozilla plugin]]		* Mozilla/Firefox plug-in: [[Documentation:Play HowTo/Advanced Use of VLC#Use the Mozilla plugin]]
	* ActiveX Control: [[ActiveX/HTML]]		* ActiveX Control: [[ActiveX/HTML]]
	Following the description in the [[ActiveX/HTML]] article, you can include some code based on the following snippet in your main HTML file (MyProject.html):		Following the description in the [[ActiveX/HTML]] article, you can include some code based on the following snippet in your main HTML file (MyProject.html):
	~~<big><big>~~<syntaxhighlight lang="html4strict">		<syntaxhighlight lang="html4strict">
	<OBJECT classid="clsid:9BE31822-FDAD-461B-AD51-BE1D1C159921"		<OBJECT classid="clsid:9BE31822-FDAD-461B-AD51-BE1D1C159921"
	codebase="http://downloads.videolan.org/pub/videolan/vlc/latest/win32/axvlc.cab"		codebase="http://downloads.videolan.org/pub/videolan/vlc/latest/win32/axvlc.cab"
Line 32:		Line 32:
	</EMBED>		</EMBED>
	</OBJECT>		</OBJECT>
	</syntaxhighlight~~></big></big~~>		</syntaxhighlight>
	Internet Explorer (IE6) responds to the code in the <OBJECT> tag, while Mozilla/Firefox uses the settings inside the <EMBED> tag.		Internet Explorer (IE6) responds to the code in the {{Tag\|OBJECT}} tag, while Mozilla/Firefox uses the settings inside the {{Tag\|EMBED}} tag.
	Replace parameters as appropriate, e.g. $mri with the [[Media resource locator\|Multimedia Resource Identifier]] of your incoming stream.		Replace parameters as appropriate, e.g. $mri with the [[Media resource locator\|Multimedia Resource Identifier]] of your incoming stream.

	=== Embedding in dynamically generated HTML code ===		== Embedding in dynamically generated HTML code ==
	It is possible to integrate the VLC plugin in dynamically generated HTML code, based on the GWT classes HTML, HTMLPanel and HTMLTable.		It is possible to integrate the VLC plugin in dynamically generated HTML code, based on the GWT classes HTML, HTMLPanel and HTMLTable.

	The integration of the VLC plugin in dynamically generated HTML code is based on DOM calls and some JavaScript as opposed to GWT API calls. For some reason(s), the GWT API calls do not support the integration of the VLC plugin, although other plugin's might work just fine. Panel.add() for example is a key method which does not hook the plugin into the DOM as expected by the VLC plugin. This is not necessarily a fault of the VLC plugin, but rather browser-specific differences in Javascript implementation, and how GWT works. Below a snippet which should contain all the necessary DOM calls and JavaScript code which worked for me for Mozilla/Firefox ''and'' IE6:		The integration of the VLC plugin in dynamically generated HTML code is based on DOM calls and some JavaScript as opposed to GWT API calls. For some reason(s), the GWT API calls do not support the integration of the VLC plugin, although other plugin's might work just fine. <code>Panel.add()</code> for example is a key method which does not hook the plugin into the DOM as expected by the VLC plugin. This is not necessarily a fault of the VLC plugin, but rather browser-specific differences in Javascript implementation, and how GWT works. Below a snippet which should contain all the necessary DOM calls and JavaScript code which worked for me for Mozilla/Firefox ''and'' IE6:
	~~<big><big>~~<syntaxhighlight lang="javascript">		<syntaxhighlight lang="javascript">
	{		{
	{		{
Line 82:		Line 82:

	}		}
	</syntaxhighlight~~></big></big~~>		</syntaxhighlight>

	It does not make a difference whether the VLC lugin is integrated on the static or dynamic level; a handle to the VLC plugin is obtained through the RootPanel method RootPanel get(java.lang.String id) which returns the browser element that embeds the VLC plugin. Code must be added to the HTML code to create a browser element with an ID which can be captured by the RootPanel mathod get(java.lang.String id), e.g. as follows:		It does not make a difference whether the VLC lugin is integrated on the static or dynamic level; a handle to the VLC plugin is obtained through the RootPanel method RootPanel get(java.lang.String id) which returns the browser element that embeds the VLC plugin. Code must be added to the HTML code to create a browser element with an ID which can be captured by the RootPanel mathod get(java.lang.String id), e.g. as follows:
	~~<big><big>~~<syntaxhighlight lang="html5">		<syntaxhighlight lang="html5">
	<table><tr><td id="browserElementInHTMLCode">		<table><tr><td id="browserElementInHTMLCode">

	</td></tr></table>		</td></tr></table>
	</syntaxhighlight~~></big></big~~>		</syntaxhighlight>

	=== User interaction ===		== User interaction ==
	The VLC plugin has a Javascript API which allows the implementation of user interactions like Play or Pause on the web application level. The plug-in can be called through Javascript as described in the [[ActiveX/HTML]] article. GWT/Java wrappers for these calls are not available (yet). Below a couple of examples.		The VLC plugin has a Javascript API which allows the implementation of user interactions like Play or Pause on the web application level. The plug-in can be called through Javascript as described in the [[ActiveX/HTML]] article. GWT/Java wrappers for these calls are not available (yet). Below a couple of examples.
	~~<big><big>~~<syntaxhighlight lang="javascript">		<syntaxhighlight lang="javascript">
	/**		/**
	* stop VLC plugin		* stop VLC plugin
Line 107:		Line 107:
	$doc[targetId].playlist.play();		$doc[targetId].playlist.play();
	}-*/;		}-*/;
	</syntaxhighlight~~></big></big~~>		</syntaxhighlight>

DoesItReallyMatter: Show Template:Howto, +{{Example code}}

2019-06-09T07:59:29Z

Show Template:Howto, +{{Example code}}

← Older revision		Revision as of 07:59, 9 June 2019
Line 1:		Line 1:
	{{howto\|~~silent=yes~~}}		{{howto\|integrate with Google Web Toolkit}}
			{{Example code}}
	== GWT ==		== GWT ==
	VLC can be integrated in Google Web Toolkit (GWT) web applications. The easiest way is to embed the VLC browser plugin in your web application. This also ensures that no question arises whether your web application is derivative work or not, as a clean separation between the web application and VLC exists. Alternatively, a build of VLC can be integrated in a web app, using applicable bindings. This article discusses integration based on the VLC plugin. There are two levels of integration:		VLC can be integrated in Google Web Toolkit (GWT) web applications. The easiest way is to embed the VLC browser plugin in your web application. This also ensures that no question arises whether your web application is derivative work or not, as a clean separation between the web application and VLC exists. Alternatively, a build of VLC can be integrated in a web app, using applicable bindings. This article discusses integration based on the VLC plugin. There are two levels of integration:

DoesItReallyMatter: syntaxhighlight

2019-01-29T08:09:55Z

syntaxhighlight

← Older revision		Revision as of 08:09, 29 January 2019
Line 11:		Line 11:
	* ActiveX Control: [[ActiveX/HTML]]		* ActiveX Control: [[ActiveX/HTML]]
	Following the description in the [[ActiveX/HTML]] article, you can include some code based on the following snippet in your main HTML file (MyProject.html):		Following the description in the [[ActiveX/HTML]] article, you can include some code based on the following snippet in your main HTML file (MyProject.html):
	<~~pre~~><~~nowiki~~>		<big><big><syntaxhighlight lang="html4strict">
	<OBJECT classid="clsid:9BE31822-FDAD-461B-AD51-BE1D1C159921"		<OBJECT classid="clsid:9BE31822-FDAD-461B-AD51-BE1D1C159921"
	codebase="http://downloads.videolan.org/pub/videolan/vlc/latest/win32/axvlc.cab"		codebase="http://downloads.videolan.org/pub/videolan/vlc/latest/win32/axvlc.cab"
Line 31:		Line 31:
	</EMBED>		</EMBED>
	</OBJECT>		</OBJECT>
	</~~nowiki~~></~~pre~~>		</syntaxhighlight></big></big>
	Internet Explorer (IE6) responds to the code in the <OBJECT> tag, while Mozilla/Firefox uses the settings inside the <EMBED> tag.		Internet Explorer (IE6) responds to the code in the <OBJECT> tag, while Mozilla/Firefox uses the settings inside the <EMBED> tag.
	Replace parameters as appropriate, e.g. $mri with the [[Media resource locator\|Multimedia Resource Identifier]] of your incoming stream.		Replace parameters as appropriate, e.g. $mri with the [[Media resource locator\|Multimedia Resource Identifier]] of your incoming stream.
Line 39:		Line 39:

	The integration of the VLC plugin in dynamically generated HTML code is based on DOM calls and some JavaScript as opposed to GWT API calls. For some reason(s), the GWT API calls do not support the integration of the VLC plugin, although other plugin's might work just fine. Panel.add() for example is a key method which does not hook the plugin into the DOM as expected by the VLC plugin. This is not necessarily a fault of the VLC plugin, but rather browser-specific differences in Javascript implementation, and how GWT works. Below a snippet which should contain all the necessary DOM calls and JavaScript code which worked for me for Mozilla/Firefox ''and'' IE6:		The integration of the VLC plugin in dynamically generated HTML code is based on DOM calls and some JavaScript as opposed to GWT API calls. For some reason(s), the GWT API calls do not support the integration of the VLC plugin, although other plugin's might work just fine. Panel.add() for example is a key method which does not hook the plugin into the DOM as expected by the VLC plugin. This is not necessarily a fault of the VLC plugin, but rather browser-specific differences in Javascript implementation, and how GWT works. Below a snippet which should contain all the necessary DOM calls and JavaScript code which worked for me for Mozilla/Firefox ''and'' IE6:
	<~~pre~~><~~nowiki~~>		<big><big><syntaxhighlight lang="javascript">
	{		{
	{		{
Line 81:		Line 81:

	}		}
	</~~nowiki~~></~~pre~~>		</syntaxhighlight></big></big>

	It does not make a difference whether the VLC lugin is integrated on the static or dynamic level; a handle to the VLC plugin is obtained through the RootPanel method RootPanel get(java.lang.String id) which returns the browser element that embeds the VLC plugin. Code must be added to the HTML code to create a browser element with an ID which can be captured by the RootPanel mathod get(java.lang.String id), e.g. as follows:		It does not make a difference whether the VLC lugin is integrated on the static or dynamic level; a handle to the VLC plugin is obtained through the RootPanel method RootPanel get(java.lang.String id) which returns the browser element that embeds the VLC plugin. Code must be added to the HTML code to create a browser element with an ID which can be captured by the RootPanel mathod get(java.lang.String id), e.g. as follows:
	<~~pre~~><~~nowiki~~>		<big><big><syntaxhighlight lang="html5">
	<table><tr><td id="browserElementInHTMLCode">		<table><tr><td id="browserElementInHTMLCode">

	</td></tr></table>		</td></tr></table>
	</~~nowiki~~></~~pre~~>		</syntaxhighlight></big></big>

	=== User interaction ===		=== User interaction ===
	The VLC plugin has a Javascript API which allows the implementation of user interactions like Play or Pause on the web application level. The plug-in can be called through Javascript as described in the [[ActiveX/HTML]] article. GWT/Java wrappers for these calls are not available (yet). Below a couple of examples.		The VLC plugin has a Javascript API which allows the implementation of user interactions like Play or Pause on the web application level. The plug-in can be called through Javascript as described in the [[ActiveX/HTML]] article. GWT/Java wrappers for these calls are not available (yet). Below a couple of examples.
	<~~pre~~><~~nowiki~~>		<big><big><syntaxhighlight lang="javascript">
	/**		/**
	* stop VLC plugin		* stop VLC plugin
Line 106:		Line 106:
	$doc[targetId].playlist.play();		$doc[targetId].playlist.play();
	}-*/;		}-*/;
	</~~nowiki~~></~~pre~~>		</syntaxhighlight></big></big>

DoesItReallyMatter: /* Static integration in MyProject.html */ Fix broken wikilink

2019-01-28T08:02:04Z

Static integration in MyProject.html: Fix broken wikilink

← Older revision		Revision as of 08:02, 28 January 2019
Line 33:		Line 33:
	</nowiki></pre>		</nowiki></pre>
	Internet Explorer (IE6) responds to the code in the <OBJECT> tag, while Mozilla/Firefox uses the settings inside the <EMBED> tag.		Internet Explorer (IE6) responds to the code in the <OBJECT> tag, while Mozilla/Firefox uses the settings inside the <EMBED> tag.
	Replace parameters as appropriate, e.g. $mri with the [[Multimedia Resource Identifier]] of your incoming stream.		Replace parameters as appropriate, e.g. $mri with the [[Media resource locator\|Multimedia Resource Identifier]] of your incoming stream.

	=== Embedding in dynamically generated HTML code ===		=== Embedding in dynamically generated HTML code ===

DoesItReallyMatter: /* Static integration in MyProject.html */ Rewrite url as an internal link, fix target

2019-01-20T07:58:17Z

Static integration in MyProject.html: Rewrite url as an internal link, fix target

← Older revision		Revision as of 07:58, 20 January 2019
Line 8:		Line 8:
	=== Static integration in MyProject.html ===		=== Static integration in MyProject.html ===
	Static integration is straightforward and based on methods described in two separate articles:		Static integration is straightforward and based on methods described in two separate articles:
	* Mozilla/Firefox plug-in: ~~http://wiki.videolan.org/~~Documentation:~~Play_HowTo~~/~~Advanced_Use_of_VLC~~#~~Use_the_mozilla_plugin~~		* Mozilla/Firefox plug-in: [[Documentation:Play HowTo/Advanced Use of VLC#Use the Mozilla plugin]]
	* ActiveX Control: [[ActiveX/HTML]]		* ActiveX Control: [[ActiveX/HTML]]
	Following the description in the [[ActiveX/HTML]] article, you can include some code based on the following snippet in your main HTML file (MyProject.html):		Following the description in the [[ActiveX/HTML]] article, you can include some code based on the following snippet in your main HTML file (MyProject.html):

DoesItReallyMatter: Parameter update for template:howto

2016-11-17T12:41:01Z

Parameter update for template:howto

← Older revision		Revision as of 12:41, 17 November 2016
Line 1:		Line 1:
	{{howto}}		{{howto\|silent=yes}}
	== GWT ==		== GWT ==
	VLC can be integrated in Google Web Toolkit (GWT) web applications. The easiest way is to embed the VLC browser plugin in your web application. This also ensures that no question arises whether your web application is derivative work or not, as a clean separation between the web application and VLC exists. Alternatively, a build of VLC can be integrated in a web app, using applicable bindings. This article discusses integration based on the VLC plugin. There are two levels of integration:		VLC can be integrated in Google Web Toolkit (GWT) web applications. The easiest way is to embed the VLC browser plugin in your web application. This also ensures that no question arises whether your web application is derivative work or not, as a clean separation between the web application and VLC exists. Alternatively, a build of VLC can be integrated in a web app, using applicable bindings. This article discusses integration based on the VLC plugin. There are two levels of integration:

DoesItReallyMatter: remove sortkey, demote headings, silence {{howto}}

2016-11-17T11:50:32Z

remove sortkey, demote headings, silence {{howto}}

← Older revision		Revision as of 11:50, 17 November 2016
Line 1:		Line 1:
	{{howto~~\|Integrate VLC with Google Web Toolkit (GWT)~~}}		{{howto}}
			== GWT ==
	= GWT =
	VLC can be integrated in Google Web Toolkit (GWT) web applications. The easiest way is to embed the VLC browser plugin in your web application. This also ensures that no question arises whether your web application is derivative work or not, as a clean separation between the web application and VLC exists. Alternatively, a build of VLC can be integrated in a web app, using applicable bindings. This article discusses integration based on the VLC plugin. There are two levels of integration:		VLC can be integrated in Google Web Toolkit (GWT) web applications. The easiest way is to embed the VLC browser plugin in your web application. This also ensures that no question arises whether your web application is derivative work or not, as a clean separation between the web application and VLC exists. Alternatively, a build of VLC can be integrated in a web app, using applicable bindings. This article discusses integration based on the VLC plugin. There are two levels of integration:
	* Static integration in the main HTML file (MyProject.html as generated by GWT/applicationCreator)		* Static integration in the main HTML file (MyProject.html as generated by GWT/applicationCreator)
Line 7:		Line 6:
	(In any case, remember that VLC treats the browser plugin for Firefox/Mozilla only as an installation option. You might have to go back and install this option and also point out in your documentation that this option needs to be installed if users run your web application with Mozilla/Firefox.)		(In any case, remember that VLC treats the browser plugin for Firefox/Mozilla only as an installation option. You might have to go back and install this option and also point out in your documentation that this option needs to be installed if users run your web application with Mozilla/Firefox.)

	== Static integration in MyProject.html ==		=== Static integration in MyProject.html ===
	Static integration is straightforward and based on methods described in two separate articles:		Static integration is straightforward and based on methods described in two separate articles:
	* Mozilla/Firefox plug-in: http://wiki.videolan.org/Documentation:Play_HowTo/Advanced_Use_of_VLC#Use_the_mozilla_plugin		* Mozilla/Firefox plug-in: http://wiki.videolan.org/Documentation:Play_HowTo/Advanced_Use_of_VLC#Use_the_mozilla_plugin
Line 36:		Line 35:
	Replace parameters as appropriate, e.g. $mri with the [[Multimedia Resource Identifier]] of your incoming stream.		Replace parameters as appropriate, e.g. $mri with the [[Multimedia Resource Identifier]] of your incoming stream.

	== Embedding in dynamically generated HTML code ==		=== Embedding in dynamically generated HTML code ===
	It is possible to integrate the VLC plugin in dynamically generated HTML code, based on the GWT classes HTML, HTMLPanel and HTMLTable.		It is possible to integrate the VLC plugin in dynamically generated HTML code, based on the GWT classes HTML, HTMLPanel and HTMLTable.

Line 91:		Line 90:
	</nowiki></pre>		</nowiki></pre>

	== User interaction ==		=== User interaction ===
	The VLC plugin has a Javascript API which allows the implementation of user interactions like Play or Pause on the web application level. The plug-in can be called through Javascript as described in the [[ActiveX/HTML]] article. GWT/Java wrappers for these calls are not available (yet). Below a couple of examples.		The VLC plugin has a Javascript API which allows the implementation of user interactions like Play or Pause on the web application level. The plug-in can be called through Javascript as described in the [[ActiveX/HTML]] article. GWT/Java wrappers for these calls are not available (yet). Below a couple of examples.
	<pre><nowiki>		<pre><nowiki>
Line 108:		Line 107:
	}-*/;		}-*/;
	</nowiki></pre>		</nowiki></pre>

	~~{{DEFAULTSORT:Google}}~~

DoesItReallyMatter: Sortkey: Google

2016-10-30T05:36:43Z

Sortkey: Google

← Older revision		Revision as of 05:36, 30 October 2016
Line 108:		Line 108:
	}-*/;		}-*/;
	</nowiki></pre>		</nowiki></pre>

			{{DEFAULTSORT:Google}}

DoesItReallyMatter: DoesItReallyMatter moved page GWT to VLC HowTo/Integrate with Google Web Toolkit: Renaming how-to articles per Talk:VLC HowTo (permalink)

2016-10-30T05:35:58Z

DoesItReallyMatter moved page GWT to VLC HowTo/Integrate with Google Web Toolkit: Renaming how-to articles per Talk:VLC HowTo (permalink)

← Older revision	Revision as of 05:35, 30 October 2016
(No difference)

Aphswarrior at 19:54, 24 March 2008

2008-03-24T19:54:16Z

← Older revision		Revision as of 19:54, 24 March 2008
Line 10:		Line 10:
	Static integration is straightforward and based on methods described in two separate articles:		Static integration is straightforward and based on methods described in two separate articles:
	* Mozilla/Firefox plug-in: http://wiki.videolan.org/Documentation:Play_HowTo/Advanced_Use_of_VLC#Use_the_mozilla_plugin		* Mozilla/Firefox plug-in: http://wiki.videolan.org/Documentation:Play_HowTo/Advanced_Use_of_VLC#Use_the_mozilla_plugin
	* ~~ActiceX~~ Control: [[ActiveX/HTML]]		* ActiveX Control: [[ActiveX/HTML]]
	Following the description in the [[ActiveX/HTML]] article, you can include some code based on the following snippet in your main HTML file (MyProject.html):		Following the description in the [[ActiveX/HTML]] article, you can include some code based on the following snippet in your main HTML file (MyProject.html):
	<pre><nowiki>		<pre><nowiki>