RE: [flexcoders] Re: Cairngorm... Where should this go?

[Bjorn Schultheiss]

Gladly,   simple example.   // view <mx:Button label="submit" enabled="{model.formValidated}" />   // model data Object public function set username(value:String):void {     _username = value;     validateForm() }   private function validateForm():void {     if (_username != undefined)         formValidated = true; }   This is code i've just typed, but the principle remains the same. Data drives the view via dataBinding. There are alternatives to the way you would structure your models and views but the principle remains the same.     Regards,   Bjorn Schultheiss Senior Flash Developer QDC Technologies   From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of grahampengelly Sent: Friday, 8 September 2006 12:24 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Cairngorm... Where should this go? Thanks all for the discussion... So it seems the consensus is the validation, from a pattern purist point of view should sit in the model. Someone suggested a model.isDataValid property... This gives us an indication but how should we be communicating back to the view which data it is that is invalid and what is it that is invalid about it? Should the model dispatch a data invalid event that the view acts upon or a checkValid function that returns the data required to act? I know this is very much academic, particularly as since posting originally, I have implemented my validation that works perfectly well. I would be interested to hear Bjorn how you get your validation information back out of the model to display it in the view. Cheers... Graham Blog --- In [EMAIL PROTECTED]ups.com, "Bjorn Schultheiss" <bjorn.schultheiss@...> wrote: > > I'm going to fly kick this thread quickly. > Validation relates to model, quite simply. > > > Regards, > > Bjorn Schultheiss > Senior Flash Developer > QDC Technologies > > > _____ > > From: [EMAIL PROTECTED]ups.com [mailto:flexcoders@yahoogroups.com] On > Behalf Of lostinrecursion > Sent: Friday, 8 September 2006 6:28 AM > To: [EMAIL PROTECTED]ups.com > Subject: [flexcoders] Re: Cairngorm... Where should this go? > > > > Sorry but I have to interject on this. Intsrestingly enough I asked a > similar question some days ago and did not receive a response from a > design pettern perspective, but from a "what works" perspective. I am > actually 85% of the tim all about what works, so not there is anything > wrong with it. But, I would like to hear some other rhoughts on it > since Validation is integral to just about every RIA that accepts data > on the planet. > > In MVC, the Validators seem to be more of a middle ground issue. Since > the Model contains the business logic and is fed data to process and > the controller merely acts as waystation back and forth from view to > model, it would seem to me that there should almost be another letter > in MVC since validation doesn't really fit anywhere. > > However, it would seem to me that a Validation function would be > placed in the model itself. Since the view should only query the model > to get its current state and accept the user input, it seems it should > not be in the View to promote modularity. {myModel.dataIsValid == true} > > Because what if you wanted to add another View to the application?? > (As the OP mentioned) Seems to me like it would be malformed in the View. > > Hmmmm... Perhaps MVCV - ;) > __._,_.___ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com SPONSORED LINKS Software development tool Software development Software development services Home design software Software development company Your email settings: Individual Email|Traditional Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___