You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by tsvetelin <ts...@rushmore-digital.com> on 2003/09/05 09:24:13 UTC
new Tree release
Hi Simon,
>I'm using it right now and I had to change it to work with Tapestry 3.0
You mean that you are using Tapestry 2.3, are you? If you take to use the
latest Tacos-Tree it is ported to Tapestry 3.0 so I think you will not have
a problem with Tapestry 3.0.
>When do you think the new Tree release will be available?
Here are few things :
1. The first one is when the Tree will be added to contrib library. To be
done this it is required to be changed the package names and to be added ASL
agreements. From my point of view the fear value is in the Tapestry 3.1
release. Yesterday was a vote for "Tapestry release 3.0-beta-3" in
developers mailing list and I am not familiar to add it in this release
because the Tree could have some problems (related to refactoring).
2. The second thing is when will be made the things from my last post. I
expect to be done ASAP (in release 3.1 too). But I see a little problem of
developing the dynamic tree node loading (using XML) because at this time I
don't know a JavaScript XML parser with license familiar to ASL. Does
someone know such JavaScript XML parser? The decision could be: I know a
parser with GPL/LGPL license so this part of the tree could be made as a
part to Tacos-Tree project but will use the Tree component/engine from
contrib library.
Tsvetelin.
-----Original Message-----
From: Simon Raveh [mailto:Simon.Raveh@nominum.com]
Sent: Thursday, September 04, 2003 9:00 PM
To: Tapestry users
Subject: RE: Sortable TreeTable
Hi Tsvetelin,
When do you think the new Tree release will be available?
I'm using it right now and I had to change it to work with Tapestry 3.0
Thanks Simon
-----Original Message-----
From: tsvetelin [mailto:tsvetelin.saykov@rushmore-digital.com]
Sent: Thursday, September 04, 2003 1:41 AM
To: Tapestry users; dcg@fixed.com
Subject: RE: Sortable TreeTable
Hi Fermin,
A long time ago I have thinking about the reducing the server calls and I
here is my view:
1. Defining the XML schema that describe the data for particular tree
element(node, row).
2. Defining the TreeService that will return the XML document. The service
will be invoked when the "open node" event occur. The service will update
the ITreeStateModel with the new open node too.
3. After receiving the XML data(information for children) for particular
node the JavaScript will pars the XML and dynamically will insert the new
nodes (rows). To be done this we should have a JavaScript XML parser. I know
a few implementations but they don't have appropriate license to ASL.
4. When the particular node will be selected then the request to the server
will be made. This is required because in case when we have a application
like "Explorer"- tree in left and table in right side of view. So when the
selected node is changed in the tree, the table should be refreshed.
Using this approach we will take the following benefits:
1. The page size (on the first loading) will be small.
2. The server calls will be reduced. Because only on first time when the
node is opened the call to the service will be invoked.
Tsvetelin.
P.S.
Please could you sent to me your implementation. I really would like to see
your stuff. At this time I am refactoring the tree(pakcage changes,
implementation improvements) because the tree will part of the contrib
library in the next tapestry release. So it will be very nice if we have
additional Tree presentations like TableTree.
-----Original Message-----
From: F. Da Costa Gomez [mailto:dcg@fixed.com]
Sent: Thursday, September 04, 2003 12:42 AM
To: Tapestry users
Subject: Sortable TreeTable
Hi,
This post is probably most interesting to Mb & tsvetelin for it concerns
both the Table and the Tree (or TreeTable)
Just finished the first version of a sortable TreeTable.
The Dynamic part is generated by Tapestry but the client stuff is taken
care of by using JS.
It can probably be improved upon but this version does the following.
- Basic html is quite simple (only some additional tbody tags required)
- Using css to put some sex-appeal to it
- NO incremental loading yet so probably there should be no more than
500-1000 rows in the structure for now
- NO server roundtripping on opening or closing nodes
- Allows for *any* type of cell (link, edit, checkbox etc). Just have to
check the dropdown.
- Sorting is done on the whole column leaving the structure of the tree
intact (only the lowest level leafs are sorted)
Decided on this approach because I did not want to start roundtripping
to much to the server if it can also be handled on the client.
For me this is esp easy because I work with a hidden JS lib on the
client. So keeping stuff and status(ses) there is no worries.
If there is any interest I'll post the stuff otherwise I won't bother.
Cheers,
Fermin DCG
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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
RE: new Tree release
Posted by Simon Raveh <Si...@nominum.com>.
Actually I d use Tapestry 3.0 beta-2 but I guess I don't have the latest
release of the Tacos-Tree because in the simple tree example you are using
"field-binding" which is no longer supported.
Simon
-----Original Message-----
From: tsvetelin [mailto:tsvetelin.saykov@rushmore-digital.com]
Sent: Friday, September 05, 2003 12:24 AM
To: Tapestry users
Subject: new Tree release
Hi Simon,
>I'm using it right now and I had to change it to work with Tapestry 3.0
You mean that you are using Tapestry 2.3, are you? If you take to use the
latest Tacos-Tree it is ported to Tapestry 3.0 so I think you will not have
a problem with Tapestry 3.0.
>When do you think the new Tree release will be available?
Here are few things :
1. The first one is when the Tree will be added to contrib library. To be
done this it is required to be changed the package names and to be added ASL
agreements. From my point of view the fear value is in the Tapestry 3.1
release. Yesterday was a vote for "Tapestry release 3.0-beta-3" in
developers mailing list and I am not familiar to add it in this release
because the Tree could have some problems (related to refactoring).
2. The second thing is when will be made the things from my last post. I
expect to be done ASAP (in release 3.1 too). But I see a little problem of
developing the dynamic tree node loading (using XML) because at this time I
don't know a JavaScript XML parser with license familiar to ASL. Does
someone know such JavaScript XML parser? The decision could be: I know a
parser with GPL/LGPL license so this part of the tree could be made as a
part to Tacos-Tree project but will use the Tree component/engine from
contrib library.
Tsvetelin.
-----Original Message-----
From: Simon Raveh [mailto:Simon.Raveh@nominum.com]
Sent: Thursday, September 04, 2003 9:00 PM
To: Tapestry users
Subject: RE: Sortable TreeTable
Hi Tsvetelin,
When do you think the new Tree release will be available?
I'm using it right now and I had to change it to work with Tapestry 3.0
Thanks Simon
-----Original Message-----
From: tsvetelin [mailto:tsvetelin.saykov@rushmore-digital.com]
Sent: Thursday, September 04, 2003 1:41 AM
To: Tapestry users; dcg@fixed.com
Subject: RE: Sortable TreeTable
Hi Fermin,
A long time ago I have thinking about the reducing the server calls and I
here is my view:
1. Defining the XML schema that describe the data for particular tree
element(node, row).
2. Defining the TreeService that will return the XML document. The service
will be invoked when the "open node" event occur. The service will update
the ITreeStateModel with the new open node too.
3. After receiving the XML data(information for children) for particular
node the JavaScript will pars the XML and dynamically will insert the new
nodes (rows). To be done this we should have a JavaScript XML parser. I know
a few implementations but they don't have appropriate license to ASL.
4. When the particular node will be selected then the request to the server
will be made. This is required because in case when we have a application
like "Explorer"- tree in left and table in right side of view. So when the
selected node is changed in the tree, the table should be refreshed.
Using this approach we will take the following benefits:
1. The page size (on the first loading) will be small.
2. The server calls will be reduced. Because only on first time when the
node is opened the call to the service will be invoked.
Tsvetelin.
P.S.
Please could you sent to me your implementation. I really would like to see
your stuff. At this time I am refactoring the tree(pakcage changes,
implementation improvements) because the tree will part of the contrib
library in the next tapestry release. So it will be very nice if we have
additional Tree presentations like TableTree.
-----Original Message-----
From: F. Da Costa Gomez [mailto:dcg@fixed.com]
Sent: Thursday, September 04, 2003 12:42 AM
To: Tapestry users
Subject: Sortable TreeTable
Hi,
This post is probably most interesting to Mb & tsvetelin for it concerns
both the Table and the Tree (or TreeTable)
Just finished the first version of a sortable TreeTable.
The Dynamic part is generated by Tapestry but the client stuff is taken
care of by using JS.
It can probably be improved upon but this version does the following.
- Basic html is quite simple (only some additional tbody tags required)
- Using css to put some sex-appeal to it
- NO incremental loading yet so probably there should be no more than
500-1000 rows in the structure for now
- NO server roundtripping on opening or closing nodes
- Allows for *any* type of cell (link, edit, checkbox etc). Just have to
check the dropdown.
- Sorting is done on the whole column leaving the structure of the tree
intact (only the lowest level leafs are sorted)
Decided on this approach because I did not want to start roundtripping
to much to the server if it can also be handled on the client.
For me this is esp easy because I work with a hidden JS lib on the
client. So keeping stuff and status(ses) there is no worries.
If there is any interest I'll post the stuff otherwise I won't bother.
Cheers,
Fermin DCG
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org