Jump to content

Collaborative HTML5 Game Engine


mfdesigner
 Share

Recommended Posts

Currenly there are very few web-based game development platforms.  Since we are working on a game engine for the web, I would like to take this opportunity to introduce our game engine to the game developer community and gather as much feedback as possible. (Technically, our engine is a app/game collaboration platform built using only web technologies.)


 


We believe web technologies can bring out a unique aspect of game development process and that is sharing.  However, comparing to C++ and Java, Javascript and HTML are missing one important ingredient: object-orientation.  To overcome that shortcoming, our platform adds an extra layer of framework on top of existing web technologies to offer object orientation.  Basically, it allows users to wrap any HTML, XML, Javascript, Vector Graphics, 3D Mesh, Texture Materials, Animations, etc. into reusable and sharable objects. We have also built a public database enabling users to exchange objects for building web applications and games.


 


This a simple 3D scene created by our platform and published to our public app repository.  This scene was written in 41 lines of javascript.  Without object reusaility, it would probably take more than hundreds lines of code and none of it can be reuse later.


 


Our long term strategy is to build a web game engine that ultimately will run on the upcoming Google game console.


 


Below are some of our promo videos:


 


BraveWeb.png


 


TDOODF.png


 


3DScene.png


 


If you consider our platform has a viable future and would like to see it to completion,  Your contribution, however little, to our soon-to-be-launched indiegogo campaign can really help us in continuing development in many areas of the platform.


 


If you have any question, please send it to [email protected]


 


Thank you,


 


Steve


Link to comment
Share on other sites

You had me until you said that JavaScript 1) lacked object orientation, and that 2) it was a short coming. IMO prototypal inheritance is a much better model than classical inheritance, and JavaScript is purely object-oriented.

 

Javascript IS object-oriented... but is at the language level like c++ and java.   All its benefits go to the programmers not to the artists. 

 

And when programmers build objects, they end up building interfaces reflecting his own understanding of the problem.

 

A top-down object-oriented design is to design the overall information flow / requirements first by the end users and then let others fill in the implementations.   (end users can pick and choose whichever object fits his/her requirements best.)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...