installer-framework/installer-framework.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	prepare script engine to get the gui object later	Tim Jenssen	2013-10-29	1	-1/+2
\| \| \| \| \| \| \| \|	- Since we need two different script engines we need to be able to set the gui object later Change-Id: Ie40f8ec3dd84dc4d5b3cf127c3e41ce25ef53b66 Reviewed-by: Karsten Heimrich <karsten.heimrich@digia.com>
*	add exceptionhandler code for connected signals/JS methods	Tim Jenssen	2013-06-03	1	-3/+4
\| \| \| \| \| \| \| \| \| \| \|	- there wasn't any error information if a C++ triggered signal resulted in a JS method which has an error, now it will create an exception for it - creating messagebox inside the lib is something what we want to avoid, so the developer itself is responsible to catch these exceptions - most cases of the installer code does that already Change-Id: I07486f73be9de13a486de235f14e3a7d7b54f5b1 Reviewed-by: Karsten Heimrich <karsten.heimrich@digia.com>
*	introduce installerscriptengine	Tim Jenssen	2013-05-16	1	-0/+87
	- it uses one scriptengine for everything and adds the components or/and the install-controller in javascript closure contexts - added the gui object to the component script context - removed tabController from controlscript context Change-Id: I3bd6c5dcf470666c30add1b7d04a8fdd094f5f11 Reviewed-by: Iikka Eklund <iikka.eklund@digia.com> Reviewed-by: Karsten Heimrich <karsten.heimrich@digia.com>