Here is another case...
I can set up listener handlers easily via template.
In
JAVA, I have to become on keyboard tapestry and determine what the
proper "javascript:... ()" notation is for the rendering output... and
hope it will work? ID's ? guesswork? Sorry.... nah uh.
I am
seeing that in order to have "listener:edit" handlers then THAT is
suppose to be in a template so that it gets processed by tapestry
properly.
Best regards
Ken in nashua
Best regards
Ken in nashua
From: [EMAIL PROTECTED]
To: users@tapestry.apache.org
Subject: RE: Combined Component Model - Is it supported ?
Date: Mon, 1 Oct 2007 09:41:38 -0400
I am assuming I cannot render the following directly from JAVA... as it will be
output as just that text... and uninterpretted?
Can someone clarify what I can and cannot do in the JAVA with regard to
template like text? I do not know if it will be interpretted along the request
pipeline and processed.... or whether it will be spit out as-is.
<div jwcid="[EMAIL PROTECTED]"
collectionType="ognl:collectionType"
tableSize="3">
<span jwcid="@RenderBody"/>
</div>
Best regards
Ken in nashua
From: [EMAIL PROTECTED]
To: users@tapestry.apache.org
Subject: RE: Combined Component Model - Is it supported ?
Date: Mon, 1 Oct 2007 09:37:49 -0400
If it means anything... I am designing a Gallery.HTML here is my component
layout...
----------------------
auto-paging
----------------------
content
----------------------
auto-paging
----------------------
1. auto-paging just operates auto-paging buttons top/bottom just like
contrib:table AND both instances are anchored to the same instance
2. content is just a collection
Parameters for CONTENT:
o tableSize - overrides default getcontentBox().width layout and forces
scrollable number of rows in the Gallery equal to the tableSize
Parameters for AUTO-PAGING
o begin - pages to front of collection
o prev - pages to previous fittable amount of collection
o next - pages to next fittable amount of collection
o end - pages to end of collection
I intend to operate the persistence of the auto-paging parameters using JSON.
I'd like to retain the layout of these components using templates.
So I need JSON, Rendering overrides and listener handlers plus simplified
layouts using templates... COMBINED.
Thanks for your feedback.
Best regards
Ken in nashua
From: [EMAIL PROTECTED]
To: users@tapestry.apache.org
Subject: Combined Component Model - Is it supported ?
Date: Mon, 1 Oct 2007 09:14:37 -0400
Folks... per doc text that follows...
1. Components that inherit from BaseComponent will use an HTML template.
2. Components that inherit from AbstractComponent will render output in Java
code, by implementing method renderComponent() .
I would like to build a component that operates combined semantics... or at
least option 2 supporting the manipulation/usage of templates within JAVA.
Option 1 only supports handlers not necessarily rendering + JSON.
WHY? Some component templates are lengthy and I would not like to implement all
that rendering in the JAVA as it is too cluttered/cumbersome. Plus some
components are best fit in just a template and others are better fit in JAVA...
I have a component anatomy a bit complex that requires everything and I want to
distribute the implementation efficiently across both models.
Can tapestry-4.1.2 deliver?
If I commit to model #1 then I end up missing what I need. Same if I commit to
model #2. I need both.
Your feedback is appreciated.
Best regards
Ken in nashua
Discover the new Windows Vista Learn more!
Invite your mail contacts to join your friends list with Windows Live Spaces.
It's easy! Try it!
Explore the seven wonders of the world Learn more!
_________________________________________________________________
Discover the new Windows Vista
http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE
