godot
godot copied to clipboard
allow disabling 2d from editor features, change default plugin to 2d
~~Depends on: https://github.com/godotengine/godot/pull/61435, https://github.com/godotengine/godot/pull/61434~~
Resolves: https://github.com/godotengine/godot-proposals/issues/1352
Follow-up to #41036
This PR allows disabling the 2D editor in the editor features dialog. Also improves the main screen plugin code by allowing no plugins to be loaded at a time.
How the editor looks without any main screen plugins (Pointless, but still possible):

Feels a bit wrong to have ability to disable 2D in the editor while we don't have scons disable_2d=yes yet. 😛
But this is just me venting, ignore. 🙂
I don't really see the point. This feature selection is meant to simplify the interface, not really to disallow you completely from making a game.
Feels a bit wrong to have ability to disable 2D in the editor while we don't have scons disable_2d=yes yet. stuck_out_tongue
I don't think this will ever happen, while there are a lot of games without 3D needs, all 3D ones need 2D. 2D is needed for interfaces, but could also be needed in embedded viewports. I don't see any situation where you would need to disable 2D in a game.
Yeah I thought the same about UI stuff, but according to quote unquote "beginners nodes dock" (godotengine/godot-proposals#1206), this could be treated separately from 2D stuff. I mean, yeah UI is certainly 2D (in 2020) but the purpose is agnostic to dimensions (they do inherit from canvas item though...)
This PR, and the ability to disable 2D in scons, are completely separate problems. See https://github.com/godotengine/godot-proposals/issues/190#issuecomment-552125902
After looking at https://github.com/godotengine/godot-proposals/issues/190, it would be nice to eventually separate 2D and GUI to different plugins. IMO 2D and GUI should never really interact directly and it can cause confusion and annoyance.
@nathanfranke https://github.com/godotengine/godot/pull/61435 is merged, so it can marked as such in first comment.
This is being force pushed for a couple months now... is it going to get in by 4.0?
This is being force pushed for a couple months now... is it going to get in by 4.0?
Probably, but only if I can figure out the memory leak. All the stack traces are going outside of the scope of the PR. :cry:
This is being force pushed for a couple months now... is it going to get in by 4.0?
There hasn't been any discussion about it lately. I guess we'll have to revisit it once it's not longer a draft.
Edit: Though it seems that reduz has left a comment that this should probably be rejected, because he believes this PR has been made obsolete by the new build profiles feature.
Thanks for the enthusiasm! I reverted the default plugin change in my staging branch (tes if anyone's curious), and I am currently working on fixing that memory leak.