using_the_web_editor.rst 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134
  1. :article_outdated: True
  2. .. _doc_using_the_web_editor:
  3. Using the Web editor
  4. ====================
  5. There is a `Web editor <https://editor.godotengine.org/>`__ you can use to work
  6. on new or existing projects.
  7. .. note::
  8. The web editor is in a preliminary stage. While its feature set may be
  9. sufficient for educational purposes, it is currently **not recommended for
  10. production work**. See :ref:`doc_using_the_web_editor_limitations` below.
  11. Browser support
  12. ---------------
  13. The Web editor requires support for WebAssembly's SharedArrayBuffer. This
  14. is in turn required to support threading in the browser. The following desktop
  15. browsers support WebAssembly threading and can therefore run the web editor:
  16. - Chrome 68 or later
  17. - Firefox 79 or later
  18. - Edge 79 or later
  19. .. UPDATE: Not supported yet. When Opera, Safari, or mobile browsers are
  20. .. supported, update or remove these paragraphs.
  21. Opera and Safari are not supported yet. Safari may work in the future once
  22. proper threading support is added.
  23. **Mobile browsers are currently not supported.**
  24. The web editor only supports the Compatibility rendering method, as there is no
  25. stable way to run Vulkan applications on the web yet.
  26. .. note::
  27. If you use Linux, due to
  28. `poor Firefox WebGL performance <https://bugzilla.mozilla.org/show_bug.cgi?id=1010527>`__,
  29. it's recommended to use a Chromium-based browser instead of Firefox.
  30. .. _doc_using_the_web_editor_limitations:
  31. Limitations
  32. -----------
  33. Due to limitations on the Godot or Web platform side, the following features
  34. are currently missing:
  35. - No C#/Mono support.
  36. - No GDExtension support.
  37. - No debugging support. This means GDScript debugging/profiling, live scene
  38. editing, the Remote Scene tree dock and other features that rely on the debugger
  39. protocol will not work.
  40. - No project exporting. As a workaround, you can download the project source
  41. using **Project > Tools > Download Project Source** and export it using a
  42. `native version of the Godot editor <https://godotengine.org/download>`__.
  43. - The editor won't warn you when closing the tab with unsaved changes.
  44. - No lightmap baking support. You can still use existing lightmaps if they were
  45. baked with a native version of the Godot editor
  46. (e.g. by importing an existing project).
  47. The following features are unlikely to be supported due to inherent limitations
  48. of the Web platform:
  49. - No support for external script editors.
  50. - No support for Android one-click deploy.
  51. .. seealso::
  52. See the
  53. `list of open issues on GitHub related to the web editor <https://github.com/godotengine/godot/issues?q=is%3Aopen+is%3Aissue+label%3Aplatform%3Aweb+label%3Atopic%3Aeditor>`__
  54. for a list of known bugs.
  55. Importing a project
  56. -------------------
  57. To import an existing project, the current process is as follows:
  58. - Specify a ZIP file to preload on the HTML5 filesystem using the
  59. **Preload project ZIP** input.
  60. - Run the editor by clicking **Start Godot editor**.
  61. The Godot Project Manager should appear after 10-20 seconds.
  62. On slower machines or connections, loading may take up to a minute.
  63. - In the dialog that appears at the middle of the window, specify a name for
  64. the folder to create then click the **Create Folder** button
  65. (it doesn't have to match the ZIP archive's name).
  66. - Click **Install & Edit** and the project will open in the editor.
  67. .. attention::
  68. It's important to place the project folder somewhere in ``/home/web_user/``.
  69. If your project folder is placed outside ``/home/web_user/``, you will
  70. lose your project when closing the editor!
  71. When you follow the steps described above, the project folder will always be
  72. located in ``/home/web_user/projects``, keeping it safe.
  73. Editing and running a project
  74. -----------------------------
  75. Unlike the native version of Godot, the web editor is constrained to a single
  76. window. Therefore, it cannot open a new window when running the project.
  77. Instead, when you run the project by clicking the Run button or pressing
  78. :kbd:`F5`, it will appear to "replace" the editor window.
  79. The web editor offers an alternative way to deal with the editor and game
  80. windows (which are now "tabs"). You can switch between the **Editor** and
  81. **Game** tabs using the buttons on the top. You can also close the running game
  82. or editor by clicking the **×** button next to those tabs.
  83. Where are my project files?
  84. ---------------------------
  85. Due to browser security limitations, the editor will save the project files to
  86. the browser's IndexedDB storage. This storage isn't accessible as a regular folder
  87. on your machine, but is abstracted away in a database.
  88. .. UPDATE: Not supported yet. When exporting from the web editor is supported,
  89. .. update this paragraph.
  90. You can download the project files as a ZIP archive by using
  91. **Project > Tools > Download Project Source**. This can be used to export the
  92. project using a `native Godot editor <https://godotengine.org/download>`__,
  93. since exporting from the web editor isn't supported yet.
  94. In the future, it may be possible to use the
  95. `HTML5 FileSystem API <https://developer.mozilla.org/en-US/docs/Web/API/FileSystem>`__
  96. to store the project files on the user's filesystem as the native editor would do.
  97. However, this isn't implemented yet.