Prism/Bundle - Revision history

Nicerobot: /* Structure */

2011-03-12T16:19:09Z

Structure

← Older revision		Revision as of 16:19, 12 March 2011
Line 30:		Line 30:

	==Structure==		==Structure==

	A bundle can contain the following files. Any other files in the .webapp file will be ignored. After the .webapp file is executed the first time, these files will be unzipped and "cached" to a local directory structure.		A bundle can contain the following files. Any other files in the .webapp file will be ignored. After the .webapp file is executed the first time, these files will be unzipped and "cached" to a local directory structure.

Teegijee: /* WebApp Bundle */ No reason for an internal link to use external syntax.

2008-10-20T16:03:04Z

WebApp Bundle: No reason for an internal link to use external syntax.

← Older revision		Revision as of 16:03, 20 October 2008
Line 1:		Line 1:
	==WebApp Bundle==		==WebApp Bundle==
	In addition to passing simple command line parameters, [~~http://wiki.mozilla.org/Prism~~ Prism] can use a zipped bundle package to install a webapp. The bundle can hold additional resources currently limited to:		In addition to passing simple command line parameters, [[Prism]] can use a zipped bundle package to install a webapp. The bundle can hold additional resources currently limited to:
	* Application INI settings		* Application INI settings
	* Application icon		* Application icon

Greylurk at 14:35, 2 January 2008

2008-01-02T14:35:10Z

← Older revision		Revision as of 14:35, 2 January 2008
Line 28:		Line 28:
	* Zip the file to [whatever].webapp		* Zip the file to [whatever].webapp
	* Double-click the webapp bundle or use <code>prism -webapp [path-to-webapp]		* Double-click the webapp bundle or use <code>prism -webapp [path-to-webapp]

			==Structure==
			A bundle can contain the following files. Any other files in the .webapp file will be ignored. After the .webapp file is executed the first time, these files will be unzipped and "cached" to a local directory structure.

			; /
			: webapp.ini
			: webapp.js
			: webapp.css
			:; winnt
			:: webapp.css
			:; darwin
			:: webapp.css
			:; linux
			:: webapp.css
			: [icon].ico
			: [icon].xpm
			: [icon].icns

MarkFinkle at 20:10, 30 October 2007

2007-10-30T20:10:54Z

← Older revision		Revision as of 20:10, 30 October 2007
Line 1:		Line 1:
	==WebApp Bundle==		==WebApp Bundle==
	In addition to passing simple command line parameters, [http://wiki.mozilla.org/~~WebRunner WebRunner~~] can use a zipped bundle package to install a webapp. The bundle can hold additional resources currently limited to:		In addition to passing simple command line parameters, [http://wiki.mozilla.org/Prism Prism] can use a zipped bundle package to install a webapp. The bundle can hold additional resources currently limited to:
	* Application INI settings		* Application INI settings
	* Application icon		* Application icon
Line 6:		Line 6:

	==Installing a Bundle==		==Installing a Bundle==
	When ~~WebRunner~~ opens a webapp bundle it will unpack it into the '''webapps/{webapp-id}''' folder in your ~~WebRunner~~ profile. The web application may save other data into this folder. ~~WebRunner~~ will not overwrite or delete any extra data added to the folder. In fact, ~~WebRunner~~ saves some extra data itself - a file that holds some persistent UI data called ''localstore.json''.		When Prism opens a webapp bundle it will unpack it into the '''webapps/{webapp-id}''' folder in your Prism profile. The web application may save other data into this folder. Prism will not overwrite or delete any extra data added to the folder. In fact, Prism saves some extra data itself - a file that holds some persistent UI data called ''localstore.json''.

	<div class="note">The webapp must have an ID in order to be installed.</div>		<div class="note">The webapp must have an ID in order to be installed.</div>

	When ~~WebRunner~~ is launched with a "-webapp [bundle]" command line, the bundle must first be unpacked before the web application is launched. This can slow the overall launch time and the unpacking is redundant if the bundle has been launched previously. This is why the preferred method of launching is to use the "-webapp [webapp-id]" command line, which looks for the previously installed (unpacked) web application in the ~~WebRunner~~ '''webapps/{webapp-id}''' folder. The web application is then launched without the unpacking overhead.		When Prism is launched with a "-webapp [bundle]" command line, the bundle must first be unpacked before the web application is launched. This can slow the overall launch time and the unpacking is redundant if the bundle has been launched previously. This is why the preferred method of launching is to use the "-webapp [webapp-id]" command line, which looks for the previously installed (unpacked) web application in the Prism '''webapps/{webapp-id}''' folder. The web application is then launched without the unpacking overhead.

	==HowTo==		==HowTo==
Line 27:		Line 27:
	</pre>		</pre>
	* Zip the file to [whatever].webapp		* Zip the file to [whatever].webapp
	* Double-click the webapp bundle or use <code>~~webrunner~~ -webapp [path-to-webapp]		* Double-click the webapp bundle or use <code>prism -webapp [path-to-webapp]

MarkFinkle: WebRunner:Bundle moved to Prism/Bundle

2007-10-30T20:05:57Z

WebRunner:Bundle moved to Prism/Bundle

← Older revision	Revision as of 20:05, 30 October 2007
(No difference)

Realgt: added link to webrunner wiki page

2007-10-19T17:14:31Z

added link to webrunner wiki page

← Older revision		Revision as of 17:14, 19 October 2007
Line 1:		Line 1:
	==WebApp Bundle==		==WebApp Bundle==
	In addition to passing simple command line parameters, WebRunner can use a zipped bundle package to install a webapp. The bundle can hold additional resources currently limited to:		In addition to passing simple command line parameters, [http://wiki.mozilla.org/WebRunner WebRunner] can use a zipped bundle package to install a webapp. The bundle can hold additional resources currently limited to:
	* Application INI settings		* Application INI settings
	* Application icon		* Application icon

MarkFinkle at 20:59, 27 September 2007

2007-09-27T20:59:40Z

← Older revision		Revision as of 20:59, 27 September 2007
Line 11:		Line 11:

	When WebRunner is launched with a "-webapp [bundle]" command line, the bundle must first be unpacked before the web application is launched. This can slow the overall launch time and the unpacking is redundant if the bundle has been launched previously. This is why the preferred method of launching is to use the "-webapp [webapp-id]" command line, which looks for the previously installed (unpacked) web application in the WebRunner '''webapps/{webapp-id}''' folder. The web application is then launched without the unpacking overhead.		When WebRunner is launched with a "-webapp [bundle]" command line, the bundle must first be unpacked before the web application is launched. This can slow the overall launch time and the unpacking is redundant if the bundle has been launched previously. This is why the preferred method of launching is to use the "-webapp [webapp-id]" command line, which looks for the previously installed (unpacked) web application in the WebRunner '''webapps/{webapp-id}''' folder. The web application is then launched without the unpacking overhead.

			==HowTo==

			Here is a simple way to build a basic web application bundle:

			* Create file called webapp.ini that contains something like:
			<pre>
			[Parameters]
			id=unique-app-id@unique-author-id.whatever
			uri=http://[the-url-what-you-want-to-connect-to]/
			status=yes
			location=no
			sidebar=no
			navigation=no
			</pre>
			* Zip the file to [whatever].webapp
			* Double-click the webapp bundle or use <code>webrunner -webapp [path-to-webapp]

MarkFinkle at 15:12, 7 September 2007

2007-09-07T15:12:13Z

← Older revision		Revision as of 15:12, 7 September 2007
Line 10:		Line 10:
	<div class="note">The webapp must have an ID in order to be installed.</div>		<div class="note">The webapp must have an ID in order to be installed.</div>

	When WebRunner is launched with a "-webapp [bundle]" command line, the bundle must first be unpacked before the web application is launched. This can slow the overall launch time and the unpacking is redundant if the bundle has been launched previously. This is why the preferred method of launching is to use the "-webapp [webapp-id]" which looks for the previously installed (unpacked) web application in the WebRunner '''webapps/{webapp-id}''' folder. The web application is then launched without the unpacking overhead.		When WebRunner is launched with a "-webapp [bundle]" command line, the bundle must first be unpacked before the web application is launched. This can slow the overall launch time and the unpacking is redundant if the bundle has been launched previously. This is why the preferred method of launching is to use the "-webapp [webapp-id]" command line, which looks for the previously installed (unpacked) web application in the WebRunner '''webapps/{webapp-id}''' folder. The web application is then launched without the unpacking overhead.

MarkFinkle at 03:47, 6 September 2007

2007-09-06T03:47:22Z

← Older revision		Revision as of 03:47, 6 September 2007
Line 6:		Line 6:

	==Installing a Bundle==		==Installing a Bundle==
	When WebRunner opens a webapp bundle it will unpack it into the '''webapps/{webapp-id}''' folder in your WebRunner profile. The ~~webapp~~ may save other data into this folder. WebRunner will not overwrite or delete any extra data added to the folder. In fact, WebRunner saves some extra data itself - a file that holds some persistent UI data called ''localstore.json''.		When WebRunner opens a webapp bundle it will unpack it into the '''webapps/{webapp-id}''' folder in your WebRunner profile. The web application may save other data into this folder. WebRunner will not overwrite or delete any extra data added to the folder. In fact, WebRunner saves some extra data itself - a file that holds some persistent UI data called ''localstore.json''.

	<div class="note">The webapp must have an ID in order to be installed.</div>		<div class="note">The webapp must have an ID in order to be installed.</div>

			When WebRunner is launched with a "-webapp [bundle]" command line, the bundle must first be unpacked before the web application is launched. This can slow the overall launch time and the unpacking is redundant if the bundle has been launched previously. This is why the preferred method of launching is to use the "-webapp [webapp-id]" which looks for the previously installed (unpacked) web application in the WebRunner '''webapps/{webapp-id}''' folder. The web application is then launched without the unpacking overhead.

MarkFinkle: initial (incomplete) save

2007-09-04T21:26:34Z

initial (incomplete) save

New page

==WebApp Bundle==
In addition to passing simple command line parameters, WebRunner can use a zipped bundle package to install a webapp. The bundle can hold additional resources currently limited to:
* Application INI settings
* Application icon
* Script for the application chrome, not the web content

==Installing a Bundle==
When WebRunner opens a webapp bundle it will unpack it into the '''webapps/{webapp-id}''' folder in your WebRunner profile. The webapp may save other data into this folder. WebRunner will not overwrite or delete any extra data added to the folder. In fact, WebRunner saves some extra data itself - a file that holds some persistent UI data called ''localstore.json''.

<div class="note">The webapp must have an ID in order to be installed.</div>