I could say, i am trying to have one View with many different Logics.
Now this logic can be nicely encapsulated inside the pages(java
classes), having their state, their data and their business rules. The
other way would of course be to encapsulate logic in some other classes,
but then i would have to manage their states manually, which does not
look elegant.
So if i have these many Pages(java classes), extending AbstractPage to
some point, i can only invoke them using many html files, no matter what
components they have inside. I already managed to do that, but that
involved using Hivemind to override few core Tapestry Framework classes,
and also did not look elegant..
Mark Stang wrote:
Have you tried "RenderBlock"? Or a Choose? You seem to have one page and want
to have different views within that one page.
Does that sound like what you are trying to do? Or do you have many pages and
want to re-use components across those pages?
Or do you have "real" tapestry components?
-----Original Message-----
From: news on behalf of Nerijus Areska
Sent: Fri 8/4/2006 9:44 AM
To: [email protected]
Subject: Re: Single HTML, many Pages
i AM encapsulating this in Pages, if i would choose components, i would
still have separate component for each entity. Which leaves with the
similar problem, you cannot have many component java files, and one
component html
Jesse Kuhnert wrote:
Have you tried encapsulating these other sections of logic into
"components"
?
On 8/4/06, Nerijus Areska <[EMAIL PROTECTED]> wrote:
Hello all,
i've stumbled upon %subject% problem. I am writing some CRUD for
myself, and soon noticed, i have too many identical html's like
ViewStudents.html, ViewGroups.html. Since only thing they got in them is
some component call, i decided to have one and only html probably
named ViewRecords.html. I will still have many .java files, where data
definitions and custom logic will reside.
Now there i found out, that Tapestry won't load a page at all, if it has
no html or specification. SpecificationResolverDelegate and
TemplateSourceDelegate are really not a sollution, because
ViewRecords.html is ON the filesystem, and CAN be loaded by Tapestry.
All i want to do is to "redirect" some of my html files to some of
others.
Nerijus
---------------------------------------------------------------------
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]