Today gear groups expose a "gear state" which roughly summarizes the state of the gear. We're not yet ready to move that to cartridges, nor are all the details of how the constants returned by gear state will be preserved over time.
If you do use gear group state I'd recommend mimicking the console:
If all gears are in the same state display that state as a string. If not, display the number currently in the "started" state (1/6 started).
There was a brief discussion yesterday about longer term representations - probably about separating intent (this cart should be stopped) and state (this cart is stopping).
Finally, as we are migrating off the old broker API we are planning to expose a new "status_message" optional array on carts that exposes the current value returned by the cart service on each gear. That will likely be transitory as we clean up state.
On Aug 31, 2012, at 6:59 PM, AndrÃ© Dietisheim <adietish redhat com> wrote: