Stefano Mazzocchi wrote: >giacomo wrote: > >>You can have a look at it using http://fw.otego.com/demoshop/ >> > >If we enter the 'pet shop' marketing arena, we might find ourselves >having to fight J2EE from one side and .NET from the other. > >*this* is exactly the marketing and technical pressure that I don't >think we can affort to stand at this very moment. > Can you clarify/expand on that? My plan is to do a series of what I call "petshop" like apps. Not in the Microsoft vs Sun performance jingo, but just sample apps that show a complete picture of how to use Cocoon for specific things. For starters: a website (I chose an auction website), two reports (why even to Excel :-). My intention is to document the pieces of Cocoon (call them blocks if you like), and the so-called "best-practices" for using them in building these sample apps. As a whole the principal problem with adopting Cocoon, is that once you read all the documentation, you're still not sure what it does. Once you figure out what it does, you're still not sure what things to use. Once you figure out what things to use (become familiar with a subset), you're still not sure how to do it.
Talk is cheap, actually showing it in use with all sources and the such and comprehensible documentation to go along with it will go a longer way in "marketing" Cocoon than "Marketing" ever could. I envision a "petshop example" (in the original context) plus howto for a set of high level use cases "how do I do a webapp", "a report", "a web service", "a portal" .... etc etc. Perhaps "petshop example" has taken on a new connotation with the recent .NET hype and we should call it "usage example" or something less loaded. -Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
