Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Content-Type: text/plain;
  charset="koi8-r"
From: Torsten Curdt <tcurdt@dff.st>
Organization: dff internet & medien
To: cocoon-dev@xml.apache.org
Subject: Re: new W3C xforms 1.0 draft - changes affect cocoon xforms
 implementation
Date: Thu, 22 Aug 2002 17:17:10 +0200
User-Agent: KMail/1.4.1
References: <B6352CB87AA70442A1C6F49E6B658C9801EFBD@POSTMAN.flagship.ru>
 <3D64ECB3.7050308@bristol.ac.uk>
In-Reply-To: <3D64ECB3.7050308@bristol.ac.uk>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200208221717.10854.tcurdt@dff.st>

On Thursday 22 August 2002 15:52, Simon Price wrote:
> Piroumian Konstantin wrote:
> >>From: Simon Price [mailto:simon.price@bristol.ac.uk]
> >>
> >>There's a new "XForms 1.0, W3C Working Draft 21 August 2002" that
> >>changes the names of some of the elements plus other minor changes.
> >>Cocoon 2.1 might want to use the new names (eg. selectOne -> select1,
> >>selectMany -> select)?
> >
> > Hm... selectOne -> select1 ?! Isn't it a typo?
> >
> > If not then, IMHO, it's much better to have something like
> > 'singleSelect', 'multiSelect'.
> >
> > Konstantin
>
> I think you're right but its probably a good idea to keep as close to
> the xforms standards as possible - even if "select1" sucks as a name ;-=
)

(Thousands of dicussions later) I still see no reason for that...
=2E..we are *NOT* implementing xforms because it's not ment to be impleme=
nted=20
for server side techniques (although chiba does quite a good job on it...=
)

I wouldn't care about the new spec...
--
Torsten

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org