Upgrading to PowerUI 2 - Revision history

188.222.158.94 at 18:33, 12 March 2017

2017-03-12T18:33:07Z

151.229.186.156: /* Nitro has been depreciated */

2017-02-18T05:18:11Z

‎Nitro has been depreciated

151.229.186.156 at 03:42, 18 February 2017

2017-02-18T03:42:14Z

151.229.186.156: /* Default styles */

2017-02-18T03:39:23Z

‎Default styles

151.229.186.156: /* Nitro has been depreciated */

2017-02-18T03:28:38Z

‎Nitro has been depreciated

151.229.186.156 at 03:22, 18 February 2017

2017-02-18T03:22:27Z

151.229.186.156: /* Slow compile times? Precompile PowerUI */

2017-02-16T03:48:54Z

‎Slow compile times? Precompile PowerUI

151.229.186.156: /* Check out the new example scenes */

2017-02-15T23:48:28Z

‎Check out the new example scenes

151.229.186.156 at 23:46, 15 February 2017

2017-02-15T23:46:25Z

151.229.186.156 at 23:44, 15 February 2017

2017-02-15T23:44:18Z

← Older revision		Revision as of 18:33, 12 March 2017
Line 1:		Line 1:
−	PowerUI 2 includes a completely new CSS engine, vast new visual effects and a broad focus on standards compliance. It has been in development for over a year so there are a lot of things that you'll need to be aware of when upgrading a project from earlier versions of PowerUI.	+	PowerUI 2 includes a completely new CSS engine, vast new visual effects and a broad focus on standards compliance. It has been in development for over a year so there are a lot of things that you'll need to be aware of when upgrading a project from earlier versions of PowerUI. You can download PowerUI 2 from [http://powerui.kulestar.com/me/ My PowerUI].

	== Check out the new example scenes ==		== Check out the new example scenes ==

← Older revision		Revision as of 05:18, 18 February 2017
Line 37:		Line 37:

	The version of Nitro currently in PowerUI 2 is getting replaced with an entirely new engine (called Nitrassic - it's Jurassic combined with Nitro's performance, flexibility and ability to be precompiled). In the meantime though, the older Nitro engine is unsupported (and has been for a little while) so you should expect it to pose a challenge if you are porting larger volumes of Nitro.		The version of Nitro currently in PowerUI 2 is getting replaced with an entirely new engine (called Nitrassic - it's Jurassic combined with Nitro's performance, flexibility and ability to be precompiled). In the meantime though, the older Nitro engine is unsupported (and has been for a little while) so you should expect it to pose a challenge if you are porting larger volumes of Nitro.
		+
		+	''Note: The Nitro engine itself is stable; the main thing is that it simply lacks access to various new PowerUI APIs.''

	On the whole most people don't use Nitro anyway so this 'gap' isn't expected to be too much of an issue. The update was phased like this to hopefully make it easier to update from earlier versions to 2 in steps as new Nitro is almost entirely ECMAScript compliant ('real Javascript') - it's case sensitive, for example. However, it brings us a big step closer to supporting major libraries like jQuery inside Unity, as well as saying hello to a much nicer scripting environment ''(bye bye to those occasional cryptic errors!)''		On the whole most people don't use Nitro anyway so this 'gap' isn't expected to be too much of an issue. The update was phased like this to hopefully make it easier to update from earlier versions to 2 in steps as new Nitro is almost entirely ECMAScript compliant ('real Javascript') - it's case sensitive, for example. However, it brings us a big step closer to supporting major libraries like jQuery inside Unity, as well as saying hello to a much nicer scripting environment ''(bye bye to those occasional cryptic errors!)''

← Older revision		Revision as of 03:42, 18 February 2017
Line 78:		Line 78:
	'''So, broadly, you ctrl+f for UIEvent and swap the name for the appropriate event.'''		'''So, broadly, you ctrl+f for UIEvent and swap the name for the appropriate event.'''

		+	== Scrollbars ==
		+
		+	If you used any of the scrollbar hacks to get e.g. convenient sliders, or styled them using the input[type="vscroll"] selector, see the [[Scrollbars\|new scrollbar guide]]. You can still use a scrollbar as a slider (it fires an onchange event); the names of the elements have changed.

	== Forms ==		== Forms ==

← Older revision		Revision as of 03:39, 18 February 2017
Line 129:		Line 129:

	* All input elements were restyled to use a more generic colour scheme by default.		* All input elements were restyled to use a more generic colour scheme by default.
		+
		+	Using the 1.9 stylesheet won't work as a quick fix. This is because elements like table now entirely define their behaviour through CSS, so swapping out the stylesheet would result in random missing selectors (such as the one which declares 'table' as using 'display:table;', for example - that wasn't in 1.9).

