Additional Persist Scope: Window State
Dear Listeners! Our customer needs multiple window/tab support in the application. Due to the current session state limitations for the web I know there is no out-of-the-box support for a window/tab state. I found an interesting article about the possibilities to overcome the problem of the browsers session state and alternative approaches to introduce a window state. I know it is a different framework but the concepts are summarized well;-) http://myfaces.apache.org/orchestra/myfaces-orchestra-core/multiwindow.html An option would be to provide a new persist strategy WindowState next to the current scopes Session, Flash, Client. If we realize such a feature, it should be supported in tapestry core. Can we create a Jira issue for this improvement? Best regards, Gerry
Re: [VOTE] Tapestry 5.3.1
On Sat, Dec 17, 2011 at 8:09 PM, Ulrich Stärk u...@spielviel.de wrote: Just to clarify: releases can't be vetoed, not even by binding PMC votes. As long as there are at least 3 binding +1 votes, it's up to the release manager, i.e. Massimo in this case, to decide whether to bury it or proceed. Thanks for clarifying the process. I agree it's unfortunate that a fix for a problem in 5.3 did not make it into the first bugfix release but that's not a reason to hold up the release. I think I will do 5.3.2 soon and will let 5.3.1 fall apart, hoping to have a quicker vote process... Will everyone agree? Cheers -- Massimo http://meridio.blogspot.com - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: [VOTE] Tapestry 5.3.1
C'mon guys, let's be less bureaucratic. We have a ready to be used release that has a fix for a serious bug (TAP5-1765). Why delaying that if we can ship? Massimo, please let the release pass. Apart from that, we have 3 binding votes (Howard, Uli and me). On Sun, Dec 18, 2011 at 12:13 PM, Massimo Lusetti mluse...@gmail.comwrote: On Sat, Dec 17, 2011 at 8:09 PM, Ulrich Stärk u...@spielviel.de wrote: Just to clarify: releases can't be vetoed, not even by binding PMC votes. As long as there are at least 3 binding +1 votes, it's up to the release manager, i.e. Massimo in this case, to decide whether to bury it or proceed. Thanks for clarifying the process. I agree it's unfortunate that a fix for a problem in 5.3 did not make it into the first bugfix release but that's not a reason to hold up the release. I think I will do 5.3.2 soon and will let 5.3.1 fall apart, hoping to have a quicker vote process... Will everyone agree? Cheers -- Massimo http://meridio.blogspot.com - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org -- Best regards, Igor Drobiazko http://tapestry5.de http://twitter.com/drobiazko
Re: [VOTE] Tapestry 5.3.1
+1 Am So, 18.12.2011, 12:34 schrieb Igor Drobiazko: C'mon guys, let's be less bureaucratic. We have a ready to be used release that has a fix for a serious bug (TAP5-1765). Why delaying that if we can ship? Massimo, please let the release pass. Apart from that, we have 3 binding votes (Howard, Uli and me). On Sun, Dec 18, 2011 at 12:13 PM, Massimo Lusetti mluse...@gmail.comwrote: On Sat, Dec 17, 2011 at 8:09 PM, Ulrich Stärk u...@spielviel.de wrote: Just to clarify: releases can't be vetoed, not even by binding PMC votes. As long as there are at least 3 binding +1 votes, it's up to the release manager, i.e. Massimo in this case, to decide whether to bury it or proceed. Thanks for clarifying the process. I agree it's unfortunate that a fix for a problem in 5.3 did not make it into the first bugfix release but that's not a reason to hold up the release. I think I will do 5.3.2 soon and will let 5.3.1 fall apart, hoping to have a quicker vote process... Will everyone agree? Cheers -- Massimo http://meridio.blogspot.com - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org -- Best regards, Igor Drobiazko http://tapestry5.de http://twitter.com/drobiazko - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: [VOTE] Tapestry 5.3.1
Taha Hafeez: +1(non-binding) BTW, Congrats Massimo !! On Dec 18, 2011, at 5:41 PM, Ulrich Stärk wrote: +1 Am So, 18.12.2011, 12:34 schrieb Igor Drobiazko: C'mon guys, let's be less bureaucratic. We have a ready to be used release that has a fix for a serious bug (TAP5-1765). Why delaying that if we can ship? Massimo, please let the release pass. Apart from that, we have 3 binding votes (Howard, Uli and me). On Sun, Dec 18, 2011 at 12:13 PM, Massimo Lusetti mluse...@gmail.comwrote: On Sat, Dec 17, 2011 at 8:09 PM, Ulrich Stärk u...@spielviel.de wrote: Just to clarify: releases can't be vetoed, not even by binding PMC votes. As long as there are at least 3 binding +1 votes, it's up to the release manager, i.e. Massimo in this case, to decide whether to bury it or proceed. Thanks for clarifying the process. I agree it's unfortunate that a fix for a problem in 5.3 did not make it into the first bugfix release but that's not a reason to hold up the release. I think I will do 5.3.2 soon and will let 5.3.1 fall apart, hoping to have a quicker vote process... Will everyone agree? Cheers -- Massimo http://meridio.blogspot.com - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org -- Best regards, Igor Drobiazko http://tapestry5.de http://twitter.com/drobiazko - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: [VOTE] Tapestry 5.3.1
François Facon: +1(non-binding) well done Massimo. Best. 2011/12/18 Taha Hafeez Siddiqi tawus.tapes...@gmail.com: Taha Hafeez: +1(non-binding) BTW, Congrats Massimo !! On Dec 18, 2011, at 5:41 PM, Ulrich Stärk wrote: +1 Am So, 18.12.2011, 12:34 schrieb Igor Drobiazko: C'mon guys, let's be less bureaucratic. We have a ready to be used release that has a fix for a serious bug (TAP5-1765). Why delaying that if we can ship? Massimo, please let the release pass. Apart from that, we have 3 binding votes (Howard, Uli and me). On Sun, Dec 18, 2011 at 12:13 PM, Massimo Lusetti mluse...@gmail.comwrote: On Sat, Dec 17, 2011 at 8:09 PM, Ulrich Stärk u...@spielviel.de wrote: Just to clarify: releases can't be vetoed, not even by binding PMC votes. As long as there are at least 3 binding +1 votes, it's up to the release manager, i.e. Massimo in this case, to decide whether to bury it or proceed. Thanks for clarifying the process. I agree it's unfortunate that a fix for a problem in 5.3 did not make it into the first bugfix release but that's not a reason to hold up the release. I think I will do 5.3.2 soon and will let 5.3.1 fall apart, hoping to have a quicker vote process... Will everyone agree? Cheers -- Massimo http://meridio.blogspot.com - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org -- Best regards, Igor Drobiazko http://tapestry5.de http://twitter.com/drobiazko - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: [VOTE] Tapestry 5.3.1
Angelo Chen: +1(non-binding) -- View this message in context: http://tapestry.1045711.n5.nabble.com/VOTE-Tapestry-5-3-1-tp5072199p5085066.html Sent from the Tapestry - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
