Return-Path: Delivered-To: apmail-xml-general-archive@xml.apache.org Received: (qmail 16383 invoked by uid 500); 20 Dec 2001 00:06:35 -0000 Mailing-List: contact general-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: general@xml.apache.org Delivered-To: mailing list general@xml.apache.org Received: (qmail 16218 invoked from network); 20 Dec 2001 00:06:34 -0000 Content-Type: text/plain; charset="iso-8859-1" From: David Crossley Reply-To: crossley@indexgeo.com.au To: cocoon-dev@xml.apache.org Subject: Re: [OT] Design Rant Date: Thu, 20 Dec 2001 11:06:54 +1100 X-Mailer: KMail [version 1.2] References: In-Reply-To: Cc: general@xml.apache.org MIME-Version: 1.0 Message-Id: <01122011065403.01064@igacer> Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N John Morrison wrote: > > > Ugo Cei wrote: > > > In other words, what I am proposing is that we stop worrying about being > > > bacward compatible in order to accomodate old, buggy and non-compliant > > > user agents, but instead start to be FORWARD compatible in order to > > > accomodate FUTURE standard-compliant user agents. > > > > > > Let me know what you think about it and sorry for being slightly OT. > > If we are using a live Cocoon then we can select different views > based on the browser no? > J. I was wondering this too - we need to use Cocoon's own capabilities to solve these very real issues. There was a thread on this, but it went quiet. The discussion came around to "why is Cocoon not generating the content on the xml.apache.org/cocoon/ site". [Vote] Improving Cocoon Site http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=100765145112325&w=2 --------------------------------------------------------------------- In case of troubles, e-mail: webmaster@xml.apache.org To unsubscribe, e-mail: general-unsubscribe@xml.apache.org For additional commands, e-mail: general-help@xml.apache.org