About IMGUI support

[dragon122]

Not sure how many people are still using U2022> but maybe it's worth dropping IMGUI support?
It just seems it doubles the amount of work for essentially a legacy feature. If it's not a problem then whatever, just afraid it hinders us all.

[TylerTemp]

Yeah, this is a pain in the ass...

SaintsField is designed to let most attributes co-exist with other plugins, except for some specific attributes which require SaintsEditor. The major considerations are:

1. Unity has many official packages that are still using IMGUI. Most of the time is fine, but for things like Netcode for GameObjects which inject a UnityEditor.Editor, missing IMGUI means it'll be completely broken
2. Odin supported UI Toolkit but can not properly align the label (I submitted a question and they never responded). Tri-Inspector has issue supporting for UI Toolkit. Both are quite popular enhancements. By allowing IMGUI it'll be compatible with them. (My workplace uses Odin, and a label misalign is acceptable)

But still, as a small, and young project, considering my time and energy, it makes sense to give at least limited support for IMGUI...

I've already included a warning in Troubleshooter & SaintsFieldConfig. Dropping IMGUI is considered, but I think I'd keep the current situation for a bit longer. The further changes might be: 1. if a component in IMGUI is easy, then it'll be supported 2. Otherwise, like Table, ListDrawerSettings which require a huge amount of work, will not be implemented in IMGUI.

(The warning message in the package, but not in the document)

And thanks for your consideration :)