On the one hand, putting things into Urho core helps community reuse them.
On the other hand, it will bloat Urho core.
Urho core is simple and lightweight for now. I am not about actual code size, I am mostly about generic achitecture. It has few basic blocks that could be reused in the million of differect tasks.
One we start adding things to Urho code, it will lose its elegance. It will be getting bloated… E.g. I dislike
RibbonTrail. It is nice feature, but I doubt that it is as generic and reusable as e.g.
StaticModel. For me it’s something that should lay as 3rdparty asset like Skybox or smth else.
Possible soluion is to put all these things into Urho3D.lib but separate them from Urho core file and class tree.