@@ Line 38: / Line 38: @@
 The version of Nitro currently in PowerUI 2 is getting replaced with an entirely new engine (called Nitrassic - it's Jurassic combined with Nitro's performance, flexibility and ability to be precompiled). In the meantime though, the older Nitro engine is unsupported (and has been for a little while) so you should expect it to pose a challenge if you are porting larger volumes of Nitro.
-On the whole most people don't use Nitro anyway so this 'gap' isn't expected to be too much of an issue. The update was phased like this to hopefully make it easier to update from earlier versions to 2 in steps as new Nitro is almost entirely ECMAScript compliant ('real Javascript') - it's case sensitive, for example.
+On the whole most people don't use Nitro anyway so this 'gap' isn't expected to be too much of an issue. The update was phased like this to hopefully make it easier to update from earlier versions to 2 in steps as new Nitro is almost entirely ECMAScript compliant ('real Javascript') - it's case sensitive, for example. However, it brings us a big step closer to supporting major libraries like jQuery inside Unity, as well as saying hello to a much nicer scripting environment ''(bye bye to those occasional cryptic errors!)''
 == Events - upgrading your event handlers ==

← Older revision		Revision as of 03:22, 18 February 2017
Line 33:		Line 33:

	</syntaxhighlight>		</syntaxhighlight>
		+
		+	== Nitro has been depreciated ==
		+
		+	The version of Nitro currently in PowerUI 2 is getting replaced with an entirely new engine (called Nitrassic - it's Jurassic combined with Nitro's performance, flexibility and ability to be precompiled). In the meantime though, the older Nitro engine is unsupported (and has been for a little while) so you should expect it to pose a challenge if you are porting larger volumes of Nitro.
		+
		+	On the whole most people don't use Nitro anyway so this 'gap' isn't expected to be too much of an issue. The update was phased like this to hopefully make it easier to update from earlier versions to 2 in steps as new Nitro is almost entirely ECMAScript compliant ('real Javascript') - it's case sensitive, for example.

	== Events - upgrading your event handlers ==		== Events - upgrading your event handlers ==

@@ Line 7: / Line 7: @@
 == Slow compile times? Precompile PowerUI ==
-PowerUI 2 has considerably more code than before - each time you update any C# file, it will all get recompiled. If you're getting long compile times, precompile PowerUI by going to Window -> PowerUI -> Precompile. You no longer need to include your custom PowerUI extensions in this either, so you can continue to add [[Custom_Content|custom tags etc]] without needing to recompile.
+PowerUI 2 has considerably more code than before - each time you update any C# file, it will all get recompiled. If you're getting long compile times, [[Precompiler|precompile PowerUI]] by going to Window -> PowerUI -> Precompile. You no longer need to include your custom PowerUI extensions in this either, so you can continue to add [[Custom_Content|custom tags etc]] without needing to recompile.
 == The DOM (Element -> HtmlElement) ==

@@ Line 3: / Line 3: @@
 == Check out the new example scenes ==
-Most of the example scenes have change, and there's many new ones in there displaying some of the new features too.
+Most of the example scenes have changed, and there's many new ones in there displaying some of the new features too.
 == Slow compile times? Precompile PowerUI ==

@@ Line 110: / Line 110: @@
 == Button ==
-The button element was long known for its quirky behaviour
+The button element was long known for its quirky behaviour. It's now standards compliant.
 == Default styles ==
@@ Line 118: / Line 118: @@
 The stylesheet has changed considerably between 1.9 and 2.0. Some common examples:
-- html and body no longer default to a height of 100%.
+* html and body no longer default to a height of 100%.
-- body now has the standard 8px margin.
-- All input elements were restyled to use a more generic colour scheme by default.
+* body now has the standard 8px margin.

← Older revision		Revision as of 23:44, 15 February 2017
Line 107:		Line 107:

	</syntaxhighlight>		</syntaxhighlight>
		+
		+	== Button ==
		+
		+	The button element was long known for its quirky behaviour
		+
		+	== Default styles ==
		+
		+	The user agent stylesheet was renamed to '''xhtml-style.html''' and is in the same location as before, when it was called style.html - ''Path/To/PowerUI/Resources/xhtml-style.html''. It contains all of the core style for elements, including the default style for [[Scrollbars\|scrollbars]] etc.
		+
		+	The stylesheet has changed considerably between 1.9 and 2.0. Some common examples:
		+
		+	- html and body no longer default to a height of 100%.
		+	- body now has the standard 8px margin.
		+	- All input elements were restyled to use a more generic colour scheme by default.