Comments on: Simplifying code using states http://www.crazygaze.com/blog/2007/12/19/simplifying-code-using-states/ Knowing is not enough; we must apply. Willing is not enough; we must do. Sat, 01 Mar 2008 02:00:42 +0000 hourly 1 http://wordpress.org/?v=abc By: Rui Figueira http://www.crazygaze.com/blog/2007/12/19/simplifying-code-using-states/comment-page-1/#comment-1536 Rui Figueira Fri, 11 Jan 2008 13:01:30 +0000 http://www.crazygaze.com/blog/archives/39#comment-1536 You're right. I often use that approach you talk about, and in my last contract, we extensively used states and events. But for this particular library, the code needs to be as tight as possible. I constantly need to balance design vs codesize. :( You’re right. I often use that approach you talk about, and in my last contract, we extensively used states and events.
But for this particular library, the code needs to be as tight as possible. I constantly need to balance design vs codesize. :(

]]> By: Rui Martins http://www.crazygaze.com/blog/2007/12/19/simplifying-code-using-states/comment-page-1/#comment-1535 Rui Martins Fri, 11 Jan 2008 12:40:59 +0000 http://www.crazygaze.com/blog/archives/39#comment-1535 You are on the right track here :) However, you should give the next Step ! And that is to process State management with a specific function, and stop handling specific states by hand. In short you need to define a function/method like changeState( new_state ), which will validate everything you need, including, if the request state is a valid transition, from the current state. it Will return success or failure. This will make it a lot easier to manage, since all state code is contained in one place. Further ahead, you can also implement event management, where changing state could trigger an event. Suppose you change state to STOPPED, after validation, the changeState(.. ) function/method could trigger the correct event, that would start an event handler that nows, what is need to stop a specific Audio Sample. This can be applied to all other states. Basically, switch from a sequential programming model to an event based model. You are on the right track here :)

However, you should give the next Step !

And that is to process State management with a specific function, and stop handling specific states by hand.
In short you need to define a function/method like changeState( new_state ), which will validate everything you need, including, if the request state is a valid transition, from the current state. it Will return success or failure.

This will make it a lot easier to manage, since all state code is contained in one place.

Further ahead, you can also implement event management, where changing state could trigger an event.
Suppose you change state to STOPPED, after validation, the changeState(.. ) function/method could trigger the correct event, that would start an event handler that nows, what is need to stop a specific Audio Sample.
This can be applied to all other states.

Basically, switch from a sequential programming model to an event based model.

]]>