You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Neil Clayton <ne...@cloudnine.net.nz> on 2003/06/05 00:33:56 UTC
Tree Components (and the Misko Hevery TreeComponent)
What are people using for a tree type component these days? In early
January I was using the component written by Misko Hevery, which I'm not
entirely sure is available or being maintained anymore.
I've got the code to this component, and have made a few changes to it.
Long (or actually, short :-) - I would like to see a good tree component
added to the standard Tapestry distribution (time for all you experts to
tell me that one exists already and I can't see it / have not found it !!!)
Regards
Neil Clayton
Re: Tacos-Tree Component
Posted by "F. Da Costa Gomez" <dc...@fixed.com>.
Hi,
See y'r back. Hope you had an ok holiday.
Got the tree working in the way we discussed.
So I would love to send you a copy to check its usefulness but guess
what? Switch to 3.0 stuffed me up completely.
First I am going to go back to 2.4-a5 have a close look again and then
send it 2u.
Sound ok?
Cheers,
Fermin DCG
btw, I also figuredout how to traverse with cursorkeys cheaply (not
implemented yet though)
tsvetelin wrote:
>Hi,
>
>Nail wrote:
>
>
>>Don't spend time on the weekend trying to fix this for me! I'm not asking
>>
>>
>for
>
>
>>a fix. I'm really just enquiring as to whether or not the components was
>>written from the start using only frames - as that would explain the way it
>>is presented currently. I'm positive it's not too hard to change, such
>>
>>
>that
>
>
>>it can be used in a non-frames based environment.
>>
>>
>
>I agree with you - the body is not required in TreeComponent. The tree was
>designed as a component that should be used in non freme environment. In the
>version for Tapetry 2.3 the TreeView doesn't contains Body but it has appear
>in TreeView after I commit the tree in the tacos project. I will try to
>remove it.
>
>
>
>Best regarts
>Tsvetelin
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
>
>
Tacos-Tree Component
Posted by tsvetelin <ts...@rushmore-digital.com>.
Hi,
Nail wrote:
>Don't spend time on the weekend trying to fix this for me! I'm not asking
for
>a fix. I'm really just enquiring as to whether or not the components was
>written from the start using only frames - as that would explain the way it
>is presented currently. I'm positive it's not too hard to change, such
that
>it can be used in a non-frames based environment.
I agree with you - the body is not required in TreeComponent. The tree was
designed as a component that should be used in non freme environment. In the
version for Tapetry 2.3 the TreeView doesn't contains Body but it has appear
in TreeView after I commit the tree in the tacos project. I will try to
remove it.
Best regarts
Tsvetelin
Re: Tree Components (and the Misko Hevery TreeComponent)
Posted by Neil Clayton <ne...@cloudnine.net.nz>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I figure if you're using this in a frames based environment, then yes, it will
probably work. HAving said that, I've never ever used Tapestry in a "frames
way", so I'm not 100% certain.
However; I'm making the assumption that a Page gets rendered into a Frame, and
that your tree component is one of these pages. That is, that the only
component you render into one of your frames is the TreeView.
I say this because the template starts with:
// javascript stuff
<jwc id="body">
<h1>Tree Test Home Page</h1>
...
as you can see, there is a body component there. The specification binds Body
to the jwcid==body. (<component id="body" type="Body"/>)
Im using the tree a different way: I have a single page, with many other
components. The page is highlly nested - lots of coponents inside other
components. One of the components I want to show is the tree. However; due
to the single page type nature of the layout, there is already a Shell, Body
and Form wrapping the TreeView component.
Therefore: Boom.
Don't spend time on the weekend trying to fix this for me! I'm not asking for
a fix. I'm really just enquiring as to whether or not the components was
written from the start using only frames - as that would explain the way it
is presented currently. I'm positive it's not too hard to change, such that
it can be used in a non-frames based environment.
I've fired off a message off to Tsvetelin with a similar question. I'll post
the answer here when I get one :-0
Neil
On Thursday 05 Jun 2003 10:34 pm, F. Da Costa Gomez wrote:
> HI,
>
> Tell u what, I quickly grabbed the files I thought were relevant.
> Of the top I can't remember doing anything funny at all (maybe the thing
> shouldn't work at all, but it does 8-) ).
>
> I will still go through the whole and clean up during the weekend but i
> figured maybe it can be of use to you anyway?
>
> Lemme know how u go.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+370iLXcfQF3yrNoRAjbhAJ9qiTEpcWto48kQSYpF9McGXgKQuACgyIBK
dYAIdqx4djvGJ9iPieaEJII=
=UdIA
-----END PGP SIGNATURE-----
Re: Tree Components (and the Misko Hevery TreeComponent)
Posted by "F. Da Costa Gomez" <dc...@fixed.com>.
HI,
Tell u what, I quickly grabbed the files I thought were relevant.
Of the top I can't remember doing anything funny at all (maybe the thing
shouldn't work at all, but it does 8-) ).
I will still go through the whole and clean up during the weekend but i
figured maybe it can be of use to you anyway?
Lemme know how u go.
Cheers,
Fermin DCG
Neil Clayton wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Righteo then ... the source HTML to TreeView has a @Body tag (this is from
>memory, I hope it is called TreeView - I think it is).
>
>from what I understand so far, this is the root component, which you need to
>provide a model (which includes both state and data). The TreeView component
>is the one that inserts the appropriate Javascript into the rendered page.
>
>When you include this component inside a page which already has a Body
>component, you get an exception.
>
>I'm not using frames at all. This is a single page, where the TreeView is
>simply another component nested alongside other components.
>
>Neil
>
>
>
Re: Tree Components (and the Misko Hevery TreeComponent)
Posted by Neil Clayton <ne...@cloudnine.net.nz>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Righteo then ... the source HTML to TreeView has a @Body tag (this is from
memory, I hope it is called TreeView - I think it is).
from what I understand so far, this is the root component, which you need to
provide a model (which includes both state and data). The TreeView component
is the one that inserts the appropriate Javascript into the rendered page.
When you include this component inside a page which already has a Body
component, you get an exception.
I'm not using frames at all. This is a single page, where the TreeView is
simply another component nested alongside other components.
Neil
On Thursday 05 Jun 2003 9:41 pm, F. Da Costa Gomez wrote:
> Whoah dude,
>
> Basically I modded some little bits and pieces. The only real work were
> the node renderer and the state-model.
> Also changed the script somewhat to muck about a bit with hashtables.
> Can't remember doing anything semi-smart to the html code though.
>
> So, what do you exactly mean by: "How do you use it INSIDE an existing
> Body tag"
> I'm using the tree within a popup or a frame (for now that is). Maybe
> thats the reason why I'm not folowing exactly?
>
> Tell ye what though.
> 2Mrow I have to be present at a wedding :-( so I'll try to clean the
> code up a bit over the weekend and post the src to the list (wish
> tsvetelin was back already so he could he a look as well).
>
> Cheers,
> Fermin DCG
>
> Neil Clayton wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >Great.
> >
> >I'm using it to present the source(s) and destination(s) for a backup
> >application, whereby each location can have rules associated with it. I
> > could do this with other UI components, but I like trees and it feels
> > natural.
> >
> >One question tho:
> >How do you use it INSIDE an existing Body tag? The TreeView (which also
> >contains the script component) has it's own, and it is not possibe in
> >Tapestry to nest body components....
> >
> >also the build.xml appears to build an incorrect jar - did you find this
> > as well?
> >
> >Neil
> >
> >On Thursday 05 Jun 2003 11:41 am, F. Da Costa Gomez wrote:
> >>Hi,
> >>
> >>Y'r abs right, it does work quite well.
> >>Dunno what y'll be using it for but I've just finished (or almost at
> >>least) making the thing selectable.
> >>Meaning? a checkbox next to every node so that a user can do 'check'
> >>(uncheck).
> >>Since less traffic is better I had to implement some additional js as
> >>well make sure that the server is only hit when a branch node is clicked.
> >>In order to 'remember what had been selected (and possibly hidden from
> >>sight again) I had to expand the state-model to incorporate a 'checked
> >>or not' memory.
> >>Actual 'checked' processing takes place on submission of the tree to a
> >>listener (this is when the whole thing gets processed for the goal the
> >>tree is being used). Again, this saves a lot of rendering and traffic.
> >>Also prepping the thing to include cursorkey-navigation (got some js
> >>snippets but still have to add them, nice to have).
> >>
> >>Done all that so there is only one thing left and that is updating the
> >>originating page with the results fromm the tree.
> >>Again, dunno what your aim is but if you got an idea on it plz don't
> >>hesitate.
> >>
> >>Cheers,
> >>Fermin DCG
> >>
> >>btw. Wanna get the code checked by tsvetelin prior to 'handing' it to
> >>tacos 'official like'.
> >>
> >>Neil Clayton wrote:
> >>>-----BEGIN PGP SIGNED MESSAGE-----
> >>>Hash: SHA1
> >>>
> >>>I did a while ago (before deciding to use Miskos one), and it didn't
> >>>render properly on Mozilla. Upon trying it again I see it does. Upon
> >>>looking at the code I see it has a much better data and state model.
> >>>
> >>>sold to the man in the green shirt.
> >>>
> >>>does anyone know why it's not part of the standard contrib of Tapestry?
> >>>
> >>>Neil
> >>>
> >>>On Wednesday 04 Jun 2003 11:50 pm, Shantanu Deo wrote:
> >>>>have you tried the tacos-tree component yet ?
> >>>>
> >>>>There is Tree component implementation that is part of tacos project:
> >>>>http://tacos.sourceforge.net/tacos-tree
> >>>>There are 2 simple demos too (please visit a
> >>>>http://tree.rushmore-register.com/tree for file system demo).
> >>>
> >>>-----BEGIN PGP SIGNATURE-----
> >>>Version: GnuPG v1.0.7 (GNU/Linux)
> >>>
> >>>iD8DBQE+3xdxLXcfQF3yrNoRAtk4AKCkJ2U7g6isQkwMoySIgXYiIliXwACeO4F0
> >>>HrfMrnHgAsgzGaVLhPPJk/0=
> >>>=12/x
> >>>-----END PGP SIGNATURE-----
> >>>
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> >>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >- --
> >Regards,
> >Neil Clayton
> >
> >(PS: If you see strange text you don't understand underneath my email,
> > don't worry - it's just my PGP signature)
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG v1.0.7 (GNU/Linux)
> >
> >iD8DBQE+36eyLXcfQF3yrNoRAuuZAKCFqa0tYZaRpEg9bjwkiNSWYhJyZwCfcBHV
> >5ZuUmF0agwkxqCtGl9E3HaA=
> >=4Ry4
> >-----END PGP SIGNATURE-----
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
- --
Regards,
Neil Clayton
(PS: If you see strange text you don't understand underneath my email, don't
worry - it's just my PGP signature)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+37P+LXcfQF3yrNoRAuaYAKCsTx2L4bzStmOpKHiFvor4oeRKzQCgxWx4
FoV+3qD3ycb0yGsF7JMgdhU=
=hPaQ
-----END PGP SIGNATURE-----
Re: Tree Components (and the Misko Hevery TreeComponent)
Posted by "F. Da Costa Gomez" <dc...@fixed.com>.
Whoah dude,
Basically I modded some little bits and pieces. The only real work were
the node renderer and the state-model.
Also changed the script somewhat to muck about a bit with hashtables.
Can't remember doing anything semi-smart to the html code though.
So, what do you exactly mean by: "How do you use it INSIDE an existing
Body tag"
I'm using the tree within a popup or a frame (for now that is). Maybe
thats the reason why I'm not folowing exactly?
Tell ye what though.
2Mrow I have to be present at a wedding :-( so I'll try to clean the
code up a bit over the weekend and post the src to the list (wish
tsvetelin was back already so he could he a look as well).
Cheers,
Fermin DCG
Neil Clayton wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Great.
>
>I'm using it to present the source(s) and destination(s) for a backup
>application, whereby each location can have rules associated with it. I could
>do this with other UI components, but I like trees and it feels natural.
>
>One question tho:
>How do you use it INSIDE an existing Body tag? The TreeView (which also
>contains the script component) has it's own, and it is not possibe in
>Tapestry to nest body components....
>
>also the build.xml appears to build an incorrect jar - did you find this as
>well?
>
>Neil
>
>On Thursday 05 Jun 2003 11:41 am, F. Da Costa Gomez wrote:
>
>
>>Hi,
>>
>>Y'r abs right, it does work quite well.
>>Dunno what y'll be using it for but I've just finished (or almost at
>>least) making the thing selectable.
>>Meaning? a checkbox next to every node so that a user can do 'check'
>>(uncheck).
>>Since less traffic is better I had to implement some additional js as
>>well make sure that the server is only hit when a branch node is clicked.
>>In order to 'remember what had been selected (and possibly hidden from
>>sight again) I had to expand the state-model to incorporate a 'checked
>>or not' memory.
>>Actual 'checked' processing takes place on submission of the tree to a
>>listener (this is when the whole thing gets processed for the goal the
>>tree is being used). Again, this saves a lot of rendering and traffic.
>>Also prepping the thing to include cursorkey-navigation (got some js
>>snippets but still have to add them, nice to have).
>>
>>Done all that so there is only one thing left and that is updating the
>>originating page with the results fromm the tree.
>>Again, dunno what your aim is but if you got an idea on it plz don't
>>hesitate.
>>
>>Cheers,
>>Fermin DCG
>>
>>btw. Wanna get the code checked by tsvetelin prior to 'handing' it to
>>tacos 'official like'.
>>
>>Neil Clayton wrote:
>>
>>
>>>-----BEGIN PGP SIGNED MESSAGE-----
>>>Hash: SHA1
>>>
>>>I did a while ago (before deciding to use Miskos one), and it didn't
>>>render properly on Mozilla. Upon trying it again I see it does. Upon
>>>looking at the code I see it has a much better data and state model.
>>>
>>>sold to the man in the green shirt.
>>>
>>>does anyone know why it's not part of the standard contrib of Tapestry?
>>>
>>>Neil
>>>
>>>On Wednesday 04 Jun 2003 11:50 pm, Shantanu Deo wrote:
>>>
>>>
>>>>have you tried the tacos-tree component yet ?
>>>>
>>>>There is Tree component implementation that is part of tacos project:
>>>>http://tacos.sourceforge.net/tacos-tree
>>>>There are 2 simple demos too (please visit a
>>>>http://tree.rushmore-register.com/tree for file system demo).
>>>>
>>>>
>>>-----BEGIN PGP SIGNATURE-----
>>>Version: GnuPG v1.0.7 (GNU/Linux)
>>>
>>>iD8DBQE+3xdxLXcfQF3yrNoRAtk4AKCkJ2U7g6isQkwMoySIgXYiIliXwACeO4F0
>>>HrfMrnHgAsgzGaVLhPPJk/0=
>>>=12/x
>>>-----END PGP SIGNATURE-----
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>
>- --
>Regards,
>Neil Clayton
>
>(PS: If you see strange text you don't understand underneath my email, don't
>worry - it's just my PGP signature)
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.0.7 (GNU/Linux)
>
>iD8DBQE+36eyLXcfQF3yrNoRAuuZAKCFqa0tYZaRpEg9bjwkiNSWYhJyZwCfcBHV
>5ZuUmF0agwkxqCtGl9E3HaA=
>=4Ry4
>-----END PGP SIGNATURE-----
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
>
>
>
Re: Tree Components (and the Misko Hevery TreeComponent)
Posted by Neil Clayton <ne...@cloudnine.net.nz>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Great.
I'm using it to present the source(s) and destination(s) for a backup
application, whereby each location can have rules associated with it. I could
do this with other UI components, but I like trees and it feels natural.
One question tho:
How do you use it INSIDE an existing Body tag? The TreeView (which also
contains the script component) has it's own, and it is not possibe in
Tapestry to nest body components....
also the build.xml appears to build an incorrect jar - did you find this as
well?
Neil
On Thursday 05 Jun 2003 11:41 am, F. Da Costa Gomez wrote:
> Hi,
>
> Y'r abs right, it does work quite well.
> Dunno what y'll be using it for but I've just finished (or almost at
> least) making the thing selectable.
> Meaning? a checkbox next to every node so that a user can do 'check'
> (uncheck).
> Since less traffic is better I had to implement some additional js as
> well make sure that the server is only hit when a branch node is clicked.
> In order to 'remember what had been selected (and possibly hidden from
> sight again) I had to expand the state-model to incorporate a 'checked
> or not' memory.
> Actual 'checked' processing takes place on submission of the tree to a
> listener (this is when the whole thing gets processed for the goal the
> tree is being used). Again, this saves a lot of rendering and traffic.
> Also prepping the thing to include cursorkey-navigation (got some js
> snippets but still have to add them, nice to have).
>
> Done all that so there is only one thing left and that is updating the
> originating page with the results fromm the tree.
> Again, dunno what your aim is but if you got an idea on it plz don't
> hesitate.
>
> Cheers,
> Fermin DCG
>
> btw. Wanna get the code checked by tsvetelin prior to 'handing' it to
> tacos 'official like'.
>
> Neil Clayton wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >I did a while ago (before deciding to use Miskos one), and it didn't
> > render properly on Mozilla. Upon trying it again I see it does. Upon
> > looking at the code I see it has a much better data and state model.
> >
> >sold to the man in the green shirt.
> >
> >does anyone know why it's not part of the standard contrib of Tapestry?
> >
> >Neil
> >
> >On Wednesday 04 Jun 2003 11:50 pm, Shantanu Deo wrote:
> >>have you tried the tacos-tree component yet ?
> >>
> >>There is Tree component implementation that is part of tacos project:
> >>http://tacos.sourceforge.net/tacos-tree
> >>There are 2 simple demos too (please visit a
> >>http://tree.rushmore-register.com/tree for file system demo).
> >
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG v1.0.7 (GNU/Linux)
> >
> >iD8DBQE+3xdxLXcfQF3yrNoRAtk4AKCkJ2U7g6isQkwMoySIgXYiIliXwACeO4F0
> >HrfMrnHgAsgzGaVLhPPJk/0=
> >=12/x
> >-----END PGP SIGNATURE-----
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
- --
Regards,
Neil Clayton
(PS: If you see strange text you don't understand underneath my email, don't
worry - it's just my PGP signature)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+36eyLXcfQF3yrNoRAuuZAKCFqa0tYZaRpEg9bjwkiNSWYhJyZwCfcBHV
5ZuUmF0agwkxqCtGl9E3HaA=
=4Ry4
-----END PGP SIGNATURE-----
Re: Tree Components (and the Misko Hevery TreeComponent)
Posted by "F. Da Costa Gomez" <dc...@fixed.com>.
Hi,
Y'r abs right, it does work quite well.
Dunno what y'll be using it for but I've just finished (or almost at
least) making the thing selectable.
Meaning? a checkbox next to every node so that a user can do 'check'
(uncheck).
Since less traffic is better I had to implement some additional js as
well make sure that the server is only hit when a branch node is clicked.
In order to 'remember what had been selected (and possibly hidden from
sight again) I had to expand the state-model to incorporate a 'checked
or not' memory.
Actual 'checked' processing takes place on submission of the tree to a
listener (this is when the whole thing gets processed for the goal the
tree is being used). Again, this saves a lot of rendering and traffic.
Also prepping the thing to include cursorkey-navigation (got some js
snippets but still have to add them, nice to have).
Done all that so there is only one thing left and that is updating the
originating page with the results fromm the tree.
Again, dunno what your aim is but if you got an idea on it plz don't
hesitate.
Cheers,
Fermin DCG
btw. Wanna get the code checked by tsvetelin prior to 'handing' it to
tacos 'official like'.
Neil Clayton wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>I did a while ago (before deciding to use Miskos one), and it didn't render
>properly on Mozilla. Upon trying it again I see it does. Upon looking at the
>code I see it has a much better data and state model.
>
>sold to the man in the green shirt.
>
>does anyone know why it's not part of the standard contrib of Tapestry?
>
>Neil
>
>On Wednesday 04 Jun 2003 11:50 pm, Shantanu Deo wrote:
>
>
>>have you tried the tacos-tree component yet ?
>>
>>There is Tree component implementation that is part of tacos project:
>>http://tacos.sourceforge.net/tacos-tree
>>There are 2 simple demos too (please visit a
>>http://tree.rushmore-register.com/tree for file system demo).
>>
>>
>>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.0.7 (GNU/Linux)
>
>iD8DBQE+3xdxLXcfQF3yrNoRAtk4AKCkJ2U7g6isQkwMoySIgXYiIliXwACeO4F0
>HrfMrnHgAsgzGaVLhPPJk/0=
>=12/x
>-----END PGP SIGNATURE-----
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
>
>
>
Re: Tree Components (and the Misko Hevery TreeComponent)
Posted by Neil Clayton <ne...@cloudnine.net.nz>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I did a while ago (before deciding to use Miskos one), and it didn't render
properly on Mozilla. Upon trying it again I see it does. Upon looking at the
code I see it has a much better data and state model.
sold to the man in the green shirt.
does anyone know why it's not part of the standard contrib of Tapestry?
Neil
On Wednesday 04 Jun 2003 11:50 pm, Shantanu Deo wrote:
> have you tried the tacos-tree component yet ?
>
> There is Tree component implementation that is part of tacos project:
> http://tacos.sourceforge.net/tacos-tree
> There are 2 simple demos too (please visit a
> http://tree.rushmore-register.com/tree for file system demo).
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+3xdxLXcfQF3yrNoRAtk4AKCkJ2U7g6isQkwMoySIgXYiIliXwACeO4F0
HrfMrnHgAsgzGaVLhPPJk/0=
=12/x
-----END PGP SIGNATURE-----
Re: Tree Components (and the Misko Hevery TreeComponent)
Posted by Shantanu Deo <sh...@elixir-it.com>.
have you tried the tacos-tree component yet ?
There is Tree component implementation that is part of tacos project:
http://tacos.sourceforge.net/tacos-tree
There are 2 simple demos too (please visit a
http://tree.rushmore-register.com/tree for file system demo).
----- Original Message -----
From: "Neil Clayton" <ne...@cloudnine.net.nz>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Wednesday, June 04, 2003 6:33 PM
Subject: Tree Components (and the Misko Hevery TreeComponent)
> What are people using for a tree type component these days? In early
> January I was using the component written by Misko Hevery, which I'm not
> entirely sure is available or being maintained anymore.
>
> I've got the code to this component, and have made a few changes to it.
> Long (or actually, short :-) - I would like to see a good tree component
> added to the standard Tapestry distribution (time for all you experts to
> tell me that one exists already and I can't see it / have not found it
!!!)
>
> Regards
> Neil Clayton
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>