Confirmed users
228
edits
MDN/Development/Emscripten: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
==What content should it have?== | ==What content should it have?== | ||
My experience and perspective is mainly from the "Game developer who has written a native game in C/C++ for Android/iOS/PC and wants to port it to FxOS/browser" viewpoint. There, the process comes with the following questions, roughly in the following chronological learning order: | Although Emscripten can be used to compile a number of different languages into JavaScript, it would make sense to start with C++, as that is the best supported and most useful target laguage for our current projects. The following quote from Jukka provides some good context for the purpose of these docs: | ||
<blockquote>My experience and perspective is mainly from the "Game developer who has written a native game in C/C++ for Android/iOS/PC and wants to port it to FxOS/browser" viewpoint. There, the process comes with the following questions, roughly in the following chronological learning order:</blockquote> | |||
(feasibility/disbelief) 1. Web doesn't do 3D well and I know web is slow. Is this port even feasible? What kind of sacrifices will I have to do in my existing game in terms of performance? How does web compare to native Android/iOS/PC? | (feasibility/disbelief) 1. Web doesn't do 3D well and I know web is slow. Is this port even feasible? What kind of sacrifices will I have to do in my existing game in terms of performance? How does web compare to native Android/iOS/PC? | ||
| Line 61: | Line 63: | ||
Currently we do have some examples of "how do I do X in Emscripten" as part of the unit test suite, but naturally that's not a good format for reading as a documentation/learning material. Some of those could be hoisted or used as a basis for a better set of example apps. | Currently we do have some examples of "how do I do X in Emscripten" as part of the unit test suite, but naturally that's not a good format for reading as a documentation/learning material. Some of those could be hoisted or used as a basis for a better set of example apps. | ||
==Raw ideas== | ==Raw ideas== | ||
==What should we talk to?== | ==What should we talk to?== | ||