Matthias, I can try - although I still have to decide whether to stay with Trinidad or not, and basically I know nothing about Tomahawk internals.
It was fairly surprising to spend a week to include Trinidad in an already working project, without actually using any of its component, just to discover that there is no way to have it running as it is. And a fairly simple application: a tree, a data table, a few buttons.
On the other way I feel attracted by promising features of Trinidad, such as skinning, dialogs, ppr, etc. But I'm also feeling that mixing up with Tomahawk is a kind of thin-ice skating game.
-- Renzo

Matthias Wessendorf wrote:
Renzo,

perhaps you can help out and provide a fix for Tomahawk 777 ?

thx,
Matthias

On 12/22/06, Renzo Tomaselli <[EMAIL PROTECTED]> wrote:

 Adam,
     thanks, indeed now I found the Tomhawk-777 jira. No way till they fix
it, my only chance to stay with Trinidad is to rewrite my dataTable stuff
through Trinidad-equivalent tr:table.
 The dataTable is by far one of mostly used components, can I expect
equivalent functionalities in tr:table ? This is an overlapping area: did
anybody compare ?
 Thanks -- Renzo


 Adam Winer wrote:
If I remember correctly, this is a bug in dataScroller - it assumes
 behavior of CommandLinkRenderer that is not at all guaranteed,
 in terms of encodeBegin()/encodeChildren()/encodeEnd() and
where
 all the content gets written.

 -- Adam


 On 12/21/06, Renzo Tomaselli <[EMAIL PROTECTED]> wrote:


  Hi, I wonder if anybody succeeded in getting dataScroller working under
 Trinidad. Mine doesn't work anymore since I updated my web.xml to Trinidad
 stuff.
 A dataScroller such as:

 <t:dataScroller id="resultScroller"   actionListener="#{
 resultBean.paginator}" ....>

 having a facet such as:

 <f:facet name="next">
     <h:panelGroup rendered="true">
         <h:commandButton value="#{msg['result.scroller.next']}"
 styleClass="nextPrevious" action=""/>
         <t:graphicImage url=""
 style="border: 1px""/>
  </h:panelGroup>
 </f:facet>

 is rendered as:

 <input id="_id50:result:_id409" name="_id50:result:_id409" type="submit"
 value="next"


 class="nextPrevious">
 <img src="" style="border: 1px">
 <a id="_id50:result:resultScrollernext"
 name="_id50:result:resultScrollernext"


                 class="OraLink" href=""></a>

 the image element has no "onclick" attribute anymore, thus is not active,
 unlike the non-Trinidad version.
 Furthermore, "next" button submits, but result is not as before (I'm still
 investigating about this).
 Any idea ?
 Thanks -- Renzo






Reply via email to