Sure, I agree, as of now Tree component can only live on its own page or in a pop-up(?). Why not just AJAX-enable the exsisting component ? Then it could coexsist with other forms on a page and user wouldnt have to wait for all that javascript being downloaded to his browser :). I dont if there is a performace issue in thoose javascript-trees. No more talk about cross browser combabillity either.
Another DHTML tree is from treeview.net, seems there is no license. but has not released since 2003(changes were made in 2004). You can even prepend checkboxes. qooxdoo gifs has remarkeble similarities with the gifs used in konqueror in my KDE :) /Frank B. Kastell On Tuesday 19 July 2005 17:23, Eelco Hillenius wrote: > We can start anew :) > > Basically, we can conclude that Tree works basically, but that it is not > very usefull for embedding in forms yet. To be usefull, it has to be a > Javascript tree, that doesn't do roundtrips all the time. Actually, it > would be perfect if it is ajax enabled too, so that you generate > roundtrips when you select a node without having to update your whole > form/ page. > > With 1.1/ HEAD, we can now create such javascript enabled components (no > ajax yet, though we're working on that too). The only thing left to do > now is to actually build the basterd. > > I wouldn't like to build a javascript/ DHTML tree from scratch, but > rather reuse a good one. From the trees I found, I like the Qooxdoo tree > (http://qooxdoo.sourceforge.net/build/public/test/user/Tree_1.html) best. > > On the Java side of things, we need to have another tree class (either > extending from Tree or from AbstractTree), which contributes any > javascript/ css references to the header, and which writes out the > initialization code nescesary for the tree. Which in the case of the > Qooxdoo tree looks like: > > root = t; > var te1 = new QxTreeFolder("Desktop", "icons/16/desktop.png", > "icons/16/desktop.png"); t.add(te1); > desktop = te1; > var te1_1 = new QxTreeFolder("Eigene Dateien"); > var te1_2 = new QxTreeFolder("Arbeitsplatz"); > var te1_3 = new QxTreeFolder("Netzwerkumgebung"); > var te1_4 = new QxTreeFolder("Papierkorb"); > te1.add(te1_1, te1_2, te1_3, te1_4); > var te1_2_1 = new QxTreeFile("Windows (C:)", > "icons/16/blockdevice.png"); var te1_2_2 = new QxTreeFile("Dokumente (D:)", > "icons/16/blockdevice.png"); > > > Any people having experience with DHTML tree's? Would Qooxdoo be a good > choice? > > Regards, > > Eelco > > frank bengtsson wrote: > >Hello, > > > >I cant find the thread[nodepanel] were we discussing javasctipt > > implementation of the tree component ?? > > > >/Frank > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user -- Frank Kastell Bengtsson Kastell ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
