One the one hand, when newer users get stuck, it will be simpler to have unified solutions.
On the other hand, we may end up with avalon components signing guestbooks. ( A little overkill )
What I would love to see is all of the examples and ideas that are in place now, but maybe with a
*best practice* flag. Having said that, my vote has to go on A. I just spend too much time figuring out "how" to do something rather than doing it :)
-----Original Message-----
From: David Leangen [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 04, 2004 12:56 AM
To: [EMAIL PROTECTED]
Subject: Vote: to unify, or not to unify (Was "RE: Business Logic in Cocoon
Applications?")
***********************************************************
[ X ] A. I think that we should show users the "best" way to get up and running with Cocoon.
[ ] B. I think that we should show users all the options possible and let them decide the best approach.
[ ] C. Yeah, whatever. Either way is good for me. Peace, man!
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
