Jules - on reflection - it'd be pretty handy integrated into the introjucer. As it'd be able to validate that the attributes being changed were at least vaild without too much work, provide useful diagnostics if you ever depreciated anything and so on... :)
But it'd open a nice easy world of automation, configuration consistency checks and all sorts...
yeah, sometimes in nightly build setups on different machines and vm, it's handy to both modify or extract specific variables from the .jucer files (from command line scripts) to maximize automation.
Now I've started using it there are a couple of changes and additions I'm thinking of putting in:
-np needs a long-form equivalent.
It needs a feature for adding items to strings, rather than replacing them. Otherwise automating additions to say the compiler defines list is risky as it might overwrite some future jucer change.
Looks good to me. I'm used to using command line package managers for web development, so to e.g. be able to pull in required modules for a project would be useful, and much quicker than fumbling around a gui.
I think this could link in nicely with the Juce module manager or whatever that might get called...