Good with the renaming. The previous one was absolutely terrible.
Bad with hiding experimental packages. Users shouldn’t have to jump out of Unity to discover them, or download them. Don’t add more mental stress to using Unity! What’s so hard about putting a BIG, BAD, RED, warning sign?
And for the love of all that is holy, can you backport this new nomenclature to 2020.3? A lot of people will be using it for a long, long time, and starting new projects in it, and having two different package nomenclatures is again, more confusion and mental stress. Especially since the old one was disastrous… it means you are dooming all your LTS users (supposedly, you are encouraging people to use LTS versions for projects…) to remain on the known bad one.
I’m here, after several google searches, trying to find the packages I need, wasting time as everyone else.
Edit:
So, for anyone else looking for UI Toolkit, here’s how it is right now:
A new project will already have a package called Unity UI. This is not the correct package, but manually add com.unity.ui … of course… that is the UI toolkit. When it installs, it shows up as “UI Toolkit” in the package manager.
This added level of hidden packages on top of the different UI solutions and inconsistent naming is pretty frustrating, I must admit… and why isn’t that package listed under these experimental packages?
I am ok with that as long as there is a place for me which list out all the experimental package name, so I don’t have to spend hours searching for it.
I have a grudge about the packages: the documentation included is in markdown (md) making it unusable when you are offline. I can export the .md files into html with Visual Studio Code but the result, although more agreeable to read, is far less practical to navigate (basically the index.md page is useless).
The documentation furnished with the editors is in html; if I click on index.html the page opens in my browser and from there I can navigate to all the pages contained in the documentation folder!
After opening index.html and clicking on “Working in Unity”:
We’ve spoken to the documentation who say that package docs should be available offline as part of the user manual in the new pipeline they are developing. However, there’s no ETA at present on when this will be released. All I can just say is that it’s being worked on.
What about today, do you have an ETA? I have limited access to the internet, I need to be able to browse the packages documentation in off line mode. Thanks.
