Browsers - Revision history

Bablakeluke: /* Websites vs UI's */

2018-12-06T23:21:12Z

‎Websites vs UI's

2017-09-04T20:33:05Z

‎So can I use it like a browser?

2017-04-04T04:22:45Z

‎What PowerUI can do

2017-03-30T21:11:37Z

‎Websites vs UI's

2017-03-18T16:51:02Z

‎What PowerUI can do

2017-03-15T21:05:27Z

‎What PowerUI can do

2017-03-15T15:07:31Z

2017-03-15T14:24:56Z

‎What PowerUI can do

2017-03-15T14:24:01Z

‎What PowerUI can do

2017-03-15T14:22:20Z

‎A UI must..

@@ Line 16: / Line 16: @@
 * Be easy to extend in order to represent as many UI concepts as possible
 * Not have awkward platform barriers
 == What PowerUI can do ==

@@ Line 43: / Line 43: @@
 * Stacking contexts aren't supported (for runtime performance reasons). This will make some elements on the web stack in strange orders.
 * Flexbox/ grid aren't supported yet.
-* JavaScript - Due to limitations on iOS and many consoles, PowerUI has a custom variant of JS called Nitro (but not for long! We've been working on a new JS engine which gets around the limitations and has suitable compliance).
+* JavaScript - Due to limitations on iOS and many consoles, PowerUI has a custom variant of JS called Nitro. We're now experimenting with fully compliant Javascript at the moment which you can get from the [[Source Control (GIT)|PowerUI source repository]].
 Currently, these things are all being worked on - PowerUI compiles in under 10 seconds, so we can iterate on new features much, much faster than any conventional browser can (and we don't have the weight of a massive userbase limiting awesome new features either!).

@@ Line 27: / Line 27: @@
 * Widget system
 * Context menu's
 * Dialogue system
 * Easy to localise

@@ Line 2: / Line 2: @@
 == Websites vs UI's ==
-Every now and then, people ask why PowerUI isn't just a wrapper for some existing web engine. It's because websites and user interfaces have extremely different requirements. Consider this:
+Every now and then, people ask why PowerUI isn't just a wrapper for some existing web engine. Why are we going to the effort of building an entirely new one 'inside' Unity. It's because websites and user interfaces have extremely different requirements. Consider this:
 === A browser must.. ===

@@ Line 25: / Line 25: @@
 * Shading/ Lighting
 * 3D text
-* Window system
+* Widget system
 * Context menu's
 * Dialogue system

@@ Line 31: / Line 31: @@
 * Extremely customisable - design a new html element etc
 * Particle systems and camera's on your UI
 * Lots more!

← Older revision		Revision as of 15:07, 15 March 2017
Line 34:		Line 34:

	Many of these things are difficult or simply impossible for an embedded browser.		Many of these things are difficult or simply impossible for an embedded browser.
		+
		+	== So can I use it like a browser? ==
		+
		+	''Sort of'', but that's not what it's designed for. PowerUI has extremely broad coverage of web technologies, but these things currently limit it from being a general purpose browser:
		+
		+	* Stacking contexts aren't supported (for runtime performance reasons). This will make some elements on the web stack in strange orders.
		+	* Flexbox/ grid aren't supported yet.
		+	* JavaScript - Due to limitations on iOS and many consoles, PowerUI has a custom variant of JS called Nitro (but not for long! We've been working on a new JS engine which gets around the limitations and has suitable compliance).
		+
		+	Currently, these things are all being worked on - PowerUI compiles in under 10 seconds, so we can iterate on new features much, much faster than any conventional browser can (and we don't have the weight of a massive userbase limiting awesome new features either!).

← Older revision		Revision as of 14:24, 15 March 2017
Line 32:		Line 32:
	* Particle systems and camera's on your UI		* Particle systems and camera's on your UI
	* Lots more!		* Lots more!
		+
		+	Many of these things are difficult or simply impossible for an embedded browser.

@@ Line 21: / Line 21: @@
 PowerUI focuses on the goals of a UI framework. As a result it can:
-* Just work on any platform
+* Just work (and be exactly the same) on any platform
 * Advanced text formatting (like knockout text)
 * Shading/ Lighting