Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 11004 invoked by uid 500); 16 Jul 2002 07:38:27 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 10993 invoked from network); 16 Jul 2002 07:38:26 -0000 Message-ID: From: Piroumian Konstantin To: "'cocoon-dev@xml.apache.org'" Subject: RE: [RT] Cocoon Integration Model Date: Tue, 16 Jul 2002 11:39:58 +0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="koi8-r" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > From: TREGAN Fabien [mailto:Fabien.TREGAN@airbus.com] > > > > >* 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: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org