[idea] Unity instead of Awesomium and nodewebkit

With the talk of Awesimoum and nodewebkit going around. I had the thought of why not instead use Unity.

Why Unity. It takes JS as a scripting language. It runs on everything. Desktops, IOS, Android, Browsers AND Consoles.

Why Unity, it runs JS as script for it's own full on engine. This means that it doesn't require WebView. This means full acceleration on on the GPU. So all those WebGL effects work across all platforms.

Why not Unity, C2 currently supports platform exporting(CocoonJS, Phonegap, HTMl, CHrome Webstore.....). And these most likely are only tweaks to the current C2 runtime. My concern with this idea is that that a Unity Exporter may require massive changes.

Why Unity. There are great benefits to using Unity, two vs one. However the conversion from runtime to compatible unity script is a lot. I only present it as an idea. But I think it's a pretty good one. just may not be a capable one with C2 as it is.

However, it might be something to think about for C3? which I don't imagine is anytime soon.

Why not unity: it's a third part plugin.

HTML5 does not require any plugin/download to work in a browser.

Technology

As for export in exe, awesomium or nodewebkit are probably a better fit anyway.

Now that would be fantastic. Don't know why people are so finicky when it only takes you 5 minutes or less to download an extra plugin to play within a browser.Having an option to use scripts would be most welcome too.I bought play maker for unity and it works ok.Just imagine if it was as easy as construct 2.

Unity is not a standards compliant web browser, so even if it supports Javascript we would likely have to rewrite various parts of the engine for it to work. I think with node-webkit in the next release there shouldn't be any need to use another engine anyway.

I have looked into that before, trying to use the C2 behaviours in Unity.

Unity's javascript is not the web's javascript. One of the main differences are prototypes, Unity's javascript does not support them.

So, yes, like Ashley said, it would require some major rewrite.

Unity is not a standards compliant web browser, so even if it supports Javascript we would likely have to rewrite various parts of the engine for it to work.

This was my largest concern. As I'm sure C2 makes many canvas references where as a Unity export would require large amounts of api references instead.

I think with node-webkit in the next release there shouldn't be any need to use another engine anyway.

While i'm sure node-webkit is good or great. As I understand node-webkit from the website it's a desktop only solution. As it seems now performance on desktop is fantastic and it's going to get better as time goes on. As power increases and browsers improve, and as OS start increasing native-web app support(like Win8). it would strike me that packaging for for desktop isn't a long term productive future endeavour, but instead a current place holder for convenience and steam like support of distribution.

My suggestions and of course I understand the limitations. Was that Unity wasn't limited to the desktop environment. Right now that the desktop is starting to see a decline in average consumer purchases. This was replaced by the laptop and netbook market. It's now seeing a strong shift towards the tablet. While I believe that it's going a decade for this shift to become dominant factor for the average user to PC to mobile. It does eventually leave desktop support in a minority. However, I mention that I think C2 will have a very productive life in the direction it's going.

I guess part of the frustrations is the glacial pace that development of HTMl5 technology for mobile devices have hit in the last few years. For a while it seemed like there were great strides being made, but now not so much. Actually it seems like I can find comments from 2011 wondering when WebGL for mobile will be supported. Checking with current today's support(http://caniuse.com/webgl) it doesn't seem like it's coming all that soon or in anykind of realistic time. For groups trying to achieve native performance for mobile(CocoonJS, Phonegap, appmobi) it seems that they are strangely quite bursts.

Finally I'm dropping it from there as I do believe the technological limitations of the design structure between C2 and Unity would have been substantially large. However I thought to make the suggestion anyways as I only suspected the design differences rather than knowing the details.

suggestion dropped :D

I think with node-webkit in the next release there shouldn't be any need to use another engine anyway.

VERY excited for this release <img src="smileys/smiley4.gif" border="0" align="middle" />

Jase00: It's out already: beta r115

jayderyu : what you are going to see evolve in the next few month, is solutions like Ejecta/EjectaGL, that allows the use of HTML5 pages with javascript code natively accelerated by a thin layer of code accessing directly the OpenGLES framework. Just wait a few months...

Looks like it has a lot of promise. After doing some research on it. I'm hoping that others take up the design of skipping the webuiview and just do something similar to this.

As it is Ash has a good point. Mac is out of my reach, but I admit I might pick up a cheap used one if required.

well if you can afford every platforme and the pro version ... thene go ahead