Jump to content

  • Log In with Google      Sign In   
  • Create Account


#Actualtcaudilllg

Posted 20 May 2013 - 11:15 AM

Tell you what I will do: I'll make an add-on system for Gamestar proper, that will permit Gamestar to be used as a vessel for tools. This might not seem like that big of a deal, but it would save a lot of memory compared to using separate apps with their own heap for the same purposes. I don't intend to open Gamestar's code though... rather, this system will read all HTML files from a given directory, and load them in with innerHTML. But they won't be active unless specified by the user.

Also worth mentioning is that Gamestar can be styled: just make a file called Gamestar.css and put it in your directory. The element IDs are apparent in the source.

Mozilla is making a big deal about Gamestar's reliance on innerHTML... they think it's a means for exploiting vulnerabilities in their own code. But it's essential to the rationale of making a game maker web app, because without the freedom of HTML 5 you really have nothing.

I think that critical thinking should be considered: yes for some apps, made for use by hundreds of thousands or millions, there should be caution regarding innerHTML. But I really don't expect that tens of thousands of people will want to use Gamestar regularly. I really don't. Game dev is niche -- very niche -- and always will be. As such it is highly unlikely Gamestar's doubtlessly very intelligent users would fall prey to a scammer.

#2tcaudilllg

Posted 20 May 2013 - 11:13 AM

Tell you what I will do: I'll make an add-on system for Gamestar proper, that will permit Gamestar to be used. This might not seem like that big of a deal, but it would save a lot of memory compared to using separate apps with their own heap. I don't intend to open Gamestar's code though... rather, this system will read all HTML files from a given directory, and load them in with innerHTML. But they won't be active unless specified by the user.

Also worth mentioning is that Gamestar can be styled: just make a file called Gamestar.css and put it in your directory. The element IDs are apparent in the source.

Mozilla is making a big deal about Gamestar's reliance on innerHTML... they think it's a means for exploiting vulnerabilities in their own code. But it's essential to the rationale of making a game maker web app, because without the freedom of HTML 5 you really have nothing.

I think that critical thinking should be considered: yes for some apps, made for use by hundreds of thousands or millions, there should be caution regarding innerHTML. But I really don't expect that tens of thousands of people will want to use Gamestar regularly. I really don't. Game dev is niche -- very niche -- and always will be. As such it is highly unlikely Gamestar's doubtlessly very intelligent users would fall prey to a scammer.

#1tcaudilllg

Posted 20 May 2013 - 11:06 AM

Tell you what I will do: I'll make an add-on system for Gamestar proper, that will permit Gamestar to be used. This might not seem like that big of a deal, but it would save a lot of memory compared to using separate apps with their own heap. I don't intend to open Gamestar's code though... rather, this system will read all HTML files from a given directory, and load them in with innerHTML. But they won't be active unless specified by the user. Also worth mentioning is that Gamestar can be styled: just make a file called Gamestar.css and put it in your directory. The element IDs are apparent in the source. Mozilla is making a big deal about Gamestar's reliance on innerHTML... they think it's a means for exploiting vulnerabilities in their own code. But it's essential to the rationale of making a game maker web app, because without the freedom of HTML you really have nothing.

PARTNERS