ציטוט Jamie Orchard-Hays:
The syntax to use the tacos PartialLink and Part is really trivial. It's
just a Tapestry component, after all.
Sure, but I had "understanding" in the foreground, not simple syntax...
Cheers..
You should check it out. I'm using it now for shopping cart links. It
makes sense in this situation, because all I want to do is add an item
to the cart, and show it's added ("add to cart" changes to "remove from
cart") but not refresh the page, take the user somewhere else, etc.
Jamie
Ron Piterman wrote:
ציטוט Jamie Orchard-Hays:
I didn't suggest AJAX because it's trendy but because this is a good
situation to use it. AJAX is going to be extremely prevalent in the
coming months and for very good reason: it mitigates the need to
refresh whole pages at once, thus giving the user a much more
rich-client kind of experience.
Sure, I am also very impressed from it, and would like to use it more,
only in this case... well, since its some one who is new to Tapestry,
and I was not sure of the reseblance of the data...
I guess I am a bit traditional when it comes to learning, so I thought
- what dahell - if he is new, he should get started, and prefferably
not by makeing the roof fly...
Cheers,
Ron
Jamie
Ron Piterman wrote:
I disagree with jamie, using Ajax would be a trendy thing, but the
"traditional" solution, which does not require Javascript running,
would be...
Well, it depends on the diversity of the content.
If you can use one component to render all types of content, than
you can use one page, which will have a table. On the right side
there will be three (or more?) DirectLink (or ActionLink ?)
components, which change some property (say "content") of your page.
The right side of the table will contain a component which renders
some java bean which is dependant on the "content" property.
This model is likeley to be used to show, say, different articles:
all are of the same type, and the links just tell the page which one
to show.
If the content of the pages vary and cannot be simply rendered with
the same component, you should create a Border component, which
contains the layout, the links to different pages, and a RenderBody
component instead of the content.
In each page you use this border component, and as its body, you use
components which render to the content. On each page individually...
like that:
border:
<span jwcid="@Shell" title="bla">
<span jwcid="@Body" />
<table><tr>
<td> links ... </td>
<td> <span jwcid="@RenderBody" /> </td>
</tr> </table>
</span>
</span>
page:
<span jwcid="@Border">
page 1
</span>
Note I use the Shell and Body components - if this is strange to
you, use for a start just normal <html><head></><body></></>
Later on you can use them if you need to...
Cheers,
Ron
ציטוט Jamie Orchard-Hays:
So you have this?
link 1 some content
link 2 that renders in one
link 3 area on the right side
If that's what your doing, then this would be a perfect place to
use the tacos AJAX components. Using the PartialLink and the Part
components, you could populate the right side of your page from the
links on the left without refreshing the whole page.
http://tacos.sourceforge.net/
Jamie
Vinicius Caldeira Carvalho wrote:
Hello there! As I'm new to tapestry, I have a page design that is
letting me confused when converting it to a Tapestry page.
The page is very simple, it's a table with 2 columns, the left
column has the links and the right the contents. Pretty much like
a frame page.
My question is, Do I have one page for everthing (I will have a
lot of components) or just one big conteiner that has it all, and
every little "tile" (sorry for the word, too damn used to struts)
is a diferent component (page, html, and java class)???
Thanks
Vinicius
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
