Fetching documentation…
Part of: The Story of Morph
The questions people actually ask — each answered in detail on its own page.
| Question | Page |
|---|---|
| Is Morph just Electron with extra steps? | Q: Electron? |
| Do I need to know C++ to use Morph? | Q: Do I need C++? |
| Is it React? Can I use React? | Q: Is it React? |
| Does Morph use a virtual DOM like React? | Q: Virtual DOM? |
| What is reactivity in Morph? Why this design? | Q: Reactivity |
| Is it for games or for apps? | Q: Games or apps? |
| What about the web — can I build websites with Morph? | Q: What about the web? |
| What happens to my JavaScript at runtime? | Q: JS at runtime |
| Can I use npm packages? | Q: npm packages |
| How does hot reload work if everything is compiled? | Q: Hot reload |
| Is it production-ready? | Q: Production-ready |
| How do I install Morph? | Q: Installation |
| What are the new morph commands? | Q: CLI commands |
| How do I deploy/distribute my app? | Q: Deployment |
| How do I debug a Morph app? | Q: Debugging |
Why two generated headers (_morph_state.h vs morph_api.h)? |
Q: Headers? |
Windows & navigation — <a> vs morph-*, GL contexts, WID/RID, same-route windows? |
Q: Windows? |
Not answered here? Ask at suggestions.morph@levizr.com or in a repo issue — the best questions get their own page, answered in detail.