Great! If you have a working solution for issue #2 i would be pleased to hear about it. Would be interesting to me how you have solved it.
However, you have made me the idea of extending our ppr solution in a way that we can say: Take a js event and bind it to a dom node which is located inside a ppr group. Through fireing the event the partial page inside the ppr group section is updated. Sounds very useful to me, if there is some time at the end of the day i will investigate some work on it. regards, Gerald On 10/10/06, John Ruffin <[EMAIL PROTECTED]> wrote:
Note to self: use a current build :-). Things look good now. John Ruffin wrote: > > I'm using snapshot1.1.4 which I built awhile back. I'll build the latest. > > Hopefully, issue #1 will go away as demo'ed on in your example. Even the > example built from the snapshot1.1.4 only contains the snippet and not the > selected value in the input textbox. > > Yes, I think I can resolve issue #2 with <a4j:support> or something > similar. > > Thanks. I'll build the latest. > > Gerald Müllan wrote: >> >> Hi, >> >> are you using latest version of this component? >> >> On our examples page [1], i cannot reproduce your first mentioned issue. >> All the dom nodes are updated with the full value, when hovering the >> columns with cursor or clicking on them. >> >> ad second issue; This is not the usecase the component was originally >> designed for. Just fetching some correspondig values and putting them >> to some dom nodes in order to reduce >> needed steps when doing some inputs. >> >> If i understand your usecase, you need some partial page rendering >> mechanism in order to update model values behind the dom nodes to >> which the values where pushed. >> >> Currently this does not work with this component in a lonely manner. >> >> In this case, you need some ajax stuff afterwards the values where >> pushed to the dom nodes. In sandbox there is currently PPR (partial >> page rendering) [2] which should do this in future times. Currently it >> does this only with button-clicks, not automatically triggered. >> >> If its really that needed, you ma achieve this approach with ajax >> frameworks like ajax4jsf. >> >> cheers, >> >> Gerald >> >> [1] http://example.irian.at/example-sandbox-20061010/tableSuggestAjax.jsf >> [2] http://example.irian.at/example-sandbox-20061010/pprPanelGroup.jsf >> >> On 10/10/06, John Ruffin <[EMAIL PROTECTED]> wrote: >>> >>> I've successfully added s:tableSuggestAjax to a page and it displays the >>> given table rows and columns. >>> >>> What I think I want to do is: when a column is clicked I want to update >>> the >>> value of the inputTextBox. It currently only contains the snippet used >>> for >>> the suggestedItemsMethod. >>> >>> Also, I want to use t:updateActionListener to set the selected object to >>> a >>> backing bean attribute. >>> >>> Problem is: when I put a commandLink around the s:outputText - the data >>> doesn't display. >>> >>> Question is: how are you using s:tableSuggestAjax and what/how do you >>> update >>> things when a row is selected? >>> -- >>> View this message in context: >>> http://www.nabble.com/s%3AtableSuggestAjax-next-step--tf2417654.html#a6739537 >>> Sent from the MyFaces - Users mailing list archive at Nabble.com. >>> >>> >> >> >> -- >> http://www.irian.at >> >> Your JSF powerhouse - >> JSF Consulting, Development and >> Courses in English and German >> >> Professional Support for Apache MyFaces >> >> > > Note to self -- View this message in context: http://www.nabble.com/s%3AtableSuggestAjax-next-step--tf2417654.html#a6743989 Sent from the MyFaces - Users mailing list archive at Nabble.com.
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
