For opening closing, there is a treeState property of the tree model
that stores the expanded/collapsed paths of the tree. These paths are
made up of indexes (not node IDs - be careful on this one, it is not
documented anywhere) that are zero based.

So the tree (assuming A is the root node)

A
 B
   C
 D
   E

Would have expanded 0 (A), 0:0 (A, B), and 0:1 (A, D).

The default tree state simple remembers these paths and as it is
rendering, looks at these to determine which are expanded and which
are collapsed.

Hope that helps with 1-4

-Andrew

On 5/31/06, Hans Sowa <[EMAIL PROTECTED]> wrote:
Hi Sean

I guess I could solve the #5 with checkboxes and an attribute "selected" for
every node so it should not be a problem.

But I don't know how I can solve #1 to #4. I tried but I didn't work. So is
there a example around where I can have a look or a description about this
topic.

Thanks.

best regards


On 5/30/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> Tree2 basically can do everything but #5.  With some work I'm sure #5
> would be possible although I can't say that I would find it very
> useful.  You would need a submit button to tell the tree component
> that you are done selecting.  Otherwise how would the component handle
> your selections?  Seems awkward.
>
> Sean
>
> On 5/29/06, Hans Sowa < [EMAIL PROTECTED]> wrote:
> > So, I always get an error-message If I try to send to
> > [EMAIL PROTECTED] This is my last try:
> >
> > Hi Andrew
> >
> > Here are the points which I hade/have problems:
> > 1) The possibility to close the whole tree.
> > 2) The possibility to open a certain path.
> > 3) If the tree is created the first time we would like to open the first
> > level.
> > 4) The possiblity to close the last path if the user opens an other
path.
> > (This means only one path should open at any time and all other paths
should
> > be closed).
> > 5) Multiselect should work. (Maybe with checkboxes).
> > 6) The created HTML code should be as small as possible. (I don't think
if
> > this is really possible but it is not so important for me yet).
> >
> > The really important thinks for me are 1,2, 3 and 4.
> >
> > Becuase of 5) I think this should work with checkboxes without any
problems
> > but I had not try it so far.
> >
> > Because of 6) The created HTML Code is really to much. I saw a .NET Tree
> > from a colleague and the created code are really small. So it would be
great
> > if the tree2 could make a diet for the future.
> >
> > So, it would be great if I could help for this items.
> >
> > Thanks in advance.
> >
> > best regards Hans
> >
> >
> > On 5/26/06, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> > > A good thought, but not always very practical. If there are a lot of
> > > visible nodes, and the visible nodes have a lot of children, the
> > > performance would be really bad. With the work Jacob and others are
> > > doing on the Avatar front, an AJAX request to get the nodes could take
> > > milliseconds, so the user wouldn't really notice it.
> > >
> > > Perhaps we can make sure that someone could extend the tree and do
> > > this if they want under specific circumstances where they know it
> > > would work.
> > >
> > > -Andrew
> > >
> > > On 5/25/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> > > > Here's something to think about in your free time.  I was thinking
> > > > that all nodes one level below all visible closed nodes should be
> > > > buffered and made visible instanly via DHTML.  Then an AJAX request
> > > > goes out and creates a buffer for the nodes below the one you just
> > > > opened.  It should be as fast as client side toggle that way but
> > > > without the overhead of tens of thousands of nodes in your DOM that
> > > > never get shown anyways.
> > > >
> > > > Sean
> > > >
> > > > On 5/25/06, Andrew Robinson < [EMAIL PROTECTED]> wrote:
> > > > > Will do, just may be a month or two before I have time for some
open
> > > > > source development.
> > > > >
> > > > > On 5/25/06, Sean Schofield < [EMAIL PROTECTED]> wrote:
> > > > > > I'm definitely interested in adding AJAX support to tree2.
Perhaps
> > > > > > you would like to help me with it?  As a starting point you
should
> > > > > > familiarize yourself with the realtively new TreeWalker stuff if
you
> > > > > > are not already.
> > > > > >
> > > > > > My thinking with the TreeWalker is that it will ultimately be
easier
> > > > > > to render a portion of the Tree during AJAX requests b/c you can
> > > > > > specify a start and end point, etc.  Let me know how serious you
are
> > > > > > about helping and I can make some time for it.
> > > > > >
> > > > > > Sean
> > > > > >
> > > > > > On 5/25/06, Andrew Robinson < [EMAIL PROTECTED]>
wrote:
> > > > > > > I have used AjaxAnywhere and put a <aa:zoneJSF> tag around the
> > tree.
> > > > > > > With the Ajax4Jsf library getting some press, it would be
> > interesting
> > > > > > > to see how to make tree2 have AJAX support built in, or to
create
> > a
> > > > > > > new tree component that extends or is similar to tree2 that
would
> > > > > > > support AJAX natively.
> > > > > > >
> > > > > > > I have avoided non-JSF AJAX solutions (like DOJO integration?)
as
> > I
> > > > > > > want the full JSF lifecycle (no hacks) and AjaxAnywhere
supports
> > it
> > > > > > > (and it looks from the website that Ajax4Jsf does as well -
and
> > does
> > > > > > > it better).
> > > > > > >
> > > > > > > Who knows, maybe we can scrounge up a team of volunteers to
> > integrate
> > > > > > > Ajax4Jsf into some new Tomahawk and/or Sandbox components.
Once I
> > get
> > > > > > > some of the projects I am working on, on the side, done I may
be
> > > > > > > interested in looking into this (too bad writing open source
code
> > > > > > > doesn't pay well - or at all).
> > > > > > >
> > > > > > > -Andrew
> > > > > > >
> > > > > > > PS - I think we need a tax amendment in the US to get tax
breaks
> > for
> > > > > > > open source development
> > > > > > >
> > > > > > > On 5/25/06, Vesa Lindfors <[EMAIL PROTECTED]> wrote:
> > > > > > > >
> > > > > > > > We have also used tree2 successfully, with more or less
similar
> > requirements - but only for small trees  (<100 nodes)
> > > > > > > >  In the near future we will also need tree for quite large
> > amount of data (> 10 000 nodes).
> > > > > > > >  Andrew, it would be very usefully, if you could share some
of
> > your knowledge of combining the tree2 and Ajax...
> > > > > > > >  Or is there any known plans to add ajax support directly to
the
> > MyFaces tree2 component?
> > > > > > > >  ---VLi---
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On 5/24/06, Andrew Robinson <[EMAIL PROTECTED]>
> > wrote:
> > > > > > > > >  What is the problem(s) with tree2? I have been using it
with
> > the
> > > > > > > > > functionality you requested. The only I find myself doing
is
> > using
> > > > > > > > > server side nodes most of the time (with AJAX, as I have
trees
> > with >
> > > > > > > > > 100,000 nodes), and I usually create custom tree models
and
> > custom
> > > > > > > > > tree nodes as the "Base" ones don't ever have what I need.
> > Perhaps we
> > > > > > > > > can help you through your tree2 problems?
> > > > > > > > >
> > > > > > > > > -Andrew
> > > > > > > > >
> > > > > > > > > On 5/24/06, Hansjörg Meuschel <[EMAIL PROTECTED] > wrote:
> > > > > > > > > > Hi
> > > > > > > > > > you could take a look at http://www.ourfaces.net or
> > > > > > > > > >
> >
http://www.jamesholmes.com/JavaServerFaces/#software-comp
> > (a list of jsf
> > > > > > > > > > comp.)
> > > > > > > > > > I'm not sure if there is a tree meeting your
requirements
> > ...
> > > > > > > > > >
> > > > > > > > > > maybe this helps...
> > > > > > > > > > greets hans
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Hans Sowa wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi all
> > > > > > > > > > >
> > > > > > > > > > > We had a lot of problems with the tree2 component and
we
> > search now
> > > > > > > > > > > for an alternative. The tree component is the most
> > important component
> > > > > > > > > > > in our webapplication and therefore this is a big risk
in
> > our
> > > > > > > > > > > application.
> > > > > > > > > > >
> > > > > > > > > > > Following behaviour to we need:
> > > > > > > > > > > - The possibility to klick on every node and to be
able to
> > react
> > > > > > > > > > > (ActionListener).
> > > > > > > > > > > - The possibility to show graphics on the right side
of
> > the node.
> > > > > > > > > > > - The possibility to close the whole tree.
> > > > > > > > > > > - The possibility to open a certain path.
> > > > > > > > > > > - The possiblity to close the last path if the user
opens
> > an other
> > > > > > > > > > > path. (This means only one path should open at any
time
> > and all other
> > > > > > > > > > > paths should be closed).
> > > > > > > > > > > - Multiselect should work. (Maybe with checkboxes).
> > > > > > > > > > > - The created HTML code should be as small as
possible.
> > > > > > > > > > > - If the tree is created the first time we would like
to
> > open the
> > > > > > > > > > > first level.
> > > > > > > > > > >
> > > > > > > > > > > It would be great if someone has experience with an
other
> > tree
> > > > > > > > > > > component and could help me.
> > > > > > > > > > >
> > > > > > > > > > > Thanks in advance.
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > mfg Hans Sowa
> > > > > > > > > > > mailto: [EMAIL PROTECTED] <mailto:
[EMAIL PROTECTED]>
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> >
> > mfg Hans Sowa
> > mailto:[EMAIL PROTECTED]
>



--

mfg Hans Sowa
mailto:[EMAIL PROTECTED]

Reply via email to