Add "update all" command to update all created projects

[Chocrates]

Scenario:

1. I have created a macOS and an iOS project.
2. I make a code change that I am happy with using briefcase dev
3. I want to push the code to all created projects with one command, it has been suggested that briefcase update all might fit the current standards
   • briefcase in the background would determine what types of projects have been created (if it doesn't already have that data) and run the update commands for those projects

[freakboy3742]

Definitely an interesting idea - "Update/build/publish all my apps" is a use case I can definitely see existing.

Some open questions:

• Does the "all" target apply to other commands? If so:
  • Which platforms would create all target?
  • Would build all be possible ? It isn't possible to build macOS apps on Windows; if there is a macOS folder in your Windows code checkout, what happens? (Similar for
  • What happens with run? Run already requires a -a to nominate a specific app; is there any sense in which run all makes sense?
• Is there an alternative/better UI? I made the suggestion about update all because it potentially allows for all to be a "meta-platform" - a platform that invokes the commands for each of the relevant actual platforms. However, I'm open to other suggestions.

[Chocrates]

Good questions, some thoughts:

• Does the "all" target apply to other commands? If so:

I think it would be good to make it consistent across commands if we can make it make sense

• Which platforms would create all target?

Perhaps all valid platforms for the current environment? I don't know if you can build *nix and windows on macOS but you can't build macOS on windows, like you mention below

• Would build all be possible ? It isn't possible to build macOS apps on Windows; if there is a macOS folder in your Windows code checkout, what happens? (Similar for

Similar to create all, a warning/info message would make sense to let the user know what it is doing and why it can't build macOS (or presumably iOS) when they exist on a non mac platform

• What happens with run? Run already requires a -a to nominate a specific app; is there any sense in which run all makes sense?

I don't have a great idea here. It looks like at most we are talking about 3 programs on macOS (native, iOS and Android), it may make sense to open all three and let the user know that it can't run the windows or linux builds.
Similar on Windows and Linux the most it looks like it could open is android and the native app.

• Is there an alternative/better UI? I made the suggestion about update all because it potentially allows for all to be a "meta-platform" - a platform that invokes the commands for each of the relevant actual platforms. However, I'm open to other suggestions.

I'll have to defer to you and team for this one. I am not sure what makes the most sense for the current usage Obviously what the current maintainers think should trump any of the above 😄