Sean,
I think all the features from your proposal can be implemented based on the current tree component. I will not stop you from starting your tree component from scratch, but with some refactorings and extensions we can get the current tree to support client-side node expansion or facets with less effort. What do you think?
Oliver
Sean Schofield wrote:
Could be nice. I'll probably focus on getting the basic tree down
first though. One thought that occurred to me is that we might want
to rename the component so that we can check into CVS as we go along. That way users don't have to wait forever until the final version with
all of the features is done in order to use it. Then we could phase
out the old tree.
Just a thought. I'm interested to hear what Oliver and others have to say on that.
sean
On Fri, 28 Jan 2005 15:16:06 -0600, Heath Borders
<[EMAIL PROTECTED]> wrote:
I would definitely use this.
It would be nice if we had multiple selection for nodes.
Sort of like having the tree extend UISelectOne or UISelectMany.
Thoughts?
On Fri, 28 Jan 2005 16:09:29 -0500, Sean Schofield
<[EMAIL PROTECTED]> wrote:
My coworker and I have developed an excellent tree component to run in Struts as a TilesController. Its basically already a component although its not JSF compliant. We are planning on porting it over to JSF and I've been in talks with Oliver (the original tree component author) about how best to go about this.
IMO there are several areas where the current version of tree component is lacking. The biggest problem for us is that it has no javascript and requires contact with the server everytime you open a node. The second is that its difficult to provide specific customization of the icons at various levels.
So far, the plan would be for me to write a new tree component from scratch. I will incorporate the ideas of the existing tree component when possible. Initially it would only function with javascript, but then either myself or Oliver will add the server-side expansion functionality. Once this is all done, we would replace the existing tree component with the new and improved one.
I'm hoping to get a discussion going on this and solicit some feedback on our approach. I am going to post a follow up email in a few minutes detailing my proposal.
sean
-- -Heath Borders-Wing [EMAIL PROTECTED]
-- Oliver Rossmueller Software Engineer and IT-Consultant Hamburg, Germany http://www.rossmueller.com
