RE: Best practices: inheritance

2005-07-12 Thread Joel Trunick
e- From: Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 12, 2005 9:56 AM To: Tapestry users Subject: Re: Best practices: inheritance Darío Vasconcelos wrote: >Thanks for your responses, > >I noticed that in Tapestry in Action, Howard uses inheritance very >often, ie the ToDo

Re: Best practices: inheritance

2005-07-12 Thread Davor Hrg
I'm not sure if I understand it well, but would you consider introducing an parameter (ExternalService) that tells you which part of the query to display ? On 7/12/05, Robert <[EMAIL PROTECTED]> wrote: > > Darío Vasconcelos wrote: > > >Thanks for your responses, > > > >I noticed that in Tapestr

Re: Best practices: inheritance

2005-07-12 Thread Robert
Darío Vasconcelos wrote: Thanks for your responses, I noticed that in Tapestry in Action, Howard uses inheritance very often, ie the ToDo examples. While it sounds like a desirable approach, I still can't force my mind to think in terms of page hierarchies. That's the reason why I asked this qu

Re: Best practices: inheritance

2005-07-12 Thread Dirk Dittert
Darío Vasconcelos <[EMAIL PROTECTED]> wrote: > I noticed that in Tapestry in Action, Howard uses inheritance very > often, ie the ToDo examples. While it sounds like a desirable > approach, I still can't force my mind to think in terms of page > hierarchies. That's the reason why I asked this ques

Re: Best practices: inheritance

2005-07-11 Thread Darío Vasconcelos
Sorry, forgot to thank Jeff for the great tip. Using the same .page file is another trick I was wondering about... On 7/11/05, Darío Vasconcelos <[EMAIL PROTECTED]> wrote: > Thanks for your responses, > > my guess is that I should build one component that will render the > dynamic part of the pag

Re: Best practices: inheritance

2005-07-11 Thread Darío Vasconcelos
Thanks for your responses, my guess is that I should build one component that will render the dynamic part of the pages (it has the same appearance in all of them), ant this component will receive a parameter to specify the name of the SQL sentence that will feed it. This way, I can use the same c

Re: Best practices: inheritance

2005-07-11 Thread Pablo Ruggia
If your java classes will look equals, then just create only one java class and reference it from all your .page files. If you have some logic, then create a super class and extend it when you need it. You should subclass only for things like data, security, logic, etc. For same titlte, layout,

Re: Best practices: inheritance

2005-07-11 Thread jeff emminger
i believe you can map multiple page names to one file in your .application e.g. so whatever "Page" is requested, the same class and template is reused. Darío Vasconcelos wrote: Hi, I have a burning question in my mind: suppose I have 10 pages that have the same basic layout: some titles a

Best practices: inheritance

2005-07-11 Thread Darío Vasconcelos
Hi, I have a burning question in my mind: suppose I have 10 pages that have the same basic layout: some titles and a table containing the results from some DB query. Now, I know I can use the power of Tapestry to build components out of my 10 pages and that would save me a lot of effort. My questi