-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the state of C#/.NET support as of 4.2 #8142
Update the state of C#/.NET support as of 4.2 #8142
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like "experimental Android support" doesn't say much from the user's perspective. What does experimental mean to users? Maybe we should list the limitations of Android exports somewhere.
Sure, I'm not aware of any specificities, but I can add whatever makes sense to the notes. As for "experimental", I think it makes it pretty clear that it's in a working state but in need of public testing. But we can also link something relevant to its status if we have any external resources, or add some details as you suggest. |
By the way, I'm not against using the word "experimental" and I think it's the right word to use for the current status. My concern was only that it's not descriptive enough to users about the limitations, so adding some more details somewhere and linking to it sounds good to me. Off the top of my head, the current limitations for Android exports are:
|
I'll adjust my notes, but want to mention that this is probably something that needs to be described in more detail somewhere... Not sure where though. Somewhere in the C# parts of the docs, but not exactly sure where. |
8984127
to
f25a29e
Compare
@raulsntos Okay, I've added more details into notes, and also improved the index page for C# with a bit of structure, some renames for clarity and more details about platform support (which I link to from all those notes). Let me know what you think. |
|
||
.. _doc_c_sharp_platforms: | ||
|
||
C# platform support |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love the new index page, but I'm not sure if this is the best place for this section. We have similar sections in c_sharp_basics
(Current gotchas and known issues or Common pitfalls) but I'm not sure if that's better, to be honest I think the c_sharp_basics
page should probably be split into multiple pages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know what you mean, and I was thinking removing some stuff from the basics page that can be now found on the index page... but ultimately decided that a bit of duplication is fine. These are likely to be the two landing pages, so it makes sense to have a bit of important information on both of them.
I do support reorganizing the docs, though. I'm not entirely sure why we have articles framed as introduction to C#. That's probably unnecessary and we could go straight into Godot-specific stuff (with some notes here and there that link Godot API to C# concepts).
I could give it a go as time allows, but it would be harder for me to find a good angle here since I'm neither a C# user nor maintainer 🙃 But I can help, if you're interested.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would love that, maybe we can do that after the 4.2 release. For now I think this is good.
f25a29e
to
ac728e8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks for all the improvements to the C#/.NET documentation.
Thanks! Merged. |
Add more details to the documentation to avoid confusion, and also remove a scary message that we don't really need anymore. See also godotengine/godot-website#671.