I'm good either way, but the custom component idea seems to be consensus, also if the user doesn't want it they can always leave out the new component.
On Mon, Apr 22, 2013 at 12:38 AM, Thomas Andraschko < [email protected]> wrote: > +1 for the custom component > > > 2013/4/22 Christian Kaltepoth <[email protected]> > > > I like the idea of a custom component because it makes it more explicit > > what the component is used for and perhaps would even provide more > control > > over what is happening. > > > > So +1 for a custom component > > > > > > 2013/4/21 Mark Struberg <[email protected]> > > > > > Gerhard brought up another alternative: simply provide a component > which > > > doesn't render any html but adds the windowhandler.js and stores the > > > component in the ViewRoot. > > > > > > LieGrue, > > > strub > > > > > > > > > > > > > > > ----- Original Message ----- > > > > From: Romain Manni-Bucau <[email protected]> > > > > To: Mark Struberg <[email protected]>; > > > [email protected] > > > > Cc: > > > > Sent: Sunday, 21 April 2013, 20:56 > > > > Subject: Re: windowId postback detection > > > > > > > > 1 sounds easier to track too > > > > Le 21 avr. 2013 18:09, "Mark Struberg" <[email protected]> a > > > > écrit : > > > > > > > >> Hi! > > > >> > > > >> There are technically 2 options for extracting the windowId on > POSTs: > > > >> > > > >> 1.) setting a hidden UIOutput component in the ViewRoot > > > >> > > > >> > > > >> 2.) provide a custom renderkit/ResponseStateManager > > > >> > > > >> I think 1.) is much easier. Any input? > > > >> > > > >> LIeGrue, > > > >> strub > > > >> > > > >> > > > > > > > > > > > > > > > -- > > Christian Kaltepoth > > Blog: http://blog.kaltepoth.de/ > > Twitter: http://twitter.com/chkal > > GitHub: https://github.com/chkal > > > -- Jason Porter http://en.gravatar.com/lightguardjp
