I'm trying to keep things as simple as possible for my first PureMVC application and would appreciate any input.
I understand the need to keep the view components as simple as possible but am confused as to when you should refactor the logic out of the view and into one of the other core PureMVC actors.
A simple example
Arrow buttons on the stage that, when clicked, simply moves an image in the corresponding direction....no change to the application logic, simply updating the view.
Ok, now instead of arrow buttons, we have a scrollbar that when scrolled, changes the opacity, saturation, rotation value, etc of the image.
What core PureMVC actors would be required and what would there repsonsiblities be?
I've read all the best practice documents and I can still see several ways of accomplishing the above....
For instance in the 'minmalist example'http://www.as3dp.com/2007/12/27/minimalist-mvc-example-using-the-puremvc-framework/
it seems like overkill to me to have a seprate proxy just for keypresses...am I wrong?