Godot: Add hard-to-miss info in Mono binaries pointing that they're WIP / alpha
Godot version:
Current master, Mono build (37cb029f)
Issue description:
The Mono builds as of 3.0 will be released with various known issues, including crashes, and no support for exporting projects. It's fine as there's still a lot that can be done with them already, and the additional feedback from new users will help shape it further.
Still, tons of users will get started with Godot using this version, and might be put off if it's lacking features and crashing on them.
So we need to make it crystal clear both in our public communication AND in the editor itself that the C# support as of 3.0-stable is in beta alpha stage, and that bugs and missing features are to be expected.
It could be a big warning sign with explanations on the project manager (only for the Mono flavour of course) and/or a popup message when opening a first project with 3.0 giving explanations about the state of the Mono build (with option not to show this message again).
akien-mga
All 10 comments
The term "Beta" implies feature-completeness. As exporting is not available, it is not feature-complete.
aaronfranke
on 22 Jan 2018
Have to agree with @aaronfranke, as long as projects with C# can't be exported and projects aren't synced and need to be edited by hand on changing/renaming/moving files, I'd call it "alpha", not "beta".
mhilbrunner
on 22 Jan 2018
I agree with @aaronfranke too, it should be considered alpha until it's feature complete or in some shippable form. For instance, if it could export to at least standalones I think it could be considered beta.
NathanWarden
on 22 Jan 2018
With that said, I obviously agree with @akien-mga that the messaging should be clear that it isn't in shippable form yet. :)
NathanWarden
on 22 Jan 2018
I'm working on adding an opt-out popup when you start the editor with information about the state of the C# support:
What's missing is to find out how to get it shown in the editor once it finished initialising (I declare it in the Mono module and at that time EditorNode is not ready to show stuff yet), and fix that super tiny icon (currently using get_icon("NodeWarning", "EditorIcons"), @djrm any idea how I could get that SVG in 64x64 instead of 16x16?).
akien-mga
on 22 Jan 2018
@akien-mga Looks fine besides the things you mentioned, but I'd drop "frequent" and change "in future releases" to "soon".
mhilbrunner
on 22 Jan 2018
Looks fine besides the things you mentioned, but I'd drop "frequent" and change "in future releases" to "soon".
OK to drop "frequent", but changing "in future releases" to "soon" sounds like not committing to anything, since "soon" could be "in the next 18 months" (just like Godot 3.0 was coming soonâ„¢ at the end of 2016).
akien-mga
on 22 Jan 2018
Haha, maybe thats jus a opinion/feeling thing then... for me it's the opposite, "soon" is vague but sounds like more of a commitment than "in future releases" to me. Maybe "in one of the next releases"?
Not really that important though.
mhilbrunner
on 22 Jan 2018
Well let's commit to "in 3.0.1", and if @neikeq doesn't implement it by then we'll burn him at the stake. 🔥
akien-mga
on 22 Jan 2018
@akien-mga Thanks RemÃ, I think this notice is perfect and very clearly sets user expectations.
NathanWarden
on 22 Jan 2018
Related issues
Zylann
·
3Comments
Spooner
·
3Comments
rgrams
·
3Comments
blurymind
·
3Comments
testman42
·
3Comments
Most helpful comment
The term "Beta" implies feature-completeness. As exporting is not available, it is not feature-complete.