Hi Michael, thanks, you're right, experience with other technologies can be misleading when learning a new one, especially when the two things are not the same kind. The hint on ComponentPageElement sounds really promising! I will study this, and will come back my results!
Thanks again! Cheers, janos On 16/04/2008, Michael Gerzabek <[EMAIL PROTECTED]> wrote: > > Hi János, > > In your very first mail 2 days ago you say "I'm new to Tapestry technology > and to this mailing list". I think though I played around with T5 quite some > time I'm also new to it. So please don't take my word to be the final truth. > I think there is a simple solution to your problem. Look into > ComponentPageElement [1]. You can get it via PagePool that you Inject into > your page. > > I also suggest to look into the docs on the concepts of T5. They are quite > well documented and VERY powerful. I say this because I realized that > applying thinking patterns originated in the past (JSP, Struts, etc.) might > not be as helpful in learning a new technology than reading and applying the > actual docs are. Speaking from my own experiences here. > > Regards, > Michael > > [1] > http://tapestry.formos.com/nightly/tapestry5/apidocs/org/apache/tapestry/internal/structure/ComponentPageElement.html > > I would suggest before you go into in-depth application writing > > Jarecsni schrieb: > > > And one really last thing :) I had a shallow look at wicket to check > > this > > feature... There should be some common unconscious conceptual path here, > > as > > wicket too misses this. All it has is an Include component to include > > non-wicket (! :D) content. Why these frameworks are so much reluctant to > > this? :) > > > > J > > > > On 16/04/2008, János Jarecsni <[EMAIL PROTECTED]> wrote: > > > > > > > One more thing... although Tapestry is component oriented (which is a > > > goood thing :)), this kind of flexibility (dynamic template > > > generation) > > > which is available in JSP is an essential feature to be really > > > flexible. A > > > templating framework should allow this level of redirection, or > > > abstraction, > > > that the templates are dynamically produced driven by runtime > > > conditions or > > > configuration. Otherwise we get a very intelligent and elegant HTML > > > (in > > > terms of this kind of staticness). Sorry for the lengthy arguing, but > > > I > > > think this issue is vital for Tapestry too (not just me :)) > > > > > > Cheers, > > > Janos > > > > > > On 16/04/2008, János Jarecsni <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Yes, I felt this too :) However, this is no special usage scenario I > > > > would say, just a bit different usage pattern that calls for a > > > > different > > > > approach. As I see now, the Tapestry framework is well suited to > > > > sites, > > > > where the user travels from Login to Browse items from there to > > > > Shopping > > > > cart and so on. This from a.tml to b.tml from b.tml to c.tml. > > > > > > > > This approach is somewhat clumsy when it comes to a portal-like > > > > scenario > > > > where there is no longer a "browse items" "page" but rather the user > > > > is > > > > manipulating components (like clicking on a voter component to show > > > > the > > > > results or clicking on a "top 10 news" component to load one news > > > > into the > > > > "workspace area"). Here the notion of a "page" is no longer really > > > > meaningful. What you have is a few templates (which specify the > > > > layout and > > > > design) and you'd like to manipulate (load and manage state of) > > > > components > > > > dynamically. > > > > > > > > I hope I could make my approach clear enough :) > > > > > > > > Cheers, > > > > Janos > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
