Fixed some spelling errors and there's a multicore version as well. Demo's still fine.

Hi Cliff!

Thanks! I'd like to donate this to the project. I put the headers into the files and attached them once more. I'll comment the demo files as soon as possible.

Lukas

Hi everybody!

PureMVC saved my life and washed my brains. However, something that I've been missing for some time now is a strict and well-defined method that allows you to validate data before and after an operation is executed. Therefore I wrote a little extension to PureMVC which introduces ConditionalCommand, an extension to the Command pattern. It allows you to implement pre- and postconditions without changing the overall behaviour of the native pattern.

I attached two archives. One contains a flex demo, the other one the source files and some asdocs. You'll need Flex SDK 4 to compile the demo and the extension was written on top of PureMVC 2.0.4 which is included in the demo archive.

I'd be glad to read your thoughts on this.
Lukas

Hi Cliff,

thanks for your quick answer. I'll give this some thought.

Lukas

I'm just getting started with the pureMVC-framework and the mvc principle in general. I discovered this website and it's content. I got into several wikipedia-articles treating the topic last night and now I feel like the mvc model seems to be just the thing I've been looking for to organize my workflow.

Now I have a simple beginner's question:
Down to which level does the use of mvc models make sense?
An example:
I got a form with controllers controlling the data flow between the form mediator and a given proxy, a mediator which provides the form's view with the needed data etc. The form view itself consists of common form elements like radios, checkboxes, dropdowns and so on. Is it sensible to write these lowest level components with mvc principles? Have I misunderstood something?