Teaman wrote:
Then it's not really a wiki. You've made it a blog posting (article).

Well, no ... and if that's what you want to see in these you're certainly free to add that in there yourself. I'm just saying *I'm* not going to do it because I don't see it as necessary. We don't block anyone from editing the wiki.

Any time comments can be injected to clarify something, it's helpful.
I'm not suggesting that what is in the primer be rewritten as in
starting over.  I'm suggesting adding to it.

And by all means feel free to do that--your experience and what you're going through with all of this is important, and I'd prefer not to speak for you on the wiki since I look at this very differently than you do.

Diving into code is too specific for what I mean by "guidance" or
"directions".

Totally disagree--without talking in terms of code we're just spitting in the wind.

I think I'm more comforatable with Adam's approach at this point.
Have a validation component that checks the form data and puts the
errors in an array. Then pass that via the event obj to the view.
That's where I'm headed.

Great! Thanks for jumping in Adam.

I'm familiar with the event obj.  Just want to confirm there's not
some other mechanism for passing data around.

Nope, it's all about the event object.

I'll have to check that out. Thanks again for all your time.

And I appreciate the back and forth as well. I'll start working on the type of newbie documentation we've been discussing as I have time.

--
Matt Woodward
[email protected]
http://www.mattwoodward.com/blog

Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to