AppSuite:UI build system - Revision history

Viktor.Pracht: Undo revision 22287 by Khgras (talk)

2016-08-10T09:00:18Z

Undo revision 22287 by Khgras (talk)

← Older revision		Revision as of 09:00, 10 August 2016
Line 116:		Line 116:
	Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.		Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.

	==== debug ~~build~~ ====		==== debug ====
	Enables a debug build.		Enables a debug build.

Khgras: /* debug */

2016-08-10T08:56:36Z

debug

← Older revision		Revision as of 08:56, 10 August 2016
Line 116:		Line 116:
	Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.		Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.

	==== debug ====		==== debug build ====
	Enables a debug build.		Enables a debug build.

Khgras: /* d */

2016-08-10T08:56:20Z

← Older revision		Revision as of 08:56, 10 August 2016
Line 116:		Line 116:
	Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.		Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.

	==== d ====		==== debug ====
	Enables a debug build.		Enables a debug build.

Khgras: /* debug */

2016-08-10T08:56:13Z

debug

← Older revision		Revision as of 08:56, 10 August 2016
Line 116:		Line 116:
	Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.		Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.

	==== ~~debug~~ ====		==== d ====
	Enables a debug build.		Enables a debug build.

Sonja.krause-harder at 13:24, 2 October 2014

2014-10-02T13:24:34Z

← Older revision		Revision as of 13:24, 2 October 2014
Line 1:		Line 1:
	{{Stability-~~experimental~~}}		{{Stability-deprecated}}

	<div class="title">Build System</div>		<div class="title">Build System</div>

Robert.lihm: /* coreDir */

2014-09-30T12:23:52Z

coreDir

← Older revision		Revision as of 12:23, 30 September 2014
Line 116:		Line 116:
	Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.		Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.

	~~<h4><span class~~=~~"mw-headline" id~~=~~"debuging">~~debug~~</span></h4>~~		==== debug ====
	Enables a debug build.		Enables a debug build.

Robert.lihm: /* coreDir */

2014-09-30T12:23:12Z

coreDir

← Older revision		Revision as of 12:23, 30 September 2014
Line 116:		Line 116:
	Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.		Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.

	<span class="mw-headline" id="debuging">debug</span>		<h4><span class="mw-headline" id="debuging">debug</span></h4>
	Enables a debug build.		Enables a debug build.

Robert.lihm: /* debug */

2014-09-30T12:22:05Z

debug

← Older revision		Revision as of 12:22, 30 September 2014
Line 116:		Line 116:
	Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.		Currently, this parameter is used to compile <code>.less</code> files for every installed theme. This can be disabled by setting <code>[[#skipLess\|skipLess]]</code>.

	==== debug ~~====~~		<span class="mw-headline" id="debuging">debug</span>
	Enables a debug build.		Enables a debug build.

Mark.schmidts: /* Workflow */

2013-10-28T10:17:04Z

Workflow

← Older revision		Revision as of 10:17, 28 October 2013
Line 33:		Line 33:
	The build system is used not only to create source archives for packaging. It can also directly install and update the built UI in a directory during development, help with the setup of the source of a new external app and more. While all of these tasks are described in the reference section, daily work involves just a few of them.		The build system is used not only to create source archives for packaging. It can also directly install and update the built UI in a directory during development, help with the setup of the source of a new external app and more. While all of these tasks are described in the reference section, daily work involves just a few of them.

	To have an easy example about how to write, build & host your javascript code and how to initialize & build your packages, please have a look at the [[AppSuite:GettingStarted \| GettingStarted article]].		To have an easy example about how to [[AppSuite:GettingStarted#Writing \| write]], [[AppSuite:GettingStarted#Building \| build]] & [[AppSuite:GettingStarted#Running \| host]] your javascript code and how to [[AppSuite:GettingStarted#Initialization \| initialize]] & [[AppSuite:GettingStarted#Building_Packages \| build]] your packages, please have a look at the [[AppSuite:GettingStarted \| GettingStarted article]].

	==== JSHINT ====		==== JSHINT ====

Mark.schmidts: /* Workflow */

2013-10-28T10:11:49Z

Workflow

← Older revision		Revision as of 10:11, 28 October 2013
Line 32:		Line 32:

	The build system is used not only to create source archives for packaging. It can also directly install and update the built UI in a directory during development, help with the setup of the source of a new external app and more. While all of these tasks are described in the reference section, daily work involves just a few of them.		The build system is used not only to create source archives for packaging. It can also directly install and update the built UI in a directory during development, help with the setup of the source of a new external app and more. While all of these tasks are described in the reference section, daily work involves just a few of them.

	~~=== Create packaging metadata ===~~

	The first task which should be executed when creating a new external app is <code>[[#init-packaging\|init-packaging]]</code>. It creates packaging metadata in the current directory. It requires the parameter <code>package</code> to specify the package name in the generated files. All subsequent tasks will automatically extract the package name from the files generated by <code>[[#init-packaging\|init-packaging]]</code>.

	~~Before execution, the <code>apps</code> subdirectory must be created. It indicates that the current directory is actually a valid source directory.~~

	~~$ mkdir apps~~
	~~$ build-appsuite init-packaging package=example-app~~
	~~Build path: build~~
	~~Build version: 0.0.1-1.20130424.123835~~

	~~Version [0.0.1]:~~

	~~Maintainer (Name <e-mail>): Maintainer <maintainer@example.com>~~

	~~Copyright line [2013 Open-Xchange, Inc]:~~

	~~License name [CC-BY-NC-SA-3.0]:~~

	~~Short description: Hello World app to demonstrate usage of the build system~~

	The task presents a number of interactive prompts to get the necessary information about the generated packages. The entered values should follow the Debian Maintainer's Guide. Some or even all prompts can be skipped by explicitly specifying the information as a build variable. The list of variable names is available in the reference of <code>[[#init-packaging\|init-packaging]]</code>.

	~~After the task is finished, the generated files can be customized manually to account for any additional packaging requirements.~~

	~~=== Building apps ===~~

	To have an easy example about how to write, build & host your javascript code and how to initialize & build your packages, please have a look at the [[AppSuite:GettingStarted \| GettingStarted article]].		To have an easy example about how to write, build & host your javascript code and how to initialize & build your packages, please have a look at the [[AppSuite:GettingStarted \| GettingStarted article]].