> From: Jesse Erlbaum [mailto:[EMAIL PROTECTED]] > Sent: 06 June 2002 23:21 > To: 'Jeff'; [EMAIL PROTECTED]
>> All in all, the additions that led to MVP do not seem particularly >> applicable to web development - it seems to me that a simplified MVC >> may work better here. Do others concur? > > YES! I would agree whole-heartedly. As I said in my first message on > this thread, a pattern is not a panacea. Practical, useful solutions > are rarely "academically correct". > > Let's not get caught up in "pattern-for-pattern's sake" thinking here. If > an aspect of someone else's idea (and that's all patterns like MVC are -- > someone else's idea!), then TOSS IT! Jettison. Use what works and throw > out the rest. Jesse, I see your assertions, and may agree with them, but I am interested to know specifically WHY you think MVC might be more appropriate than MVP, and what parts of MVP are actually [!]cool-for-web concepts. Call me old fashioned, but when I see that a large community of folks have obviously invested much thought and effort into the original Smalltalk MVC and then into MVP. I am reluctant to throw out the baby until I am sure that the water is cold! I too like a 'use what works' approach, but tempered with a bit of 'softly slowly lookee feelee', especially when it comes to fundamental design and approach 8-) Regards Jeff
