Sample extensions are intended only as developer examples. While we intend for these extensions to work as described, they are structured to be more opinionated for specific workflows and may not be appropriate for all applications. For this reason, we encourage our customers to take these extensions as-is and to fork them for their own use. We will not include these extensions in product roadmaps, nor do we plan on implementing feature requests for them.
This is pretty clear and understandable.
However when you are developing, it is hard to keep track of this category. If KIT is the SDK, making an extension in the KIT namespace but then saying its not part of the SDK is really confusing.
Sorry for the confusion, I’m not saying anything about what I think it should be, just how it is named.
I’m assuming HOTKEYS WINDOW extension IS a sample extension, based on the image (and the documentation). The only thing I am asking for is that the extension itself be named appropriately for that category. So it is a sample, which is not part of the core SDK, but… the namespace is omni.kit.hotkeys.window. So when someone is developing, importing extensions etc. they can’t know this is a sample extension and not part of “core” kit.
So something more like omni.sample.hotkeys.window or omni_samples.hotkeys.window instead of putting it inside of the kit namespace. The same way developers shouldn’t use omni.mycompany.extension
