I've been working quite a bit with creating a Juce command-line utility that has to communicate via JSON, and I was wondering if there's an intentional reason why there aren't utility methods for creating and modifying juce::var's whose types are objects. There are a lot of methods (like append, insert, operator returning a var reference) for coercing a var into an array and modifying it. But for object-type var's, there's no setProperty or operator returning a var reference. So I've had to resort to creating temporary DynamicObjects by hand all over my code (on that note - my understanding is that once a var takes ownership of a DynamicObject created with "new," the DynamicObject doesn't need to be deleted, right?). Anyways, are there potential pitfalls with adding utility methods to juce::var to mimic how it works with arrays? I'd be happy to submit a pull request if there aren't objections or problems.