Bindings, UI-hierarchy that grows insane during runtime, Prefabs, Views, u name it...Something simple, like: how can I modify the UI or Prefabs without breaking the entire system?...nowhere to be found. 1864 files without proper structure in my opinion. (folder name, icon name etc). I'm using the RT handles only for now.

The author is using MVVM. The mvvm isn't naturally good in unity editor and it is used in large scale project or team collaboration. The data binding is all over the complex UI hierarchy, which means u might be confused where the binding is. The overdesign makes the code hard to read, and the support is irresponsive.U have to fix bugs yourself. The doc isn't good though there are many examples to explore.

Remaking the Unity Editor for play mode is probably the most ambitious task on the asset store. You'd think the scope and quality of the documentation would be comparable to Unity itself provides. But, excluding code, the documentation effectively ends at 873 words. I picked a random page from the Unity website, it was 868 words. After 873 words, you are hit with ".../IOC.cs is a simple IoC container implementation" followed by code. Why am I being told this random factoid? It's like your date asks you "Would do you like to do for fun?" and your answer is "Water is two parts hydrogen, one part oxygen." I can purposely do a bad job and produce better: "RT editor has systems X, Y, Z. System X is responsible for doing such and such. System Y does such and such. If you need to access these systems, here is a code example. If you care, which you probably don't, the design pattern is called inversion of control (IoC). Here is a link to Wikipedia explaining it." If I can't even get the basic stuff working in the first hour, I'm going to be back to where I started in a few months. Can paid support help? Apparently not, as my inquiry was not answered after 3 days. I'm actually glad now things didn't work so early, as this limits my losses to only a few hours and $50. My advice to the author: 1. People who are not yourself don't know how your asset works, what the different parts are, or how these parts work together. If you don't explain that first, showing them code doesn't help. Code isn't a replacement for documentation. The purpose of documentation is to provide a high level overview and explain why. 2. Create a forum. 3. A lot of stuff didn't work for me in obvious and immediate ways. Hire someone who doesn't know how the system works to test your releases. 4. If the user has options, such as two asset storage systems, make a dialogue explaining the difference and let the user pick. Don't just default to the one you aren't supposed to use. See Gaia for an example of good on-boarding. 5. Don't send new users around the internet to download 3rd party code for core features. That's another way of saying "This is going to break or lose support sooner or later" while I still have the asset store open with alternatives. 6. The ability to script without all the tools that come with that is a trap for beginners. Don't waste time on features you can't fully implement. 7. Answer your support emails promptly, even if it's just a "I don't offer paid support." 8. For every person such as myself who takes the time to write honest feedback, there are 100 who just don't say anything and leave.

this asset does a lot and is one of my favorite assets. the support is also top notch. im still learning as the asset is quite advance but theres plenty of documentation to learn from

If I want to use a part of an asset, I do not know how to import it. (ex. I want to use only the DockPanel and Menu Control) I also want to use DockPanel, but there is not enough sample code or demo on how to add any element in the panel to achieve what I want to do.

This is an excellent editor. I have used several editors, but in terms of functionality and optimization, it is far superior to others. Most importantly, the developer's feedback is very fast.

worst documentation

Very difficult to manage with so many folders and complexity. Documentation is decent

Due to many modifications made on the old version，how to replace the old version with a new version？

ty I appreciate your time in making this asset. Is there a new tutorial for this current version ?