Hi, thanks for the feedback!
Could you please tell us more about how you'd like to extend the concept of Kit?
For my project, I think I'll just register a new `KitInformation` subclass, in order to have a new field in the Kit to select the Cargo tool, but nothing more. I'm just a bit annoyed to have unrelated fields in there (for example the "CMake Tool" field or the Qt-related ones). Do you have another use case in your project?
It's a bit early for me to realize if my project will necessitate some missing extension points, or if the abstractions already provided are sufficient. If your project is more advanced than mine, I'll certainly benefit from your experience! Is your project publicly available? Could you give a brief overview of your design?
On a (mostly) unrelated note, I was surprized that the C++ specific classes (`GccToolChain`, for example) belong directly to the ProjectExplorer plugin. I expected them to be in a separate plugin. I hope there is not a technical limitation for this, that would mean that an "external" plugin like mine will not be able to access some features.
Olivier Renaud
_______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
