Re: [Boost-users] [statechart] Passing parameters to state objects

Subject: Re: [Boost-users] [statechart] Passing parameters to state objects
From: Robert Dailey (rcdailey_at_[hidden])
Date: 2009-09-28 17:32:05

On Mon, Sep 28, 2009 at 2:04 PM, Nat Goodspeed <nat_at_[hidden]> wrote:

> Robert Dailey wrote:
>
>  I was thinking of using Boost.Statechart as a state machine to manage
>> widget states in my wxWidgets application. Depending on what menu options
>> the user picks in my program, certain buttons on the main window will be
>> enabled or disabled.
>>
>
> Have you looked at Adobe's Adam engine?
>
> http://stlab.adobe.com/group__asl__overview.html

Yes, I have looked at it. I have determined that I don't like it at all. I
realize the language itself allows button states to be intrinsic to the
design phase of the UI, but the overhead of integrating ASL with a platform
layer looks like a nightmare. Additionally, the ASL scripting language is
VERY complex and unintuitive. It has the largest learning curve I've ever
seen in any other library.

While this does indeed count as a solution to my problem, it is not the
"kind" of a solution I am looking for. Thanks for the reference, though!