Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (nike.apache.org: domain of mario@ops.co.at designates
 194.152.182.1 as permitted sender)
Message-ID: <47A8205B.8070506@ops.co.at>
Date: Tue, 05 Feb 2008 09:37:47 +0100
From: Mario Ivankovits <mario@ops.co.at>
User-Agent: Thunderbird 2.0.0.0 (X11/20070418)
MIME-Version: 1.0
To: MyFaces Development <dev@myfaces.apache.org>
Subject: Re: Interest in an AjaxTree
References: <15258543.post@talk.nabble.com>
 <47A6A9C9.8030506@ops.co.at>	 <15275226.post@talk.nabble.com>
	 <71235db40802041134x4764e456tb88568002d0954e1@mail.gmail.com>
 <311295120802050029p6bf31f64g5abaf944fdb5994b@mail.gmail.com>
In-Reply-To: <311295120802050029p6bf31f64g5abaf944fdb5994b@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Matt!

>> welcome tree3;
>>     
>
> Matthias is right. What are the differences to the existing tree2 component?
>   
Having tree2 enhanced to do ajaxed-node-fetching would greatly increase
the chance that your patch will be accepted. We really would like to
avoid to introduce yet another tree. Do you at least use the TreeModel
of tree2?
Else it would be a no-go for me.

> Tree2 can also be extended easily via existing ajax frameworks.
>   
Just that you can't have this ajaxed-node-fetching which would be really
a nice feature I often whished to have.
Yes, you can put tree2 in a ppr group (which I already did), but you
have to fetch the whole tree in node toggling, no?


Ciao,
Mario