> > >Another reason for a PetStore style cocoon app is that it is a simple >concept that people can wrap their heads around. One thing that we >can do is provide a cookie cutter style web store. All you have to do >is change the skin and you can open up shop. Cocoon can do this >far better than JPetStore. > > While I agree, that is a seperate issue. A best practices example should be seperate from a cookie cutter app.
The issue being, you need many of these to serve as an example to those in other domains, where if you take a domain that everyone is familiar with (relatively) like an e-bay type thing or an amazon type thing, you'll be able to explain the concepts driving cocoon without creating domain experts. Bottom line, I've been working on this example app for a little while and am nearly complete. I plan to donate that cocoon with a live site actually using it with a different skin. Others are welcome to set up their own auction site with it of course. I plan to create a piece of documentation like the "blueprints" and hope to collaborate with others on this to refactor it into "true" best practices. (Right now its the best I could deduce which means there are places that it could be better. .. I couldn't make hide nor hair of database actions for instance with the current state of the documentation.) >Things like chess engines while definitely more entertaining aren't >going to show the average user how to get up and running with Cocoon >for real needs. It also shows that we should be considered a novelty, >and not considered seriously--which is definitely not the message I >want put forth. > > Totally agree with you there. Oracle did that with Oracle forms and it was a totally useless example. -Andy > > >>-----Original Message----- >>From: Anthony W. Marino [mailto:[EMAIL PROTECTED]] >>Sent: Tuesday, July 16, 2002 7:41 AM >>To: [EMAIL PROTECTED]; Piroumian Konstantin; >>'[EMAIL PROTECTED]' >>Subject: Re: [RT] Cocoon Integration Model >> >> >>My $0.02 is: >>A ) Create a Cocoon version of PetStore (XPetStore?) app >>similar to what >>JPetStore ( http://www.ibatis.com/jpetstore/jpetstore.html ) >>has done. This >>gives developers insight into the capabilities of Cocoon in a >>digestable >>manner. >> >>B ) In order for Cocoon to make it in a huge way I believe >>that there needs to >>be buy-in from business entities (Mgmt types). With that >>said, I would >>prefer to see some sort of business problem domain tackled. >>Possibly a CRM >>app with pda capabilites. >> >>Anthony >> >> >> >> >> >>>>From: TREGAN Fabien [mailto:[EMAIL PROTECTED]] >>>> >>>> >>><snip what="very useful suggestions" /> >>> >>> >>> >>>>>* Insert your own idea here. >>>>> >>>>> >>>>I've always thought that a Chess Webbapp would demonstrate Cocoon >>>>power : -It has complexe application logic (you can check the >>>>validity of a move, >>>>you can get the whole state of the board from an XML db on >>>>only get 1 move >>>>and calculate the new board. I think that a standard XML >>>>allready exists for >>>>this) >>>>-SVG will display the board >>>>-Abstraction layer would allow to use differents rules (I >>>>like Go more than >>>>Chess :) >>>>-We can make PDF report of the game with all moves in text >>>>format + pictures >>>>of the board after strategic moves. >>>>-We can use the same presentation component with a game >>>>database or with an >>>>an inline multiplayer Chess client. >>>>-It's more fun than a screw-shop sample. >>>> >>>> >>>I've been working on a gaming site a few years ago and if we had >>>Cocoon that time our job would be much easier, cause we had >>> >>> >>to format >> >> >>>our games to fit different browsers resolutions, including WebTV >>>(544px width), WebGate (576px), etc. >>> >>>Although your idea is very interesting, I don't think that >>> >>> >>writing a >> >> >>>Chess engine will be of any fun and it will be too complex for a >>>demonstration application. >>> >>>IMO, the application should be business oriented, e.g. Banking, >>>Billing, CRM, Reporting or so. We can questionnairre users >>> >>> >>to see what >> >> >>>is the most needed use-case. >>> >>>Konstantin >>> >>> >>> >>>>fabien. >>>> >>>> >>>> >>>> >>>> >>-------------------------------------------------------------------- >> >> >>>>- >>>>To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>For additional commands, email: [EMAIL PROTECTED] >>>> >>>> >>> >>> >>--------------------------------------------------------------------- >> >> >>>To unsubscribe, e-mail: [EMAIL PROTECTED] >>>For additional commands, email: [EMAIL PROTECTED] >>> >>> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, email: [EMAIL PROTECTED] >> >> >> > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, email: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
