[Development] QAction-like API for QML

Shawn Rutledge shawn.t.rutledge at gmail.com
Thu Dec 20 11:40:28 CET 2012

On 19 December 2012 09:13, André Somers <andre at familiesomers.nl> wrote:
> Well, I disagree with that view of what an action represents. To me, the
> core of an action really is bundling a bit of state with a trigger for
> something to happen (I try to avoid the word 'action' here) in a
> convenient API. That piece of state includes at minimum if that action
> is available right now, and can also contain a value ('checked' is the
> value that QAction can currently carry, so basically a boolean). That by
> itself is already a very useful thing to have, as it provides a very
> nice and clean way to expose functions on an API, especially for code in
> a core layer of the application.

Do you have some compelling, concrete examples of what you would use
it for?  I agree with Alan and Jens, there's no point in adding
clutter to Core unless it's really so useful that other things besides
the new action class need to be based upon it.

More information about the Development mailing list