Right. Again, that's pretty much what I described as option 1. My issue is that if I'm already indicating that an error ocurred by adding a result to the event, wouldn't it be nice if I could use that same metadata later in my view, rather than having to add yet another value into my event? It just seems like unnecessary duplication.
Sent from my iPhone On 2009-11-21, at 9:05 AM, Chris Blackwell <[email protected]> wrote: > I totally agree you don't want to have to search through controllers > to find error messages, i was simplifying for sake of the example. > Its very easy to put all your messages (error or otherwise) into a > config file and either have the controller grab the right one, or > set an error code which the view can then lookup. > > Chris > > 2009/11/21 Bob Silverberg <[email protected]> > Responses to two emails inline below: > > On Sat, Nov 21, 2009 at 6:42 AM, Chris Blackwell <[email protected]> > wrote: > maybe i'm missing something, but I just have my controller set an > error message into the event before adding my "EmailNotFound" > result. Then my password reminder form can simply check if there's > an error message to display. > > > That is another approach that would work, but I'd prefer to keep any > display specific code out of my controller, and keep it encapsulated > in my view. I don't want to have to edit a controller to change an > error message. So that really leads me back to option 1, which is > similar to what you suggest, but rather than setting an error > message in the controller, I'd just be setting a value into the > event which I would then check in my view. > > Again, as this "result checking" mechanism does not currently exist, > are there any other ways that people are dealing with this? > > -- > Bob Silverberg > www.silverwareconsulting.com > -- > Model-Glue Sites: > Home Page: http://www.model-glue.com > Documentation: http://docs.model-glue.com > Bug Tracker: http://bugs.model-glue.com > Blog: http://www.model-glue.com/blog > > You received this message because you are subscribed to the Google > Groups "model-glue" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/model-glue?hl=en > > -- > Model-Glue Sites: > Home Page: http://www.model-glue.com > Documentation: http://docs.model-glue.com > Bug Tracker: http://bugs.model-glue.com > Blog: http://www.model-glue.com/blog > > You received this message because you are subscribed to the Google > Groups "model-glue" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/model-glue?hl=en -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/model-glue?hl=en
