Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [CForms] Tree widget based on XML document
Date: Mon, 19 Jun 2006 11:56:29 +0200
Message-ID: <A955EA1F8FE31749AEC8C998082F6C7C8F4D15@hai01.hippo.local>
Thread-Topic: [CForms] Tree widget based on XML document
Thread-Index: AcaStjKePwbvhFEuTEqrJ+qRaQO4VAAz8tXQ
From: "Martijn C. Vos" <m.vos@hippo.nl>
To: <dev@cocoon.apache.org>


Bruno Dumon [mailto:bruno@outerthought.org] wrote:
>=20
> > I think Cocoon only needs one tree model and that is a tree=20
> > model based on
> > XML. The selection-list widget has the possibility to=20
> > declare static content
> > in the form definition and can also refer to an xml=20
> > document in the src
> > attribute. Something like that would be nice for the tree widget.
>=20
> I don't see why the tree widget should be limited to XML models only,
> the selection list isn't limited to that either (see e.g. the jxpath
> selection list). Dictating to use XML would again require needless
> conversions from Java to XML when it is not needed.

I don't think it should necessarily be the only one, but it
definitely should be the default tree. Everything can be converted
to XML, and Cocoon is designed around XML. The only reason to use
something else is to skip a conversion step and save a bit of
time, but unlike the current trees, a good XML tree can do anything.


mcv.